Overview
Run and measure
Building one detection is a project. Running a few hundred of them is a job, and this part covers the job: the meetings and roles, the metrics, ATT&CK coverage, maturity, and where the program runs out of room. It's also where you find out whether any of it is working, which is the question leadership will ask first.
On this page
Meetings
WeeklyIntake and orderWhat enters build this week, and which candidates are blocked on telemetry.
MonthlyLive reviewWhat gets tuned with a named exclusion, what gets retired, what gets left alone.
QuarterlyCoverage and capacityNext quarter's telemetry asks, whether the weights still match the threat picture, and which ceiling to spend against.
Within 5 working days of every incidentDetection review after an incidentWhich live detections get a fix carrying the incident's events as a fixture, which candidates enter intake with what threat relevance, and which rules put live by hand during it enter intake.
In this part
Operating rhythmMeetings, roles, the first 90 days, and common failures.Read this when you've just been handed the function.MetricsEvery number the program reports, each defined once.Read this when you owe somebody a report.Coverage scoring rulesThe rules behind every color in the ATT&CK coverage map and workbook.Read this when a coverage number needs defending.ATLAS and D3FENDAttacks on AI systems from ATLAS, and the defenses D3FEND links to each ATT&CK technique.Read this when you detect attacks on AI, or want a named analysis to start a hypothesis from.Maturity levelsEach dimension scored 0 to 4 on evidence, with your level set by the lowest.Read this when you need to say where you stand.ScalingThe ceilings that cap a program, and what breaks at each size.Read this when you're planning headcount or telemetry.Handling objectionsThe objections a rollout meets, and the answer to each.Read this when you're about to present this.
Roles
Detection leadIntake, the backlog order, the metric set, and the quarterly report
Detection engineerThe hypothesis, the detection, the record, the fixtures, and the score's evidence lines
Reviewer, a second engineerThe approval on the change, and the argument with the blind spots section
Incident response leadInvestigation, containment, and the notification path
Platform or data ownerThe log source inventory, the silence alerts, parsing and retention
Ceilings
The smallest ceiling is the size of your program.
Triage ceilingHow many live detections can the analysts absorb?
Maintenance ceilingHow many live detections can the engineers keep current?
Telemetry ceilingHow many detections can be built at all?
The other overviews: The framework · Build detections · The tools.