pySigma Splunk Backend
This is the Splunk backend for pySigma. It provides the package sigma.backends.splunk with the SplunkBackend class.
Further, it contains the following processing pipelines in sigma.pipelines.splunk:
- splunk_windows_pipeline: Splunk Windows log support
- splunk_windows_sysmon_acceleration_keywords: Adds fiels name keyword search terms to generated query to accelerate search.
It supports the following output formats:
- default: plain Splunk queries
- savedsearches: Splunk savedsearches.conf format.
Data model (tstats) query settings
The data_model output format generates accelerated tstats queries against a Splunk data
model. The following settings let you tune the generated query without changing the Sigma
rules themselves. They are read from the pipeline processing state (set with a
SetStateTransformation / the set_state pipeline item), so detection logic stays separate
from environment-specific query configuration. Defaults keep the generated query unchanged.
summariesonly(also available as thesummariesonlybackend option, e.g.-O summariesonly=truewith sigma-cli): controls thetstats summariesonly=...flag. Accepts a boolean or a string (true/false). When both are set, the pipeline processing state takes precedence over the backend option. Default:false.
The following are Splunk-specific extensions of the data model output and have no direct representation in the Sigma standard:
tstats_span: adds_timeto thebyclause and aspan=<value>bucket, e.g.tstats_span: 1h. The value is a number followed by an optional Splunk time unit (s,sec,secs,second,seconds,m,min,mins,minute,minutes,h,hr,hrs,hour,hours,d,day,days,mon,mont,months); a bare number (e.g.30) is treated as seconds.tstats_aggregations: a list of additional aggregation functions appended after the defaultcount. Each entry is a mapping withfunc(one of the supported Splunk stats functions, e.g.values,sum,dc),field, and an optionalas/alias, e.g.[{func: values, field: Processes.process_name, as: process_names}].countis always present and cannot be redefined here.tstats_aggregation: a raw aggregation string appended verbatim aftercount(advanced use). When set, it takes precedence overtstats_aggregations.
This backend is currently maintained by:
Metadata
Release files for pysigma-backend-splunk 3.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pysigma_backend_splunk-3.0.1.tar.gz | 24.2 kB | With provenance | Details for pysigma_backend_splunk-3.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pysigma_backend_splunk-3.0.1-py3-none-any.whl | Python 3 | none | any | Details for pysigma_backend_splunk-3.0.1-py3-none-any.whl |
Total release size: 50.1 kB
Release files / pysigma_backend_splunk-3.0.1.tar.gz
| Download URL | pysigma_backend_splunk-3.0.1.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bd920634c43f67124445a207f8a804c13cc71d7cd4fd1d2ddb6313d4f974b613
|
|
BLAKE2b-256 checksum How to use checksums |
39c3ba13d06eef24583b36a2dc39c4fb642251c8cef456dd69ee1d47931156c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.
Transparency logRelease files / pysigma_backend_splunk-3.0.1-py3-none-any.whl
| Download URL | pysigma_backend_splunk-3.0.1-py3-none-any.whl |
|---|---|
| Size | 25.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cb983c86c409227d25b3c39f4420b0508f630db012071fff0920a999cce92a05
|
|
BLAKE2b-256 checksum How to use checksums |
6b1afd16b60fa5905ed2d544f005e7c7119b76075d29fe5e9b6b67dd15540089
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.
Transparency logSecurity for pysigma-backend-splunk 3.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pysigma_backend_splunk-3.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.