Section 14
Scaling
Do it in the browser Find your ceiling
Remember
- Analyst triage time, engineering upkeep time, and telemetry each cap a program, and the smallest cap sets your size.
- Each live detection costs about 20 minutes a month to maintain, on top of its triage minutes.
- Replace the 20-minute default with your own number after a quarter of measuring.
- Tuning and retirement raise the triage ceiling for less than hiring analysts does.
- A candidate blocked on telemetry needs a log source request before it needs an engineer.
Triage minutes cap how many alerts analysts can absorb, engineering minutes cap how many detections stay current, and telemetry readiness caps what you can build at all. The smallest of the three sets the size of your program.
On this page
14.1The ceilings
| Ceiling | What it limits | How it is computed |
|---|---|---|
| Triage ceiling | How many live detections can the analysts absorb? | (analysts x triage hours each per day x 60) / (alerts per detection per day x minutes per alert) |
| Maintenance ceiling | How many live detections can the engineers keep current? | (engineers x upkeep hours each per week x 60 x 52 / 12) / upkeep minutes per detection per month |
| Telemetry ceiling | How many detections can be built at all? | count of techniques whose log sources are all at readiness 3 or above; one detection per technique until you have measured your own ratio |
I count both recurring ceilings in minutes, because minutes are what run out. The maintenance figure defaults to 20 minutes per live detection per month. That covers the precision check, one look at the tuning queue, and fixing the query after a field changes. Replace it once you've measured a quarter.
Triage ceiling
- Cut alerts per detection: tighten the logic, exclude one named source of noise, or raise the threshold.
- Cut minutes per alert: enrich the alert with the context the analyst looks up by hand.
- Group related alerts into one case, so 10 alerts cost one triage.
Common mistake: Hiring analysts is the most expensive way to raise this ceiling.
Maintenance ceiling
- Generate the query for every target from one source rule.
- Let the precision check propose retirements, so upkeep shrinks the estate.
- Template the detections that differ only by a field or a threshold.
Common mistake: Nobody books the recurring cost when the detection ships, so this ceiling goes unnoticed until upkeep falls behind.
Telemetry ceiling
- Onboard first the source that unblocks the most scored candidates.
- Fix sampling, truncation, and short retention. That moves a source from readiness 2 to 3, where this ceiling starts counting it; parsing the fields then takes it to 4.
- Ship the silence alert, so a source that dies doesn't take its detections with it.
Common mistake: Treating a blocked candidate as engineering work keeps it in the detection backlog. It belongs on the log source request list until someone onboards the data.
14.2Breaking points by size
| Live detections | What still works | What breaks first | The change that reaches the next order of magnitude |
|---|---|---|---|
| About 10 | A spreadsheet, a shared folder, and one person's memory. | Nobody can say why a detection exists once its author is on leave. | Write the record: goal, technique, blind spots, response. |
| About 50 | Records, a written backlog, manual deployment. | Alert volume becomes a rostering problem, and tuning changes lose their history. | Put the definitions of done in CI and start measuring precision per detection. |
| About 200 | CI, scores, a metric set. | No one person knows the estate. Near-duplicates appear, and hand-converting queries per platform stops scaling. | One source rule per detection, converted to every target by the pipeline; ownership assigned per platform. |
| About 1000 | Generated queries, owners, automated checks. | Coverage claims become unfalsifiable and the maintenance ceiling binds before the triage one. | Automate retirement, decouple alert volume from detection count by grouping into cases, and report coverage weighted by robustness. |
At every step, coordination between people fails before the detections do. Each move swaps something one person remembers for a file, a definition of done, or a generated artifact.
14.3Work that doesn't scale
- Counting detections. 200 detections that match filenames add up to the same weighted coverage as 40 at robustness 5, and each of the 200 still costs upkeep every month.
- One query per platform maintained by hand. Every new target multiplies the estate by the number of SIEMs.
- Triage headcount. Alert volume grows with the estate; analyst hours grow with the budget cycle.
- Review by the author. It's the first check dropped under deadline.
Review is the cheapest of these to keep. A second engineer's review costs 20 minutes, and it's the only check that catches an assumption the author didn't know they were making.