from sigma.policy import SafePolicy
from sigma.processing.pipeline import ProcessingPipeline
pipeline = ProcessingPipeline.from_yaml(yaml_string, policy=SafePolicy())
from sigma.policy import SigmaPolicy
from sigma.policy.regex_engine import PythonRegexEngine
from sigma.processing.pipeline import ProcessingPipeline
policy = SigmaPolicy(
allow_template_vars=True,
allow_external_sources=True,
vars_allowed_paths=("/trusted/rules",),
regex_engine=PythonRegexEngine()
)
pipeline = ProcessingPipeline.from_yaml(yaml_string, policy=policy)
from sigma.processing.transformations import GenericTypeValueTransformation
import re
class ExtractHashValue(GenericTypeValueTransformation):
pattern = re.compile(r'SHA256=([0-9a-fA-F]{64})')
field = 'Hashes'
# Attach to a SigmaProcessingPipeline as a transformation step
detection:
selection:
Status|neq: 'success'
condition: selection
PYSIGMA_ALLOW_VARS_EXECUTION=1 python convert_rules.py
rules:
- any
from sigma.processing.transformations import ReplaceStringTransformation
transformation = ReplaceStringTransformation(
regex="^win_",
replacement="windows_",
interpret_special=True,
)
from sigma.processing.transformations import ReplaceStringTransformation
transformation = ReplaceStringTransformation(
regex="(?i)windows\\system32\\",
replacement="%SystemRoot%\\system32\\",
interpret_special=False
)
from sigma.processing.conditions import RuleContainsFieldCondition
condition = RuleContainsFieldCondition(field="CommandLine")
# Returns True when the active rule references the 'CommandLine' field
if condition.match(pipeline_context, rule):
apply_commandline_mapping()
ReplaceStringTransformation(search='*', replacement='', skip_special=True)
from sigma.processing.transformations import ConvertTypeTransformation
transformation = ConvertTypeTransformation(field="event_id", target_type="int")
from sigma.processing.conditions import RuleProcessingStateCondition
from sigma.processing.transformations import FieldMappingTransformation
from sigma.processing.pipeline import ProcessingItem
item = ProcessingItem(
transformation=FieldMappingTransformation({"src_ip": "source.ip"}),
rule_conditions=[
RuleProcessingStateCondition(key="normalized", val=True)
]
)
from sigma.rule import SigmaRule
from sigma.types import SigmaLevel
rules = [SigmaRule.from_yaml(r) for r in raw_rules]
high_and_above = [r for r in rules if r.level >= SigmaLevel.HIGH]
from collections import defaultdict
from sigma.types import SigmaLevel
buckets = defaultdict(list)
for rule in rules:
buckets[rule.level].append(rule)
for level, matched in buckets.items():
print(f"{level}: {len(matched)} rules")
from sigma.collection import SigmaCollection
collection = SigmaCollection.load_ruleset(["./rules"])
unreferenced = collection.get_unreferenced_rules()
for rule in unreferenced:
print(rule.title)
from sigma.processing.pipeline import ProcessingPipeline
pipeline = ProcessingPipeline(
items=[...],
postprocessing_items=[my_postprocessing_item],
finalizers=[my_finalizer],
vars={},
)
detection:
selection:
CommandLine|cased: 'PowerShell.exe -EncodedCommand'
condition: selection
backend = MyBackend(processing_pipeline=pipeline)
query = backend.convert_rule(rule)
applied_ids = [item.identifier for item in backend.last_processing_pipeline.applied_items]
if 'normalize_field_names' not in applied_ids:
raise RuntimeError('Required processing item was not applied')
detection:
condition: selection
selection:
CommandLine|exists: true
detection:
condition: selection
selection:
CommandLine|re|i|m: '^powershell.*-enc'
from sigma.pipelines.common import generate_windows_logsource_items, windows_logsource_mapping
processing_items = generate_windows_logsource_items(windows_logsource_mapping)
ProcessingItem(
transformation=FieldMappingTransformation({"EventID": "winlog.event_id"}),
field_name_conditions=[
IncludeFieldCondition(fields=["EventID", "CommandLine"])
]
)
class MyBackend(TextQueryBackend):
cidr_expression: ClassVar[str] = 'cidr({field}, "{value}")'
detection:
selection:
CommandLine|windash|contains:
- ' -enc '
- ' -nop '
from sigma.processing.transformations import SetState
from sigma.processing.pipeline import ProcessingPipeline, ProcessingItem
pipeline = ProcessingPipeline(
items=[
ProcessingItem(
transformation=SetState("index", "winlogbeat-*")
)
]
)
What you can do now
Checking Plays…
Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed Plays.
Summary
pysigma is an open-source Python library that parses, processes, and converts Sigma detection rules into queries for security monitoring systems, aimed at detection engineers and developers building rule-conversion workflows. It is installed with a Python package manager and imported into other code, requiring Python 3.11 or later; its documentation describes it as the successor to sigmac, while the README identifies sigma-cli as the command-line equivalent. Backends and processing pipelines are separate projects, keeping the library vendor-agnostic. The project is marked pre-release, with six tracked releases and a release 10 days ago.
Pysigma is a python library to parse and convert Sigma rules into queries (and whatever else you could imagine)
Which Sigma rules can be converted into queries for my monitoring backend?
parses the rules, applies the selected backend’s conversion logic, and produces queries in that backend’s language; the backend implementation determines which rule features it can represent
How do my Sigma rules need to change for the log data model used by my monitoring system?
runs processing pipelines that transform fields, values, placeholders, and other rule content before conversion; the result depends on the mappings and transformations defined by the selected pipeline
Can I express exclusions and negative matches directly in my detections?
parses not-equal conditions and Sigma filters, including filters applied broadly across rules, then passes that logic to the backend for query generation; the final query still depends on backend support for the condition
How can I convert correlation rules into queries while preserving their aggregations?
parses correlation conditions and supported aggregation types, including sums, averages, percentiles, and medians, and lets the backend finalize the resulting query; unsupported correlation semantics remain dependent on the backend
Which rule metadata and framework references are available during processing?
exposes rule attributes, scope, and on-demand MITRE ATT&CK data from configured remote or local sources to processing and conversion; references unavailable from those sources cannot be resolved
Built from pysigma'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.
pysigma covers 3 of the 11 logs and telemetry capabilities we track.
What pysigma offers you
Plugin API support1
Plugin system1
Python scripting support1
Command-line interface
No capabilities match.
+Security event correlation6 featuresLogs and telemetrysince 2023▸
+Correlation Query Advanced FeaturesNot checked yet · Date unknownAdds typing, arbitrary parameter passing, multi-rule search, and query expression support to correlation query generation.7 releases · first seen Mar 2024▸
Shared capability: Security event correlation
+Sigma Correlation Rule SupportNot checked yet · Date unknownParses and converts Sigma correlation rules in addition to detection rules.4 releases · 1 other source · first seen Dec 2023▸
Shared capability: Security event correlation
+Correlation Rule Processing SupportNot checked yet · Date unknownExtends pipeline application, log source filtering, and aggregation template variables to correlation rules.4 releases · first seen May 2024▸
Shared capability: Security event correlation
+Fractional thresholds in correlation conditionsNot checked yet · Date unknownSupports fractional (non-integer) threshold values in correlation condition definitions.2 releases · first seen Oct 2026▸
Shared capability: Security event correlation
+Correlation Logic and Type ExtensionsNot checked yet · Date unknownExtends correlation conditions with additional rule logic and adds support for new aggregation types such as value_sum, value_avg, value_percentile, and value_median.1 release · first seen Feb 2026▸
Shared capability: Security event correlation
+Sigma Spec 2.1.0 Correlation Type SupportNot checked yet · Date unknownSupports new correlation aggregation types including value_sum, value_avg, value_percentile, and value_median.1 release · first seen Nov 2025▸
Shared capability: Security event correlation
+Log parsing and normalization2 featuresLogs and telemetrysince 2025▸
+Advanced Rule ValidatorsNot checked yet · Date unknownAdds validators for WinDash formatting and strict field mapping enforcement to improve rule quality.3 releases · first seen Nov 2025▸
Shared capability: Log parsing and normalization
+Regex-Based Field ExtractionNot checked yet · Date unknownProvides a GenericTypeValueTransformation class to extract structured field values from raw strings using regex capture groups.1 release · 1 other source · first seen Jul 2026▸
Shared capability: Log parsing and normalization
+Log search1 featureLogs and telemetrysince 2024▸
+Special Character and Modifier SupportNot checked yet · Date unknownAdds support for em/en dashes in Windows dash variants and allows special characters in string expressions.2 releases · first seen Jul 2024▸
Shared capability: Log search
+Other / not yet classified38 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+SigmaPolicy trust-model configurationNot checked yet · Date unknownProvides a `SigmaPolicy` dataclass that centralises trust-model settings (regex engine, template variables, external sources, allowed paths) and propagates them automatically through every pipeline call, replacing ad-hoc per-parameter flags.12 releases · 1 other source · first seen Jan 2025▸
+Pipeline Transformation LibraryNot checked yet · Date unknownsuggestedAdds various processing transformations including string mapping, value setting, field manipulation, type conversion, and regex application.13 releases · first seen Jan 2024▸
Suggested capability: Log parsing and normalization. This is our guess, not confirmed.
+Sigma String and Regex Processing ImprovementsNot checked yet · Date unknownExpands string pattern to regex conversion, supports special characters in expressions, and adds controls for wildcard handling during replacement.8 releases · 2 other sources · first seen Aug 2024▸
+Pipeline YAML security hardeningNot checked yet · Date unknownRejects security-related keys in pipeline YAML and strips them before instantiation, preventing untrusted pipeline definitions from enabling privileged features at runtime.6 releases · first seen Nov 2025▸
+Predefined SafePolicy and TrustedPolicy profilesNot checked yet · Date unknownShips two ready-made `SigmaPolicy` profiles — `SafePolicy` (RE2 engine, all risky features disabled) and `TrustedPolicy` (Python engine, all features enabled) — for common deployment patterns.3 releases · 3 other sources · first seen Feb 2023▸
+Advanced Pipeline Conditions and RoutingNot checked yet · Date unknownsuggestedAdds conditions based on processing state, rule attributes, tags, log source, and field presence to gate or route pipeline transformations.6 releases · first seen Apr 2024▸
Suggested capability: Log routing. This is our guess, not confirmed.
+Backend compatibility validation for YAML pipelinesNot checked yet · Date unknownValidates that a pipeline loaded from YAML is compatible with the target backend before use.5 releases · first seen Feb 2023▸
Also counts toward: Plugin API support, Plugin system
+Extended Sigma Condition LogicNot checked yet · Date unknownAdds support for negative operators, list-based rule attributes, and exact value matching within detection conditions.4 releases · 1 other source · first seen Nov 2025▸
+Processing Condition EnhancementsNot checked yet · Date unknownExpands processing conditions to include negation, field name scoping via dedicated lists, and state tracking for visibility into which items were applied.5 releases · first seen Apr 2022▸
+RE2 regex engine with ReDoS protectionNot checked yet · Date unknownSwitches the default regex engine to Google RE2, eliminating ReDoS risk from untrusted Sigma rules, while keeping the Python `re` engine available as an explicit opt-in via `SigmaPolicy`.4 releases · first seen Oct 2026▸
+Template Variable Security HardeningNot checked yet · Date unknownDisables template variables by default and introduces explicit opt-in controls (`allow_template_vars`, `vars_allowed_paths`) plus an environment variable fallback to prevent accidental code execution from untrusted pipelines.4 releases · first seen Apr 2026▸
+Enhanced Backend Configuration and IntegrationNot checked yet · Date unknownExtends backend configuration via pipeline options and template helper functions, while enabling field references and query finalization control.4 releases · first seen Jan 2025▸
+Sigma Rule Filtering and Severity BucketingNot checked yet · Date unknownEnables filtering rules by severity/status using comparison operators and bucketing rules by severity for reporting.2 releases · 2 other sources · first seen Mar 2024▸
+Pipeline Composition and Directory ResolutionNot checked yet · Date unknownEnables loading pipelines from directories and composing complex pipelines by nesting other pipelines.3 releases · first seen Jul 2024▸
+Nested post-processing pipeline items from YAMLNot checked yet · Date unknownAllows nested query post-processing items to be loaded directly from YAML pipeline definitions.3 releases · first seen Oct 2026▸
+Sigma FiltersNot checked yet · Date unknownIntroduces capability to suppress or exclude matching Sigma rule results.2 releases · 1 other source · first seen Jun 2024▸
+Metadata ValidatorNot checked yet · Date unknownValidates Sigma rule metadata fields.3 releases · first seen Nov 2023▸
+Sigma Rule Validation EnhancementsNot checked yet · Date unknownAdds validators for dangling conditions, wildcard usage in detection items, and logsource naming conventions.3 releases · first seen Jun 2024▸
+Environment variable fallback for security settingsNot checked yet · Date unknownSupports `PYSIGMA_ALLOW_VARS_EXECUTION` and `PYSIGMA_ALLOW_EXTERNAL_SOURCES` environment variables as a legacy fallback for configuring security-related settings when a `SigmaPolicy` instance is not provided.2 releases · first seen Jul 2026▸
+Template processing sandboxingNot checked yet · Date unknownRestricts template processing so that only safe built-in types can have methods called, blocking arbitrary object method invocation from untrusted rule content.2 releases · first seen Oct 2026▸
+External Data Source IntegrationNot checked yet · Date unknownsuggestedSupports loading dynamic lookup data from File, HTTP, or Command sources into Sigma rules at transformation time.2 releases · first seen Jun 2026▸
Suggested capability: Log enrichment. This is our guess, not confirmed.
+Sigma Specification Compliance UpdatesNot checked yet · Date unknownAdds missing UTF-16 modifiers, extends CommandPlaceholderTransformation placeholders, and adds temporal_extended correlation types to align with the Sigma specification.2 releases · first seen Jul 2026▸
+Sigma Taxonomy and Data UpdatesNot checked yet · Date unknownAdds MITRE D3FEND namespace support and updates bundled MITRE ATT&CK data.2 releases · first seen Aug 2024▸
+Custom Backend and Expression SupportNot checked yet · Date unknownsuggestedAdds equality expression support for text backends and allows custom fields in logsource definitions.2 releases · first seen Apr 2024▸
Suggested capability: Log search. This is our guess, not confirmed.
+Pipeline State ManagementNot checked yet · Date unknownsuggestedEnables passing format-specific context and state across pipeline steps using SetState transformations.2 other sources · first seen May 2022▸
Suggested capability: Log parsing and normalization. This is our guess, not confirmed.
+Sigma Collection InspectionNot checked yet · Date unknownProvides methods to inspect Sigma collections for unreferenced rules and rule outputs.1 release · 1 other source · first seen Jan 2024▸
+In-Process Rule MatchingNot checked yet · Date unknownProvides a `sigma.matching` module that matches live or logged events directly against Sigma rules in Python without converting rules to a query language first.1 release · first seen Nov 2026▸
Also counts toward: Python scripting support
+Hyphenated Detection Identifier SupportNot checked yet · Date unknownAllows dashes in `1/all of` selector patterns so rule conditions that reference hyphenated detection identifiers parse correctly.1 release · first seen Nov 2026▸
+Windows Logsource Taxonomy ExtensionsNot checked yet · Date unknownAdds named Windows logsource definitions (such as `adfs` for Active Directory Federation Services) to the bundled taxonomy for use in Sigma rules.1 release · first seen Nov 2026▸
+Rule Tag ComparisonNot checked yet · Date unknownEnables comparing Sigma rule tags directly with their string representations.1 release · first seen Aug 2024▸
+Plugin Upgrade SupportNot checked yet · Date unknownEnables upgrading plugins via dedicated upgrade plugin support.1 release · first seen Dec 2023▸
+SigmaRelated ClassNot checked yet · Date unknownProvides a dataclass for expressing relationships between Sigma rules.1 release · first seen Dec 2023▸
+SigmaRule Quality ValidatorsNot checked yet · Date unknownValidates author and title fields within the SigmaRule class for quality assurance.1 release · first seen Dec 2023▸
+Summiting the Pyramid Tag SupportNot checked yet · Date unknownSupports Summiting the Pyramid v1.0.0 tags in Sigma rules.1 release · first seen Dec 2023▸
+Duplicate References ValidatorNot checked yet · Date unknownDetects Sigma rules that reference the same source more than once.1 release · first seen Nov 2023▸
+Filename ValidatorNot checked yet · Date unknownEnforces naming conventions on Sigma rule files.1 release · first seen Nov 2023▸
+Tags ValidatorNot checked yet · Date unknownEnforces valid tag usage in Sigma rules.1 release · first seen Nov 2023▸
+Wildcard ValidatorNot checked yet · Date unknownValidates Sigma rules to catch invalid wildcard usage in string fields.1 release · first seen Oct 2023▸
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.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for pysigma, 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.
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 pysigma 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.
Nothing first seen in this window. That doesn't mean pysigma shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-11
1
How we count
Read from 4 of 40 release notes and docs updates we hold for pysigma. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through pysigma's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
Show
Coverage in all entries
40 entries
No entries match these filters.
November 20262
October 20262
July 20261
June 20261
April 20261
February 20261
January 20261
November 20251
May 20251
January 20251
October 20242
September 20243
August 20242
July 20241
June 20242
May 20241
April 20241
March 20241
January 20241
December 20231
November 20232
October 20231
July 20231
May 20231
April 20231
February 20231
December 20221
September 20221
August 20221
July 20221
May 20221
April 20221
Project health
Issue, contributor and maintainer activity in sigmahq/pysigma, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed64%of issues opened, last 12 months
Median time to close6.2 daysfirst maintainer reply 5.7 days
Open backlog3of 140 issues ever filed
Issues opened / month3 · 0communitymaintainers
Open backlog3
Contributors / monthnot measured
Commits / monthnot measured
Starsnot measured
Issue themes, last 12 months
features 5%
other 95%
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.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.