Skip to content

Commit c647591

Browse files
author
Ken Lawson
committed
Fixed minor MD issues and improved Acrolinx scores.
1 parent 43ac2b1 commit c647591

12 files changed

+48
-61
lines changed

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/1-introduction.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Introduction
44
metadata:
55
title: Introduction
66
description: "Introduction."
7-
ms.date: 05/10/2023
8-
author: wwlpublish
7+
ms.date: 04/28/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
durationInMinutes: 3

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/2-explore-extended-detection-response-use-cases.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Explore Extended Detection & Response (XDR) response use cases
44
metadata:
55
title: Explore Extended Detection & Response (XDR) response use cases
66
description: "Explore Extended Detection & Response (XDR) response use cases"
7-
ms.date: 05/10/2023
8-
author: wwlpublish
7+
ms.date: 04/28/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
durationInMinutes: 3

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/3-understand-defender-security-operations-center.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Understand Microsoft Defender XDR in a Security Operations Center (SOC)
44
metadata:
55
title: Understand Microsoft Defender XDR in a Security Operations Center (SOC)
66
description: "Understand Microsoft Defender XDR in a Security Operations Center (SOC)"
7-
ms.date: 05/10/2023
8-
author: wwlpublish
7+
ms.date: 04/28/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
durationInMinutes: 3

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/4-explore-microsoft-security-graph.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Explore Microsoft Security Graph
44
metadata:
55
title: Explore Microsoft Security Graph
66
description: "Explore the Microsoft Security Graph."
7-
ms.date: 5/31/2023
8-
author: wwlpublish
7+
ms.date: 04/28/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
durationInMinutes: 10

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/5-investigate-security-incident-defender.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ title: Investigate security incidents in Microsoft Defender XDR
44
metadata:
55
title: Investigate security incidents in Microsoft Defender XDR
66
description: "Investigate security incidents in Microsoft Defender XDR"
7-
ms.date: 05/10/2023
8-
author: wwlpublish
7+
ms.date: 04/28/2025
8+
author: KenMAG
99
ms.author: kelawson
1010
ms.topic: unit
1111
durationInMinutes: 3

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/includes/1-introduction.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,10 @@ In the sample attack chain graphic example, see the attacker activity visible to
66
:::image type="content" source="../media/defend-attack-chains.png" alt-text="Diagram of Microsoft Defender XDR tools to defend across attack chains.":::
77

88
You're a Security Operations Analyst working at a company that is implementing Microsoft Defender XDR solutions. You need to understand how Extended Detection and Response (XDR) combines signals from:
9-
- endpoints
10-
- identity
11-
- email
12-
- applications
9+
10+
- endpoints
11+
- identity
12+
- email
13+
- applications
1314

1415
to detect and mitigate threats.

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/includes/2-explore-extended-detection-response-use-cases.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Restore Access – Once the infected devices are remediated, MDE signals Intune
2323
Remediate Threat Variants in MDO and others – The threat signals in Microsoft Threat intelligence are used by Microsoft tools securing other parts of your organization’s attack surface. MDO and Microsoft Defender for Cloud use the signals to detect and remediate threats in email, office collaboration, Azure, and more.
2424

2525

26-
## from the previous graphic when the user’s device was still compromised
26+
## From the previous graphic when the user’s device was still compromised
2727

2828
:::image type="content" source="../media/suspend-access-compromise.png" alt-text="Diagram of steps to Suspend access during compromise.":::
2929

@@ -38,4 +38,3 @@ During this time, the user is restricted from accessing corporate resources. Thi
3838
Once the threat has been remediated and cleaned up, MDE triggers Intune to update Microsoft Entra ID, and Conditional Access restores the user’s access to corporate resources.
3939

4040
This mitigates risk to the organization by ensuring attackers who might be in control of these devices can't access corporate resources, while minimizing the impact on user productivity to minimize disruption of business processes.
41-

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/includes/3-understand-defender-security-operations-center.md

Lines changed: 14 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,72 +1,61 @@
1-
2-
The following graphic provides an overview of how Microsoft Defender XDR and Microsoft Sentinel are integrated in a Modern Security Operations Center (SOC).
1+
The following graphic provides an overview of how Microsoft Defender XDR and Microsoft Sentinel are integrated in a Modern Security Operations Center (SOC).
32

43
:::image type="content" source="../media/security-operations.png" alt-text="Diagram that shows the layers and technologies of Security Operations.":::
54

