+1
Daily
11,513
stars
2,949
forks
342
watchers
5,684
prs
680
issues
39
releases
README
Sigma - Generic Signature Format for SIEM Systems Welcome to the Sigma main rule repository. The place where detection engineers, threat hunters and all defensive security practitioners collaborate on detection rules. The repository offers more than 3000 detection rules of different type and aims to make reliable detections accessible to all at no cost. Currently the repository offers three types of rules: Generic Detection Rules - Are threat agnostic, their aim is to detect a behavior or an implementation of a technique or procedure that was, can or will be used by a potential threat actor. Threat Hunting Rules - Are broader in scope and are meant to give the analyst a starting point to hunt for potential suspicious or malicious activity Emerging Threat Rules - Are rules that cover specific threats, that are timely and relevant for certain periods of time. These threats include specific APT campaigns, exploitation of Zero-Day vulnerabilities, specific malware used during an attack,...etc. Compliance Rules - Are rules that help you identify compliance violations based on well known security frameworks such as CIS Controls, NIST, ISO 27001,...etc. Placeholder Rules - Are rules that get their final meaning at conversion or usage time of the rule. Explore Sigma To start exploring the Sigma ecosystem, please visit the official website sigmahq.io What is Sigma Sigma is a generic and open signature format that allows you to describe relevant log events in a straightforward manner. The rule format is very flexible, easy to write and applicable to any type of log file. The main purpose of this project is to provide a structured form in which researchers or analysts can describe their once developed detection methods and make them shareable with others. Sigma is for log files what Snort is for network traffic and YARA is for files. Why Sigma Today, everyone collects log data for analysis. People start working on their own, processing numerous white papers, blog posts and log analysis guidelines, extracting the necessary information and build their own searches and dashboard. Some of their searches and correlations are great and very useful but they lack a standardized format in which they can share their work with others. Others provide excellent analyses, include IOCs and YARA rules to detect the malicious files and network connections, but have no way to describe a specific or generic detection method in log events. Sigma is meant to be an open standard in which such detection mechanisms can be defined, shared and collected in order to improve the detection capabilities for everyone. 🌟 Key Features A continuously growing list of detection and hunting rules, peer reviewed by a community of professional Detection Engineers. Vendor agnostic detection rules. Easily shareable across communities and reports 🏗️ Rule Creation To start writing Sigma rules please check the following getting started g
Top issues
#5590Changelog: add guid's?12 comments · 2025-08-11#6480test_fieldname_case is a no-op for every cloud log source (empty allowlists are falsy)5 comments · 2026-10-18#6132[Rule modification] Testing Usage of Uncommonly Used Port5 comments · 2026-07-13#6520Rule ID reused3 comments · 2026-10-26#4542Based on suspicious regedit changes sigma rules3 comments · 2023-11-04#6594Service Installed By Unusual Client - System2 comments · 2026-11-10#6249Coverage Gap: proc_creation_win_schtasks_creation — Schedule.Service COM Object Bypass2 comments · 2026-08-22#6596Potentially Suspicious PowerShell Child Processes (`e4b6d2a7`): empty `contains` value makes the wmic filter a catch-all1 comments · 2026-11-10
Discussions
#6550A log source for AI coding-agent tool calls?0 comments · 2026-10-31#6159detkit — unit-testing Sigma rules against sample events (would love feedback)0 comments · 2026-07-21#6044Feedback Request: Open-Source Sigma Rule Quality Linter Beyond Schema Validation0 comments · 2026-06-03#5874Create new logsource pipeline for zeek:conn.log in Security Onion1 comments · 2026-02-19#5858How can I explicitly exclude an event from a correlation rule?1 comments · 2026-02-04#5794SigmaQuery — a simple Sigma search tool0 comments · 2025-12-05#5653Proposal to Standardize Azure Rule Log Assumptions5 comments · 2025-09-17#5633How to write Sigma rules for mixed event detection with different log sources?1 comments · 2025-08-28
Latest release
Release r2026-07-01 r2026-07-01 2026-07-09New Rules - new: Antivirus - APT Malware Signature - new: Antivirus - Remote Access Tools Signature - new: AppLocker Application Would Have Been Blocked - new: Authencesn Crypto Module Load via Modprobe - Copy-Fail Indicator - new: Curl File Upload To File Sharing Websites - new: Failed Event Log Clear Via WMI NTEventLogFile ClearEventLog - new: LSASS Crash Via Netlogon Stack Buffer Overflow - CVE-2026-41089 - new: Linux AF_ALG Socket Creation - Kernel Crypto API Exploit Indicator - new: NTLM Hash Leak Via Curl NTLM Authentication - new: New Agent Skills Installation Attemp