
What Is MITRE ATT&CK? The Complete Guide to the Enterprise Framework
What is MITRE ATT&CK? If you have ever read a breach report and wondered how security teams describe an attack so precisely — which technique the intruder used, in which order, and what should have stopped them — the answer is usually MITRE ATT&CK. It is the shared language modern defenders use to talk about adversary behaviour, and it has become one of the most important frameworks in cybersecurity.
In this guide, you will learn what MITRE ATT&CK is, how tactics, techniques, sub-techniques and procedures fit together, what the 14 Enterprise tactics cover, and how security teams use the framework for threat detection, red teaming and gap analysis, and how it compares with the Cyber Kill Chain.
What Is MITRE ATT&CK?
MITRE ATT&CK — short for Adversarial Tactics, Techniques, and Common Knowledge — is a free, openly available knowledge base of adversary behaviour, created and maintained by MITRE, the US not-for-profit research organisation. It was first released in 2013 and is updated several times a year as new techniques appear.
Instead of listing vulnerabilities or products, ATT&CK describes what attackers actually do once they target an organisation: how they get in, how they move around, how they steal credentials, and how they take data out. Each behaviour is given a name, a short ID such as T1566 for phishing, and a detailed page explaining how it works and how defenders can detect and stop it.
The framework is organised into three matrices, covering different environments:
- Enterprise — Windows, macOS, Linux, cloud, containers and network infrastructure. This is the matrix most teams use, and the one this guide focuses on.
- Mobile — Android and iOS devices, and the techniques attackers use against them.
- ICS — industrial control systems, such as power, water and manufacturing plants.
ATT&CK is not a security standard, a compliance checklist or a product. You cannot “pass” ATT&CK. It is a model for thinking and communicating about attacks — and it works best when teams map their own detections, controls and test results to it.
Tactics vs Techniques: What Is the Difference?
Three words cause most of the confusion around ATT&CK: tactic, technique and procedure. They describe the same attack at three levels of detail, and understanding the difference is the key to using the framework well.
| Concept | What it answers | Example |
|---|---|---|
| Tactic | What is the attacker trying to achieve? | Persistence — staying in the environment after a reboot |
| Technique | How does the attacker achieve it? | Scheduled Task/Job — creating a task that runs malware at logon |
| Sub-technique | How, exactly? | Scheduled Task — a specific type of scheduled job on Windows |
| Procedure | How did a specific group do it in the wild? | A named threat group using a scheduled task to launch a backdoor |
In short, the tactic is the goal, the technique is the method, the sub-technique is the precise method, and the procedure is the real-world example. One tactic can be achieved with many techniques — attackers can gain persistence through scheduled tasks, registry run keys, startup folders or malicious services — and one technique can serve more than one tactic.
Here is how the levels fit together in a real attack. An attacker sends a phishing email (Initial Access, technique Phishing). When the victim opens the attachment, it runs a script (Execution). The script creates a scheduled task (Persistence), dumps credentials from memory (Credential Access) and uses them to log in to another server (Lateral Movement). Each step is a different tactic — which is why ATT&CK is so useful for detection: spotting the technique can stop the attack at that step.
It also explains why social engineering attacks feature so heavily in ATT&CK. Phishing, pretexting and baiting are not just “user mistakes”; they are documented initial access and credential access techniques with known indicators that security teams can monitor, test and train against.
The 14 Enterprise Tactics, in Order
The Enterprise matrix is a grid. Its columns are the tactics, in the order an attack usually unfolds from left to right, and each column lists the techniques attackers use to achieve that tactic. The 14 tactics are:
| # | Tactic | What it means |
|---|---|---|
| 1 | Reconnaissance | Researching the target — people, systems and public information — before an attack begins. |
| 2 | Resource Development | Setting up the infrastructure and tools needed for an attack, such as domains, accounts and malware. |
| 3 | Initial Access | Getting a first foothold in the environment, for example through phishing or an exposed service. |
| 4 | Execution | Running malicious code on a victim system, such as a script, macro or binary. |
| 5 | Persistence | Keeping access after restarts, password changes or other interruptions. |
| 6 | Privilege Escalation | Gaining higher-level permissions than the attacker started with, often to administrator or SYSTEM. |
| 7 | Defense Evasion | Avoiding detection by security tools, logs and analysts. |
| 8 | Credential Access | Stealing usernames, passwords, tokens and hashes to impersonate legitimate users. |
| 9 | Discovery | Learning about the environment — what systems, users and data exist — after getting in. |
| 10 | Lateral Movement | Moving from one system to another inside the network. |
| 11 | Collection | Gathering the information the attacker wants, such as files, emails and screenshots. |
| 12 | Command and Control | Communicating with compromised systems to issue instructions and control them remotely. |
| 13 | Exfiltration | Taking collected data out of the organisation, often to an attacker-controlled server. |
| 14 | Impact | Disrupting, destroying or manipulating systems and data, for example with ransomware or wiping. |
To read the matrix, pick one tactic and ask two questions: “Which of these techniques could work against us?” and “Which of them would we detect?” A team that can answer both questions for every column has a realistic picture of its defences.
How Security Teams Use MITRE ATT&CK
ATT&CK is a working tool, not a poster. Here are the four main ways security teams use it every day.