6-
7-
85
## Security Operations Model - Functions and Tools
96

10-
11-
127
While the assignment of responsibilities to individual people and teams vary based on organization size and other factors, security operations are composed of several distinct functions. Each function/team has a primary focus area and also must collaborate closely with other functions and outside teams to be effective. This diagram depicts the full model with fully staffed teams. In smaller organizations, these functions are often combined into a single role or team, performed by IT Operations (for technical roles), or are performed as a temporary function by leadership/delegates (for incident management)
138

14-
> [!NOTE]
15-
> We primarily refer to the analysts by the team name, not the Tier numbers as these teams each have unique specialized skills, they are not a literal ranking/hierarchical of value.
16-
9+
> [!NOTE]
10+
> We primarily refer to the analysts by the team name, not the Tier numbers as these teams each have unique specialized skills, they aren't a literal ranking/hierarchical of value.
1711
1812
:::image type="content" source="../media/security-operations-model.png" alt-text="Diagram that shows the Security Operations Model with functions and tools.":::
1913

20-
21-
22-
2314
### Triage and Automation
2415

25-
We'll start with handling reactive alerts – which begins with:
16+
We start with handling reactive alerts – which begins with:
2617

2718
- **Automation** – Near real-time resolution of known incident types with automation. These are well-defined attacks that the organization has seen many times.
28-
- **Triage (aka Tier 1)** –Triage analysts focus on rapid remediation of a high volume of well-known incident types that still require (quick) human judgment. These are often tasked with approving automated remediation workflows and identifying anything anomalous or interesting that warrant escalation or consultation with investigation (Tier 2) teams.
19+
- **Triage (aka Tier 1)** –Triage analysts focus on rapid remediation of a high volume of well-known incident types that still require (quick) human judgment. These are often tasked with approving automated remediation workflows and identifying anything anomalous or interesting that warrant escalation or consultation with investigation (Tier 2) teams.
2920

3021
Key learnings for Triage and Automation:
31-
- **90% true positive** - We recommend setting a quality standard of 90% true positive for any alert feeds that require an analyst to respond so analysts aren’t required to respond to a high volume of false alarms.
32-
- **Alert Ratio** – In Microsoft’s experience from our Cyber Defense Operations Center, XDR alerts produce most of the high-quality alerts, with the remainders coming from user reported issues, classic log query based alerts, and other sources
33-
- **Automation** is a key enabler for triage teams as it helps empower these analysts and reduce the burden of manual effort (for example, provide automated investigation and then prompt them for a human review before approving the remediation sequence that was automatically built for this incident).
34-
- **Tool Integration** - One of the most powerful time saving technologies that improved time to remediation in Microsoft’s CDOC is the integration of XDR tools together into Microsoft Defender XDR so analysts have a single console for endpoint, email, identity, and more. This integration enables analysts to rapidly discover and clean up attacker phishing emails, malware, and compromised accounts before they can do significant damage.
35-
- **Focus** - These teams can't maintain their high speed of resolution for all types of technologies and scenarios, so they keep their focus narrow on a few technical areas and/or scenarios. Most often this is on user productivity, like email, endpoint AV alerts (versus EDR that goes into investigations), and first response for user reports.
22+
- **90% true positive** - We recommend setting a quality standard of 90% true positive for any alert feeds that require an analyst to respond so analysts aren’t required to respond to a high volume of false alarms.
23+
- **Alert Ratio** – In Microsoft’s experience from our Cyber Defense Operations Center, XDR alerts produce most of the high-quality alerts, with the remainders coming from user reported issues, classic log query based alerts, and other sources
24+
- **Automation** is a key enabler for triage teams as it helps empower these analysts and reduce the burden of manual effort (for example, provide automated investigation and then prompt them for a human review before approving the remediation sequence that was automatically built for this incident).
25+
- **Tool Integration** - One of the most powerful time saving technologies that improved time to remediation in Microsoft’s CDOC is the integration of XDR tools together into Microsoft Defender XDR so analysts have a single console for endpoint, email, identity, and more. This integration enables analysts to rapidly discover and clean up attacker phishing emails, malware, and compromised accounts before they can do significant damage.
26+
- **Focus** - These teams can't maintain their high speed of resolution for all types of technologies and scenarios, so they keep their focus narrow on a few technical areas and/or scenarios. Most often this is on user productivity, like email, endpoint AV alerts (versus EDR that goes into investigations), and first response for user reports.
3627

