Measuring Defensive Coverage with ATT&CK
What you'll learn: How to use the ATT&CK framework to systematically evaluate which threats your security controls actually detect and where dangerous blind spots exist.
Understanding Defensive Coverage Measurement
Imagine a castle with walls, moats, and towers—but you've never tested whether guards can actually see attackers approaching from the east. That's what many security programs face: lots of tools deployed, but no clear picture of what adversary behaviors they actually catch.
Defensive coverage measurement means mapping your security controls (EDR, SIEM rules, network sensors, etc.) to specific ATT&CK techniques, then identifying which techniques lack adequate detection or prevention.
The Core Process
Start by inventorying your security controls and determining which ATT&CK techniques each one addresses. For example:
- Your EDR might detect T1003 (Credential Dumping) and T1059 (Command-Line Execution)
- Your SIEM rule for abnormal PowerShell might cover T1086 (PowerShell)
- Network monitoring might catch T1071 (Application Layer Protocol) for C2 traffic
Next, use ATT&CK Navigator to visualize this coverage. Color-code techniques by detection maturity: green for strong detection, yellow for partial, red for no coverage.
Finding and Prioritizing Gaps
The real value emerges when you discover coverage gaps—techniques adversaries commonly use that you cannot detect. If your threat intelligence (lesson 2180) shows adversaries targeting your sector use T1098 (Account Manipulation), but you have zero detection for it, that's a critical blind spot to address.
This measurement becomes a living process: test defenses through red team exercises (lesson 2169), update coverage maps, and guide blue team improvements (lesson 2170).
Key Takeaway: Measuring defensive coverage with ATT&CK transforms security from "we have tools" to "we can detect these specific adversary actions"—turning unknown protection into quantified, improvable defense posture.