1. Threat detection
Detection engineers map each detection rule, alert and log source to the technique it covers. If a rule fires when a scheduled task is created, it maps to Persistence. This mapping shows, at a glance, which techniques are covered, which are covered only partly, and which are blind spots. When a new technique appears in the news, the team can check within minutes whether they would see it — instead of discovering the gap during an incident.
2. Threat hunting and threat intelligence
Threat intelligence reports are often written in ATT&CK language: a report might say a group uses Valid Accounts for initial access and Web Protocols for command and control. Hunters turn those technique IDs into searches across logs, looking for the same behaviours in their own environment before an alert ever fires. It also helps teams prioritise: techniques used by groups targeting their industry move to the top of the list.
Detection also matters for insider threats. Many ATT&CK techniques, from Valid Accounts to data staging and exfiltration, describe actions a malicious insider can take with legitimate access, which is why insider threat programmes combine monitoring, least privilege and behavioural baselines with ATT&CK-based detection.
3. Red teaming and adversary emulation
Red teams use ATT&CK to plan realistic attack simulations. Instead of testing random exploits, they pick a threat group, copy the techniques that group is known to use, and run them against the organisation in a controlled exercise — a process called adversary emulation. The blue team then learns exactly which steps it detected, which it missed, and how long each detection took. This is closely related to penetration testing, but the goal is different: a penetration test usually asks “can you get in?”, while an ATT&CK-based red team exercise asks “which of these known techniques can you get away with, and where do we stop you?”
4. Gap analysis and prioritisation
Security leaders use ATT&CK coverage maps — often coloured like a heat map, with green for well-covered techniques and red for blind spots — to decide where to spend money and time. If the map shows strong coverage for execution techniques but nothing for credential access, the next investment is obvious. The map also makes risk concrete for executives: it shows precisely which attacker behaviours the team can and cannot see.
MITRE ATT&CK vs Cyber Kill Chain
The Cyber Kill Chain, published by Lockheed Martin in 2011, is the framework most people meet before ATT&CK. They describe the same problem from different angles, and most mature teams use both.
| Aspect | MITRE ATT&CK | Cyber Kill Chain |
|---|---|---|
| Origin | MITRE, first released 2013 | Lockheed Martin, 2011 |
| Structure | 14 tactics, 200+ techniques and sub-techniques | 7 linear stages |
| View of an attack | Non-linear: attackers can loop back, skip steps and use many techniques per tactic | Linear: each stage must happen in order, from reconnaissance to actions on objectives |
| Focus | Behaviour inside the network, including post-compromise activity | Stopping the attack before it reaches its target, mostly at the perimeter |
| Granularity | Very detailed, with real-world procedures and detection guidance | High-level, with one description per stage |
| Best for | Detection, hunting, red teaming, gap analysis and reporting | Explaining the attack lifecycle and justifying early, preventive controls |
| Weakness | Can feel overwhelming, and does not rank techniques by risk | Misses attacks that start inside the network and treats every attack as a straight line |
The Kill Chain’s most famous idea is that breaking any one link stops the attack. ATT&CK assumes the attacker will get in somewhere and asks a harder question: how many of their techniques can you detect and stop after that? Use the Kill Chain to explain the attack lifecycle, and ATT&CK to measure what happens once an attacker is inside.
How to Get Started with MITRE ATT&CK
You do not need a new tool or a big budget to start. A practical first month looks like this:
- Pick one threat that worries you — ransomware is a good choice — and find the techniques ransomware groups use on the ATT&CK website.
- Map your existing detections to those techniques, marking each one covered, partly covered or not covered.
- Close the biggest gap first, whether that is a missing log source, a detection rule or multi-factor authentication.
- Test your coverage with a small red team exercise, and record what was detected and what was missed.
Frequently Asked Questions
What does MITRE ATT&CK stand for?
ATT&CK stands for Adversarial Tactics, Techniques, and Common Knowledge. It is a knowledge base of adversary behaviour maintained by MITRE, based on real-world observations.
How many tactics and techniques are in MITRE ATT&CK Enterprise?
The Enterprise matrix has 14 tactics and more than 200 techniques, plus hundreds of sub-techniques. The exact number changes with each release, so check the current version on the ATT&CK website.
Is MITRE ATT&CK free to use?
Yes. MITRE ATT&CK is free and openly available. Anyone can read it, map their detections to it, and build tools on top of it.
What is the difference between a tactic and a technique in ATT&CK?
A tactic is the attacker’s goal — what they are trying to achieve, such as persistence or credential access. A technique is how they achieve it — for example, creating a scheduled task to stay persistent.
Is MITRE ATT&CK the same as the Cyber Kill Chain?
No. The Cyber Kill Chain describes an attack as seven linear stages and focuses on stopping it early. ATT&CK describes attacker behaviour in far more detail, is non-linear, and covers post-compromise activity inside the network.
Conclusion
MITRE ATT&CK turns the vague idea of “being attacked” into a concrete, testable list of behaviours. Learn the 14 tactics, map your detections to the matrix, and test the result with red teaming — remembering it does not rank techniques by risk, so use it alongside control frameworks such as NIST or CIS. Do that, and you will know, rather than guess, which attacks you can see and stop.



[…] MITRE ATT&CK […]
[…] last point matters for defenders. The MITRE ATT&CK framework catalogues attacker tactics and techniques, and enumeration maps closely to its discovery tactics, […]