CLI Reference
backend
convert

`rsigma backend convert`

Convert Sigma rules into backend-native queries (SQL, SPL, …).

Synopsis

rsigma backend convert [OPTIONS] --target <TARGET> [RULES]...

Description

Reads one or more rule files (or a directory) and emits backend-native query strings, one per rule. Output goes to stdout by default; use -o to write to a file. Use backend targets to list available backends and backend formats to list the output formats supported by a specific backend.

Targets with no native backend are delegated to an external sigma-cli when one is installed, unlocking the full pySigma backend ecosystem (splunk, elasticsearch, kusto, qradar, loki, …). See sigma-cli delegation for discovery, the RSIGMA_SIGMA_CLI override, the flag mapping, and limitations.

For narrative coverage, including the PostgreSQL and LynxDB workflows, see Rule Conversion.

Flags

Required

Flag	Description
`-t, --target <TARGET>`	Backend to convert to. Run `backend targets` for the live list. Native: `postgres` (aliases `postgresql`, `pg`), `lynxdb`, `fibratus`, `test`. Any other target is delegated to sigma-cli when installed.
`[RULES]...`	Path(s) to Sigma rule file(s) or a directory.

Output

Flag	Default	Description
`-f, --format <FORMAT>`	`default`	Backend-specific output format. Run `backend formats <TARGET>` for the list. PostgreSQL examples: `default`, `view`, `timescaledb`, `continuous_aggregate`, `sliding_window`.
`-o, --output <PATH>`	stdout	Write to a file instead of stdout.

Pipeline

Flag	Description
`-p, --pipeline <PIPELINE>`	Processing pipeline(s) (repeatable). Builtin names (`ecs_windows`, `sysmon`) or YAML file paths.
`--without-pipeline`	Skip the pipeline-requirement check that some backends enforce. Use when you know the rules already match your target schema.

Backend options and error handling

Flag	Description
`-O, --option <KEY=VALUE>`	Backend-specific option. Repeatable. PostgreSQL examples: `-O table=okta_events`, `-O json_field=data`, `-O timestamp_field=time`, `-O case_sensitive_re=true`. See PostgreSQL backend reference for the full list.
`-s, --skip-unsupported`	Skip rules that the backend cannot represent instead of failing the run with exit `2`. The skipped rules are reported on stderr.

Examples

PostgreSQL default

rsigma backend convert -t postgres rules/

SELECT * FROM security_events WHERE "CommandLine" ILIKE '%whoami%'

PostgreSQL view per rule

rsigma backend convert -t postgres -f view -p ecs_windows rules/

CREATE OR REPLACE VIEW sigma_8b1d8c97_5b3a_4d77_9b48_7c5f7c8b1a2a AS
    SELECT * FROM security_events WHERE "process.command_line" ILIKE '%whoami%'

JSONB mode against an Okta-style schema

rsigma backend convert -t postgres \
    -O table=okta_events \
    -O json_field=data \
    -O timestamp_field=time \
    rules/

SELECT * FROM okta_events
WHERE data->>'eventType' = 'group.user_membership.add'
  AND data->'actor'->>'alternateId' ILIKE '%@partner.example.com'

LynxDB SPL2

rsigma backend convert -t lynxdb rules/

Sliding-window correlation (skip the base detection rules)

rsigma backend convert -t postgres -f sliding_window --skip-unsupported rules/

Base detection rules return unknown output format: sliding_window and are skipped; only the correlation rule converts.

Convert a whole tree to a file

rsigma backend convert rules/ -t postgres -f view \
    -p pipelines/ocsf_postgres.yml \
    --skip-unsupported \
    -o /var/lib/rsigma/sql/views.sql
psql -f /var/lib/rsigma/sql/views.sql

Exit codes

Code	Meaning
`0`	Conversion succeeded.
`2`	One or more rules failed to convert (unless `--skip-unsupported`), rules path empty, or a delegated sigma-cli run exited non-zero (its stderr is relayed).
`3`	Unknown `--format`, unwritable `--output`, a target with no native backend and no sigma-cli installed, a directory `--output` for a delegated target, or other CLI configuration error.