Merge pull request #4994 from MicrosoftDocs/main

[AutoPublish] main to live - 09/10 07:31 PDT | 09/10 20:01 IST

Author: m365-skilling-repo-management[bot]

ATPDocs/whats-new.md

@@ -25,6 +25,18 @@ For updates about versions and features released six months ago or earlier, see
 
 ## September 2025
 
+### New API support for unified agent 
+We are excited to announce the availability of a new Graph-based API for managing unified agent server actions in Microsoft Defender for Identity.
+This capability is currently in preview and available in API Beta version.
+
+This API allows customers to:
+
+* Monitor the status of unified agent servers
+* Enable or disable the automatic activation of eligible servers
+* Activate or deactivate the agent on eligible servers
+ ​
+For more information, see [Managing response actions through Graph API](/graph/api/resources/security-api-overview?view=graph-rest-beta).
+
 ### Microsoft Defender for Identity sensor version updates
 
 |Version number |Updates |

defender-vulnerability-management/fixed-reported-inaccuracies.md

@@ -33,6 +33,13 @@ This article provides information on inaccuracies that have been reported. You c
  
 The following tables present the relevant vulnerability information organized by month.
 
+## September 2025
+
+| Inaccuracy report ID | Description | Fix date |
+|---|---|---|
+| - | Added MDVM support for Zoom vulnerability- CVE-2025-49457 | 03-September-25 |
+| - | Added MDVM support for 8 Tableau Server vulnerabilities- CVE-2025-52446, CVE-2025-52447, CVE-2025-52448, CVE-2025-52449, CVE-2025-52452, CVE-2025-52453, CVE-2025-52454 and CVE-2025-52455 | 09-September-25 |
+
 ## August 2025
 
 | Inaccuracy report ID | Description | Fix date |
@@ -50,6 +57,15 @@ The following tables present the relevant vulnerability information organized by
 | 109858 | Fixed inaccuracy in Microsoft SQL Server Management Studio vulnerability- CVE-2025-29803 | 21-August-25 |
 | - | Updated CPE detection logic for Cisco Identity Services Engine | 26-August-25 |
 | - | Fixed inaccuracy in VMware Fusion vulnerability- CVE-2025-41236 | 26-August-25 |
+| 105343 | Fixed bad normalization in Elasticsearch Enterprise Search | 26-August-25 |
+| - | Fixed Publisher data to improve accuracy for pgAdmin | 26-August-25 |
+| 111784 | Added MDVM support for BambuLab Bambu Studio | 26-August-25 |
+| - | Fixed bad normalization in Microsoft Excel | 26-August-25 |
+| 110983 | Added MDVM support for Sigmatek Sigmanest | 26-August-25 |
+| 110984 | Added MDVM support for Sigmatek License Server | 26-August-25 |
+| - | Added MDVM support for Microsoft Privilege Management For Windows | 26-August-25 |
+| - | Improved accuracy for Dell SupportAssistOSRecovery | 26-August-25 |
+| - | Updated CVE-2025-55229, CVE-2025-55230 and CVE-2025-55231 with accurate vulnerability details | 28-August-25 |
 
 ## July 2025
 

exposure-management/classify-critical-assets.md

@@ -6,7 +6,7 @@ author: dlanger
 manager: ornat-spodek
 ms.topic: overview
 ms.service: exposure-management
-ms.date: 07/23/2025
+ms.date: 09/08/2025
 ---
 
 # Review and classify critical assets
@@ -34,6 +34,9 @@ Impact analysis and crown jewels analysis are essential methodologies for identi
 
 The NIST Cybersecurity Framework (CSF) 800-53 also emphasizes guidance for asset management and criticality analysis, as outlined in ID.AM-05, which can be found at: [https://csf.tools/reference/nist-cybersecurity-framework/v2-0/id/id-am/id-am-05/](https://csf.tools/reference/nist-cybersecurity-framework/v2-0/id/id-am/id-am-05/).
 
+> [!NOTE]
+> When multiple classification rules apply to an asset, the rule with the highest criticality level takes precedence. This classification remains in effect until the asset no longer meets the criteria for that rule, at which point it will automatically revert to the next applicable classification level.
+
 ## Prerequisites
 
 Before you begin, ensure you meet the following requirements for working with critical assets in Microsoft Security Exposure Management.

exposure-management/predefined-classification-rules-and-levels.md

@@ -25,6 +25,10 @@ Current asset types are:
 
 > [!Note]
 > The critical asset out-of-the-box classification logic classifies your assets based on asset behavior accumulated from Microsoft Defender workloads and  third-party integrations set up in your environment.
+> 
+> When multiple classification rules apply to an asset, the rule with the highest criticality level takes precedence. This classification remains in effect until the asset no longer meets the criteria for that rule, at which point it will automatically revert to the next applicable classification level.
+
+
 
 ##### Device