Methodology, read 12 Nov 2026

# How each cell of the Stage Coverage Map was decided

**The short answer:** Each of the 90 cells was decided from the vendor's product pages, documentation and third-party sources read on 12 Nov 2026. 80 cells are native, 5 via integration and 5 none found. The map records evidence; the weighted scores decide every ranking.

[Open the map](https://ctemvendors.com/stage-coverage-map/) | [The scoring method](https://ctemvendors.com/method/)

## The three marks

- **Native**: the vendor's own product does the stage's work, documented on a public page of the vendor or confirmed by a third party.
- **Via integration**: the vendor documents the stage only through another tool, a partner or data taken in from other products.
- **None found**: nothing the stage's criterion counts was found on the pages read on 12 Nov 2026; for validation, a cell where only analysis (such as attack path modeling) was found is marked none found and the note says what analysis exists. It is a statement about the evidence, not a finding that the vendor lacks the capability.

## What counts for each stage

- **Scoping**: Business context, views by unit or crown-jewel asset, reporting a board can read.
- **Discovery**: Assets and exposures across cloud, on-premises, identity and the external surface, found by the product or taken in from other tools.
- **Prioritization**: Ranking that uses validation results, threat intelligence and business context, not severity scores alone.
- **Validation**: Proof of which exposures can be exploited in this environment: attack simulation, automated penetration testing or red teaming, and testing of the controls in place.
- **Mobilization**: Remediation guidance, mitigation rules for the controls already deployed, ticketing and automation integrations, tracking to closure.

## How the cells were filled

One research pass per vendor read its home page, the CTEM or exposure management product pages, documentation, pricing, integrations, release notes and published research, plus at least two third-party sources. Each cell cites the fact it rests on. A reviewer with fresh context checked the cells against the facts alongside the scores. Cells change when a sourced fact changes, and the change is logged on the [corrections page](https://ctemvendors.com/corrections/).

## Limits

- A native mark says the capability exists, not how deep it goes; depth is what the seven scores measure.
- Vendors that document a stage only for some environments are marked by what they document, and the note says which.
- The map is refreshed monthly; the read date on each cell is the date the evidence was read.

## Cite and download

Cite this: CTEM Vendors, CTEM Stage Coverage Map, read 12 Nov 2026, https://ctemvendors.com/stage-coverage-map/. The dataset is published under CC BY 4.0 as [CSV](https://ctemvendors.com/datasets/stage-coverage-map.csv) and [JSON](https://ctemvendors.com/datasets/stage-coverage-map.json).

## Sources

- [https://web.archive.org/web/20260110234446/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes](https://web.archive.org/web/20260110234446/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes), read 12 Nov 2026
- [https://creativecommons.org/licenses/by/4.0/](https://creativecommons.org/licenses/by/4.0/), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://ctemvendors.com/stage-coverage-map/methodology/
