Skip to content

Commit 0538b58

Browse files
authored
Merge branch 'main' into docs-editor/dex-xdr-overview-1721255716
2 parents 1e9b83f + cfa24c7 commit 0538b58

File tree

3 files changed

+10
-3
lines changed

3 files changed

+10
-3
lines changed

defender-endpoint/comprehensive-guidance-on-linux-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ The following table lists the supported proxy settings:
130130

131131
#### Step 3: Verify SSL inspection isn't being performed on the network traffic
132132

133-
To prevent man-in-the-middle attacks, all Microsoft Azure hosted traffic uses certificate pinning. As a result, SSL inspections by major firewall systems aren't allowed. You must bypass SSL inspection for Microsoft Defender for Endpoint URLs. For additional information about the certificate pinning process, see [enterprise-certificate-pinning] (/windows/security/identity-protection/enterprise-certificate-pinning).
133+
To prevent man-in-the-middle attacks, all Microsoft Azure hosted traffic uses certificate pinning. As a result, SSL inspections by major firewall systems aren't allowed. You must bypass SSL inspection for Microsoft Defender for Endpoint URLs. For additional information about the certificate pinning process, see [enterprise-certificate-pinning](/windows/security/identity-protection/enterprise-certificate-pinning).
134134

135135
##### Troubleshoot cloud connectivity issues
136136

defender-xdr/automatic-attack-disruption.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.topic: conceptual
1818
search.appverid:
1919
- MOE150
2020
- MET150
21-
ms.date: 05/29/2024
21+
ms.date: 09/11/2024
2222
---
2323

2424
# Automatic attack disruption in Microsoft Defender XDR
@@ -65,7 +65,13 @@ Automatic attack disruption uses Microsoft-based XDR response actions. Examples
6565

6666
- [Device contain](/defender-endpoint/respond-machine-alerts#contain-devices-from-the-network) - based on Microsoft Defender for Endpoint's capability, this action is an automatic containment of a suspicious device to block any incoming/outgoing communication with the said device.
6767

68-
- [Disable user](/defender-for-identity/remediation-actions) - based on Microsoft Defender for Identity's capability, this action is an automatic suspension of a compromised account to prevent additional damage like lateral movement, malicious mailbox use, or malware execution.
68+
- [Disable user](/defender-for-identity/remediation-actions) - based on Microsoft Defender for Identity's capability, this action is an automatic suspension of a compromised account to prevent additional damage like lateral movement, malicious mailbox use, or malware execution. The disable user action behaves differently depending on how the user is hosted in your environment.
69+
- When the user account is hosted in Active Directory: Defender for Identity triggers the disable user action on domain controllers running the Defender for Identity agent.
70+
- When the user account is hosted in Active Directory and is synced on Microsoft Entra ID: Defender for Identity triggers the disable user action via onboarded domain controllers. Attack disruption also disables the user account on the Entra ID synced account.
71+
- When the user account is hosted in Entra ID only (cloud native account): attack disruption disable the user account on the Entra ID synced account.
72+
73+
> [!NOTE]
74+
> Disabling the user account in Microsoft Entra ID is not dependent on the deployment of Microsoft Defender for Identity.
6975
7076
- [Contain user](/defender-endpoint/respond-machine-alerts#contain-user-from-the-network) - based on Microsoft Defender for Endpoint's capability, this response action automatically contains suspicious identities temporarily to help block any lateral movement and remote encryption related to incoming communication with Defender for Endpoint's onboarded devices.
7177

exposure-management/whats-new.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ Security Exposure Management is currently in public preview.
3232
Read how the *ExposureGraphEdges* and *ExposureGraphNodes* tables in Advanced Hunting helps your organizations proactively manage and understand your security posture by analyzing asset relationships and potential vulnerabilities.
3333

3434
**Blog** - [Microsoft Security Exposure Management Graph: Prioritization is the king](https://techcommunity.microsoft.com/t5/security-compliance-and-identity/microsoft-security-exposure-management-graph-prioritization-is/ba-p/4160316)
35+
3536
For more information, see, [Query the enterprise exposure graph](query-enterprise-exposure-graph.md)
3637

3738
## August 2024

0 commit comments

Comments
 (0)