PAGES
← all tools
◆ Detection Engineering

sigma-cli

v4.0.0 open-source

CLI for managing, listing, and converting Sigma rules into SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. query languages using the pySigma library.

Summary

sigma-cli is an open-source command-line tool that converts Sigma detection rules into queries for specific SIEM and log-analysis backends, built on the pySigma library. You install it with pipx, pip, or Homebrew, or run it from source via Poetry, and use it as the sigma command to convert, list, and analyze rules against backend plugins like Splunk. It's aimed at detection engineers and SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. teams who maintain Sigma rule sets and need to deploy them across different query languages rather than write backend-specific queries by hand; commands for analyzing field coverage and mapping rules to MITRE ATT&CKMITRE ATT&CKA publicly maintained knowledge base of adversary tactics and techniques observed in real attacks, maintained by MITRE. Cyber tools use it as a common taxonomy to classify, map, and communicate threat behavior. support auditing rule sets before deployment. The README frames it as the official CLI companion to the Sigma rule format itself, rather than a competing product. First committed in 2022 and still under active, frequent development, with 23 contributors and a release only 45 days old, though its own status badge still marks it pre-release.

CLI for managing, listing, and converting Sigma rules into SIEM query languages using the pySigma library.

How sigma-cli helps

How do I turn a directory of Sigma rules into queries my SIEM actually understands?

it walks the rule files through a chosen backend and pipeline and prints or writes the equivalent queries, ready to load into that system

Which Sigma rules will fail or behave unexpectedly against a given backend before I deploy them?

conversion runs with verbose output shows how each rule is processed through the pipeline, surfacing the step where a rule breaks or resolves unexpectedly

How much of MITRE ATT&CK does my current rule set actually cover?

it analyzes the rules and produces an ATT&CK Navigator layer, filterable by rule severity or status, showing which techniques have detections and which don't

Which log sources are my Sigma rules written against, and are any environments left uncovered?

it scans the rule set and lists the log sources referenced, letting you check that against what your environment actually generates before rollout

How do I keep converted queries organized in a rule repository instead of one big output blob?

it can write each converted rule to its own file, mirroring the source directory layout or using a filename template, including an index suffix when one rule yields multiple queries

all 20 features, with the evidence for each →

Languages

Not documented

Features

20 capabilities · 4 backed by code, an API document or a real run

Built from sigma-cli'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 →

What sigma-cli offers you

  • Command-line interface13
  • CI/CD pipeline integration1
All capabilities 20 capabilities
Rule conversion to individual output files verified Converts Sigma rules to separate per-rule files, with control over output directory, filename templating, and optional preservation of the source directory hierarchy. 9 releases · 10 other sources · first seen Feb 2023

release 9 total

  • Adds --output-dir and --output-filename-template flags to write each converted rule to a separate file, with optional preservation of the source directory hierarchy. v3.1.0 · Jul 2026 · source · release history
  • New separate-file output mode writes each converted rule to its own file while preserving the original directory structure. v3.1.0 · Jul 2026 · source · release history
  • Adds --verbose option to sigma convert for detailed conversion output. v1.0.5 · Jan 2025 · source · release history
  • Adds pySigma 0.11 backend integration enabling correlation rules processing within the CLI workflow. v1.0.0 · Jan 2024 · source · release history
  • Adds query post-processing and output finalization stages and transformations in processing pipelines v0.7.7 · Aug 2023 · source · release history
  • Removes support for --min-time and --max-time flags v0.7.0 · Feb 2023 · source · release history

command line

  • --output-dir — Write individual converted rules to separate files in this directory. Mutually exclusive with --output. v3.1.0 · Jul 2026 · command-line history
  • --output-filename-template — Template for output filenames when using --output-dir. Available variables: {path} (relative source path), {stem} (filename without extension), {index} (query index for rules that generate multiple queries). Example: '{path}/{stem}-{index}.txt' or 'converted/{stem}.esql' v3.1.0 · Jul 2026 · command-line history

example 8 total

  • Flatten all converted rules into a single directory with per-rule files, handling rules that emit multiple queries by appending an index suffix. sigma convert -t esql -p ecs_windows --output-dir translated/ --output-filename-template "{stem}-{index}.esql" rules/ v3.1.0 · Jul 2026 · source
  • Output each converted rule as its own file mirroring the source directory layout — useful for version-controlled rule repos or selective SIEM deployment. sigma convert -t esql -p ecs_windows --output-dir translated/ --output-filename-template "{path}/{stem}.esql" rules/ v3.1.0 · Jul 2026 · source
  • Identify all field names referenced across your Sigma rules to audit coverage or plan backend mappings. sigma analyze <path> v2.0.0 · Nov 2025 · source
  • Troubleshoot conversion issues by seeing exactly how each rule is processed through a pipeline. sigma convert --verbose -t splunk -p my_pipeline.yml rules/ v1.0.5 · Jan 2025 · source
  • Audit which log sources are covered across your Sigma rule set before deploying to a new environment. sigma analyze logsources rules/ v1.0.5 · Jan 2025 · source
  • List available plugins in the new system sigma plugin list v0.6.0 · Feb 2023 · source
