Merge pull request #223546 from danielledennis/main

Edit Discovery Seed List

Author: v-shils

articles/external-attack-surface-management/using-and-managing-discovery.md

@@ -62,7 +62,7 @@ Custom discoveries are organized into Discovery Groups. They are independent see
 
     ![Screenshot of pre-baked attack surface selection page.](media/Discovery_7.png)
 
-    Alternatively, users can manually input their seeds. Defender EASM accepts domains, IP blocks, hosts, email contacts, ASNs, certificate common names, and WhoIs organizations as seed values. You can also specify entities to exclude from asset discovery to ensure they are not added to your inventory if detected. For example, this is useful for organizations that have subsidiaries that will likely be connected to their central infrastructure, but do not belong to your organization.
+    Alternatively, users can manually input their seeds. Defender EASM accepts organization names, domains, IP blocks, hosts, email contacts, ASNs, and WhoIs organizations as seed values. You can also specify entities to exclude from asset discovery to ensure they are not added to your inventory if detected. For example, this is useful for organizations that have subsidiaries that will likely be connected to their central infrastructure, but do not belong to your organization.
 
     Once your seeds have been selected, select **Review + Create**.
 
@@ -90,7 +90,7 @@ Run history is organized by the seed assets scanned during the discovery run. To
 
 ### Viewing seeds and exclusions
 
-The Discovery page defaults to a list view of Discovery Groups, but users can also view lists of all seeds and excluded entities from this page. Simply click the either tab to view a list of all the seeds or exclusions that power your discovery groups.
+The Discovery page defaults to a list view of Discovery Groups, but users can also view lists of all seeds and excluded entities from this page. Simply click either tab to view a list of all the seeds or exclusions that power your discovery groups.
 
 ### Seeds
 
@@ -106,4 +106,4 @@ Similarly, you can click the “Exclusions” tab to see a list of entities that
 
 - [Discovering your attack surface](discovering-your-attack-surface.md)
 - [Understanding asset details](understanding-asset-details.md)
-- [Understanding dashboards](understanding-dashboards.md)
+- [Understanding dashboards](understanding-dashboards.md)

articles/external-attack-surface-management/what-is-discovery.md

@@ -22,15 +22,13 @@ Through this process, Microsoft enables organizations to proactively monitor the
 
 To create a comprehensive mapping of your organization’s attack surface, the system first intakes known assets (i.e. “seeds”) that are recursively scanned to discover additional entities through their connections to a seed. An initial seed may be any of the following kinds of web infrastructure indexed by Microsoft:
 
-- Pages
-- Host Name
-- Domain
-- Contact Email Address
-- IP Block
-- IP Address
-- ASN
-
-![Screenshot of Seed list view on discovery screen](media/Discovery-2.png)
+- Organization Names
+- Domains
+- IP Blocks
+- Hosts
+- Email Contacts
+- ASNs
+- Whois organizations
 
 Starting with a seed, the system then discovers associations to other online infrastructure to discover other assets owned by your organization; this process ultimately creates your attack surface inventory. The discovery process uses the seeds as the central nodes and spiders outward towards the periphery of your attack surface by identifying all the infrastructure directly connected to the seed, and then identifying all the things related to each of the things in the first set of connections, etc. This process continues until we reach the edge of what your organization is responsible for managing.