On this page
Your external attack surface is everything an attacker on the internet can find and interact with: domains and subdomains, IP addresses, open ports and services, web applications, APIs, login portals, cloud storage, TLS certificates and the software versions behind them.
The problem is that this surface is never static. A developer launches a staging site. Marketing adds a campaign microsite through an agency. A test VM is left with SSH open. A certificate quietly expires. Each change can open a door, and most organisations only find out when someone else does.
External Attack Surface Management (EASM) is the practice of continuously discovering, inventorying and assessing those internet-facing assets, from the outside in, the way an attacker would.
Why traditional asset inventories miss things
Internal inventories (CMDBs, cloud consoles, spreadsheets) only list what someone remembered to register. They routinely miss:
- Shadow IT: services set up outside the normal process.
- Forgotten assets: old marketing sites, retired product versions, pre-acquisition infrastructure.
- Third-party hosting: assets on SaaS or agency infrastructure that still carry your brand and data.
- Drift: a firewall rule changed "temporarily" six months ago.
What an EASM programme does
A mature EASM capability works as a loop:
- Discover. Starting from a few seeds (your root domains, company name, known IP ranges), it maps related subdomains, IPs, certificates and services using sources such as DNS, certificate transparency and internet-wide scanning.
- Inventory and attribute. It confirms which assets really belong to you and groups them by business unit, environment or owner.
- Assess. It identifies exposures: outdated software with known CVEs, exposed admin panels, weak TLS, misconfigured cloud storage, dangling DNS records vulnerable to subdomain takeover, and services that simply should not be public.
- Prioritise. Not every finding matters equally. Risk ranking considers severity, exploitability and how important the asset is, so teams fix what matters first.
- Monitor. It repeats continuously and alerts on change: a new subdomain, a newly opened port, a certificate about to expire.
EASM vs. penetration testing vs. vulnerability scanning
These are complementary, not competing:
| EASM | Vulnerability scanning | Penetration testing | |
|---|---|---|---|
| Question answered | What do we expose? | What known weaknesses exist on assets we list? | What could an attacker actually achieve? |
| Scope | Discovered from the outside | Assets you provide | Agreed, specific targets |
| Frequency | Continuous | Scheduled | Periodic (e.g. annually or per release) |
| Depth | Broad | Medium | Deep, manual |
A common pattern is to use EASM to keep the inventory honest, scanning to cover known assets regularly, and penetration testing to go deep on the systems that matter most.
Quick wins EASM typically surfaces
The first item on this list takes three commands to spot:
# Passive subdomain discovery (certificate transparency and public sources)$ subfinder -d example.com -silentwww.example.comstaging.example.comold-promo.example.com# Where does the forgotten campaign site point?$ dig +short CNAME old-promo.example.comexample-promo.azurewebsites.net.$ dig +short example-promo.azurewebsites.net[!] No answer: the cloud resource was deleted but DNS still points at it (subdomain takeover risk)- Subdomains pointing at deprovisioned cloud resources (subdomain takeover risk).
- Admin interfaces, databases or remote access services exposed to the internet.
- Expired or soon-to-expire certificates and weak TLS configurations.
- Internet-facing software with publicly known, actively exploited vulnerabilities.
- Staging and development environments that were never meant to be public.
FUTAQSEC EASM
Written by
Huzaifa Hafeez
Chief Technology Officer, FutaqSec