Template variable path control and security shipped Controls which paths are allowed for template variable expansion during rule conversion, enabling custom allowlists and requiring explicit opt-in to mitigate security risks. 6 releases · 3 other sources · first seen Apr 2026

Also counts toward: Command-line interface

release

  • Enable template variable expansion when needed with --enable-template-vars (emits a security warning) on convert and check. v4.0.0 · Oct 2026 · source · release history
  • Adds --url parameter to the pysigma update-cache subcommand, enabling specification of a custom URL for cache updates. v3.0.1 · Apr 2026 · source · release history
  • Without --template-vars-path, template vars Python files must now reside in the same directory or a sub-directory of the pipeline YAML configuration; files in other locations will no longer load. v3.0.0 · Apr 2026 · source · release history
  • New --template-vars-path flag defines a custom allowlist of paths from which template vars Python files may be loaded. v3.0.0 · Apr 2026 · source · release history
  • Custom template vars are now disabled by default; existing pipelines using template vars will break unless --enable-template-vars is passed. v3.0.0 · Apr 2026 · source · release history
  • New --enable-template-vars flag explicitly opts in to custom template variable Python files (previously on by default). v3.0.0 · Apr 2026 · source · release history

example

  • Convert rules from a trusted internal library that use template variables and Python-native regex patterns — upgrade from v3 behaviour by passing --policy trusted --enable-template-vars. sigma convert -t splunk -p sysmon --policy trusted --enable-template-vars sigma/rules/windows/ v4.0.0 · Oct 2026 · source
  • Pull the pySigma plugin cache from a self-hosted or alternative URL instead of the default upstream source. sigma pysigma update-cache --url https://your-internal-mirror.example.com/sigma-cache.json v3.0.1 · Apr 2026 · source
  • Re-enable template vars for an existing pipeline that relies on them, pointing to a trusted vars file outside the default allowed path. sigma convert -t splunk -p my_pipeline.yml --enable-template-vars --template-vars-path /opt/sigma/vars my_rules/ v3.0.0 · Apr 2026 · source
Backend and pipeline capabilities listing shipped Enumerates supported processing transformations, condition types, and modifiers available in the current installation. 3 releases · 3 other sources · first seen Apr 2023

Also counts toward: Command-line interface

release

  • Adds a Plugin column to sigma list targets and sigma list pipelines output, showing which plugin provides each target or pipeline. v2.0.2 · Apr 2026 · source · release history
  • Enhances sigma-plugin list and sigma-plugin details commands to expose the full set of plugin capabilities. v1.0.0 · Jan 2024 · source · release history
  • Adds sigma list subcommand (with modifiers, processing_transformations, and conditions variants) to list supported capabilities. v0.7.3 · Apr 2023 · source · release history

docs

  • CLI for managing, listing, and converting Sigma rules into SIEM query languages using the pySigma library.

example

  • View which capabilities a specific plugin exposes after installation. sigma-plugin details some-plugin-name v1.0.0 · Jan 2024 · source
  • List all available plugins sigma plugin list
Rule validation and syntax checking shipped Validates Sigma rules against the specification and detects syntax errors, with support for stdin input, explicit file requirements, and rule exclusion during checks. 4 releases · 1 other source · first seen Oct 2022

Also counts toward: Command-line interface

release

  • Adds the --exclude argument to sigma check to allow disabling some rules during validation. v0.7.10 · Nov 2023 · source · release history
  • Changes sigma check to require explicit input files; passing nothing no longer silently succeeds. v0.7.3 · Apr 2023 · source · release history
  • sigma check now fails if no input file arguments are provided (previously it exited silently). v0.7.3 · Apr 2023 · source · release history
  • Adds rule validation to the CLI v0.5.1 · Oct 2022 · source · release history

example

  • Validate a rule set with check while keeping the safe policy but explicitly allowing external sources for a controlled pipeline environment. sigma check --policy safe --allow-external-sources sigma/rules/windows/process_creation/ v4.0.0 · Oct 2026 · source
