#Five stages and their outputs
| Stage | Question | Output handed on | Metric |
|---|---|---|---|
| Scoping | Which business processes and assets matter this cycle? | A named scope with owners | Share of crown-jewel systems in scope |
| Discovery | What exists and what is weak within scope? | Asset and exposure inventory | Unknown assets found vs CMDB |
| Prioritization | Which exposures matter most? | Ranked list using likelihood, impact and paths | Exposures per owner, by rank |
| Validation | Can they actually be exploited, and would we see it? | Proven attack paths, control results | Proven paths to crown jewels; detection rate |
| Mobilization | Who fixes what, by when? | Tickets with SLAs, verified fixes | Time to verified fix |
#A first cycle in practice
A realistic first cycle takes 60 to 90 days. Pick one scope with an executive owner — the external attack surface plus one revenue-critical application is common. Discovery usually finds assets nobody listed; record that number, it is the first metric leadership will remember. Prioritize with likelihood signals (EPSS, known-exploited status) and path context. Validate by actually exploiting the top candidates in a controlled way and checking whether detection fired. Mobilize with tickets that name an owner, a fix, and a retest date. Then re-scope: the second cycle should add a surface, not repeat the first.
CTEM is vendor-neutral by design; no single tool covers all five stages. What matters is that each stage's output is the next stage's input, and that the loop actually closes with verified fixes.
#How CTEM programs fail
- Prioritization without validation. Ranking by severity reproduces vulnerability management. Our simulation shows severity-first fixing barely beats random at reducing breach probability.
- Validation without mobilization. Proven paths nobody owns become a more alarming backlog.
- Annual cadence with a new name. The C stands for continuous; the exposure-window model shows why cadence and fix time dominate.
#Sources
Talk to an operator.
Thirty minutes, no slides. We'll show you what bad AI finds in one of your systems.
Book a briefing