PAGES
← all tools
◆ Detection Engineering

pysigma

v2.1.0 open-source

Free plan: not checked yet · Open source: yes

Pysigma is a python library to parse and convert Sigma rules into queries (and whatever else you could imagine)

What you can do now

Checking Plays…

Summary

pysigma is an open-source Python library that parses, processes, and converts Sigma detection rules into queries for security monitoring systems, aimed at detection engineers and developers building rule-conversion workflows. It is installed with a Python package manager and imported into other code, requiring Python 3.11 or later; its documentation describes it as the successor to sigmac, while the README identifies sigma-cli as the command-line equivalent. Backends and processing pipelines are separate projects, keeping the library vendor-agnostic. The project is marked pre-release, with six tracked releases and a release 10 days ago.

Pysigma is a python library to parse and convert Sigma rules into queries (and whatever else you could imagine)

How pysigma helps

Which Sigma rules can be converted into queries for my monitoring backend?

parses the rules, applies the selected backend’s conversion logic, and produces queries in that backend’s language; the backend implementation determines which rule features it can represent

How do my Sigma rules need to change for the log data model used by my monitoring system?

runs processing pipelines that transform fields, values, placeholders, and other rule content before conversion; the result depends on the mappings and transformations defined by the selected pipeline

Can I express exclusions and negative matches directly in my detections?

parses not-equal conditions and Sigma filters, including filters applied broadly across rules, then passes that logic to the backend for query generation; the final query still depends on backend support for the condition

How can I convert correlation rules into queries while preserving their aggregations?

parses correlation conditions and supported aggregation types, including sums, averages, percentiles, and medians, and lets the backend finalize the resulting query; unsupported correlation semantics remain dependent on the backend

Which rule metadata and framework references are available during processing?

exposes rule attributes, scope, and on-demand MITRE ATT&CK data from configured remote or local sources to processing and conversion; references unavailable from those sources cannot be resolved

all 47 features, with the evidence for each →

Languages

Not documented

Features

47 capabilities across 3 capability groups

Built from pysigma's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • pysigma covers 3 of the 11 logs and telemetry capabilities we track.

What pysigma offers you

  • Plugin API support1
  • Plugin system1
  • Python scripting support1
  • Command-line interface

Security event correlation 6 features Logs and telemetry since 2023
Correlation Query Advanced Features Adds typing, arbitrary parameter passing, multi-rule search, and query expression support to correlation query generation. 7 releases · first seen Mar 2024

Shared capability: Security event correlation

Sigma Correlation Rule Support Parses and converts Sigma correlation rules in addition to detection rules. 4 releases · 1 other source · first seen Dec 2023

Shared capability: Security event correlation

Correlation Rule Processing Support Extends pipeline application, log source filtering, and aggregation template variables to correlation rules. 4 releases · first seen May 2024

Shared capability: Security event correlation

Fractional thresholds in correlation conditions Supports fractional (non-integer) threshold values in correlation condition definitions. 2 releases · first seen Oct 2026

Shared capability: Security event correlation

Correlation Logic and Type Extensions Extends correlation conditions with additional rule logic and adds support for new aggregation types such as value_sum, value_avg, value_percentile, and value_median. 1 release · first seen Feb 2026

Shared capability: Security event correlation

Sigma Spec 2.1.0 Correlation Type Support Supports new correlation aggregation types including value_sum, value_avg, value_percentile, and value_median. 1 release · first seen Nov 2025

Shared capability: Security event correlation

Log parsing and normalization 2 features Logs and telemetry since 2025
Advanced Rule Validators Adds validators for WinDash formatting and strict field mapping enforcement to improve rule quality. 3 releases · first seen Nov 2025

Shared capability: Log parsing and normalization

Regex-Based Field Extraction Provides a GenericTypeValueTransformation class to extract structured field values from raw strings using regex capture groups. 1 release · 1 other source · first seen Jul 2026

Shared capability: Log parsing and normalization

Log search 1 feature Logs and telemetry since 2024
Special Character and Modifier Support Adds support for em/en dashes in Windows dash variants and allows special characters in string expressions. 2 releases · first seen Jul 2024

Shared capability: Log search

