Skip to content
Commitpedia
Log in Join & edit

Sigma: the open detection-rule format for log data

The SigmaHQ repository holds the vendor-neutral Sigma rule specification and a community library of thousands of detection rules that converters translate into queries for Splunk, Elastic, Loki and other log tools.

Drafted with AI from official documentation. Scripts were run in a test environment and repository links verified. Awaiting a human check. Did it work for you? Last edited Outdated?

Edit history of Sigma: the open detection-rule format for log data: 1 recorded edit
Edit history · 1 edit
Type
Repo
Edits
1
Editors
1
First issued
15 Oct 2026
Last edit
15 Oct 2026
Source
SigmaHQ/sigma

SigmaHQ/sigma

Stars
11.2k
Forks
2.9k
Language
Python
Licence
NOASSERTION
Last push
15 Oct 2026

On GitHub: Main Sigma Rule Repository

Open on GitHub

Sigma (about 11,000 stars on GitHub) is often described as “the YARA of log files” or “Snort for logs”: a generic, open signature format for describing suspicious activity in log data. The project was started in 2017 by Florian Roth and Thomas Patzke and is now run by the SigmaHQ organisation with a core maintainer team and several hundred contributors. The repository contains the rule specification, a library of more than three thousand community rules organised by log source (Windows, Linux, macOS, cloud providers, network devices, web servers and applications), and documentation on how rules are written and reviewed.

What a Sigma rule is

A Sigma rule is a short YAML file that describes one pattern of interest in a vendor-neutral way: which kind of log it applies to, what values or combinations of values make an event suspicious, and how severe a hit is. The rule itself is never run directly. A separate converter reads it and produces an equivalent query in the language of the tool you actually use, so one rule written once can become a Splunk search, an Elasticsearch or Kibana query, a Microsoft Sentinel KQL statement, a Grafana Loki LogQL query or an entry for many other backends. That separation is the whole point: detections become shareable text that any team can read, review in version control and adopt without being tied to a product.

Who it is for

  • Security operations centre (SOC) teams and detection engineers who want a common format for their own rules and a large starting library.
  • Administrators who run a log platform such as Loki or Elastic and want to add detection on top of existing monitoring.
  • Vendors and open source projects that implement Sigma support in their products; dozens already do.
  • Students and researchers studying how attacks appear in logs, since each rule links to references and MITRE ATT&CK tags.

How to browse and install it

Rules can be read directly on GitHub under the rules/ tree and its siblings for emerging threats and threat hunting, or searched on the companion site sigmasearchengine.com. The converter lives in a separate repository, SigmaHQ/sigma-cli, built on the pySigma library, and installs from PyPI; backends for individual tools are installed as plugins:

pipx install sigma-cli
sigma plugin list
sigma plugin install loki
git clone --depth 1 https://github.com/SigmaHQ/sigma.git

The how-to Try Sigma rules against your own logs walks through a first conversion. The older sigmac tool and the original sigmatools package are deprecated; new work should use sigma-cli and pySigma.

Credit

Sigma was created by Florian Roth and Thomas Patzke and is maintained by the SigmaHQ team and community. The rules in the repository are published under the Detection Rule License (DRL) 1.1, a permissive licence written for detection content; the tooling in the related repositories is under the LGPL. See the LICENSE files in each repository for the exact terms.

Did this work for you?

No votes yet. Be the first.

If it did not work, the report form below tells the editors what went wrong.

See also

  • 0431 What is a detection rule? Sigma explained for beginners A detection rule describes one kind of suspicious activity in logs. Sigma is the shared, tool-independent way to write such rules, so… Beginner · Explains an idea · Any system Article Alerting & dashboards · Security resources & detection 15 Oct 2026
  • 0432 Try Sigma rules against your own logs Install the sigma-cli converter, take a rule from the public SigmaHQ library, convert it into a query for a log tool you… Intermediate · Step by step · Linux, macOS Article Logs · Security resources & detection 15 Oct 2026
  • 0433 What is an awesome list? Awesome lists are hand-curated link collections on GitHub, one per subject, that follow a shared convention. How they work, how to tell… Beginner · Explains an idea · Any system Article Security resources & detection 15 Oct 2026
  • 0443 Security monitoring explained: IDS, SIEM, EDR and where the logs go A plain language map of the security monitoring tool families, what each one watches, how they feed one another, and where the… Beginner · Explains an idea · Any system Article Detection & threat hunting · Logs 15 Oct 2026
  • 0455 Which security tool does what? A map for beginners A beginner's map of open source security tool families: vulnerability scanners, secret detection, static analysis, host audits, web application testing, network inventory… Beginner · Explains an idea · Any system Article Security resources & detection · Server hardening 15 Oct 2026

History

Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.

  1. Dominik +2,969 chars

Report a problem

Something wrong, unsafe or copied? Tell the editors.
What is wrong?