sigmahq/sigma

Main Sigma Rule Repository

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 5th, 2026
Created on December 24th, 2016
Open Issues & Pull Requests: 195 (+0)
GitHub issues: Enabled
Number of forks: 2,784
Total Stargazers: 10,994 (+0)
Total Subscribers: 347 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.3 hours
Mean response time: 6.4 days
90th percentile: 16.3 days
Tracked items: 78

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 7% of issues opened in the past year have been closed. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 267 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • False-Positive (21)
  • Create Pull-Request (9)
  • Work In Progress (8)
  • Rule Idea (2)
  • Author Input Required (1)
  • Correlation-Rules (1)
  • Correlation-Rules-To-Migrate (1)
  • Emerging-Threats (1)

Detailed Description

Sigma is a generic and open rule format for log detection that enables security teams to write detection rules once and deploy them across multiple security tools and platforms.

The problem Sigma addresses is the fragmentation of detection logic across different security information and event management systems, intrusion detection systems, and log analysis platforms, each with their own proprietary rule syntax. Sigma solves this by providing a standardized, tool-agnostic rule format that describes what to detect in logs. Rules written in Sigma can then be converted to the native formats of various backends including Elasticsearch, Splunk, Sysmon, and other security platforms through automated translation, eliminating the need to rewrite detection logic for each tool.

Organizations should adopt Sigma if they operate multiple security tools and want to maintain a single source of truth for detection rules. The format is particularly suited for teams managing complex security infrastructures where rules need to be deployed across heterogeneous systems. It works well for security researchers and analysts who want to share detections without being locked into a specific vendor's ecosystem. Teams with limited resources benefit from writing rules once rather than maintaining parallel versions for each platform they use.

The project maintains an active repository of community-contributed detection rules covering common attack patterns and security events. Development shows consistent engagement with regular updates to both the rule collection and the underlying framework. The project accepts contributions from the security community, indicating ongoing collaboration to expand detection coverage. The codebase demonstrates active maintenance with attention to supporting new backends and improving the translation layer between the generic Sigma format and platform-specific rule languages. The project's documentation and tooling are regularly refined to lower the barrier for new contributors and users adopting the format.