Skip to content

Commit 72ced92

Browse files
authored
Merge pull request #3518 from MicrosoftDocs/diannegali-xdrfreshnessapril
freshness review
2 parents 5a9fdd6 + 259f87b commit 72ced92

20 files changed

+76
-98
lines changed

defender-xdr/alert-classification-malicious-exchange-connectors.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Alert classification for malicious exchange connectors
3-
description: Alert grading recipients from malicious exchange connectors activity and protect their network from malicious attack.
2+
title: Alert classification for malicious Exchange connectors
3+
description: Learn how to classify alerts on malicious Exchange connectors activity and protect your network from attacks.
44
ms.service: defender-xdr
55
f1.keywords:
66
- NOCSH
@@ -17,7 +17,7 @@ ms.topic: how-to
1717
search.appverid:
1818
- MOE150
1919
- MET150
20-
ms.date: 03/11/2024
20+
ms.date: 04/18/2025
2121
appliesto:
2222
- Microsoft Defender XDR
2323
#customer intent: As a SOC analyst, I want to know how to investigate and classify alerts for malicious Exchange connectors so that I can take the necessary actions to remediate the attack and protect my network.
@@ -27,7 +27,7 @@ appliesto:
2727

2828
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
2929

30-
Threat actors use compromised exchange connectors for sending out spam and phishing emails in bulk to unsuspecting recipients by masquerading legitimate emails. Since the connector is compromised, the emails would usually be trusted by the recipients. These kinds of phishing emails are common vectors for phishing campaigns, and business email compromise (BEC) scenario. Hence, such emails need to be monitored heavily due to the likelihood of successful recipients' compromises being high.
30+
Threat actors use compromised Microsoft Exchange connectors for sending out spam and phishing emails in bulk to unsuspecting recipients by masquerading legitimate emails. Since the connector is compromised, the emails would usually be trusted by the recipients. These kinds of phishing emails are common vectors for phishing campaigns, and business email compromise (BEC) scenario. Hence, such emails need to be monitored heavily due to the likelihood of successful recipients' compromises being high.
3131

3232
This playbook helps in investigating instances where malicious connectors are setup/deployed by malicious actors. Accordingly, they take necessary steps to remediate the attack and mitigate the security risks arising from it. The playbook helps in classifying the alerts as either true positive (TP) or false positive (FP). If alerts are TP, the playbook lists necessary recommended actions for remediating the attack. This playbook is available for security teams who review, handle/manage, and grade the alerts.
3333

@@ -44,15 +44,15 @@ Connectors are used to route mail traffic between remote email systems and Offic
4444

4545
### Malicious Exchange connectors
4646

47-
Attackers may compromise an existing exchange connector or compromise an admin, and set up a new connector by sending phish or spam/bulk emails.
47+
Attackers may compromise an existing Exchange connector or compromise an admin, and set up a new connector by sending phish or spam/bulk emails.
4848

4949
The typical indicators of a malicious connector can be found when looking at email traffic and its headers. For example, when email traffic is observed from a connector node with a mismatch in P1 (header sender) and P2 (envelope sender) sender addresses along with no information on Sender's AccountObjectId.
5050

5151
This alert tries to identify such instances of mail flow, wherein the mail sending activity seems suspicious adding to that relevant information on sender is unavailable.
5252

5353
## Playbook workflow
5454

55-
You must follow the sequence to identify malicious exchange connectors:
55+
You must follow the sequence to identify malicious Exchange connectors:
5656

5757
- Identify which accounts are sending emails:
5858
- Do accounts appear to be compromised?
@@ -69,7 +69,7 @@ You must follow the sequence to identify malicious exchange connectors:
6969
This section describes the steps to investigate an alert and remediate the security risk due to this incident.
7070

7171
- Determine whether the connector demonstrates bad (malicious) behavior.
72-
- Look for events indicating unusual mail traffic and identify, whether any new exchange connector was added recently.
72+
- Look for events indicating unusual mail traffic and identify, whether any new and recently added Exchange connector.
7373
- For mail traffic observed, determine if the email accounts are compromised by inspecting whether the accounts are responsible for unusual mail traffic.
7474
- Look for mail content containing malicious artifacts (bad links/attachments).
7575
- Look for domains that are not part of your environment.

defender-xdr/alert-classification-password-spray-attack.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.topic: how-to
1717
search.appverid:
1818
- MOE150
1919
- met150
20-
ms.date: 02/11/2024
20+
ms.date: 04/18/2025
2121
appliesto:
2222
- Microsoft Defender XDR
2323
#customer intent: As a SOC analyst, I want to know how to investigate and classify alerts for password spray attacks so that I can take the necessary actions to remediate the attack and protect my network.

