ATT&CK for Detection and Analytics
What you'll learn: How to translate ATT&CK techniques into actionable detection rules and analytics that strengthen your defensive security posture.
From Knowledge to Detection
You've learned the ATT&CK framework as a taxonomy of adversary behavior. Now comes the powerful next step: using that knowledge to build detections. Think of ATT&CK as a recipe book of attacker moves—detection analytics are your burglar alarms tuned to catch those specific moves in action.
Building Technique-Based Detections
Each ATT&CK technique describes what attackers do. Your job as a defender is to identify observable artifacts that technique leaves behind:
Example: T1003.001 - LSASS Memory Dumping
- Observable: Process access to
lsass.exewith specific access rights (0x1010 or 0x1410) - Data source: Windows Security Event 4656 or Sysmon Event ID 10
- Detection logic: Alert when non-system processes request memory read access to LSASS
Analytics Design Process
- Select a technique from ATT&CK that's high-risk for your environment
- Map to data sources (what logs capture this behavior?)
- Define detection logic (what pattern indicates malicious use vs legitimate?)
- Tune for false positives (exclude known-good tools and processes)
- Test with red team or adversary emulation
Detection Coverage Mapping
ATT&CK lets you visualize your detection gaps. By tracking which techniques you can and cannot detect, you identify blind spots and prioritize where to build new analytics. This turns defense from reactive guesswork into strategic, intelligence-driven engineering.
Key Takeaway: ATT&CK for detection transforms adversary knowledge into defensive rules—map techniques to observable artifacts, build analytics around those indicators, and systematically close coverage gaps in your security monitoring.