CLI Reference
rule
validate

`rsigma rule validate`

Parse all Sigma rules in a directory (recursive) and report results.

Synopsis

rsigma rule validate [OPTIONS] <PATH>

Description

Walks a directory, parses every *.yml/*.yaml Sigma file with rsigma-parser, optionally applies one or more processing pipelines, and compiles each rule with the evaluator’s compiler. Reports the counts on stdout. Exits with code 2 if any rule fails to parse or compile.

This is the cheapest CI gate: no events are evaluated, just rules and pipelines. Wire it as the first step of every detection-as-code pipeline before rule lint and engine eval fixture tests.

For narrative coverage see Linting Rules and CI/CD.

Flags

Flag	Description
`<PATH>`	Path to a directory containing Sigma YAML files (recursive).
`-v, --verbose`	Show details for each file, not just the summary.
`-p, --pipeline <PIPELINES>`	Processing pipeline(s) to apply. Builtin names (`ecs_windows`, `sysmon`) or YAML file paths. Repeatable.
`--resolve-sources`	For dynamic pipelines, also fetch every declared source during validation. Sources must be reachable for validation to pass.

Examples

Plain validation

rsigma rule validate rules/

Output:

Parsed 24 documents from rules/
  Detection rules:   22
  Correlation rules: 2
  Filter rules:      0
  Parse errors:      0
  Pipeline applied:  0 pipeline(s)
  Compiled OK:       24
  Compile errors:    0

Validate with a pipeline applied

rsigma rule validate rules/ -p pipelines/ecs.yml

Catches rules that reference fields the pipeline drops or renames in an incompatible way.

Strict CI: also exercise dynamic sources

rsigma rule validate rules/ -p pipelines/dynamic.yml --resolve-sources

The job fails with exit 3 if any HTTP, file, or command source is unreachable. Use this on PR builds for repos that ship dynamic pipelines.

Verbose per-file output

rsigma rule validate rules/ -v

Shows one line per file with its parse/compile status.

Exit codes

Code	Meaning
`0`	Every rule parsed and compiled cleanly.
`2`	At least one parse or compile error.
`3`	Pipeline file could not be loaded, or `--resolve-sources` failed on a dynamic source.