Rule-processing security policy shipped Controls the security posture of rule conversion and checking via a --policy flag, where the default safe mode switches the regex engine to RE2, disables template variable expansion, and blocks external rule sources, while trusted mode restores prior permissive behaviour. 4 releases · 1 other source · first seen Oct 2026

Also counts toward: Command-line interface

release

  • Allow external rule sources explicitly with --allow-external-sources on convert and check. v4.0.0 · Oct 2026 · source · release history
  • The default policy is now safe, which switches the regex engine to RE2, disables template variable expansion, and blocks external rule sources — existing scripts that rely on Python-native regex, template variables, or external sources will break unless --policy trusted (or the relevant individual flags) is added. v4.0.0 · Oct 2026 · source · release history
  • Override the regex engine independently with --regex-engine re2 or --regex-engine python regardless of the active policy. v4.0.0 · Oct 2026 · source · release history
  • Control rule-processing security with --policy safe (default) or --policy trusted on both the convert and check commands — safe mode uses the RE2 regex engine, disables template variable expansion, and blocks external rule sources.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v4.0.0 · Oct 2026 · source · release history

example

  • Convert untrusted community rules with the safe default policy to guard against regex DoS — no extra flags needed; RE2 and blocked external sources are on by default. sigma convert -t splunk -p sysmon --policy safe sigma/rules/windows/process_creation v4.0.0 · Oct 2026 · source
CLI help and dependency updates shipped Adds the -h short option for viewing command help and updates the pySigma dependency to the current version. 3 releases · 2 other sources · first seen Jun 2024

Also counts toward: Command-line interface

release

  • ATT&CK Navigator layers exported via mitre analyze now include a title field for easier identification. v1.0.6 · Apr 2025 · source · release history
  • Adds -h short option for the help command in sigma-cli v1.0.4 · Jun 2024 · source · release history
  • Updates pySigma dependency to current version v1.0.4 · Jun 2024 · source · release history

example

  • Scope a MITRE ATT&CK coverage analysis to only high-severity, stable rules to reduce noise in the Navigator layer. sigma mitre analyze --level high --status stable rules/ v1.0.6 · Apr 2025 · source
  • Quickly view command help without typing --help sigma-cli -h v1.0.4 · Jun 2024 · source
JUnit XML output for converted rules verified Exports sigma convert results in JUnit XML format, enabling integration with CI pipelines that consume standard test reporting. 2 releases · 2 other sources · first seen Jul 2026

Also counts toward: CI/CD pipeline integration, Command-line interface

release

  • Adds JUnit XML export for sigma convert results, enabling CI pipeline integration with standard test reporting tools. v3.1.0 · Jul 2026 · source · release history
  • New --junit-xml export parameter outputs rule conversion results in JUnit XML format for CI pipeline integration. v3.1.0 · Jul 2026 · source · release history

command line

  • --junitxml — Output results in JUnit XML format to the specified file. v3.1.0 · Jul 2026 · command-line history

example

  • Export conversion results as JUnit XML to fail CI pipelines on rule errors and surface per-rule pass/fail in test reporters. sigma convert -t splunk rules/ --junit-xml results.xml v3.1.0 · Jul 2026 · source
Plugin compatibility enforcement shipped Detects incompatible pySigma versions after plugin installation and provides flags to override these checks. 2 releases · 1 other source · first seen Jan 2024

Also counts toward: Command-line interface

release

  • Adds a post-installation check that detects incompatible pySigma versions after plugin installation and prompts for reinstallation. v1.0.0 · Jan 2024 · source · release history
  • Adds the --force-install (shortcut -f) CLI flag to bypass compatibility checks when installing plugins. v1.0.0 · Jan 2024 · source · release history

example

  • Force install a plugin that the CLI considers incompatible with the current version. sigma-plugin install --force-install some-incompatible-plugin v1.0.0 · Jan 2024 · source
Pipeline configuration and validation shipped Manages pipeline configuration formats and validates that processing pipelines are correctly intended for or required by the target. 3 releases · first seen Aug 2022

release

  • The sigma.cli.pipelines config key now expects a dict of pipeline definitions instead of its previous format. v0.5.0 · Aug 2022 · source · release history
  • Adds validation step in pipeline usage check that confirms whether used pipelines are intended for use with the target. v0.5.0 · Aug 2022 · source · release history
  • Adds validation step in processing pipeline check that verifies if the target requires a specific pipeline. v0.5.0 · Aug 2022 · source · release history
Homebrew installation on macOS shipped Supports installing sigma-cli on macOS via Homebrew, providing a quick setup path without requiring Python tooling. 1 release · 1 other source · first seen Jul 2026

release

  • Supports Homebrew installation on macOS, enabling brew install sigma-cli as a new install path. v3.0.3 · Jul 2026 · source · release history

