What category of knowledge base this is
MITRE ATT&CK is a knowledge base of adversarial techniques based on real-world observations. The Get Started page states that ATT&CK focuses on how adversaries interact with systems during an operation. Tactics are why an adversary performs an action. Techniques are how adversaries achieve those tactical goals. ATT&CK is a language for behaviors and evidence. ATT&CK is not a score system that proves defensive coverage.
ATT&CK serves detection engineers and SOC learners who tag a case once evidence exists. It serves threat intelligence readers who need a shared behavior term. It serves AppSec readers who meet technique titles on vendor slides. ATT&CK is an industry knowledge base. ATT&CK is not a U.S. statute, and ATT&CK is not a certificate scheme.
A green matrix cell, a compliance badge, a finished CSF profile, and a product that "has ATT&CK" are four different objects.
Edition covered
The edition string is ATT&CK v19.2. The August 2026 updates page marks ATT&CK v19 as the current version of ATT&CK. On that page, the ATT&CK v19.2 release has a start date of 2026-08-06 (6 August 2026). The same page points the data at v19.2 on MITRE/CTI (release tag ATT&CK-v19.2). That page describes v19.2 as the first Agile release. That page also states that this release updates Groups and Software for Enterprise. The versions page lists ATT&CK v19.2 as the current version. If a newer version appears, this pin must change. The older claim is then UNKNOWN.
Major v19 has a start date of 2026-04-28 on the April 2026 updates page. That release split the former Defense Evasion tactic into Stealth and Defense Impairment. Older tactic counts are not current.
A behavior tag needs evidence
The habit starts with one real or synthetic case. Only techniques that evidence supports go on the map. The other techniques stay unmarked. The useful question is what telemetry can show a technique. The share of a matrix that looks green is not the question.
A SOC tags a case with techniques only after evidence exists. A colored matrix cell is not a finding. A coverage limit for a missing connector is a statement about missing evidence, not an ATT&CK coverage score.
The MITRE Get Started page lists three cautions. The first caution is against a checklist treated as done. The second caution is against an attempt at complete coverage. The third caution is against a green box because one way to perform a technique was seen. Adversaries have more than one way to perform most techniques. Not every tactic or technique applies to every organization.
A matrix cell is a behavior tag
A matrix cell is a tag for a behavior class. Green paint on the cell does not mean that the next bulk data export will be caught. One detection does not paint a technique green forever. The same Get Started page states that the matrix documents observed real-world behaviors. The page also states that adversaries can use behaviors that the matrix does not document yet.
ATT&CK Navigator can visualize defensive coverage, plans, and detected techniques. Paint is not evidence.
What ATT&CK is not
ATT&CK is not proof that attackers will skip an organization. ATT&CK is not a CSF 2.0 profile.
Rewrite the one-line claim
The claim "we are ATT&CK, covered, CSF, and product-badge secure" mixes four objects. Exact replacement: "We use ATT&CK v19.2 as a knowledge base to tag behaviors and to hunt for evidence." That use is different from CSF 2.0 outcomes and from a compliance attestation. That use is also different from product promotion that states a tool has ATT&CK.
A slide can show a green heatmap. The team then privately asks which behaviors have evidence. The team also asks which telemetry can show those behaviors. Those answers come before any treatment of paint as coverage.
A matrix cell is not coverage, not compliance, not a CSF profile, and not a product badge
| Phrase people use | Literacy correction |
|---|---|
| This matrix cell is green, so we have coverage | A cell is a behavior tag. Green paint is not proof that the relevant telemetry and analytic will catch the next case. Reference card: /reference/frameworks/mitre-attack-v19-2/. |
| We are ATT&CK compliant / certified | ATT&CK is not a compliance framework and not a certificate scheme. The comparison row lists certifiable as No. Six-map comparison: /reference/frameworks/compare/. |
| ATT&CK done means CSF profile done | CSF 2.0 is outcomes and function language. ATT&CK is adversary-behavior description. Related maps can exist. The two objects stay separate. Atlas card: /reference/frameworks/nist-csf-2-0/. Lesson: /learn/topics/outcomes-then-controls/. |
| The product has ATT&CK, so we are safe | A vendor badge that states that the product has ATT&CK is not evidence that local detections work on local telemetry. Reference card: /reference/frameworks/mitre-attack-v19-2/. |
| We detected one way to perform this technique, so the technique is covered | Most techniques have more than one procedure. One detection shows one observed way, not the technique as a whole. |
| We can invent a coverage percentage for the board | An invented coverage percentage is not evidence. The map holds only evidence-backed techniques. Gaps stay visible. SOC evidence habit: /learn/topics/identity-alert-triage/ and /learn/topics/investigate-respond-verify/. |
Common misconceptions
A green matrix cell means detection coverage, so the organization is safe.
Only local telemetry and a working analytic can show that the next case will be caught. One detection does not close a technique forever.
ATT&CK is a compliance framework, and completion of ATT&CK is a certificate.
ATT&CK is an adversary behavior knowledge base. The six-map comparison lists ATT&CK as not certifiable. ATT&CK is not a compliance framework.
ATT&CK done, a CSF profile done, and a product badge are the same seal.
Those three items are different objects. ATT&CK describes adversary behaviors. CSF 2.0 is outcomes language. A vendor badge is sales copy. A map between those objects does not finish the others.
Defense Evasion is still one ATT&CK tactic.
Major v19 (start date 2026-04-28) split the former Defense Evasion tactic into Stealth and Defense Impairment. Tactic counts from before v19 are not current.
A vendor homepage shield attests ATT&CK coverage.
A homepage shield is not evidence that local detections work on local telemetry.
CHECK THE CATEGORY
Which sentence matches ATT&CK literacy?
Glossary and nearby pages
- MITRE ATT&CK Reference card (framework summary)
- Compare the six maps (a row is not a heatmap)
- Triage a synthetic identity alert (S1, evidence habit)
- Investigate, respond, and verify recovery (S3)
- Agentic SOC: a reference architecture (S4)
- Outcomes first, then controls (F8a)
- NIST CSF 2.0 framework card (outcomes, not a behavior matrix)
- SOC analyst practice path
- Privacy is not a CIA checkbox
Use the agency page in the sources for the authoritative text.