MITRE ATT&CK for executives means understanding and using MITRE ATT&CK well enough to ask the security team the right questions. MITRE ATT&CK is a knowledge base of the ways attackers have really operated, laid out as a table that is easy to read. Executives do not need the technical detail, but they should be able to read the table and know which questions produce useful answers.
What MITRE ATT&CK is
MITRE describes ATT&CK as a knowledge base of adversary techniques based on real-world observations. The attack.mitre.org site also lists attacker groups (groups), the software they use (software) and specific attack operations (campaigns).
ATT&CK is not a product you can buy, and it is not a pass-or-fail checklist. Our own view is to treat it as a common language that executives, the SOC team (the team that monitors and responds to security events), providers and vendors can use to describe attacker behavior in the same way.
How to read the matrix: tactics, techniques and sub-techniques
The ATT&CK matrix has three levels. A tactic is the attacker's goal at a given stage, a technique is the way the goal is reached, and a sub-technique is a more detailed version of that way. Tactics are the column headings, and techniques sit under the columns.
The matrix executives meet most often is Enterprise, which covers corporate networks, servers, user devices and cloud. According to the MITRE pages we read on 4 November 2026, the current version is ATT&CK v20.0, released on 13 October 2026. Enterprise has 15 tactics, 227 techniques and 479 sub-techniques.
The 15 tactics in plain language
The 15 Enterprise tactics below follow the order on the MITRE site. We group them into five sets to make them easier to remember. The grouping is our own view; MITRE does not divide them this way:
- Prepare (2 tactics): Reconnaissance is gathering information about the target, and Resource Development is setting up the tools and infrastructure for the attack
- Get in and stay (4 tactics): Initial Access is the first way in, Execution is running the attacker's code, Persistence is keeping a way back in, and Privilege Escalation is gaining higher permissions
- Hide or weaken the defenses (2 tactics): Stealth is hiding and blending in with normal activity, and Defense Impairment is making security controls and monitoring less effective
- Explore and spread inside the network (4 tactics): Credential Access is stealing credentials such as passwords and tokens, Discovery is learning what is in the network, Lateral Movement is moving on to other machines, and Collection is gathering the data the attacker wants
- Reach the goal (3 tactics): Command and Control is remotely controlling the machines taken over, Exfiltration is sending data out of the organization, and Impact is causing damage, such as encrypting files or stopping systems
Real attackers do not have to follow this order, and they may repeat or skip steps. Our own view is to use the order as a map that helps you think, not as a fixed procedure.
What happened to Defense Evasion
The v20 Enterprise matrix no longer has a Defense Evasion column. Two tactics sit in that position: Stealth (ID TA0005, 31 techniques) and Defense Impairment (ID TA0112, 18 techniques). According to the MITRE pages, Stealth covers techniques that help an attacker hide and blend in with normal activity without disabling security controls or interfering with monitoring. Defense Impairment covers techniques that degrade or disable security controls and monitoring. The Defense Impairment page says the tactic was created on 14 April 2026.
Older reports and vendor documents may still use the name Defense Evasion, so always ask which ATT&CK version a report refers to. Our own view is that the split makes it easier to ask a sharper question: if an attacker switches off or cripples our monitoring tools, will the team notice?
What executives can use ATT&CK for
The content of this section is our own view, not a MITRE requirement. Executives can use ATT&CK to ask the team the following:
- Which techniques matter most to us: ask the team to pick a few dozen key techniques, based on the attacker groups that target our industry or country and on incidents the organization has already faced, rather than reviewing all of them
- What do we have against each technique: ask whether we can detect it, prevent it, or have nothing yet, and ask the team for evidence, such as the alert rule in use
- Have we tested it: MITRE states that ATT&CK can be used to emulate specific threats and plan operations; for examples of attack-simulation tools, see the Network and Cyber Security Simulator guide
- Do providers' reports use the same language as ours: ask that incident reports, test results and vendor documents say which ATT&CK techniques and which version they refer to
MITRE offers a tool called ATT&CK Navigator for visualizing and planning which parts of the matrix the organization has controls for. On detection, MITRE says ATT&CK helps defenders develop analytics (rules and queries that look for signs of an activity) to detect the techniques attackers use. For an overview of using AI to reduce MTTD (mean time to detect) and MTTR (mean time to resolve), see Using AI in the SOC to Reduce MTTD and MTTR.
Common mistakes
- Treating a fully green map as proof of security: the map shows that a technique has a control, not how well it works; our own view is that it needs test evidence behind it
- Accepting "covers ATT&CK" without a follow-up question: a vendor may only mean that it can collect logs, not that it can detect or stop the attack; ask which techniques are covered and how
- Using an old report without checking its version: tactic names and structure can change, as Defense Evasion was replaced by two tactics in v20
- Starting from all 227 techniques: the team drowns in a long list; our own view is to start from a short list tied to the organization's risks
- Treating ATT&CK as the whole security program: ATT&CK describes attacker behavior, and you still need risk assessment, vulnerability management and an incident response plan alongside it
Weak questions
- What % of the matrix do we coversays nothing about how well it works
- Does the vendor support ATT&CKa yes does not say how it is covered
- Can we cover all 227 techniquestoo long a list, the team drowns
Strong questions
- Which techniques matter most to uschosen from relevant groups and past incidents
- What do we have for each key onedetect, prevent or nothing, with evidence
- Did the system alert when testedsimulate one technique and observe
Start today
- Open the Enterprise matrix once: read the names of the 15 tactics, then ask the team which side the organization is most and least confident about
- Ask for a list of 10-20 key techniques: have the team propose them with the reason each one matters to us
- Ask for the status of each one: detect, prevent or nothing yet, with evidence
- Schedule a test of at least one: pick one key technique and simulate the attack to see whether the systems raise an alert; see Vulnerability Assessment, Pen Test and Red Team: What Is the Difference? to choose the form of test
To see where the organization stands overall, try the self-assessment.
Scope and accuracy
The ATT&CK information in this article comes from attack.mitre.org, which we read on 4 November 2026. MITRE updates the content regularly, so the numbers and the tactic list may change in later versions; check MITRE's versions page before relying on them. We have not confirmed whether Defense Evasion was split in v19 or v20, so we write only what the v20 matrix shows. The grouping of the 15 tactics and the advice for executives are our own view.
References and further reading
- ATT&CK Enterprise Matrix: the matrix of 15 tactics and the technique count in each column
- Enterprise Tactics: the names and IDs of all 15 tactics
- Stealth (TA0005): the description of the Stealth tactic and its technique count
- Defense Impairment (TA0112): the description of the Defense Impairment tactic and its creation date
- ATT&CK Versions: the current version and its release date
- ATT&CK v20 release notes (October 2026): counts of techniques, sub-techniques and groups, and the v20 changes
- ATT&CK: Adversary Emulation and Red Teaming: using ATT&CK to emulate threats and test
- ATT&CK: Detections and Analytics: using ATT&CK to build detections
- ATT&CK Navigator: a tool for visualizing and planning coverage