Cyber Asset Attack Surface Management (CAASM) is an approach that builds a single, unified inventory of all of an organisation's assets — including internal ones — by pulling data from the tools you already run through their APIs, rather than by scanning from the outside. CAASM answers "what do we own, and what state is it in?" It is an asset-visibility and inventory problem, solved by integration rather than by reconnaissance.
How CAASM works
Instead of probing the internet, a CAASM tool connects to your existing sources — endpoint agents, cloud provider APIs, identity providers, vulnerability scanners, CMDBs — and reconciles them into one view. The value is deduplication and completeness: it finds the laptop that no scanner sees, the cloud instance missing an agent, or the asset that exists in one system but not another. It depends on having those integrations and credentials.
CAASM versus EASM — different questions
CAASM and external attack surface management (EASM) are often confused, but they answer opposite questions:
- CAASM looks inward, through API integrations, at everything you own — internal and external — to build a complete inventory.
- EASM looks outward, through unauthenticated scanning, at only the internet-facing assets an attacker can reach, from the attacker's perspective.
CAASM needs access to your internal tools; EASM needs nothing but your domain. One gives you the full picture from the inside; the other gives you the attacker's view from the outside.
Which one do you need
If your problem is "we do not have a complete inventory of our assets and their status across all our tools," that is a CAASM problem. If your problem is "we do not know what we are exposing to the internet, or what attackers can already see," that is an EASM problem. Larger organisations with many internal tools often want both; a small team usually starts with the external view, because that is what gets attacked first.
The one-line answer
EASM shows what attackers see from outside; CAASM shows everything you own from inside. They are complementary, not the same thing.
How ThreatPort fits — and where it does not
ThreatPort is an EASM tool, not a CAASM tool. It scans your external, attacker-visible surface from a domain, with no agents and no integrations, and it does not build an internal asset inventory or connect to your internal systems. If you need a full internal inventory reconciled from APIs, that is a CAASM platform and ThreatPort is not it. If you want the outside-in, attacker's-eye view of what you are exposing, that is exactly what external attack surface management does.