Explainer · Exposure management

What is continuous threat exposure management (CTEM)?

Continuous threat exposure management (CTEM) is a program for continuously finding, prioritizing, validating and fixing the exposures an attacker could use against an organization. It is a way of running security work, not a product. Gartner introduced the term in 2022 and describes five stages: scoping, discovery, prioritization, validation and mobilization.

01 Why it matters

Why CTEM exists

Traditional vulnerability management produces long lists ranked by severity score. Teams cannot fix everything, many items are not reachable or not exploitable, and exposures that are not CVEs at all, such as leaked credentials, public source maps, misconfigured cloud storage or a dangling DNS record, often fall outside the process.

CTEM changes the question from “what vulnerabilities do we have?” to “what could an attacker actually use against us, and what should we fix first?” It ties security work to business priorities and measures progress by exposures closed, not findings reported.

02 Five stages

The five stages of a CTEM cycle

A CTEM program runs in cycles. Each cycle passes through five stages, then starts again with a fresh look at scope.

  1. Scoping

    Decide what the cycle covers: business-critical systems and the attack surfaces around them, such as internet-facing assets, cloud services, identities and code.

  2. Discovery

    Find the assets in scope and their exposures: vulnerabilities, misconfigurations, leaked credentials and assets nobody listed.

  3. Prioritization

    Rank by what an attacker could use and what it would cost the business, with exploitability context such as CISA KEV, EPSS and exploit availability, not severity scores alone.

  4. Validation

    Confirm that an exposure can be exploited, how far an attacker could get, and whether your controls would detect or stop it.

  5. Mobilization

    Get fixes done: agree owners, remediation paths, exceptions and deadlines across teams, then verify the result.

03 Check yourself

How to tell where your program stands

Answer these questions from your own records. The weakest answer shows which stage to strengthen first.

  1. Is the scope written down?

    Name the business-critical systems and attack surfaces this cycle covers, and who owns each one.

  2. How fast do new assets appear?

    Measure how long a new subdomain, application or vendor takes to reach your inventory.

  3. What drives priority?

    Check whether ranking uses exploitability and business impact, or severity scores alone.

  4. Do fixes close?

    Follow one important finding from report to retest, and check whether resolved items come back.

04 Get started

How to start a CTEM program

Start small and complete a full cycle before you expand:

  • pick one scope that matters, such as the internet-facing systems of one business unit;
  • use the tools and teams you already have, and note which stage is weakest;
  • agree with system owners how fixes will be assigned and tracked before the first findings arrive;
  • validate the top exposures before escalating them, so engineers trust what reaches them;
  • measure exposures closed and time to fix, then widen the scope.
05 Our coverage

Where NorthBound fits in a CTEM program

CTEM is a program you run, and NorthBound is not a CTEM platform. We support these stages for your external attack surface, and our in-house team can test your internal network by separate agreement.

Where NorthBound fits in a CTEM program
StageWhat NorthBound contributes
ScopingWe agree scope, testing modes and exclusions with you. Our virtual CISO service can help set priorities.
DiscoveryAttack surface discovery and exposure intelligence: subdomains, technologies, source maps, leaked credentials and more.
PrioritizationContinuous CVE matching for the technologies you run, enriched with CISA KEV, EPSS and exploit availability, then reviewed by our team.
ValidationTesting with an evidence gate: findings are Validated with class-specific evidence, or reported as Signals capped at medium severity.
MobilizationGuidance for your engineers, a retest after each fix, and run-to-run comparison of new, resolved and resurfaced findings.
06 FAQ

Questions about CTEM

Is CTEM a product we can buy?

No. CTEM is a way of running a program. Tools and services support individual stages, but the scoping and mobilization decisions stay with your organization.

How is CTEM different from vulnerability management?

It covers more than CVEs, ranks by exploitability and business impact rather than severity alone, validates exposures before escalating them, and treats getting fixes done as part of the job.

Where does penetration testing fit in CTEM?

Mostly in validation, where it shows what an attacker could actually do. Continuous penetration testing also feeds discovery, because it keeps watching for new assets and exposures.

Who created the CTEM framework?

Gartner introduced continuous threat exposure management in 2022 and describes it in five stages: scoping, discovery, prioritization, validation and mobilization.

Find it before an attacker does.

Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.

Facts on this page verified 11 November 2026.