Skip to content

Commit 2c72232

Browse files
committed
Fixing conflict
1 parent 641ac93 commit 2c72232

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,8 @@ This article provides information about new features and important product updat
2525
2626
## November 2025
2727

28-
- (GA) **Microsoft Secure Score now includes new recommendations** to help organizations proactively prevent common endpoint attack techniques.
2928
- (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).
30-
- (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.
3130
- **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.
3231
- **Encrypt LDAP client traffic** - prevents exposure of credentials and sensitive user information by enforcing encrypted communication instead of clear-text LDAP.
3332
- **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)