EASM (continuous discovery and monitoring of internet-exposed assets) stands for External Attack Surface Management, seen from an attacker's point of view, and shows which websites, servers or services are exposed that the organization may have forgotten. The term comes from the product market, not a standard, and we found no formal definition from NIST or CISA. This article explains what EASM does, how it differs from vulnerability scanning, and how to start.
The area an attacker can see from outside
The related term is attack surface. The NIST Glossary defines it as the set of points on the boundary of a system or environment where an attacker can try to enter, cause an effect or extract data. The external attack surface is the part that anyone can try to reach from the internet without first being inside the organization's network.
Examples of assets that often sit in this area (our view):
- Domains and subdomains: the main site name and sub-names such as mail.example.com that sometimes nobody maintains
- IP addresses and open ports: a port is a connection channel on a machine, and one left open without need is a way in for an attacker
- Web apps and APIs: systems offered over the internet, including login pages of internal systems that were exposed by mistake
- Management pages and remote access: such as a VPN (a channel into the organization's network from outside) and network device settings pages
- Cloud and SaaS: cloud accounts and software services that departments signed up for themselves
- Shadow IT: systems a department uses without the IT team knowing, so they are missing from the asset inventory
EASM runs as a continuous cycle
The idea matches continuous monitoring in NIST SP 800-137 (September 2011), which NIST says gives visibility into assets, threats and vulnerabilities, and which is still the latest edition we could confirm on the NIST page. An EASM tool does the same from outside: it starts from seed data such as the domain names and IP ranges the organization provides, then searches for related assets. In short, the cycle in the figure is discover, confirm ownership, prioritize, fix, then discover again; this is our summary, not a standard procedure. The three jobs in the next list differ in the question they answer.
- EASM: answers what of ours is exposed on the internet, including what nobody knew existed
- Vulnerability scan: checks assets that are already known for vulnerabilities or weak configuration
- Penetration test: testers attempt a real attack to prove how far an intruder could get
These three jobs support each other rather than replace each other. EASM feeds the asset list into a Vulnerability Management program. For the difference between a vulnerability scan and a penetration test, read Pentest, Vulnerability Assessment and Red Team: how they differ.
What to watch for when choosing a tool or service
- Confirm ownership: some tools may list assets of another company with a similar name, so someone inside the organization must check before counting them as its own
- Scan scope: searching public data differs from active scanning that sends traffic to targets; actively scan only the organization's own assets and have legal counsel confirm; this is not legal advice
- Prioritize: findings are often numerous, so rank them by real risk; see CVSS, EPSS and KEV: how to prioritize vulnerability risk
- Have an owner who can fix: each asset found needs someone responsible for closing or fixing it, or the report changes nothing
As a US government example, CISA states that its Cyber Hygiene services help secure internet-facing systems from weak configurations and known vulnerabilities, and on 13 June 2023 CISA issued a binding directive for US federal civilian agencies (BOD 23-02) requiring that management interfaces of network devices exposed to the internet be removed or protected with Zero Trust (do not trust anyone automatically; verify every time) capabilities. It binds only US federal agencies, but other organizations can use it as a model.
Where to start
- This week: gather the domain names, IP ranges and cloud accounts the organization already knows as seed data
- This month: run a discovery with a free tool or a chosen service and compare it with the existing asset inventory
- Find owners: name an owner for each asset found and close what does not need to be open
- Repeat in cycles: set a continuous review cycle rather than checking once and stopping
If you are not sure where the organization stands, try the self-assessment and close the asset-visibility gaps first.