Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

sigma

sigma: An open signature format for describing relevant log events in a straightforward, shareable manner.

What problem it solves

Defensive security practitioners often develop useful searches and correlations without a standardized format for sharing them. Sigma provides a structured, vendor-agnostic format for describing log-event detection methods so they can be shared and converted for different SIEM query languages.

Key features

  • Generic and flexible rule format — Sigma rules describe relevant log events and can be applied to any type of log file. The format is designed to be straightforward to write and suitable for sharing detection methods.

    Source: README

  • Vendor-agnostic detection content — Detection rules avoid tying detection content to a specific vendor, making it easier to share work across communities and tools.

    Source: README

  • Multiple rule categories — The repository separates rules by detection purpose, including generic detections, threat hunting, emerging threats, compliance, and placeholders whose meaning is resolved during conversion or use.

    Source: README

  • Community-reviewed rule collection — The main repository provides detection and hunting rules that are reviewed by a community of professional detection engineers. Rule packages are released regularly for download and use.

    Source: README

  • Conversion and integration paths — Rules can be converted with the Sigma CLI or web-based converters, while pySigma supports integration into custom toolchains and products.

    Source: README

Who it may suit

This repository may suit detection engineers, threat hunters, and other defensive security practitioners who want to write, share, use, or contribute to detection rules.

Topics to discuss

  • How can rule quality be evaluated consistently across the repository’s different rule categories?

  • Which workflows and checks should contributors use when proposing or updating detection rules?

  • How can the community make emerging-threat and placeholder rules easier to discover and use?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/SigmaHQ/sigma#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/SigmaHQ/sigma

Comments

…