defender-xdr/alert-classification-playbooks.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.custom:
1818
- autoir
1919
- admindeeplinkDEFENDER
2020
ms.reviewer: evaldm, isco
21-
ms.date: 02/11/2024
21+
ms.date: 04/18/2025
2222
appliesto:
2323
- Microsoft Defender XDR
2424
#customer intent: As a SOC analyst, I want to know how to review and classify alerts by using alert classification playbooks so that I can take the necessary actions to remediate the attack and protect my network.
@@ -89,6 +89,7 @@ See these playbooks for steps to more quickly classify alerts for the following
8989
- [Suspicious inbox forwarding rules](alert-grading-playbook-inbox-forwarding-rules.md)
9090
- [Suspicious IP addresses related to password spray activity](alert-classification-suspicious-ip-password-spray.md)
9191
- [Password spray attacks](alert-classification-password-spray-attack.md)
92+
- [Malicious Exchange connectors](alert-classification-malicious-exchange-connectors.md)
9293

9394
See [Investigate alerts](investigate-alerts.md) for information on how to examine alerts with the Microsoft Defender portal.
9495
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

defender-xdr/alert-classification-suspicious-ip-password-spray.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Alert classification for suspicious IP address related to password spraying activity
3-
description: Alert classification for suspicious IP address related to password spraying activity to review the alerts and take recommended actions to remediate the attack and protect your network.
3+
description: Investigate and review alerts related to suspicious IP address related to password spraying activity and take recommended actions to protect your network.
44
ms.service: defender-xdr
55
f1.keywords:
66
- NOCSH
@@ -17,7 +17,7 @@ ms.topic: how-to
1717
search.appverid:
1818
- MOE150
1919
- met150
20-
ms.date: 02/11/2024
20+
ms.date: 04/18/2025
2121
appliesto:
2222
- Microsoft Defender XDR
2323
#customer intent: As a SOC analyst, I want to know how to investigate and classify alerts for suspicious IP addresses related to password spray attacks that I can take the necessary actions to remediate the attack and protect my network.

defender-xdr/alert-grading-playbook-email-forwarding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.topic: how-to
1717
search.appverid:
1818
- MOE150
1919
- met150
20-
ms.date: 04/03/2024
20+
ms.date: 04/18/2025
2121
appliesto:
2222
- Microsoft Defender XDR
2323
#customer intent: As a SOC analyst, I want to know how to review and classify alerts about suspicious email forwarding activity so that I can take the necessary actions to remediate the attack and protect my network.

defender-xdr/alert-grading-playbook-inbox-forwarding-rules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.topic: how-to
1717
search.appverid:
1818
- MOE150
1919
- met150
20-
ms.date: 07/26/2024
20+
ms.date: 04/18/2025
2121
appliesto:
2222
- Microsoft Defender XDR
2323
#customer intent: As a SOC analyst, I want to know how to review and classify suspicious inbox forwarding rules alerts so that I can take the necessary actions to remediate the attack and protect my network.

defender-xdr/alert-grading-playbook-inbox-manipulation-rules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.topic: how-to
1717
search.appverid:
1818
- MOE150
1919
- met150
20-
ms.date: 04/05/2023
20+
ms.date: 04/18/2025
2121
appliesto:
2222
- Microsoft Defender XDR
2323
#customer intent: As a SOC analyst, I want to know how to review and classify suspicious inbox manipulation rules alerts so that I can take the necessary actions to remediate the attack and protect my network.

defender-xdr/api-access.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,17 +18,15 @@ search.appverid:
1818
- MOE150
1919
- MET150
2020
ms.custom: api
21-
ms.date: 02/08/2024
21+
ms.date: 04/15/2025
22+
appliesto:
23+
- Microsoft Defender XDR
2224
---
2325

2426
# Access the Microsoft Defender XDR APIs
2527

2628
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
2729

28-
**Applies to:**
29-
30-
- Microsoft Defender XDR
31-
3230
> [!NOTE]
3331
> **Try our new APIs using MS Graph security API**. Find out more at: [Use the Microsoft Graph security API - Microsoft Graph | Microsoft Learn](/graph/api/resources/security-api-overview).
3432

defender-xdr/api-advanced-hunting.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,17 +18,15 @@ search.appverid:
1818
- MOE150
1919
- MET150
2020
ms.custom: api
21-
ms.date: 04/01/2024
21+
ms.date: 04/18/2025
22+
appliesto:
23+
- Microsoft Defender XDR
2224
---
2325

2426
# Microsoft Defender XDR Advanced hunting API
2527

2628
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
2729

28-
**Applies to:**
29-
30-
- Microsoft Defender XDR
31-
3230
> [!WARNING]
3331
> This advanced hunting API is an older version with limited capabilities. A more comprehensive version of the advanced hunting API is already available in the **[Microsoft Graph security API](/graph/api/resources/security-api-overview)**. See **[Advanced hunting using Microsoft Graph security API](/graph/api/resources/security-api-overview#advanced-hunting)**
3432

defender-xdr/api-articles.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,8 @@ ms.date: 02/08/2024
3737
3838
The following resources provide more information about APIs available for other Microsoft security solutions, beyond the Microsoft Defender XDR API.
3939

40-
- [Microsoft Defender for Endpoint](/windows/security/threat-protection/microsoft-defender-atp/apis-intro)
40+
- [Microsoft Defender for Endpoint](/defender-endpoint/api/apis-intro)
4141
- [Microsoft Defender for Office 365](/office/office-365-management-api/)
4242
- [Microsoft Defender for Cloud Apps](/cloud-app-security/api-introduction)
43+
4344
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]

0 commit comments

Comments
 (0)