Skip to content

Commit 5d5691d

Browse files
authored
Merge pull request #248330 from danielledennis/main
Inventory Deltas + Asset Change History
2 parents c6368f4 + 2522cd4 commit 5d5691d

File tree

4 files changed

+22
-1
lines changed

4 files changed

+22
-1
lines changed
149 KB
Loading
144 KB
Loading

articles/external-attack-surface-management/understanding-asset-details.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -259,6 +259,16 @@ The following fields are included in the table in the **Values** section on the
259259

260260
Many organizations opt to obfuscate their registry information. Sometimes contact email addresses end in *@anonymised.email*. This placeholder is used instead of a real contact address. Many fields are optional during registration configuration, so any field with an empty value wasn't included by the registrant.
261261

262+
263+
264+
### Change history
265+
266+
The "Change history" tab displays a list of modifications that have been applied to an asset over time. This information helps you track these changes over time and better understand the lifecycle of the asset. This tab displays a variety of changes, including but not limited to asset states, labels and external IDs. For each change, we list the user who implemented the change and a timestamp.
267+
268+
[ ![Screenshot that shows the Change history tab.](media/change-history-1.png) ](media/change-history-1.png#lightbox)
269+
270+
271+
262272
## Next steps
263273

264274
- [Understand dashboards](understanding-dashboards.md)

articles/external-attack-surface-management/understanding-inventory-assets.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,19 @@ All assets are labeled as one of the following states:
4646

4747
These asset states are uniquely processed and monitored to ensure that customers have clear visibility into the most critical assets by default. For instance, “Approved Inventory” assets are always represented in dashboard charts and are scanned daily to ensure data recency. All other kinds of assets are not included in dashboard charts by default; however, users can adjust their inventory filters to view assets in different states as needed. Similarly, "Candidate” assets are only scanned during the discovery process; it’s important to review these assets and change their state to “Approved Inventory” if they are owned by your organization.
4848

49+
50+
## Tracking inventory changes
51+
52+
Your attack surface is constantly changing, which is why Defender EASM continuously analyzes and updates your inventory to ensure accuracy. Assets are frequently added and removed from inventory, so it's important to track these changes to understand your attack surface and identify key trends. The inventory changes dashboard provides an overview of these changes, displaying the "added" and "removed" counts for each asset type. You can filter the dashboard by two date ranges: either the last 7 or 30 days. For a more granular view of these inventory changes, refer to the "Changes by date" section.
53+
54+
55+
[ ![Screenshot of Inventory Changes screen.](media/inventory-changes-1.png)](media/inventory-changes-1.png#lightbox)
56+
57+
58+
59+
4960
## Next steps
5061

51-
- [Deploying the EASM Azure resource](deploying-the-defender-easm-azure-resource.md)
62+
- [Modifying inventory assets](labeling-inventory-assets.md)
5263
- [Understanding asset details](understanding-asset-details.md)
5364
- [Using and managing discovery](using-and-managing-discovery.md)

0 commit comments

Comments
 (0)