Explainer · Attack surface management
EASM vs. vulnerability scanning: what is the difference?
External attack surface management (EASM) is the continuous discovery and monitoring of an organization’s internet-facing assets, including ones its security team does not know about. Vulnerability scanning tests a known list of assets for known weaknesses. EASM answers “what do we expose?”; scanning answers “what is wrong with what we listed?” Most programs need both.
A scanner only sees what you point it at
Every scanner starts from a target list. Assets that never made the list, such as a forgotten marketing site, a test server, a vendor-hosted portal or a subdomain another team created, are never scanned, however exposed they are. Attackers do not start from your list. They start from your name, your certificates and your DNS.
Assets drift out of inventories in ordinary ways: a campaign site launched by marketing, a proof of concept left running, the domains of an acquired company, a portal a vendor hosts under your name.
EASM builds and maintains the list; scanning checks what is on it. Neither proves that a weakness can be exploited. That is the job of penetration testing, where people confirm what an attacker could actually do.
How EASM and vulnerability scanning compare
| EASM | Vulnerability scanning | |
|---|---|---|
| Question it answers | What do we expose to the internet? | What known weaknesses do these assets have? |
| Starting point | A seed, such as a root domain or organization name | A target list you provide |
| Typical methods | DNS, certificate transparency, passive sources, HTTP probing and technology fingerprinting | Signature and version checks against hosts, ports and applications |
| Typical findings | Unknown assets, exposed services, technologies in use, dangling DNS records | Missing patches, known CVEs, weak configurations |
| Cadence | Continuous | Scheduled, for example weekly, monthly or quarterly |
| Common noise | Assets that turn out not to be yours | False positives from version-based checks |
| Blind spot | Does not confirm exploitability | Assets outside the list; does not confirm exploitability either |
How to find assets your scanner misses
Work only with domains, networks and cloud accounts you own or are authorized to test. Vendor-hosted assets need the vendor’s permission before any testing.
-
Export the target list
Pull the current targets from your scanner: hostnames, IP ranges and applications.
-
Build an outside-in list
List hostnames for your domains from DNS and Certificate Transparency logs, plus the public assets in your cloud accounts.
-
Compare the two
Anything on the outside-in list but not in the scanner is untested. Note who owns each one: a team, a vendor or nobody.
-
Close the gap
Add confirmed assets to scanning and testing scope, and retire the ones nobody owns, starting with their DNS records.
How EASM and scanning work together
- Feed discovery into scope. New assets found by EASM should reach scanning and testing scope after an ownership check, not months later.
- Prioritize with exposure context. A medium-severity CVE on an internet-facing sign-in page can matter more than a critical one on a host nobody can reach. Use CISA KEV, EPSS and exploit availability, not CVSS alone.
- Validate what matters. Confirm exploitability with penetration testing before escalating to engineering.
- Repeat after change. Run discovery again after releases, migrations and acquisitions.
How NorthBound combines discovery, matching and testing
Our attack surface discovery finds assets through DNS, certificate transparency, passive sources and HTTP probing. Tech stack intelligence fingerprints what they run with 120+ hand-tuned and 4,000+ community signatures, and matches it continuously to new CVEs, enriched with CISA KEV, EPSS and exploit availability; new matches can trigger an email alert. Experienced people then test what matters, within the mode you approve. Each finding is Validated with class-specific evidence, or reported as a Signal capped at medium severity until proven.
Questions about EASM and vulnerability scanning
Does EASM replace vulnerability scanning?
No. EASM tells you what to scan, and scanning tells you what is wrong with it. Most programs need both, plus penetration testing to confirm what is exploitable.
Is EASM the same as penetration testing?
No. EASM discovers and monitors assets; penetration testing shows what an attacker could do with them. Good discovery makes a penetration test more complete, because testers see everything in scope.
Can EASM or continuous testing stand in for required vulnerability scans?
Not always. Some standards say who must run the scans. PCI DSS, for example, requires external vulnerability scans by an Approved Scanning Vendor (ASV), and NorthBound is not an ASV.
How often should EASM run?
Continuously, or as close to it as your provider allows. Its value is catching changes between scheduled scans and tests.
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.