Sigma rule testing
Most detection rules ship without ever seeing your data. In Huntbase, every Sigma rule is compiled onto OCSF, backtested on your history, run in shadow and versioned like code.
The lifecycle
Five stages. A rule moves on when the evidence says it is ready, and goes back when it floods.
The backtest
Pick a window of up to 90 days and Huntbase runs the rule over your own history. You see how often it would have fired, on which hosts, and a sample of the events.
The fast count is approximate, so Huntbase also runs the rule's exact logic over a sample and tells you when the two disagree.
title: Encoded PowerShell command line logsource: { category: process_creation, product: windows } detection: selection: Image|endswith: '\powershell.exe' CommandLine|contains: ' -enc ' condition: selection tags: [attack.t1059.001]
Compiles · bound to process_activity · process.file.path, process.cmd_line
What you get
Read next:Detection EngineeringIntelligence in HuntbaseTest detections against real attacksWhat is Sigma?
Questions
In Huntbase, backtest it over your own history for up to 90 days to see what it would have fired on, then run it in shadow mode, where it is evaluated on live data but only reaches the digest. Turn it on when the evidence says it is ready.
Yes. Enable the SigmaHQ community rules for your organisation and Huntbase fetches them for you. They arrive as watchers, switched off. Rules that cannot run on your data are grouped by reason, such as a field that is not mapped.
Huntbase compiles Sigma natively onto OCSF-normalised data. For data that stays in another SIEM, any rule can also be converted to Splunk SPL, Microsoft Sentinel KQL or Elastic ES|QL.
Yes. Sigma correlation rules (event count, value count and temporal ordering) run on Huntbase's correlation engine.
Bring your own Sigma or start from SigmaHQ, and see what it would have fired on before it goes live.
Sign up.
Run a guided hunt on the sample workspace. No connector needed.
Connect your own sources when you're ready.