Home / Guides / Measuring a CTEM program: three measures that hold up
Guide, read 12 Nov 2026
Count proven exposures and the time to close them; drop raw finding totals
Good measures follow the stage outputs
A CTEM measure should count something a stage produces and a decision changes. Validation produces proven exposures. Mobilization produces fixes and re-tests. Control testing produces block and detect results per technique. Measures built on those outputs move when the program works and stay flat when it does not.
Measures built on discovery output move for the wrong reasons. Add a scanner and the vulnerability count rises; narrow a scan and it falls. Neither change says anything about what an attacker could do in the scope. Gartner's 21 Aug 2023 article says the volume of discovered assets and vulnerabilities is not success in itself.
Measure one: validated exposure count
Count, per scope and per cycle, the exposures that validation proved usable: a path from an entry point to an in-scope asset that worked on test. Report it with the number tested, so a falling count is not mistaken for progress when fewer tests ran.
Split the count by entry point (internet, internal foothold, third party) and by kind (missing patch, misconfiguration, identity, SaaS setting). The split tells the CISO where the program's fixes should go next. Over several cycles, a stable scope with a falling proven count and a stable test count is the clearest sign the program is reducing exposure.
Measure two: time to mitigate proven exposures
Measure the days from the validation result to the re-test that shows the path closed, whether by patch, configuration change or a mitigation in an existing control. Use the median and the 90th percentile; a mean hides the long tail that matters.
Count only proven items. Time-to-patch across every finding mixes urgent and irrelevant work. Report against the tiers the program set in mobilization, and against any external deadline: CISA's BOD 26-04 (10 Jun 2026) starts the federal clock when a CVE enters the KEV catalog or is found on an asset, whichever comes first. Accepted risks are reported separately with their expiry dates, never counted as mitigated.
Measure three: control efficacy by technique
For each ATT&CK technique tested in the scope, record the share of test runs that were prevented, detected, or neither, by control. MITRE ATT&CK v20.1, current since 13 Oct 2026, has 227 Enterprise techniques and 479 sub-techniques, so state the denominator: techniques tested, not techniques in ATT&CK.
Choose the techniques first. MITRE's Center for Threat-Informed Defense says defending against all techniques is not practical; its Top ATT&CK Techniques project (14 Aug 2024) builds a top 10 list from prevalence, choke points and actionability.Report efficacy as a trend for the same technique set across cycles.
Break the result out by control as well as by technique. If the endpoint agent prevents a technique on servers but only detects it on laptops, that is two results, and the fix belongs to two different owners. Efficacy by control tells the CISO which tool is underperforming against the techniques that matter for the scope, which is a budget question the board may need to decide.
Measures that do not hold up
Each of these is easy to produce and hard to act on.
- Total open vulnerabilities. Moves with scanner coverage, not with risk.
- Average severity score. A score of a flaw in isolation, averaged, describes nothing an attacker would do.
- Percent of all findings patched in SLA. Rewards closing easy, irrelevant items first.
- Percent of ATT&CK covered. Coverage of a technique by one simulation is not efficacy against it.
- Number of tests run. Activity, not outcome; report it only as the denominator for measure one.
- A single composite risk score. Hides which of the three real measures changed and why.
A measurement sheet for one cycle
One row per scope per cycle is enough. The sheet below is a template; the numbers are placeholders to show the form.
| Field | Definition | Example form |
|---|---|---|
| Scope | Business service named in the scope statement | Payments |
| Items tested | Short-list items that ran validation | n |
| Validated exposures | Items proven usable | n, split by entry point |
| Median days to mitigate | Validation date to closing re-test, proven items | days |
| 90th percentile days | Same, 90th percentile | days |
| Accepted risks | Proven items accepted, with expiry | n |
| Techniques tested | Distinct ATT&CK techniques in the scope's test set | n |
| Prevented / detected / neither | Share of technique runs | percent each |
Keep the measures honest
Every measure can be gamed. A validated exposure count falls if validation tests fewer items or easier ones, so always report the items tested beside it and keep a stable core of tests from cycle to cycle. Time to mitigate falls if teams mark items as accepted risk instead of fixing them, so report accepted risks next to it. Control efficacy rises if the technique set shrinks to what already passes, so freeze the set for at least four quarters and change it only with a note.
Have someone outside the exposure team, internal audit or the validation lead, sample a few closed items per quarter and check that a dated re-test exists for each. That one check does more for the credibility of the numbers than any dashboard.
Forecasts are not program metrics
Gartner's 2023 prediction that organizations prioritizing investments through a continuous exposure management program would be three times less likely to suffer a breach by 2026 is an analyst forecast across many companies. One program cannot measure it. Breach counts inside one company are too rare and too delayed to steer a 4 to 6 week cycle.
The three measures above can be reported each quarter, each answers a question a manager can act on, and each traces back to evidence a reviewer can check. The board reporting guide picks one for the board, and the site's method explains how vendor stage coverage is judged.
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-26-04-prioritizing-security-updates-based-risk, read 12 Nov 2026
- https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json, read 12 Nov 2026
- https://attack.mitre.org/techniques/enterprise/, read 12 Nov 2026
- https://attack.mitre.org/resources/versions/, read 12 Nov 2026
- https://ctid.mitre.org/projects/top-attack-techniques/, read 12 Nov 2026
Last reviewed 12 Nov 2026.