Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the ATT&CK Navigator?

The ATT&CK Navigator is MITRE’s free web tool for annotating the ATT&CK matrix. Teams use layers to record detection coverage, threat actor techniques, and the gap between the two.

Illustration for the cybersecurity term ATT&CK Navigator
Home / Blog / Cybersecurity Terms / What Is the ATT&CK Navigator?
17 November 2026

What Is the ATT&CK Navigator?

What Is the ATT&CK Navigator?

The ATT&CK Navigator is a browser-based tool published by MITRE for annotating the ATT&CK matrix. It renders techniques as a grid, lets you assign each one a score, a colour, a comment, and metadata, and saves the result as a layer file in JSON. It can be used at mitre-attack.github.io/attack-navigator or self-hosted, which most organisations prefer once the layers contain information about their own gaps.

Layers Are the Whole Idea

A layer is simply a set of annotations over the matrix. Its power comes from keeping each one single-purpose and then combining them. A typical set looks like this:

Navigator can then combine layers using an expression such as a - b, producing a new layer that shows where a threat group’s techniques exceed your coverage. That difference layer is the deliverable worth taking to a steering group; the individual layers are working material.

Building a Coverage Layer That Means Something

The temptation is to mark a technique green because a rule exists with a matching name. Resist it, because a rule that has never fired in testing and a rule validated last week are not the same control. A defensible scoring scheme distinguishes at least three states: no detection, detection written but untested, and detection tested against a real execution of the technique within a defined period.

It is also worth separating detection from prevention. A technique blocked by application control is in a different position from one that is merely visible, and conflating them hides the cases where you would see nothing if the preventive control were bypassed. Many teams maintain two layers and present them side by side.

Be careful with sub-techniques. Scoring at the parent level overstates coverage dramatically: detecting T1003.001, LSASS memory dumping, says nothing about T1003.003, NTDS extraction from a domain controller. Score the sub-techniques you have actually addressed and let the parent inherit the lowest value.

The Colouring-In Trap

A fully green matrix is almost always wrong. ATT&CK v17 describes over 200 techniques and more than 400 sub-techniques for enterprise alone, and no organisation detects all of them reliably. When a coverage layer looks too good, the cause is usually one of three things: scoring from rule names rather than from tests, counting a generic catch-all rule across dozens of techniques, or marking a technique covered because a product claims to cover it.

The related discipline of DeTT&CT, an open project that scores data source quality before coverage, is a useful corrective. It forces the question of whether your logs have the right fields, retention, and completeness to support a detection at all, which is where most coverage claims quietly fail.

Using It Beyond the SOC

Navigator layers travel well. A purple team exercise can produce a before-and-after layer in a morning. A detection coverage map built in Navigator gives a detection engineering backlog an order of priority that is tied to threat rather than to whichever rule was easiest to write. And for UK organisations assessed against the NCSC Cyber Assessment Framework, a coverage layer is practical evidence for principle C1, which asks whether monitoring is driven by an understanding of the threats that matter to the organisation.

Export layers as JSON and keep them in version control alongside your rules, so coverage changes are reviewable like any other change. Our red team services deliver results as Navigator layers for exactly that reason.

FAQ – Frequently Asked Questions

Is the ATT&CK Navigator Free?

Yes. It is an open-source project published by MITRE under the Apache 2.0 licence and can be used in a browser at the hosted instance or deployed on your own infrastructure. Most organisations self-host or run it locally, because layer files describing where your detection is weak are sensitive documents that should not be saved into a public instance.

How Should Coverage Be Scored?

Use at least three levels so that untested rules are distinguishable from validated ones. A common scheme is 0 for no detection, 1 for a rule that exists but has not been exercised, 2 for a rule confirmed by a recent test, and a separate colour for techniques prevented outright. Score at sub-technique level and let the parent take the lowest score of its children.

Can Navigator Compare Our Coverage Against a Specific Threat Group?

Yes, and it is the tool’s most useful function. Export the group’s technique layer from the ATT&CK website, load it alongside your coverage layer, and use the layer combination expression to subtract one from the other. The result highlights techniques the group is known to use that you cannot currently detect, which is a far better prioritisation input than the matrix as a whole.

Does a Green Matrix Mean We Are Secure?

No. Coverage layers measure whether a detection exists, not whether it works under real conditions, survives tuning, or would be noticed in a busy queue. Treat the layer as a map of intent and validate it with execution testing. A matrix that is mostly amber but backed by test evidence is far more trustworthy than one that is entirely green and backed by rule names.

Related Terms

You May Be Interested In These