Piscium SecurityPISCIUMSECURITY
blog

Attack Surface Management vs. CTEM: What's the Difference?

ASM discovers your exposure. CTEM validates, prioritizes, remediates, and verifies it. Understand why discovery alone isn't enough for critical infrastructure.

By Emanuelle Jiménez

Two Acronyms, One Objective

Attack surface management (ASM) finds and inventories what an organization exposes to the internet and watches it for change. Continuous threat exposure management (CTEM) is the larger program. ASM covers part of its discovery stage, and CTEM adds prioritization by attack path, validation of what is really exploitable, and mobilization that confirms each fix. ASM tells you an exposure exists. CTEM tells you whether an attacker can use it and whether your fix closed it.

Understanding the distinction matters because choosing the wrong framing leads to the wrong investment. Organizations that treat ASM as "good enough" leave critical gaps in their security posture. Those that understand CTEM as the larger framework know exactly where ASM fits, and where it stops.

What ASM Does (and Doesn't Do)

Attack Surface Management platforms focus on discovery: finding all assets, services, and exposures visible from an attacker's perspective. A typical ASM solution:

  • Discovers external-facing assets: domains, subdomains, IP ranges, cloud services, SaaS applications, exposed APIs
  • Inventories the attack surface: ports, services, technologies, SSL certificates, DNS records
  • Monitors for changes: new assets appearing, services exposed, configurations modified
  • Alerts on known exposures: CVEs in detected software versions, misconfigurations, expired certificates

This is valuable and necessary. Many organizations don't know the full extent of their attack surface. Shadow IT, cloud sprawl, and M&A activity create exposure that internal asset inventories miss.

But discovery is only the first step. Knowing that a service exists and has a CVE doesn't tell you:

  • Is the vulnerability actually exploitable in your environment?
  • Does an attacker have a viable path from this asset to critical targets?
  • Has the remediation you applied actually closed the exposure?
  • Did last week's network change reintroduce a previously fixed vulnerability?

These questions require validation, prioritization, remediation tracking, and verification: capabilities beyond ASM's scope.

The CTEM Framework

CTEM, as defined by Gartner, is a five-phase continuous program:

Phase 1: Scoping

Define what matters. Not just "all external assets" but business-critical systems, crown jewels, regulatory scope, and operational boundaries. For OT/ICS environments, scoping extends to Level 0-3 of the Purdue Model, covering assets that ASM typically can't see because they're not internet-facing.

Phase 2: Discovery

Identify all assets, exposures, and potential attack paths within scope. This overlaps with ASM but goes deeper: internal discovery, OT protocol enumeration, identity mapping, and configuration analysis.

Phase 3: Prioritization

Rank exposures by actual business risk, not just CVSS score. Prioritization considers exploitability in context, attack path analysis, business impact of the target asset, active threat intelligence, and compensating controls. A CVSS 9.8 on an isolated test server ranks below a CVSS 6.5 on a directly reachable HMI controlling critical processes.

Phase 4: Validation

Prove whether exposures are genuinely exploitable. Safe exploitation testing and control validation confirm that theoretical vulnerabilities translate to real risk, or don't. This is the phase that ASM lacks entirely.

Phase 5: Mobilization

Drive remediation through integrated workflows. Assign tickets, track resolution, define SLAs by risk tier, and verify that fixes actually work. Mobilization closes the loop, turning findings into action and action into verified risk reduction.

The Comparison

CapabilityASMCTEM
External asset discoveryCore capabilityIncluded in Phase 2
Internal asset discoveryOut of scopeFull internal + OT
Continuous monitoringSurface-level changesDeep configuration + exposure
Vulnerability detectionKnown CVEs from versionsContextual exploitability
Attack path analysisNo path modelingDynamic attack graphs
Exploitation validationNot performedSafe, protocol-aware validation
Remediation trackingBasic alertingFull workflow integration
Verification of fixesNot performedRe-validation post-remediation
OT/ICS coverageUsually internet-facing IT onlyInternal and OT assets, passive first
Business risk scoringLimited contextAsset criticality + path analysis

Why ASM alone falls short

For organizations with operational technology on the network, ASM addresses a narrow slice of the risk picture:

Visibility without context: ASM tells you a substation's engineering workstation has an exposed RDP service. It doesn't tell you that RDP → local admin → PLC programming software → Level 1 control = a complete attack path to physical process manipulation.

Discovery without validation: ASM identifies a CVE in your historian server's web interface. It doesn't verify whether the vulnerability is exploitable given your specific configuration, network segmentation, and authentication controls.

Alerting without action: ASM generates findings. CTEM generates findings, prioritizes them by business impact, validates exploitability, assigns remediation workflows, and verifies the fix. The difference between a report and a risk reduction.

ASM as a CTEM Component

ASM is the discovery engine inside a CTEM program. In Piscium Radius it is the observe step: Radius discovers and keeps watching the attack surface, then reasons over the attack graph, attacks and validates the paths that matter, and attacks each fixed path again.

Keep reading

blog
Shadow AI vs AI Sprawl: What Each Is and How to Control It

The shadow AI vs AI sprawl distinction decides what security teams measure and fix. See how the two problems differ and which controls address each one.

Read More
blog
Jev Guards Agent Tools, but It Can't Stand Alone

Jev is cheap and fast enough to judge every agent tool call. The first two weeks of evidence show where it helps and how attacker-written context flips it.

Read More
blog
How Distillation Attacks Work Against AI Models

Distillation attacks turn an AI model's own answers against it, copying its skills, pulling out its training data, or stripping its safety limits.

Read More

See what your own domain exposes

A free external scan: Radius maps your internet-facing assets from the outside, nothing is exploited, and we confirm you are authorized for the domain first.