Core Concepts

What is the MITRE ATT&CK Framework?

The MITRE ATT&CK Framework is a globally used knowledge base of adversary behaviors. In simple terms, ATT&CK catalogs who attackers are and what they do at each stage of an attack.

MITRE describes ATT&CK as "a globally-accessible knowledge base of adversary tactics and techniques based on real-world observations." It's essentially the encyclopedia of TTPs drawn from public cyber attacks.

The ATT&CK Matrix

ATT&CK organizes tactics and techniques into matrices. The Enterprise Matrix (for corporate IT) includes columns for tactics like Reconnaissance, Initial Access, Execution, Persistence, etc. Under each tactic are specific techniques (with sub-techniques) that attackers use.

TacticDescriptionExample Technique
ReconnaissanceGathering info to plan an attackActive Scanning
Initial AccessGaining initial footholdSpearphishing Attachment
ExecutionRunning malicious codePowerShell Execution
PersistenceMaintaining accessRegistry Run Keys
Privilege EscalationGaining higher permissionsCredential Dumping
Defense EvasionHiding activitiesObfuscated Files
Credential AccessStealing credentialsBrute Force
DiscoveryExploring the environmentNetwork Discovery
Lateral MovementMoving through networkWindows Admin Shares
CollectionGathering sensitive dataScreen Capture
Command & ControlCommunicating with C2DNS Tunneling
ExfiltrationRemoving dataEncrypted Transfer
ImpactDisrupting operationsData Destruction

Why It Matters Today

ATT&CK is the common language for threat intelligence. It helps you measure coverage: you can check which ATT&CK techniques your security controls can detect, and where you have gaps. In 2026, ATT&CK's community contributions (over 200 contributors) mean it stays current with cloud-native attacks and IoT exploits.

Practical Uses

Detection Engineering

Use ATT&CK to design SIEM/SOAR rules that cover critical techniques. For example, log patterns for "Privilege Escalation: SeDebugPrivilege" can map to ATT&CK.

Reporting

Classify incidents by ATT&CK tactics when briefing management. Saying "we detected an Execution and Persistence technique" is clearer than raw technical details.

Threat Modeling

When evaluating new software or architecture, ask "which ATT&CK techniques apply here, and do we have defenses?"

Pitfalls to Avoid

  • Treating ATT&CK as a rigid checklist. It's a living document – not all tactics apply to every organization
  • Incomplete mappings: if you only search for exact technique names, you might miss variations
  • Always combine ATT&CK usage with actual context

Next Steps

In our TTPs article we discuss how tactics, techniques, and procedures relate to ATT&CK. Also see Indicators of Compromise – knowing ATT&CK helps you tag indicators correctly.