Section 3
Sizing the practice
Adopting every practice at once stalls a small team. Each practice works on its own, and the tables give the smallest working version of each and how a team of your size divides the roles.
Remember
- Start with the practice that fixes a problem you have today. You can adopt the practices in any order.
- A team of one can start with detection zero, the scored backlog, and the retirement triggers.
- Adopt the smallest working version of a practice first, and grow it when it stops answering a question somebody asks.
- Below five engineers, adopt detection as code last, once hand-converting queries has become the bottleneck.
On this page
3.1The practices
| Practice | What it fixes | What it needs first | Effort |
|---|---|---|---|
| Detection zero, the log source silence alert | A detection can't fire on telemetry that stopped arriving, and a silent log source looks exactly like a quiet network. | A list of log sources and their normal event rate. | An afternoon for the first source, an hour for each one after. |
| The scored backlog | Detection backlogs are longer than the team's capacity, so whoever asked most recently decides the order. | Nothing but the candidates. Readiness needs the log source inventory to be honest. | An hour to score 10 candidates once the score wording in Appendix B is read. |
| Countable definitions of done | You can't report on stages that end on judgment ("it looks ready"). Work stalls between them and nobody sees it. | Somewhere to record the count: a ticket field is enough. | One editing session on your ticket template. |
| The detection record | If a detection's intent, log sources, blind spots, and response steps live only in the author's head, nobody else can triage it, review it, or safely change it. | A place to keep it next to the detection: a repository, a wiki page, or the detection's own description field. | 30 minutes per detection, most of it recall. |
| Second-engineer review | A detection approved only by its author reaches production carrying the author's assumptions about the environment. | A pull request, a ticket transition, or a change record. | 20 minutes per detection for the reviewer. |
| Retirement triggers and the precision floor | Detections leave production far less often than they enter it, so analysts spend their day triaging alerts from detections nobody owns. | Alert outcomes from the SIEM: how many alerts fired and how many were true positives. | A scheduled query per month, plus one review of the results. |
| The metric set | Detection metrics get redefined between reports, so a change in the trend line can come from a changed definition. | The stages in use, plus alert outcomes for the live-side numbers. | Half a day to wire the first four; the rest as the data becomes available. |
| Detection as code, with a CI job per definition of done | When only habit enforces the definitions of done, people skip them under deadline pressure, and nobody notices until an alert fires on a detection that was never tested. | Version control, a CI runner, and detections stored as files. | A week for the first pipeline, then minutes per detection. |
| Threat-model intake | Threat models end as a document with a list of unmitigated threats, and the detection backlog never hears about them. Impact scores come from the engineer's guess about which assets matter. | A threat model for at least one service, with its threats mapped to ATT&CK techniques and a named owner. | An hour per threat model to file the candidates, once the handoff fields are agreed with whoever runs the modeling. |
3.2The smallest version of each
| Practice | Smallest version that still works |
|---|---|
| Detection zero | One saved search per source that compares the gap since the last event against three times the median gap, with a one-hour floor. |
| The scored backlog | Score the open backlog in the spreadsheet on the downloads page. Keep the evidence line for each input; drop the weights and the presets until someone disputes the order. |
| Countable definitions of done | Copy the definition of done column into the template for your detection ticket type. |
| The detection record | For detections already live, four sections to start: goal, categorization (the ATT&CK technique), blind spots and assumptions, and response. For a new detection, you write goal, categorization, strategy abstract, and blind spots at hypothesis. |
| Second-engineer review | A checklist in the pull request: the fixtures pass, the query matches the approved copy, the blind spots section is filled in. |
| Retirement triggers and the precision floor | Once a month, compute 30-day precision for every live detection and compare each with its floor. At the smallest size that is a short list, and a spreadsheet does it. |
| The metric set | Detections live, percent with tests, precision over 30 days, and minutes per true positive. |
| Detection as code | One job that validates the rule file and the score record on every pull request. |
| Threat-model intake | Add the handoff fields to the threat model template, and file one candidate per unmitigated threat at the next intake meeting. |
3.3Teams and roles
Stage owners are roles, and one person can own several.
| Team | Who owns which role | Work in progress limit | Adopt first |
|---|---|---|---|
| One engineer, detection part-time | Every stage owner is you. For review, use a colleague outside the team, a peer elsewhere, or a 24-hour wait before you approve your own change. | One detection in flight. Two half-built detections is the failure mode at this size. | Detection zero, the scored backlog, retirement triggers and the precision floor |
| Two to four engineers | One person has the lead role and owns intake and the backlog order. The others rotate build and review, so no detection is approved by its author. | Weekly engineering hours divided by the hours one detection takes from hypothesis through validation. Eight hours per detection until you measure your own. | The scored backlog, countable definitions of done, the detection record, retirement triggers and the precision floor |
| Five or more, or several teams | Stage owners map to real seats. The lead owns intake and prioritization, engineers build, and a rotating reviewer approves. The SOC lead co-owns tuning, because the triage cost lands on their analysts. | Set it per engineer, so one engineer's stalled detection doesn't use up the team's limit. | Detection as code, the metric set, countable definitions of done, the scored backlog |
3.4The first month
| Team | The first month |
|---|---|
| One engineer, detection part-time | Build the log source inventory, ship the silence alert for each source, score the backlog once, and build the top three of the section 4 shortlist, one at a time. Track two numbers by hand: alerts per detection per day and minutes to triage one. |
| Two to four engineers | Put the definitions of done in the ticket template, score the open backlog, and run the retirement triggers against the live detection set. Expect the first pass to retire detections nobody has defended in a year. |
| Five or more, or several teams | Put the framework in version control. Wire one CI job per definition of done. Publish the metric set, so a number means the same thing each month. |
The detections to build come from the shortlist in section 4.