Skip to content

Commit 4243570

Browse files
committed
support updates
1 parent 89fd477 commit 4243570

File tree

1 file changed

+25
-23
lines changed

1 file changed

+25
-23
lines changed

exposure-management/external-attack-surface-management-initiative.md

Lines changed: 25 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 05/19/2025
1010
---
1111

1212

13-
# External Attack Surface Management initative in Exposure Management
13+
# External Attack Surface Management initiative in Exposure Management
1414

1515
Explore how to integrate Microsoft Defender External Attack Surface Management (MDEASM) with Microsoft Security Exposure Management (MSEM) to enhance visibility and control over your organization's external exposures. By connecting MDEASM insights to MSEM using the External Attack Surface Management initiative, you can assess the risk associated with your organization's or vendor's external attack surface and manage your security posture more effectively within the Exposure Management portal.
1616

@@ -20,9 +20,9 @@ There are two ways to use this initiative:
2020

2121
## Using the EASM initiative with pre-built footprint
2222

23-
This approach with the initiative provides high-level insights without a full connection to the MDEASM subscription and supports pre-built footprints only, hence doesn't require an active MDEASM subscription.
23+
This approach with the initiative provides high-level insights without a full connection to the MDEASM subscription and supports pre-built footprints only and doesn't require an active MDEASM subscription.
2424

25-
To configure your External Attack Surface initiative, you need to have **Global Administrator** role, or **Core security settings (manage)** permissions.
25+
**Prerequisites**: To configure your External Attack Surface initiative, you need to have **Global Administrator** role, or **Core security settings (manage)** permissions.
2626

2727
1. Go to the **Initiatives** page, select the **External Attack Surface Protection**, then choose **Open initiative page**.
2828
1. Go to the **Connect data source** to open the settings tab.
@@ -35,40 +35,42 @@ To configure your External Attack Surface initiative, you need to have **Global
3535

3636
:::image type="content" source="media/EASM/EASM-Pre-built-footprint.png" alt-text="Screenshot of side panel for EASM pre-built footprint selection" lightbox="media/EASM/EASM-Pre-built-footprint.png":::
3737

38-
5. In up to 1 hour, the initiative will be populated with high-level metrics and scores from the selected footprint.
38+
5. In up to 1 hour, the initiative is populated with high-level metrics and scores from the selected footprint.
3939

4040
> [!NOTE]
41-
> This approach does not provide asset level information and detailed exposure information.
41+
> This approach doesn't provide asset level information and detailed exposure information.
4242
4343
## Using the EASM initiative with full MSEADM integration
4444

45+
**Prerequisites**:
4546
This approach requires a full MDEASM subscription and provides comprehensive exposure analysis and asset-level details.
4647
To configure your External Attack Surface initiative, you need to have **Global Administrator** role, or **Core security settings (manage)** permissions.
4748

4849
### Environment setup:
4950

50-
If you haven’t already deployed an MDEASM resource, follow these steps:
51+
To deploy an MDEASM resource, follow these steps:
52+
53+
1. Log into [https://portal.azure.com](https://portal.azure.com).
54+
2. Create a Resource Group with the appropriate subscription and region.
55+
3. Deploy an MDEASM Resource within that group, see, [Create a Defender EASM Azure resource](/azure/external-attack-surface-management/deploying-the-defender-easm-azure-resource).
56+
57+
**Discover the attack surface**
58+
59+
You can discover your attack surface in two ways:
5160

52-
1. Deploy an EASM resource:
53-
1. Log into https://portal.azure.com.
54-
2. Create a Resource Group with the appropriate subscription and region.
55-
3. Deploy an MDEASM Resource within that group, see, [Create a Defender EASM Azure resource](/azure/external-attack-surface-management/deploying-the-defender-easm-azure-resource).
61+
1. Use the **Get Started** option to search for your organization and build a preconfigured attack surface.
62+
1. Or, create a custom discovery group by providing:
5663

57-
1. Discover the attack surface
58-
You can discover your attack surface in two ways:
59-
1. Use the **Get Started** option to search for your organization and build a preconfigured attack surface.
60-
1. Or, create a custom discovery group by providing:
61-
- Domains
62-
- IP Blocks or Addresses (use example IPs such as 203.0.113.0 if needed)
63-
- Hosts
64-
- ASNs
65-
- Emails
66-
- WHOIS organization data
64+
- Domains
65+
- IP Blocks or Addresses (use example IPs such as 203.0.113.0 if needed)
66+
- Hosts
67+
- ASNs
68+
- Emails
69+
- WHOIS organization data
6770

68-
For more information, see [Discovering your attack surface](/azure/external-attack-surface-management/discovering-your-attack-surface)
71+
For more information, see [Discovering your attack surface](/azure/external-attack-surface-management/discovering-your-attack-surface)
6972

7073
> [!TIP]
71-
>
7274
> The easiest path is to provide a host, domain, and any known external IP addresses.
7375
7476
### Configure the initiative
@@ -80,7 +82,7 @@ If you haven’t already deployed an MDEASM resource, follow these steps:
8082
> If you previously configured the initiative, you can select **Switch data source** to reconfigure it with new data.
8183
8284
1. Choose **Connect your MDEASM workspace**.
83-
1. To enable the intitiative to pull data from your Defender EASM resource, enter the values from your resource's **Essentials** section on the **Overview** pane found in Azure.
85+
1. To enable the initiative to pull data from your Defender EASM resource, enter the values from your resource's **Essentials** section on the **Overview** pane found in Azure.
8486

8587
- **Resource Name**
8688
- **Subscription ID**

0 commit comments

Comments
 (0)