Guide, read 12 Nov 2026

# CTEM is a five-stage program that repeats, and no single product supplies it

**The short answer:** Continuous threat exposure management is Gartner's five-stage program: scoping, discovery, prioritization, validation, mobilization. Gartner introduced the term in 2022, by Zafran's account, published the five steps on 21 Aug 2023 and named CTEM a top strategic technology trend for 2024 on 16 Oct 2023, predicting adopters would be three times less likely to suffer a breach by 2026.

[Stage Coverage Map](https://ctemvendors.com/stage-coverage-map/) | [All guides](https://ctemvendors.com/guides/)

## The definition Gartner published

Gartner's article How to Manage Cybersecurity Threats, Not Episodes, dated 21 Aug 2023, describes continuous threat exposure management as a program that surfaces and actively prioritizes whatever most threatens the business. It argues that automating controls and deploying patches to keep up with attackers does not reduce future exposure, and that a CTEM program needs a five-step process: scope, discover, prioritize, validate and mobilize.

Gartner's analyst Jeremy D'Hoinne gives the reason in one sentence: organizations can't fix everything, nor can they be completely sure what vulnerability remediation they can safely postpone. CTEM is the discipline of deciding, each cycle, which exposures to fix now, which to mitigate and which to carry, with evidence for each decision.

A working definition for practitioners: CTEM is a repeating cycle that takes one business-defined scope, finds the exposures in it, ranks them by how an attacker would use them, proves the top ones by test, and gets the proven ones fixed by their owners.

## Where the term came from

The term dates from 2022. Gartner's public pages blocked automated reading on 12 Nov 2026, so the 2022 date here comes from secondary accounts: Zafran's CTEM page, for example, says the term was first introduced by Gartner in 2022 and describes CTEM as a set of processes and capabilities across five phases, not a product.

Two public Gartner pages, read through archived copies, fix the later milestones. The five-step article is dated 21 Aug 2023. On 16 Oct 2023 Gartner listed Continuous Threat Exposure Management among its Top 10 Strategic Technology Trends for 2024, next to AI trust, risk and security management, platform engineering and industry cloud platforms. That listing carried CTEM from security teams to CIO agendas.

## The prediction attached to the term

The 2023 article carries a dated prediction: by 2026, organizations that prioritize their security investments based on a continuous exposure management program will be three times less likely to suffer a breach. The year has arrived. A published Gartner measurement of that prediction: none found on 12 Nov 2026.

Treat the figure as an analyst forecast, not a program metric. A CTEM lead cannot measure a breach rate across their own company in one year. The measures that do hold up inside one program are in the [measurement guide](https://ctemvendors.com/guides/measuring-a-ctem-program/).

## Changes between 2023 and 2026

Three years on, the model is the same five stages. The context around it moved in ways that matter for anyone building a program now.

- Federal prioritization changed. CISA's BOD 26-04 (10 Jun 2026) revoked BOD 22-01 and ranks fixes by public exposure, KEV status, exploit automation and technical impact, close to the CTEM prioritization stage.
- The public threat catalog grew. The CISA KEV feed held 1,779 entries in version 2026.11.10, against 311 added in its first year, 2021.
- The technique catalog grew. MITRE ATT&CK v20.1, current since 13 Oct 2026, lists 227 Enterprise techniques and 479 sub-techniques; validation coverage is measured against that list.
- Regulators began asking for proof of control. DORA has applied since 17 Jan 2025 with threat-led penetration testing for some financial entities, and NIS2 transposition was due 17 Oct 2024. The [regulated companies guide](https://ctemvendors.com/guides/ctem-for-regulated-companies/) maps these.
- Vendors relabeled products. Scanners, validation tools and remediation platforms all now market CTEM. The site's [index](https://ctemvendors.com/index/) maps who sells which stage.

## A CTEM program is none of these

Most failed programs are one of the following under a new name.

- A product. No single category covers all five stages; see [CTEM tools by stage](https://ctemvendors.com/guides/ctem-tools-by-stage/).
- A bigger scan. Gartner says the volume of discovered assets and vulnerabilities is not success in itself.
- An annual penetration test. A yearly test is one validation input; CTEM validates the short list every cycle.
- A ticket queue. Sending every finding to IT is the failure CTEM was meant to fix; see the [mobilization guide](https://ctemvendors.com/guides/mobilization-without-a-ticket-flood/).
- A dashboard score. A composite risk number with no proven exposures behind it gives a board nothing to decide.
- Fully automated remediation. Gartner says programs cannot wholly rely on it, though it may suit obvious and unobtrusive issues.

## A first-year program in practice

Most programs that hold up in their first year look similar. They start with one scope, often an internet-facing service or a SaaS estate, as Gartner suggested in 2023. They run four to eight cycles across two or three scopes, keeping the existing patch process for everything outside scope. They add validation for the short list in the second or third cycle, once owners trust the inventory.

By the end of the year such a program can show three things: a scope statement per service, a count of proven exposures found and closed per cycle, and a register of accepted risks with named owners. It usually still runs its annual penetration test, now with a narrower brief drawn from the cycles. The [first cycle guide](https://ctemvendors.com/guides/scoping-a-first-cycle/) covers the first of those cycles in detail.

## The terms that sit around CTEM

Exposure management is the broader practice; CTEM is Gartner's program structure for it. Attack surface management and asset inventory feed discovery. Breach and attack simulation and automated penetration testing feed validation. Ticketing and workflow systems carry mobilization. The [glossary](https://ctemvendors.com/glossary/) defines each term as this site uses it.

The structure is what makes the term useful. Every stage has an input and an output, as set out in the [five stages guide](https://ctemvendors.com/guides/five-stages-of-ctem/), and a program can be audited stage by stage. If a team cannot show a scope statement, a short list with reasons, validation evidence and closed items with re-tests, it is running something else.

The word continuous is the part most often dropped. A program that runs the five stages once, writes a report and stops is an assessment. CTEM repeats the cycle on a fixed clock per scope, refreshes discovery data between runs and re-tests what it fixed, so the evidence stays current as the estate changes.

## Sources

- [https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes](https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes), read 12 Nov 2026
- [https://web.archive.org/web/20241230075302/https://www.gartner.com/en/articles/gartner-top-10-strategic-technology-trends-for-2024](https://web.archive.org/web/20241230075302/https://www.gartner.com/en/articles/gartner-top-10-strategic-technology-trends-for-2024), read 12 Nov 2026
- [https://www.zafran.io/ctem](https://www.zafran.io/ctem), read 12 Nov 2026
- [https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), read 12 Nov 2026
- [https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json), read 12 Nov 2026
- [https://attack.mitre.org/techniques/enterprise/](https://attack.mitre.org/techniques/enterprise/), read 12 Nov 2026
- [https://attack.mitre.org/resources/versions/](https://attack.mitre.org/resources/versions/), read 12 Nov 2026
- [https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/digital-operational-resilience-act-dora](https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/digital-operational-resilience-act-dora), read 12 Nov 2026
- [https://digital-strategy.ec.europa.eu/en/policies/nis2-directive](https://digital-strategy.ec.europa.eu/en/policies/nis2-directive), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://ctemvendors.com/guides/continuous-threat-exposure-management-defined/
