This part follows a single detection from somebody's idea to a reviewed rule: how you choose it, research it, write it, and prove it works. It's the practitioner's half of the framework, and the half where you get to open an editor.
Every candidate starts at intake with six scored inputs. If the log source it needs isn't collected, the score is 0 and the candidate is blocked, which saves you from writing a careful rule for logs you don't have. A candidate that passes intake gets a written hypothesis, a named blind spot, and a read-only count over 7 days of production data. That count tells you how loud the rule will be before it pages anyone.
Before a rule ships, it needs real events to test against, because a rule that has only ever met its author's imagination tends to do well there. Engineers capture those events through emulation and scrub credentials and personal data out of them. The rule is written once in Sigma, converted for every target, and replayed against its fixtures on every replay engine. An agent can draft most of what each stage produces, and people keep review, deployment, and retirement.
HypothesisOne sentence: when an attacker does X, log source Y records Z.
->
EmulationRun it from a believable foothold and read what lands in the log.
->
RecordEvery section filled in, so somebody other than the author can triage and change it.
->
Detection and fixturesSigma, converted to every target, with an event it must match and one it must ignore.
->
ReviewA second engineer approves. The fixtures replay in CI.
The path a single detection takes from idea to review. The score decides which idea goes first.
ValueT + I + BThreat relevance, impact, and how hard the detection is to evade.
÷
CostE + CHours to build, and analyst minutes a day to live with.
×
Readiness(R / 5)^kIs the data in the SIEM and usable? A 0 blocks the candidate.
×
MarginalMWhat it adds to what already fires: first 1, stronger 0.8, equal 0.5.
=
Score0.03 to 7.50On the balanced preset. Scores in one 0.2 band tie, and the lower run cost goes first. Mandates due inside 90 days go ahead of every score.
Each input carries an evidence line. Readiness is scored 0 to 5 and the rest 1 to 5. Every weight and k start at 1 on the balanced preset; threat_led doubles wT, asset_led doubles wI, and telemetry_led raises k to 2.