What is EASM and how does it find forgotten servers?
EASM (External Attack Surface Management) is defenders mapping their own internet-facing systems from public records, the way an attacker would, so forgotten servers get found and checked.

EASM
Every company has systems that can be reached from the internet. Some are well known, like the main website. Others were set up years ago and forgotten. Attackers can list a company’s internet-facing systems from public records, without touching its servers. That’s how they find servers the company forgot existed.
EASM (External Attack Surface Management) is defenders running that same mapping on themselves. Instead of waiting for an attacker to find a forgotten system, the team searches the same public records first. It exists for one simple reason. You can’t protect what you don’t know is online.
What EASM actually does
It starts with seeds. A seed is something the team knows it owns: its domain, its public IP (Internet Protocol) address blocks, and its ASN (Autonomous System Number), the number that identifies its network in routing. Seeds can also be hosts, email contacts and WHOIS organizations. In Microsoft Defender EASM, private IP addresses are not allowed as seeds.
From there, the tool pivots through public records. A WHOIS lookup finds other domains registered with the same contact email. The ASN reveals other IP blocks tied to the same network. HTTPS (Hypertext Transfer Protocol Secure) certificates are recorded in public logs called CT (Certificate Transparency), so every hostname in a certificate’s SAN (Subject Alternative Name) field is searchable. Every find becomes a new seed, and the search runs again from there.
How EASM sorts what it finds
- Strong links approved automatically. Strong connections are labeled as confirmed inventory without a person stepping in.
- Humans review uncertain finds. Candidates and assets marked Requires Investigation go to a person, because a shared IP or certificate can belong to a hosting provider, not you. Microsoft recommends starting with Requires Investigation.
- Third parties stay separate. Assets owned by a third party are marked as a dependency. Systems the company doesn’t directly control are set to monitor only. Neither counts as a strong link.
- Confirmed assets get probed. Each confirmed asset is checked for open ports and software versions. Discovery re-runs weekly by default.
The result is a list of what the company really has online, not just what it remembers having. The cost of missing one is real. In 2017, attackers entered Equifax through an internet-facing online dispute portal running Apache Struts. The flaw, CVE-2017-5638 (Common Vulnerabilities and Exposures), had been fixed two months earlier. The attackers stayed inside for 76 days, and over 145 million people were affected.
EASM is not a vulnerability scanner
A common belief is that the vulnerability scanner already covers everything. It doesn’t. A scanner only checks the hosts and IP ranges it was given. A cloud or vendor server outside those ranges is never checked. EASM answers a different question: what do we have online that nobody put on the list?
What to do
- Turn off remote management on your home router today, so its admin page doesn’t face the internet. Menu names differ by brand.
- Write down your seeds: your domains, your public IP blocks and your ASN, if your organization has one.
- Search Certificate Transparency logs for your domain and check every hostname you don’t recognize.
- Ask whether your vulnerability scanner’s list includes your cloud and vendor servers.
Watch it in 60 seconds
