Skip to content

Commit f13e80e

Browse files
authored
Merge pull request #5621 from limwainstein/new-mdvm-recommendations
Secure score recommendations - GA
2 parents 4e92f18 + 2c72232 commit f13e80e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

defender-vulnerability-management/whats-new-in-microsoft-defender-vulnerability-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This article provides information about new features and important product updat
2626
## November 2025
2727

2828
- (Preview) The **Vulnerability Management** section in the Microsoft Defender portal is now located under **Exposure management**. This change is part of the vulnerability management integration to Microsoft Security Exposure Management, which significantly expands the scope and capabilities of the platform. [Learn more](#microsoft-defender-vulnerability-management-and-microsoft-security-exposure-management-integration).
29-
- (Preview) **Microsoft Secure Score now includes new recommendations** to help organizations proactively prevent common endpoint attack techniques.
29+
- (GA) **Microsoft Secure Score now includes new recommendations** to help organizations proactively prevent common endpoint attack techniques.
3030
- **Require LDAP client signing** and **Require LDAP server signing** - help ensure integrity of directory requests so attackers can't tamper with or manipulate group memberships or permissions in transit.
3131
- **Encrypt LDAP client traffic** - prevents exposure of credentials and sensitive user information by enforcing encrypted communication instead of clear-text LDAP.
3232
- **Enforce LDAP channel binding** - prevents man-in-the-middle relay attacks by ensuring the authentication is cryptographically tied to the TLS session. If the TLS channel changes, the bind fails, stopping credential replay.

0 commit comments

Comments
 (0)