Skip to content
CTEM Vendors

Home / Guides / CTEM tools by stage: which kinds of product serve which stage

Guide, read 12 Nov 2026

No single product category covers all five CTEM stages

Stage Coverage MapAll guides

Five stages, three kinds of product

Vendors market CTEM as a product. Gartner's 21 Aug 2023 article describes it as a program with five steps, and the steps need different capabilities: business judgment for scoping, data collection for discovery, analytics for prioritization, testing for validation, and workflow for mobilization. Products cluster into three kinds that each serve one or two stages well.

StageKind of product that serves itWhat the product suppliesWhat people still supply
ScopingNone as a primary function; asset and business-context features in exposure platformsAsset lists, tags, business service mappingThe choice of scope, the owner, the bad outcome
DiscoveryExposure assessment platforms, scanners, cloud and identity posture toolsAssets, vulnerabilities, misconfigurations, identity dataAccess to data sources, visibility gap review
PrioritizationExposure assessment platformsRanking by exploitation, exposure, controls, asset valueBusiness impact, acceptance of the ranking
ValidationAdversarial exposure validation: simulation, automated penetration testingTest runs, attack paths, control results by techniqueTest permission, human-led testing, review of results
MobilizationTicketing and workflow systems, remediation orchestrationRouting, deduplication, SLA tracking, re-test triggersApproval, the change itself, risk acceptance

Exposure assessment platforms cover discovery and prioritization

An exposure assessment platform collects findings from scanners, cloud accounts, identity providers and SaaS tenants, joins them to assets, and ranks them. Its value is in the join and the rank. Good ones take in public threat context, such as the CISA KEV catalog (1,779 entries in version 2026.11.10), and map exposures to attack paths.

Their limit is proof. A platform can estimate that an exposure sits on a path to a critical asset; it cannot show that the path works against the controls in place today without running a test. Some platforms add path analysis or partner with validation tools, and the site's index records which do, from each vendor's own documentation.

When reading a platform's claims, ask three things: which data sources it ingests natively, whether it records an owner and business service per asset, and whether its ranking can take a validation result as input. A platform that cannot take proof back in will keep ranking proven and unproven items the same way.

Adversarial exposure validation covers the validation stage

Validation products run tests: safe simulations of attacker techniques against controls, and automated penetration tests that chain weaknesses toward a goal. They answer Gartner's validation questions: could an attacker exploit this, by what paths, and does the response work. Results are usually reported per MITRE ATT&CK technique; ATT&CK v20.1, current since 13 Oct 2026, lists 227 Enterprise techniques and 479 sub-techniques.

Their limits are coverage and input. A validation tool tests what is in its library and what it is pointed at. Without a scope and a short list from the earlier stages, it tests whatever is easy to reach. Human-led testing still has a place: the ECB's TIBER-EU framework, in its 2025 edition, sets at least 12 weeks of active red team testing on live production systems for a threat-led test, which no automated product replaces. The validation guide covers the limits in detail.

Ticketing and workflow systems carry mobilization

Mobilization runs on the systems IT already uses for change: service management, issue trackers, pipeline tooling. CTEM products integrate with them rather than replace them. The CTEM-specific work is upstream of the ticket: deduplicating findings into fixes, routing to the owner named on the asset record, setting the SLA tier, and triggering a re-test when the ticket closes.

Gartner says programs cannot wholly rely on automated remediation, though it may make sense for some obvious and unobtrusive issues, and that cross-team approval workflows should be documented. NIST SP 800-40 Rev. 4 (April 2022) includes verifying installation in patch management. A ticketing integration that closes items without a re-test does not meet either standard. The mobilization guide covers the practice.

Three reasons no single category covers all five

The same three reasons recur across the products this site has read.

Buying for a program, not a category

Start from the program's gaps, not from a product category. If the team cannot produce a ranked short list, the gap is in prioritization. If it has a short list but owners dispute it, the gap is in validation. If proven items sit open, the gap is in mobilization and ownership, and a new tool may not help at all; see the roles guide.

The UK NCSC's vulnerability management guidance (reviewed 1 May 2026) advises starting small and growing the process. The same applies to tooling: cover one scope end to end with what exists, then add products where the cycle stalls.

Count the integration work as part of any purchase. Each new product needs data in from discovery sources and results out to ticketing and to the measures. A tool that serves its stage well but cannot pass its output to the next stage adds a manual handoff, and manual handoffs are where cycles slow down.

Using the index and the Stage Coverage Map

The site's index maps each vendor to the CTEM stages it sells, with sources, and the Stage Coverage Map shows coverage for all vendors on one page. The stage pages list vendors per stage, the situations pages group them by buyer need, and the method explains how coverage is judged. A vendor that claims all five stages is recorded against what its documentation shows for each one.

Sources

  1. https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes, read 12 Nov 2026
  2. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json, read 12 Nov 2026
  3. https://attack.mitre.org/techniques/enterprise/, read 12 Nov 2026
  4. https://attack.mitre.org/resources/versions/, read 12 Nov 2026
  5. https://www.ecb.europa.eu/pub/pdf/other/ecb.tiber_eu_framework_2025~b32eff9a10.en.pdf, read 12 Nov 2026
  6. https://csrc.nist.gov/pubs/sp/800/40/r4/final, read 12 Nov 2026
  7. https://www.ncsc.gov.uk/guidance/vulnerability-management, read 12 Nov 2026

Last reviewed 12 Nov 2026.