example

  • Install sigma-cli on macOS without Python tooling — useful for quick setup on analyst workstations. brew install sigma-cli v3.0.3 · Jul 2026 · source
Grouped field analysis shipped Groups the results of field frequency analysis by a specified dimension, such as log source or category, to contextualize which fields are most common. 1 release · 1 other source · first seen Apr 2026

Also counts toward: Command-line interface

release

  • Adds --group argument to sigma analyze fields to group field frequency results by a specified dimension. v2.0.2 · Apr 2026 · source · release history

example

  • Group field analysis results by log source or category to quickly spot which fields are most common in a given context. sigma analyze fields --group <field> <path> v2.0.2 · Apr 2026 · source
Pipeline directory support shipped Allows applying an entire directory of pipeline YAML files at once instead of requiring multiple individual flags. 1 release · 1 other source · first seen Jan 2025

Also counts toward: Command-line interface

release

  • Allows --pipeline in sigma convert to accept a directory of pipeline files, applying all pipelines within it. v1.0.5 · Jan 2025 · source · release history

example

  • Apply an entire folder of ordered pipeline YAMLs at once instead of chaining multiple --pipeline flags. sigma convert -t elastic-lucene --pipeline ./pipelines/ rules/windows/ v1.0.5 · Jan 2025 · source
Splunk query and configuration generation shipped suggested Converts Sigma rules into Splunk-specific formats, including queries for Sysmon data and savedsearches.conf configuration files. 2 other sources

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

example

  • Convert rules to Splunk queries for Sysmon sigma convert -t splunk -p sysmon sigma/rules/windows/process_creation
  • Convert rules to Splunk savedsearches.conf sigma convert -t splunk -f savedsearches -p sysmon -o savedsearches.conf sigma/rules/windows/process_creation
Dataset source override verified Allows overriding a dataset's source URL at conversion time using a dataset:url mapping. 1 other source · first seen Apr 2026

command line

  • --url — Override a dataset source in the format dataset:url. v3.0.1 · Apr 2026 · command-line history
Template variable path control verified Restricts which paths are allowed for template variable expansion during rule conversion. 1 other source · first seen Apr 2026

Also counts toward: Command-line interface

command line

  • --template-vars-path — Allowed paths for template variable expansion. Can be specified multiple times. v3.0.0 · Apr 2026 · command-line history
Field name extraction shipped Identifies all field names referenced across Sigma rules to help audit coverage or plan backend mappings. 1 release · first seen Nov 2025

Also counts toward: Command-line interface

release

  • New analyze command extracts field names from Sigma rules. v2.0.0 · Nov 2025 · source · release history
MITRE content cache management shipped Provides commands to manage the local cache for MITRE ATT&CK content. 1 release · first seen Nov 2025

Also counts toward: Command-line interface

release

Log source coverage analysis shipped Analyzes which log sources are covered by the current set of Sigma rules to assist in deployment planning. 1 other source · first seen Jan 2025

example

  • Audit which log sources are covered across your Sigma rule set before deploying to a new environment. sigma analyze logsources rules/ v1.0.5 · Jan 2025 · source
Version management shipped Displays the currently installed sigma-cli version for use in CI/CD pipelines or troubleshooting. 1 release · first seen May 2023

Also counts toward: Command-line interface

release

  • Adds version subcommand to display the installed sigma-cli version. v0.7.6 · May 2023 · source · release history
Splunk backend plugin installation shipped Provides a direct command to install the specific backend plugin required for Splunk compatibility. 1 other source

example

  • Install the Splunk backend plugin sigma plugin install splunk

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 sigma-cli, 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 sigma-cli 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 →

Website history

sigmahq.io, every change

SigmaHQ's home page and 7 more pages as they looked each month from October 2023 to October 2026: 27 renders, 9 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

19 entries

  1. October 20261
  2. July 20262
  3. April 20263
  4. November 20251
  5. April 20251
  6. January 20251
  7. June 20241
  8. January 20241
  9. November 20231
  10. August 20231
  11. May 20231
  12. April 20231
  13. February 20232
  14. October 20221
  15. August 20221
    Show

    19 entries

    Project health

    Issue, contributor and maintainer activity in SigmaHQ/sigma-cli, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 9 +3 vs prior 12 months
    2. Maintainers 2 +1 joined · −1 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 75% of issues opened, last 12 months
    5. Median time to close 224 days first maintainer reply 21 hours
    6. Open backlog 0 of 35 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 1
    4. Commits / month 1
    5. Stars 211
    Issue themes, last 12 months
    • other 100%

    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 →
    browse all tools → score card for your toolchain →