Home / FAQ
FAQ, read 12 Nov 2026
30 answers on running a CTEM program and choosing vendors by stage
The answers
What is continuous threat exposure management (CTEM)?
CTEM is a program, not a product: a repeating cycle that finds the exposures most likely to be used against the business and gets them fixed. Gartner described it in an article of 21 August 2023 as a five-step process and predicted that by 2026 organizations prioritizing security investment through such a program would be 3x less likely to suffer a breach. The stages are covered on the stage pages.
What are the five stages of a CTEM program?
Gartner names five: scoping, discovery, prioritization, validation and mobilization. Scoping sets which part of the business a cycle covers; discovery finds assets and exposures in it; prioritization picks those most likely to be exploited; validation confirms an attacker could use them here; mobilization gets them fixed through the teams that own them. Each has a page, starting with scoping and ending with mobilization.
How does CTEM differ from vulnerability management?
Vulnerability management finds and patches software flaws. CTEM starts from business scope, counts misconfigurations, identities, code repositories and social media accounts as exposures, and adds validation: proof that an attacker could use the exposure here. Gartner says the goal is not to fix every issue, and that the volume of discovered assets and vulnerabilities is not success in itself. Scanners stay in place; CTEM decides which of their findings matter.
How long does a CTEM cycle take?
Gartner gives no fixed length; the word is continuous. In practice a first cycle on a narrow scope runs about 90 days, which is how the CTEM Program Starter is laid out: scoping from day 1, mobilization through day 75, then a review to day 90. Later cycles get shorter as discovery and testing run on a schedule. CISA BOD 23-01 sets asset discovery every 7 days for federal agencies.
Who should own a CTEM program?
One named lead, usually the head of vulnerability or exposure management, reporting to the CISO, with a business sponsor who signs the risk tolerance. Gartner stresses that mobilization depends on cross-team approval workflows, so each remediation team needs a named contact. NYDFS 500.4 makes the CISO report in writing at least annually to the senior governing body, which gives the program a natural owner in regulated firms.
How do you scope the first CTEM cycle?
Pick one slice a single team can finish in 90 days. Gartner suggests two pilots: the external attack surface, a narrow scope with many tools, or SaaS security posture. Name the business services in scope, their owners and the critical assets behind them, following NIST CSF 2.0 ID.AM-05 on prioritizing assets by criticality and impact. Write the risk tolerance down before discovery starts. See the scoping stage.
What does "exposure" mean in CTEM?
An exposure is any way into an asset that matters: a software vulnerability, a misconfiguration, an excess identity privilege or a weak control. Gartner's scope includes less tangible items such as corporate social media accounts, online code repositories and integrated supply chain systems. The term is wider than a CVE. An exposure that cannot be reached or used in this environment still exists, but it sits lower on the list.
What does the discovery stage add to the scanners already in place?
Discovery joins what the scanners report to what they miss: assets absent from the CMDB, cloud accounts nobody registered, identity exposures and misconfigurations. Gartner warns that confusing scoping with discovery is often the first failure in building a CTEM program. NIST CSF 2.0 ID.RA-01 asks that vulnerabilities be identified, validated and recorded, and PCI DSS 11.3.1.2 asks that systems unable to take authenticated scans be documented.
What does the validation stage prove?
Validation proves three things Gartner lists: that an attacker could actually exploit the exposure, which attack paths lead to the asset, and whether the response in place is fast and strong enough. Evidence comes from controlled tests in the environment, such as attack simulation, automated penetration testing and control testing, planned in line with NIST SP 800-115. An exposure proven not exploitable here can move down the list with that evidence attached.
How often should exposures be re-validated?
After every fix, and on a schedule. PCI DSS 4.0 requirement 11.4.4 asks that penetration testing be repeated to verify corrections, and 11.4.2 and 11.4.3 ask for internal and external tests at least once every 12 months and after significant changes. NYDFS 500.5 asks for scans promptly after material system changes. Most programs re-test the priority list each cycle and re-test each item when its ticket closes.
What does mobilization mean in practice?
Mobilization means getting the validated exposures fixed by the teams that own the systems. Gartner warns against relying wholly on automated remediation and asks programs to document cross-team approval workflows. In practice that is one ticket per validated item in ServiceNow or Jira, a mitigation for the deployed control where a patch cannot ship, a recorded risk acceptance where the business declines to fix, and closure only after a re-test. See mobilization.
What should a CTEM program measure?
Measure outcomes on validated exposures, not raw finding counts, which Gartner says are not success in themselves. Four measures work in most programs: validated exposures on critical assets, median days from validation to verified fix, the share of priority items closed by a passing re-test, and the control detection rate from validation tests. Record a baseline on day 1. NIST CSF 2.0 ID.IM-02 expects improvements to come from security tests and exercises.
How should a CTEM program report to the board?
Report by business service: what was in scope, which exposures were proven exploitable, what was fixed, and what residual risk the business accepted and who signed it. Keep CVE counts out of the summary. NYDFS 500.4(b) lists what the annual CISO report covers, including material risks and plans for remediating material inadequacies. SEC rules adopted on 26 July 2023 ask public companies to describe board oversight of cybersecurity risk in the annual Form 10-K.
How does CTEM relate to DORA threat-led penetration testing?
DORA, Regulation (EU) 2022/2554, has applied since 17 January 2025. Article 26 requires in-scope financial entities to carry out threat-led penetration testing (TLPT) at least every 3 years on live production systems supporting critical or important functions. A CTEM program does not replace TLPT, but its scope of critical functions and its validation records feed the TLPT scope. The ECB published the 2025 edition of the TIBER-EU framework to align with the DORA TLPT standards.
How does CTEM map to PCI DSS 4.0 requirement 11?
Requirement 11 covers testing. 11.3.1 and 11.3.2 ask for internal and external vulnerability scans at least once every three months, 11.3.1.2 asks for authenticated internal scans, and 11.4 asks for internal and external penetration testing at least once every 12 months, with exploitable findings corrected and re-tested. The 51 future-dated requirements of v4.x took effect on 31 March 2025. CTEM validation and re-test records support that evidence for the cardholder data environment.
How does CTEM support NYDFS Part 500 compliance?
Section 500.5 of 23 NYCRR 500, as amended effective 1 November 2023, asks covered entities for penetration testing from inside and outside system boundaries at least annually, automated scans with manual review of systems the scans miss, and timely remediation prioritized by risk. A CTEM cycle produces each of those records. Section 500.4 adds the annual written CISO report to the senior governing body, which the cycle review can feed.
How does CTEM relate to MITRE ATT&CK?
ATT&CK is the shared vocabulary for validation: each test maps to techniques, and results read as coverage by tactic. ATT&CK v20.1, current since 13 October 2026, lists 15 Enterprise tactics, from Reconnaissance to Impact. MITRE has released two versions a year since 2022, so check which version a vendor's content uses. The Center for Threat-Informed Defense publishes a Top ATT&CK Techniques method for choosing what to test first.
How should the CISA KEV catalog be used in a CTEM program?
The Known Exploited Vulnerabilities catalog is CISA's list of vulnerabilities exploited in the wild; it showed 1,779 entries in catalog version 2026.11.10 (10 November 2026). Use it as one input to prioritization: a KEV entry on a critical, reachable asset goes near the top. KEV says a flaw has been exploited somewhere, not that it is exploitable in your environment, so validation still decides the final order. See prioritization.
What changed when CISA replaced BOD 22-01?
CISA issued BOD 26-04, Prioritizing Security Updates Based on Risk, on 10 June 2026, and BOD 22-01 of 3 November 2021 now shows as revoked and superseded. BOD 22-01 had set two weeks for KEV entries with a CVE ID assigned from 2021 on, and six months for older ones. Under BOD 26-04, federal agencies still watch the KEV catalog, the clock starts when CISA adds an entry or the agency finds it, and taking a system off the internet counts as a mitigation.
What role do attack paths play in a CTEM program?
An attack path shows how an attacker could move from an exposure to a critical asset. Gartner's validation step asks programs to analyze all potential attack pathways to the asset. Paths change priority: a medium flaw on a path to a payment system can outrank a critical flaw on an isolated test server. Ask whether a vendor's path is proven by a test or inferred from configuration data; the method scores those differently.
How do compensating controls change exposure priority?
Gartner lists the availability of compensating controls as a prioritization factor, beside urgency, tolerance for residual attack surface and risk to the organization. A flaw behind a control that a test showed blocks the technique can wait; the same flaw where the control failed cannot. Record the control by name and the test that proved it. BOD 26-04 also accepts mitigation, such as removing a system from the internet, within its timelines.
How can a CTEM program keep ticket volumes manageable?
Open tickets only for validated exposures on assets in scope, one ticket per fix rather than one per finding, and group findings that share a patch or a configuration change. Gartner says the goal is not to fix every issue. NIST SP 800-40 Rev. 4 frames patching as preventive maintenance and points to a divide between business owners and security teams over its value, which smaller, evidenced ticket queues help close.
How should a CTEM budget be built?
Build it by stage, not by product. List what the current scanners, CMDB and ticketing system already cover, then fund the gaps the first cycle exposes, which is usually validation and mobilization. Price a pilot on the narrow scope before an enterprise license. NYDFS 500.4(d) asks the senior governing body to confirm that management has allocated sufficient resources to the cybersecurity program, which gives the budget a formal sign-off point.
What staffing does a CTEM program need?
A first cycle runs with a program lead, an analyst who owns discovery and prioritization, a tester or validation engineer, and a named contact in each remediation team. Gartner's mobilization step depends on those cross-team contacts more than on headcount in security. NIST CSF 2.0 GV.RR outcomes ask that roles and responsibilities be established and that adequate resources be allocated, so write each role into the scope statement.
How should a buyer choose vendors for each CTEM stage?
Start from the stages the first cycle shows are weak, then compare vendors on those stages only. The Stage Coverage Map shows, for each vendor, whether each stage is covered natively, only through an integration, or none found on 12 Nov 2026. The method explains the evidence behind each mark. Put the stage questions from the CTEM Program Starter to every shortlisted vendor in writing.
Does one vendor cover all five CTEM stages?
The Stage Coverage Map answers this, vendor by vendor, with native, integration or none found marked for each stage, each mark sourced and dated 12 Nov 2026. Gartner describes CTEM as a program across people and processes, so read a vendor's all-five claim as the vendor's until a second source confirms it.
How does ctemvendors.com score vendors?
Seven criteria, with weights fixed on 12 November 2026 before any score existed: Validation 25, Prioritization on evidence 15, Discovery breadth 15, Mobilization 15, Works with the stack in place 10, Scoping and reporting 10, Transparency and proof 10. Each is scored 0 to 10 from sourced facts against written anchors, and the total is the weighted mean. Details are on the method page.
Why does a vendor's own claim score at most 7 of 10?
A claim found only on the vendor's site, documentation or press releases caps that criterion at 7 of 10 until a second source not controlled by the vendor confirms it, such as a regulator filing, an analyst report or a public test result. Where nothing is found, the criterion scores 0 and the page says none found on 12 Nov 2026. The rules are on the method page.
How does CTEM relate to NIST CSF 2.0?
NIST CSF 2.0, published 26 February 2024, organizes outcomes under six functions: Govern, Identify, Protect, Detect, Respond and Recover. CTEM work maps mostly to Govern and Identify: GV.OC for business context in scoping, ID.AM for assets, ID.RA-01 to ID.RA-06 for finding, validating and prioritizing vulnerabilities and choosing risk responses, and ID.IM-02 for improvements from security tests. CSF gives the outcomes; CTEM is one way to run them.
What should a first 90-day CTEM cycle produce?
By day 90: a signed scope and risk tolerance, a reconciled asset and exposure list, a written priority list with reasons, validation results per item and per control, tickets closed on a passing re-test, a risk acceptance register, a board report and the scope for cycle two. The CTEM Program Starter lists the steps, deliverables and vendor questions for each stage.
Sources
- https://web.archive.org/web/20251230022449/https://www.gartner.com/en/articles/how-to-manage-cybersecurity-threats-not-episodes, read 12 Nov 2026
- https://www.cisa.gov/news-events/directives/bod-23-01-improving-asset-visibility-and-vulnerability-detection-federal-networks, read 12 Nov 2026
- https://www.dfs.ny.gov/system/files/documents/2023/12/rf23_nycrr_part_500_amend02_20231101.pdf, read 12 Nov 2026
- https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf, read 12 Nov 2026
- https://listings.pcisecuritystandards.org/documents/PCI-DSS-v4-0-SAQ-D-Merchant.pdf, read 12 Nov 2026
- https://csrc.nist.gov/pubs/sp/800/115/final, read 12 Nov 2026
- https://www.ncsc.gov.uk/collection/vulnerability-management/guidance, read 12 Nov 2026
- https://www.sec.gov/newsroom/press-releases/2023-139, read 12 Nov 2026
- https://www.digital-operational-resilience-act.com/Article_26.html, read 12 Nov 2026
- https://www.esma.europa.eu/esmas-activities/digital-finance-and-innovation/digital-operational-resilience-act-dora, read 12 Nov 2026
- https://www.ecb.europa.eu/paym/cyber-resilience/tiber-eu/html/index.en.html, read 12 Nov 2026
- https://blog.pcisecuritystandards.org/now-is-the-time-for-organizations-to-adopt-the-future-dated-requirements-of-pci-dss-v4-x, read 12 Nov 2026
- https://www.dfs.ny.gov/industry_guidance/cybersecurity, read 12 Nov 2026
- https://attack.mitre.org/resources/versions/, read 12 Nov 2026
- https://attack.mitre.org/tactics/enterprise/, read 12 Nov 2026
- https://ctid.mitre.org/projects/top-attack-techniques/, read 12 Nov 2026
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog, read 12 Nov 2026
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk, read 12 Nov 2026
- https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities, read 12 Nov 2026
- https://csrc.nist.gov/pubs/sp/800/40/r4/final, read 12 Nov 2026
- https://www.nist.gov/cyberframework, read 12 Nov 2026
Last reviewed 12 Nov 2026.