Continuous Threat Exposure Management (CTEM) is a program, not a product. It is a repeating five-stage cycle for finding, prioritising and reducing an organisation's exposure on an ongoing basis, rather than in a once-a-year audit. The term was introduced by Gartner as a way to describe how the separate pieces — asset discovery, vulnerability management, external attack surface monitoring and validation — fit together into one continuous loop.
The five stages
CTEM is usually described in five stages that run in a loop, not a straight line:
- Scoping — decide which part of the business and which assets the cycle covers.
- Discovery — find the assets and their exposures, including the internet-facing ones you did not know about.
- Prioritisation — rank what to fix by real risk, not raw severity, so limited time goes to what attackers are most likely to exploit.
- Validation — confirm an exposure is actually reachable and exploitable, rather than theoretical.
- Mobilisation — get the fixes done: assign owners, track remediation, and close the loop.
CTEM versus a one-off scan
A one-off scan tells you what was exposed on the day it ran. CTEM is built around the fact that your attack surface changes constantly — a new subdomain, an expired certificate, a freshly disclosed CVE — so the assessment has to be continuous. The difference is cadence and follow-through: CTEM keeps discovering and re-prioritising, and it does not consider a finding closed until it is verified fixed.
Where external attack surface management fits
External attack surface management (EASM) is the engine for the discovery and monitoring of the internet-facing part of a CTEM program. It answers "what can an attacker see and reach from outside?" and feeds that into prioritisation. EASM is not the whole of CTEM — validation and internal asset data come from other tools — but for the external surface, it is the discovery layer the rest of the cycle depends on.
The one-line answer
CTEM is the continuous program; EASM, vulnerability management and validation are the capabilities inside it. You do not buy "a CTEM" — you run a CTEM process using tools that cover its stages.
How ThreatPort fits
ThreatPort covers the external discovery, monitoring and prioritisation part of a CTEM approach: it continuously maps your internet-facing assets, flags exposures, and ranks CVE risk using the CISA KEV catalogue and FIRST.org EPSS. It is one component of a CTEM program — the external-surface engine — not the entire framework, and it is honest about that. If you are building a CTEM process on a small budget, external attack surface monitoring is a sensible place to start, because the external surface is where attackers start too.