Skip to content

Commit 2a2582b

Browse files
authored
Merge branch 'main' into docs-editor/governance-actions-1756026617
2 parents 677045d + f5f6be2 commit 2a2582b

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

ATPDocs/unmonitored-active-directory-federation-services-servers.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,7 @@ This article describes the Microsoft Defender for Identity's unmonitored Active
1818
Unmonitored Active Directory Federation Services (ADFS) servers are a significant security risk to organizations. ADFS controls access to both cloud and on-premises resources as the gateway for federated authentication and single sign-on. If attackers compromise an ADFS server, they can issue forged tokens and impersonate any user, including privileged accounts. Such attacks might bypass multi-factor authentication (MFA), conditional access, and other downstream security controls, making them particularly dangerous. Without proper monitoring, suspicious activity on ADFS servers might go undetected for extended periods. Deploying Microsoft Defender for Identity version 2.0 sensors on ADFS servers is essential. These sensors enable real-time detection of suspicious behavior and help prevent token forgery, abuse of trust relationships, and stealthy lateral movement within the environment.
1919

2020
> [!NOTE]
21-
> This security assessment is only available if Microsoft Defender for Endpoint detects an eligible ADFS server in the environment.
22-
21+
> This security assessment is only available if Microsoft Defender for Endpoint detects eligible ADFS servers in the environment. In some cases, servers running ADFS might not be identified with the required role and therefore will not appear in this assessment, even if they exist in the environment.
2322
2423
## How do I use this security assessment?
2524

0 commit comments

Comments
 (0)