Other / not yet classified 38 features Features we have not matched to a capability yet. A suggested match is marked.
SigmaPolicy trust-model configuration Provides a `SigmaPolicy` dataclass that centralises trust-model settings (regex engine, template variables, external sources, allowed paths) and propagates them automatically through every pipeline call, replacing ad-hoc per-parameter flags. 12 releases · 1 other source · first seen Jan 2025
Pipeline Transformation Library suggested Adds various processing transformations including string mapping, value setting, field manipulation, type conversion, and regex application. 13 releases · first seen Jan 2024

Suggested capability: Log parsing and normalization. This is our guess, not confirmed.

Sigma String and Regex Processing Improvements Expands string pattern to regex conversion, supports special characters in expressions, and adds controls for wildcard handling during replacement. 8 releases · 2 other sources · first seen Aug 2024
Pipeline YAML security hardening Rejects security-related keys in pipeline YAML and strips them before instantiation, preventing untrusted pipeline definitions from enabling privileged features at runtime. 6 releases · first seen Nov 2025
Predefined SafePolicy and TrustedPolicy profiles Ships two ready-made `SigmaPolicy` profiles — `SafePolicy` (RE2 engine, all risky features disabled) and `TrustedPolicy` (Python engine, all features enabled) — for common deployment patterns. 3 releases · 3 other sources · first seen Feb 2023
Advanced Pipeline Conditions and Routing suggested Adds conditions based on processing state, rule attributes, tags, log source, and field presence to gate or route pipeline transformations. 6 releases · first seen Apr 2024

Suggested capability: Log routing. This is our guess, not confirmed.

Backend compatibility validation for YAML pipelines Validates that a pipeline loaded from YAML is compatible with the target backend before use. 5 releases · first seen Feb 2023

Also counts toward: Plugin API support, Plugin system

Extended Sigma Condition Logic Adds support for negative operators, list-based rule attributes, and exact value matching within detection conditions. 4 releases · 1 other source · first seen Nov 2025
Processing Condition Enhancements Expands processing conditions to include negation, field name scoping via dedicated lists, and state tracking for visibility into which items were applied. 5 releases · first seen Apr 2022
RE2 regex engine with ReDoS protection Switches the default regex engine to Google RE2, eliminating ReDoS risk from untrusted Sigma rules, while keeping the Python `re` engine available as an explicit opt-in via `SigmaPolicy`. 4 releases · first seen Oct 2026
Template Variable Security Hardening Disables template variables by default and introduces explicit opt-in controls (`allow_template_vars`, `vars_allowed_paths`) plus an environment variable fallback to prevent accidental code execution from untrusted pipelines. 4 releases · first seen Apr 2026
Enhanced Backend Configuration and Integration Extends backend configuration via pipeline options and template helper functions, while enabling field references and query finalization control. 4 releases · first seen Jan 2025
Sigma Rule Filtering and Severity Bucketing Enables filtering rules by severity/status using comparison operators and bucketing rules by severity for reporting. 2 releases · 2 other sources · first seen Mar 2024
Pipeline Composition and Directory Resolution Enables loading pipelines from directories and composing complex pipelines by nesting other pipelines. 3 releases · first seen Jul 2024
Nested post-processing pipeline items from YAML Allows nested query post-processing items to be loaded directly from YAML pipeline definitions. 3 releases · first seen Oct 2026
Sigma Filters Introduces capability to suppress or exclude matching Sigma rule results. 2 releases · 1 other source · first seen Jun 2024
Metadata Validator Validates Sigma rule metadata fields. 3 releases · first seen Nov 2023
Sigma Rule Validation Enhancements Adds validators for dangling conditions, wildcard usage in detection items, and logsource naming conventions. 3 releases · first seen Jun 2024
Environment variable fallback for security settings Supports `PYSIGMA_ALLOW_VARS_EXECUTION` and `PYSIGMA_ALLOW_EXTERNAL_SOURCES` environment variables as a legacy fallback for configuring security-related settings when a `SigmaPolicy` instance is not provided. 2 releases · first seen Jul 2026
Template processing sandboxing Restricts template processing so that only safe built-in types can have methods called, blocking arbitrary object method invocation from untrusted rule content. 2 releases · first seen Oct 2026
External Data Source Integration suggested Supports loading dynamic lookup data from File, HTTP, or Command sources into Sigma rules at transformation time. 2 releases · first seen Jun 2026

Suggested capability: Log enrichment. This is our guess, not confirmed.

