Coverage
The Coverage tab in Intelligence is a map of the MITRE ATT&CK techniques and where your organization stands on each one: whether a watcher is watching for it, whether a recent hunt answered it, whether you at least hold the data that would show it, or whether you're blind to it. It also marks the techniques used by the threats that are relevant to you, so you can see which gaps matter most. Each technique opens a technique page with Hunt this and Watch for this.
Intelligence is in beta, and access is by request. It may not be enabled for your organization.
Open Coverage
Open Threat intel › Threats & indicators in the new navigation (or Intelligence in the classic menu), then the Coverage tab.
Coverage is measured per organization. If your scope is Personal, the tab shows Select an organization. Pick an organization in the Scope selector.
Read the map
Each column is an ATT&CK tactic, in attack order, such as Initial Access or Execution. Each cell in a column is one technique. Sub-techniques are rolled up into their parent technique.
Every technique has one of four states. The strongest one that applies wins:
| State | What it means |
|---|---|
| Watching | An enabled watcher carries this technique, so it is checked as data arrives. |
| Hunted | No watcher, but a hunt tagged with this technique reached a verdict in the last 90 days. Confirmed, Clear, False positive and Benign count; Inconclusive doesn't. |
| Can see | A connected source holds data that could show it, but no watcher or recent hunt is looking. Can see is not coverage: someone could look, but nothing is. |
| Blind | No connected source holds the data ATT&CK uses to detect this technique. |
Cells are shaded from darkest (Watching) to lightest (Blind); the legend explains each state when you hover it. A dashed outline marks a technique used by a threat relevant to you. A warning icon means the watchers for the technique are waiting for data you don't send yet, so they can't fire.
Hover over a cell, or focus it with the keyboard, to see why it has its state: the watchers on it, the last hunt and its verdict, or which data and which source could show it. Watchers in shadow and Library playbooks appear here as detail; they never make a technique Watching or Hunted on their own.
Click a cell to open the technique page.
A source that can't be queried right now (inactive, or failing run after run) doesn't count towards Can see. The note under the map names any such sources.
The map scrolls sideways on narrow screens. A tactic with many techniques shows the first ones and a +N more link.
Summary counts
Above the map:
| Count | Meaning |
|---|---|
| Techniques | All ATT&CK techniques in the map. |
| Watching | Techniques with an enabled watcher. When some of those watchers have no data yet, a line under the count says how many: they are on but can't fire. |
| Hunted (last 90 days) | Techniques answered by a recent hunt, with no watcher. |
| Can see, not looking | Techniques you hold data for, with nothing looking. |
| Blind | Techniques with no data that would show them. |
Under the counts, one line sums up the techniques that matter most to you, for example Of 48 techniques used by threats relevant to you: 12 watching · 5 hunted · 20 can see · 11 blind.
Narrow the map
| Control | What it does |
|---|---|
| Only techniques relevant to your threats | Shows only techniques that a relevant threat uses. |
| All techniques / Gaps only / Covered only | Shows every technique; only the gaps (Can see and Blind); or only those Watching or Hunted. |
| ATT&CK order / Best covered first | Orders cells in ATT&CK order, or from Watching down to Blind. |
Your choices are kept in the page address, so a link you share opens the same view.
Export coverage
Click Export above the map to download what the map shows (all techniques, or only the relevant ones if that switch is on):
| Format | What you get |
|---|---|
| CSV | A spreadsheet with one row per technique: its tactics, state, whether it's relevant to you and which threats use it, watchers on and in shadow, the last hunt and its verdict, and the data and sources that could show it. The first lines carry the summary sentence, for example Of 48 techniques used by threats relevant to you: 12 watching · 5 hunted · 20 can see · 11 blind. |
| ATT&CK Navigator layer | A JSON layer for MITRE's ATT&CK Navigator (Open Existing Layer › Upload from local). Each technique is coloured by its state (green Watching, blue Hunted, amber Can see, red Blind), with a legend. The summary sentence is the layer's description, and each technique's comment says why it has its state. |
Use either to report coverage to leadership or to compare it with other ATT&CK tools.
Technique pages
Each ATT&CK technique has its own page, opened from a cell on the map or from a technique's name on a threat or a threat report. Technique ids elsewhere open it too: on an insight, a Library watcher, an indicator, an entity in the graph, a detection record and a hunt's ATT&CK tags. A small icon next to the name still opens the technique on the MITRE ATT&CK site.
Techniques newer than Huntbase's ATT&CK version
Huntbase uses one ATT&CK Enterprise release for the map. A threat can use a technique that came out after it. Such a technique has no state: threats and reports count it separately, as 1 not in our ATT&CK version, and its name opens it on the MITRE ATT&CK site instead of a technique page.
The page shows the technique's state with a one-line reason, its ATT&CK description and tactics, and these sections:
| Section | What it shows |
|---|---|
| Who uses it | The threats relevant to you that use this technique, with their Seen, Vulnerable, Targeted and Gap badges. |
| Can we see it | Each kind of data ATT&CK detects the technique from, and which of your sources holds it, or that none does. |
| Watching | The watchers that carry the technique, with their state (On, Shadow, Off), and a link to Watcher health. |
| Hunts | Your hunts tagged with the technique, with their verdicts. Hunts answered in the last 90 days count towards Hunted. |
| Library playbooks | Hunt playbooks tagged with the technique. |
| MITRE D3FEND countermeasures | Defensive techniques MITRE D3FEND links to this one, for reference. Huntbase doesn't apply them for you. |
| Frameworks | The security controls that address this technique: NIST SP 800-53 controls from the Center for Threat-Informed Defense's ATT&CK mappings, and NIST CSF and CIS Controls through the technique's tactics. Hover a control for where the mapping comes from. Shown only when framework mappings are enabled for your organization and something maps. |
Hunt this
Hunt this is in the technique page's header and on every technique row of a threat or a threat report. It opens a dialog that first shows Where to look: the data ATT&CK detects the technique from, and which of your sources holds it (no connected source holds this when none does).
- If the Library has a playbook for the technique, Start from the playbook is the default.
- Otherwise, choose A new hunt with a note on where to look. The hunt starts with that note; ask Scout to plan the queries from it.
Click Start hunt. The hunt is tagged with the technique, so once it reaches a verdict the technique counts as Hunted.
Watch for this
Watch for this lists the Library's watchers tagged with the technique, each with its state. Enable starts one in shadow: it records to the digest until you turn it on. Right under it, the dialog then offers Turn on now, so it opens hunts from now and the technique counts as Watching, or Open watcher to watch it run first. If an automated rollout is checking it, only Open watcher is offered: the rollout turns it on. Customise makes your own copy and opens it. Open goes to the watcher.
When the Library has no watcher for the technique, the dialog says so and offers Write a watcher. The watcher editor opens with a starter rule tagged with the technique; replace its selection with what the technique looks like in your data. The editor shows what the rule would match before you save. See Watchers.
Where the data comes from
- Watching comes from your watchers' ATT&CK tags and whether each watcher is on, in shadow or off for your organization.
- Hunted comes from the verdicts of your hunts tagged with the technique. With sample data in scope, the sample's hunts count too.
- Can see comes from the data ATT&CK's detection guidance reads for each technique, matched against the kinds of data your working connections and lake hold.
- Relevant comes from the threats relevant to you on the Threats tab.
- The technique list comes from the ATT&CK data in Huntbase. If it hasn't been loaded yet, the tab says No ATT&CK techniques loaded yet.
Next steps
- Intelligence overview — the headline numbers and what needs attention
- Pulse — the ATT&CK coverage card
- Threats — the threats behind the dashed outlines, with Hunt this per technique
- Watchers — turn watchers on, off or into shadow
- Conclude a hunt — the verdicts that make a technique Hunted