3728
### Investigation and Incident Management (Tier 2)
3829

3930
This team serves as the escalation point for issues from Triage (Tier 1), and directly monitors alerts that indicate a more sophisticated attacker. Specifically alerts that trigger behavioral alerts, special case alerts related to business-critical assets, and monitoring for ongoing attack campaigns. Proactively, this team also periodically reviews the Triage team alert queue and can proactively hunt using XDR tools in their spare time.
4031

41-
This team provides deeper investigation into a lower volume of more complex attacks, often multi-stage attacks conducted by human attack operators. This team pilots new/unfamiliar alert types to document processes for Triage team and automation, often including alerts generated by Microsoft Defender for Cloud on cloud hosted apps, VMs, containers and Kubernetes, SQL databases, etc.
32+
This team provides deeper investigation into a lower volume of more complex attacks, often multi-stage attacks conducted by human attack operators. This team pilots new/unfamiliar alert types to document processes for Triage team and automation, often including alerts generated by Microsoft Defender for Cloud on cloud hosted apps, VMs, containers, and Kubernetes, SQL databases, etc.
4233

4334
**Incident Management** – This team takes on the nontechnical aspects of managing incidents including coordination with other teams like communications, legal, leadership, and other business stakeholders.
4435

45-
4636
### Hunt and Incident Management (Tier 3)
4737

4838
This is a multi-disciplinary team focused on identifying attackers that could have slipped through the reactive detections and handling major business-impacting events.
4939

5040
- **Hunt** – This team proactively hunts for undetected threats, assists with escalations and advanced forensics for reactive investigations, and refines alerts/automation. These teams operate in more of a hypothesis-driven model than a reactive alert model and are also where red/purple teams connect with security operations.
5141

52-
53-
### How It Comes Together
42+
### How It Comes Together
5443

5544
To give you an idea of how this works, let’s follow a common incident lifecycle
5645

5746
1. **Triage (Tier 1)** analyst claims a malware alert from the queue and investigates (for example, with Microsoft Defender XDR console)
5847
1. While most Triage cases are rapidly remediated and closed, this time the analyst observes that malware might require more involved/advanced remediation (for example, device isolation and cleanup). Triage escalates the case to the Investigation analyst (Tier 2), who takes lead for investigation. The Triage team has option to stay involved and learn more (Investigation team might use Microsoft Sentinel or another SIEM for broader context)
59-
1. **Investigation** verifies investigation conclusions (or digs further into it) and proceeds with remediation, closes case.
48+
1. **Investigation** verifies investigation conclusions (or digs further into it) and proceeds with remediation, closes case.
6049
1. Later, **Hunt (Tier 3)** might notice this case while reviewing closed incidents to scan for commonalities or anomalies worth digging into:
6150
- Detections that might be eligible for autoremediation
6251
- Multiple similar incidents that might have a common root cause
6352
- Other potential process/tool/alert improvements
6453
In one case, Tier 3 reviewed the case and found that the user had fallen for a tech scam. This detection was then flagged as a potentially higher priority alert because the scammers had managed to get admin level access on the endpoint. A higher risk exposure.
6554

66-
6755
### Threat intelligence
6856

6957
**Threat Intelligence teams** provide context and insights to support all other functions (using a threat intelligence platform (TIP) in larger organizations). This could include many different facets including
58+
7059
- Reactive technical research for active incidents
7160
- Proactive technical research into attacker groups, attack trends, high profile attacks, emerging techniques, etc.
7261
- Strategic analysis, research, and insights to inform business and technical processes and priorities.

learn-pr/wwl-sci/introduction-microsoft-365-threat-protection/includes/4-explore-microsoft-security-graph.md

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
Microsoft Graph provides a unified programmability model that you can use to access the data in Microsoft 365, Windows, and Enterprise Mobility + Security. You can use the data in Microsoft Graph to build customized apps for your organization.
22

3-
The Microsoft Graph API offers a single endpoint, https://graph.microsoft.com (either v1.0 or beta versions). You can use REST APIs or SDKs to access the endpoint and build apps that support Microsoft 365 scenarios. Microsoft Graph also includes a powerful set of services that manage user and device identity, access, compliance, and security and help protect organizations from data leakage or loss.
3+
The Microsoft Graph API offers a single endpoint, <https://graph.microsoft.com> (either v1.0 or beta versions). You can use REST APIs or SDKs to access the endpoint and build apps that support Microsoft 365 scenarios. Microsoft Graph also includes a powerful set of services that manage user and device identity, access, compliance, and security and help protect organizations from data leakage or loss.
44

