Guide, read 12 Nov 2026

# CTEM keeps vulnerability management and adds scope, proof and owners

**The short answer:** Vulnerability management scans for CVEs and patches by severity. CTEM, in Gartner's 21 Aug 2023 description, runs five stages and proves which exposures an attacker can use. CISA's KEV catalog held 1,779 exploited CVEs on 10 Nov 2026, and BOD 26-04 (10 Jun 2026) now ranks federal fixes by exposure, exploitation and impact.

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

## Vulnerability management answers a narrower question

A vulnerability management program asks one question: which known flaws exist on the assets we scan, and have we patched them? NIST SP 800-40 Rev. 4 (April 2022) describes enterprise patch management as identifying, prioritizing, acquiring, installing and verifying the installation of patches, updates and upgrades. That is a sound loop, and every CTEM program still needs it.

The unit of work is the finding: one CVE on one host. The output is a queue sorted by severity, and the usual success measure is the share of that queue closed inside a deadline. NIST notes a divide between business or mission owners and security or technology management about the value of patching. Most programs feel that divide as a backlog that grows faster than it closes.

The narrowness is the point and the problem. A scanner sees what it is pointed at, rates each flaw on its own, and says nothing about whether an attacker could chain that flaw to anything the business cares about.

## CTEM starts from a business scope instead of a scanner range

Gartner's August 2023 article lays out five steps: scope, discover, prioritize, validate and mobilize. Scoping comes first, and Gartner says the attack surface it covers extends beyond the focus of typical vulnerability management programs. It names corporate social media accounts, online code repositories and integrated supply chain systems as examples.

Discovery then looks inside that scope for visible and hidden assets, vulnerabilities, misconfiguration and other risks. Gartner warns that confusing scoping with discovery is often the first failure when a CTEM program is built, and that the volume of assets and vulnerabilities found is not success in itself.

So the first practical difference is the starting list. Vulnerability management starts from an IP range or an agent count. CTEM starts from a service the business names, such as payments or the customer portal, and asks what an attacker could reach there. The [five stages guide](https://ctemvendors.com/guides/five-stages-of-ctem/) sets out what each stage hands to the next.

## Exposure covers more than a CVE

An exposure in CTEM can be a missing patch, but it can also be a cloud storage policy, an over-privileged service account, a SaaS tenant setting or an unmanaged repository. None of these carry a CVE number, and several never show up in a network scan.

Prioritization then weighs more than severity. Gartner lists urgency, security, availability of compensating controls, tolerance for residual attack surface and level of risk to the organization. Exploit likelihood models fit here as one input; FIRST describes EPSS as estimating the probability that a published CVE will be exploited in the wild in the next 30 days. The CTEM question is wider: does this exposure sit on a path to something in scope, and does a control already stop it?

## Validation is the step vulnerability management leaves out

Gartner's validation step asks three things: could an attacker actually exploit the exposure, what are the possible attack paths to the asset, and is the current response fast and substantial enough to protect the business. A vulnerability program rarely asks any of the three. It assumes a high score means high risk and a patch means the risk is gone.

Penetration testing sits nearby but plays a different role. The UK NCSC's penetration testing guidance (published 8 Aug 2017, reviewed 10 Jan 2022) frames a test as a way of gaining assurance in an organization's vulnerability assessment and management processes, compared to a financial audit, and says it should not be the primary method for finding vulnerabilities. CTEM keeps that audit role and adds continuous, narrower validation of the short list each cycle. The [validation guide](https://ctemvendors.com/guides/what-validation-proves/) covers what those tests can and cannot show.

## Federal patching rules moved toward risk factors in 2026

CISA's BOD 22-01, issued 3 Nov 2021, set fixed deadlines for KEV entries: two weeks for most, six months for CVEs assigned before 2021. On 10 Jun 2026 CISA issued BOD 26-04, which supersedes and revokes BOD 22-01 and BOD 19-02.

BOD 26-04 sets urgency from four factors: whether the asset is publicly exposed, KEV status, whether every exploitation step can be automated, and whether exploitation gives partial or total control of the asset. Agencies have 60 days to update processes and 180 days to meet the new remediation timelines. The catalog itself has grown: version 2026.11.10 lists 1,779 entries, 361 of them marked as known to be used in ransomware campaigns.

For a CTEM lead the signal is plain. US federal civilian agencies now rank patching work by exposure, exploitability and impact, which is the prioritization stage of a CTEM cycle written as federal policy.

## The two programs side by side

The table compares the two as they usually run in practice. Neither column is a product; both describe programs.

| Dimension | Vulnerability management | CTEM program |
|---|---|---|
| Starting list | Scanner ranges and agents | One business service and its systems |
| Unit of work | CVE on a host | Exposure on a path to an in-scope asset |
| Prioritization input | Severity score, sometimes exploit likelihood | Exposure, exploitation, controls in place, business impact |
| Proof | Assumed from the score | Tested in validation, with evidence |
| Output | Patch tickets | Fixes, mitigations and accepted risks, each with an owner |
| Closure | Scanner no longer sees the CVE | Re-test shows the path no longer works |
| Cadence | Scan cycle | First cycle about 90 days; later cycles 4 to 6 weeks per scope (site practice) |

## Keep the scanner and change the program around it

Nobody should retire a vulnerability scanner to start CTEM. Discovery depends on it. What changes is what happens to its output: findings are filtered by scope, joined with identity, cloud and SaaS data, ranked by the factors above, and only the short list moves to validation and then to owners.

Start with one scope, as the [first cycle guide](https://ctemvendors.com/guides/scoping-a-first-cycle/) describes, and keep the existing patch deadlines running in parallel. The NCSC's vulnerability management guidance (reviewed 1 May 2026) advises starting small, for example with vulnerabilities in critical systems only, then growing the process. The [program starter](https://ctemvendors.com/ctem-program-starter/) lists the first decisions, and the [stage pages](https://ctemvendors.com/stages/prioritization/) show which vendors on the [index](https://ctemvendors.com/index/) sell each stage.

## 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://csrc.nist.gov/pubs/sp/800/40/r4/final](https://csrc.nist.gov/pubs/sp/800/40/r4/final), read 12 Nov 2026
- [https://www.ncsc.gov.uk/guidance/penetration-testing](https://www.ncsc.gov.uk/guidance/penetration-testing), read 12 Nov 2026
- [https://www.ncsc.gov.uk/guidance/vulnerability-management](https://www.ncsc.gov.uk/guidance/vulnerability-management), read 12 Nov 2026
- [https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities](https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities), 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://www.first.org/epss/](https://www.first.org/epss/), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://ctemvendors.com/guides/ctem-vs-vulnerability-management/
