Study guide
14.1 Microsoft Defender External Attack Surface Management (EASM)
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
14.1 Microsoft Defender External Attack Surface Management (EASM)
Key Takeaways Explain This Topic AI
Defender EASM discovers internet-facing assets from the outside using seeds such as domains, IP blocks, and organization names — no agent or credential is required.
Discovered assets land in the discovery chain and must be approved into the Approved Inventory before they count as yours.
EASM asset types include domains, hosts, pages, IP blocks, IP addresses, ASNs, and SSL certificates.
Built-in dashboards cover attack surface summary, security posture, GDPR compliance, and OWASP Top 10 exposure.
Data connections export EASM asset and insight data to Log Analytics or Azure Data Explorer so findings can drive Sentinel detections.
Last updated: August 2026
The Blind Spot EASM Closes
Every posture tool discussed so far looks outward from your subscription : Defender for Cloud enumerates resources you own in a cloud you control. Defender External Attack Surface Management (EASM) looks inward from the internet. It answers a different question — what can an attacker see and reach that belongs to us? — and the answers routinely include assets nobody in the security team knew existed:
A marketing microsite registered on a corporate credit card and hosted at a third party.
A subsidiary's domain still resolving to an unpatched web server after an acquisition.
A staging host with an expired TLS certificate and a default admin page.
An IP range that used to be yours and now serves someone else's content.
None of these appear in Azure Resource Graph, so no amount of Defender for Cloud tuning finds them.
How Discovery Works
EASM is deployed as an Azure resource in a resource group and needs no agents and no credentials in the target environment , because it observes from outside.
Seeds → discovery → inventory:
Discovery seeds are things you know are yours: domain names, IP blocks, host names, ASNs, WHOIS contact details, and organization names.
A discovery group bundles seeds and a run schedule. Microsoft also offers pre-built attack surfaces for many organizations as a starting point.
EASM performs recursive discovery , following relationships — shared WHOIS registrant, shared SSL certificate, DNS records, hosting relationships — to infer further assets. Each inferred asset carries a discovery chain showing the evidence path back to a seed.
Results land in the inventory in a state such as Approved Inventory , Candidate , Dependency , Monitor Only , or Requires Investigation .
You must review and approve candidates. Recursive discovery is deliberately generous; an asset that merely shares a hosting provider is not yours. Approving assets into the Approved Inventory is the human step that makes the data trustworthy, and labels let you group assets by business unit, subsidiary, or environment.
Asset Types
- Asset type Example
- Domain contoso.com
- Host payments.contoso.com
- Page A specific reachable URL with its response headers and technologies
- IP block 203.0.113.0/24
- IP address A single address with its open services
- ASN An autonomous system number registered to the organization
- SSL certificate Certificate details, issuer, and expiry across all hosts using it
Each asset carries observed metadata: detected web technologies and versions, HTTP response headers, open ports and services, certificate chain and expiry, and the discovery chain that justified its inclusion.
Dashboards and Insights
EASM ships four dashboards that map cleanly to security conversations:
Dashboard Use
Attack Surface Summary Overall counts by asset type, high/medium/low severity insights, and new assets over time
Security Posture Concrete weaknesses — expired or expiring certificates, weak cipher suites, missing security headers, exposed admin interfaces
GDPR Compliance Privacy-relevant exposure such as sites lacking HTTPS enforcement or with cookie and privacy-policy issues, scoped to relevant jurisdictions
OWASP Top 10 Assets showing evidence of the OWASP Top 10 categories
Insights are the findings themselves, classified high , medium , or low , each listing the affected assets and the observation that produced it. High-severity insights typically include CVEs on identified technology versions and services that should never face the internet.
Operationalising EASM
EASM is only useful if its findings reach the teams that fix things:
Data connections push asset data and insights to Azure Log Analytics or Azure Data Explorer on a schedule. From Log Analytics, Microsoft Sentinel can run analytics rules over the data — for example, alert whenever a newly discovered host appears in Approved Inventory that is not in the CMDB, or whenever an insight of high severity is raised.
The REST API supports pulling inventory and insights into ticketing and CMDB systems.
Defender CSPM in Defender for Cloud consumes external attack surface data to enrich internet-exposure context in attack path analysis, so an internet-facing VM's real reachability is assessed with outside-in evidence rather than only NSG configuration.
Billing is per asset per day in the Approved Inventory, which is another practical reason to keep the approval discipline tight rather than approving every candidate.
The operating rhythm is straightforward: schedule discovery, triage new candidates weekly, treat high-severity insights as incidents, and reconcile the Approved Inventory against your asset register so that "shadow IT" becomes a measured number that trends downward.