55
### What's in Microsoft Graph?
66

77
Microsoft Graph exposes REST APIs and client libraries to access data on the following Microsoft cloud services:
88

9-
- Microsoft 365 core services: Bookings, Calendar, Delve, Excel, Microsoft Purview eDiscovery, Microsoft Search, OneDrive, OneNote, Outlook/Exchange, People (Outlook contacts), Planner, SharePoint, Teams, To Do, Viva Insights
10-
- Enterprise Mobility + Security services: *Advanced Threat Analytics*, *Advanced Threat Protection*, Microsoft Entra ID, Identity Manager, and Intune
11-
- Windows services: activities, devices, notifications, Universal Print
12-
- Dynamics 365 Business Central services
9+
- Microsoft 365 core services: Bookings, Calendar, Delve, Excel, Microsoft Purview eDiscovery, Microsoft Search, OneDrive, OneNote, Outlook/Exchange, People (Outlook contacts), Planner, SharePoint, Teams, To Do, Viva Insights
10+
- Enterprise Mobility + Security services: *Advanced Threat Analytics*, *Advanced Threat Protection*, Microsoft Entra ID, Identity Manager, and Intune
11+
- Windows services: activities, devices, notifications, Universal Print
12+
- Dynamics 365 Business Central services
1313

1414
### Microsoft Graph Security API
1515

@@ -19,33 +19,34 @@ The Microsoft Graph security API is an intermediary service (or broker) that pro
1919

2020
Developers can use the Security Graph to build intelligent security services that:
2121

22-
- Integrate and correlate security alerts from multiple sources.
23-
- Stream alerts to security information and event management (SIEM) solutions.
24-
- Automatically send threat indicators to Microsoft security solutions to enable alert, block, or allow actions.
25-
- Unlock contextual data to inform investigations.
26-
- Discover opportunities to learn from the data and train your security solutions.
27-
- Automate SecOps for greater efficiency.
22+
- Integrate and correlate security alerts from multiple sources.
23+
- Stream alerts to security information and event management (SIEM) solutions.
24+
- Automatically send threat indicators to Microsoft security solutions to enable alert, block, or allow actions.
25+
- Unlock contextual data to inform investigations.
26+
- Discover opportunities to learn from the data and train your security solutions.
27+
- Automate SecOps for greater efficiency.
2828

2929
### Use the Microsoft Graph Security API
3030

3131
There are two versions of the Microsoft Graph Security API.
3232

33-
- Microsoft Graph REST API v1.0
34-
- Microsoft Graph REST API Beta
33+
- Microsoft Graph REST API v1.0
34+
- Microsoft Graph REST API Beta
3535

3636
The beta version provides new or enhanced APIs that are still in preview status. APIs in preview status are subject to change, and may break existing scenarios without notice.
3737

3838
For Security Operations Analysts, both Microsoft Graph API versions support advanced hunting using the **runHuntingQuery** method. This method includes a query in Kusto Query Language (KQL).
3939

40-
- Advanced hunting example in Microsoft Defender XDR:
40+
- Advanced hunting example in Microsoft Defender XDR:
4141

42-
```html
42+
```html
4343
POST https://graph.microsoft.com/v1.0/security/runHuntingQuery
4444

4545
{
4646
"Query": "DeviceProcessEvents | where InitiatingProcessFileName =~ \"powershell.exe\" | project Timestamp, FileName, InitiatingProcessFileName | order by Timestamp desc | limit 2"
4747
}
4848
```
49+
4950
You can use [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) to run the hunting query:
5051

5152
:::image type="content" source="../media/graph-explorer-hunting-kql-query-2023-06-08.png" alt-text="Screenshot of the Microsoft Graph Explorer running the KQL hunting query.":::
Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11

22
The following cloud guide demonstrates Microsoft Defender XDR and Microsoft Sentinel working together to investigate a security incident in a hybrid environment.
33

4-
54
[Launch Investigate Security Incident](https://mslearn.cloudguides.com/guides/Investigate%20security%20incidents%20in%20a%20hybrid%20environment%20with%20Azure%20Sentinel)

0 commit comments

Comments
 (0)