Schedule icon
Parallel icon
Download icon
WorkingDirectory icon
Clone icon
Script icon
Docker icon
If icon
Fail icon
Log icon

Audit Sigma rules for outdated MITRE ATT&CK mappings

Audit Sigma rule tags against MITRE ATT&CK, report outdated technique mappings and explicit replacements, and optionally block a detection release.

Categories
Infrastructure

ATT&CK changes while detection repositories keep old technique tags. This flow audits a real Sigma checkout against an Enterprise ATT&CK STIX snapshot.

How it works

  1. A manual run or weekly schedule clones the selected rule branch and downloads MITRE's bundle.
  2. Python parses every YAML rule below rules_path, records the Git commit, and extracts technique tags.
  3. The audit distinguishes active, revoked, deprecated, unknown and malformed mappings. Explicit revoked-by relationships provide replacement IDs and their status.
  4. CSV, JSON and Markdown evidence is saved before an optional failing gate.

What you get

  • Per-rule findings, all mappings as CSV, the source commit and a reference SHA-256.
  • Counts of rules with no technique tags; these are not silently counted as covered.
  • A failed run on empty selections, invalid YAML or an unusable reference, rather than false success.
  • Reports remain available when fail_on_findings blocks a release.

Who it's for

Detection engineers and SOC platform teams maintaining Sigma repositories.

Why orchestrate this with Kestra

Scheduled retrieval, download retries, separate parsing and reconciliation tasks, retained artifacts and an explicit gate make taxonomy maintenance repeatable.

Prerequisites

Kestra 2.0 with Git, Python and Docker runner plugins, a Docker-compatible worker, and HTTPS access to GitHub, the MITRE bundle and PyPI. No SIEM is required.

Secrets

None for the public defaults. This blueprint supports public repositories.

Quick start

  1. Import the flow and execute the defaults to audit SigmaHQ/sigma on master, under rules. For a raw repository file, omit the catalog-only extend block before importing.
  2. Download the flow outputs report, mappings and audit. Review unknown tags against the selected Enterprise snapshot; they may belong to another ATT&CK domain.
  3. Set repository, branch and rules_path for your own rules. Use a version-specific attack_url for reproducible comparisons.
  4. Set fail_on_findings to true for a release gate. Enable weekly for recurring maintenance.

How to extend

Route the saved finding report to an existing review process or compare audit artifacts across releases. Never automatically replace a tag: a replacement still needs a detection engineer's semantic review. This is not a coverage test.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.