Sigma Specification Compliance Updates Adds missing UTF-16 modifiers, extends CommandPlaceholderTransformation placeholders, and adds temporal_extended correlation types to align with the Sigma specification. 2 releases · first seen Jul 2026
Sigma Taxonomy and Data Updates Adds MITRE D3FEND namespace support and updates bundled MITRE ATT&CK data. 2 releases · first seen Aug 2024
Custom Backend and Expression Support suggested Adds equality expression support for text backends and allows custom fields in logsource definitions. 2 releases · first seen Apr 2024

Suggested capability: Log search. This is our guess, not confirmed.

Pipeline State Management suggested Enables passing format-specific context and state across pipeline steps using SetState transformations. 2 other sources · first seen May 2022

Suggested capability: Log parsing and normalization. This is our guess, not confirmed.

Sigma Collection Inspection Provides methods to inspect Sigma collections for unreferenced rules and rule outputs. 1 release · 1 other source · first seen Jan 2024
In-Process Rule Matching Provides a `sigma.matching` module that matches live or logged events directly against Sigma rules in Python without converting rules to a query language first. 1 release · first seen Nov 2026

Also counts toward: Python scripting support

Hyphenated Detection Identifier Support Allows dashes in `1/all of` selector patterns so rule conditions that reference hyphenated detection identifiers parse correctly. 1 release · first seen Nov 2026
Windows Logsource Taxonomy Extensions Adds named Windows logsource definitions (such as `adfs` for Active Directory Federation Services) to the bundled taxonomy for use in Sigma rules. 1 release · first seen Nov 2026
Rule Tag Comparison Enables comparing Sigma rule tags directly with their string representations. 1 release · first seen Aug 2024
Plugin Upgrade Support Enables upgrading plugins via dedicated upgrade plugin support. 1 release · first seen Dec 2023
SigmaRelated Class Provides a dataclass for expressing relationships between Sigma rules. 1 release · first seen Dec 2023
SigmaRule Quality Validators Validates author and title fields within the SigmaRule class for quality assurance. 1 release · first seen Dec 2023
Summiting the Pyramid Tag Support Supports Summiting the Pyramid v1.0.0 tags in Sigma rules. 1 release · first seen Dec 2023
Duplicate References Validator Detects Sigma rules that reference the same source more than once. 1 release · first seen Nov 2023
Filename Validator Enforces naming conventions on Sigma rule files. 1 release · first seen Nov 2023
Tags Validator Enforces valid tag usage in Sigma rules. 1 release · first seen Nov 2023
Wildcard Validator Validates Sigma rules to catch invalid wildcard usage in string fields. 1 release · first seen Oct 2023

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for pysigma, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail pysigma puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Coverage

Missing something? Tell us

What pysigma connects to, runs on and detects, read from its release notes and docs. So far: 1 new supported platform.

Show

1 change, tracked since Nov 8, 2026.

  • Nov 82026

    new ADFS Windows logsource

    Add adfs Windows logsource for Active Directory Federation Services by @4ndr3w6 in https://github.com/SigmaHQ/pySigma/pull/604

    v2.0.3 Source ↗

How we count

Read from 4 of 40 release notes and docs updates we hold for pysigma. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through pysigma's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

40 entries

  1. November 20262
  2. October 20262
  3. July 20261
  4. June 20261
  5. April 20261
  6. February 20261
  7. January 20261
  8. November 20251
  9. May 20251
  10. January 20251
  11. October 20242
  12. September 20243
  13. August 20242
  14. July 20241
  15. June 20242
  16. May 20241
  17. April 20241
  18. March 20241
  19. January 20241
  20. December 20231
  21. November 20232
  22. October 20231
  23. July 20231
  24. May 20231
  25. April 20231
  26. February 20231
  27. December 20221
  28. September 20221
  29. August 20221
  30. July 20221
  31. May 20221
  32. April 20221
    Show
    Coverage in all entries

    40 entries

    Project health

    Issue, contributor and maintainer activity in sigmahq/pysigma, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 64% of issues opened, last 12 months
    5. Median time to close 6.2 days first maintainer reply 5.7 days
    6. Open backlog 3 of 140 issues ever filed
    1. Issues opened / month 3 · 0 communitymaintainers
    2. Open backlog 3
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • features 5%
    • other 95%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.