Patterns & prevention
If you can only do a few things, do the ones that cover the most. These are ranked by breadth — how many of the 657 catalogued attacks a single telemetry source or mitigation touches, and across how many of the 10 categories. A control that spans many categories is a real choke point, not a point fix.
Collect once, see many
The one log source that, if you collect it, gives you visibility into the most attacks. Straight from each attack's ATT&CK data components.
Each dot is one telemetry source. Up = it spans more of the 10 categories; right = it touches more attacks. The top-right corner is where a single log source is a real choke point, not a point fix.
Deploy once, cover many
The one mitigation linked as a defence for the most attacks. The category spread is the tell: a control that reaches across the taxonomy is leverage, not a niche fix.
Read this honestly
- Breadth, not efficacy. A mitigation linked to 80 attacks is not proven to stop any of them — it means the corpus records it as a relevant defence that often. Coverage tells you where to start, not that you are done.
- Category breadth is the signal. A source or control that spans 9–10 categories is a genuine choke point; one that is common inside a single category is not.
- D3FEND is excluded from the mitigation table on purpose: its artifact-to-technique mapping is coarse (several classes share identical scores), which would crowd the ranking with a mapping artifact rather than real leverage.
Generated from analysis/patterns.py over the compiled corpus — a pure,
deterministic projection, regenerated and never hand-edited.