Threat Scenarios
Chain existing detections into an ordered, risk-scored kill chain — a scenario raises one Splunk notable when a single risk object accrues risk across every stage inside a correlation window, instead of leaning on any one noisy rule.
Building a scenario
Scenarios are Git-backed like everything else — each is versioned as JSON under Talon/threat-scenarios/ in the workspace repo.
Preview, replay & deploy
Preview compiled artifact shows the exact Splunk risk-incident saved search a scenario becomes — compiled against the live state of its stage detections, with warnings when a stage has lost its technique or risk model since you saved. Active scenarios are recompiled into the bundled Splunk app on every deploy; a scenario that can't compile is skipped, never a deploy blocker.
Run replay (in the scenario's row menu) tests the chain without any SIEM: each stage's detection runs its Sigma rule against its own sample telemetry — golden events and JSON attack data — in kill-chain order. Each stage reads detected, false coverage (telemetry arrived but the rule stayed silent), no telemetry or error, and the chain reads Chain detected, Chain broken or No telemetry. Run history keeps past verdicts, and a chain that used to fire and no longer does is flagged as regressed.