Skip to content

Commit 98dd417

Browse files
committed
Merge branch 'main' into release-sentinel-only
2 parents d55e089 + 3f974f8 commit 98dd417

File tree

76 files changed

+980
-162
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

76 files changed

+980
-162
lines changed

defender-endpoint/machines-view-overview.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,6 +136,7 @@ The available device properties to use as filters vary based on the device inven
136136
|**Device subtype**|<ul><li>**All devices**</li><li>**IoT/OT**</li></ul>|The subtype value assigned to the device. Enter a value or select an available value (for example, **Video conference**).|
137137
|**Device type**|<ul><li>**All devices**</li><li>**IoT/OT**</li></ul>|The type value assigned to the device. Enter a value or select an available value (for example, **Audio and Video**).|
138138
|**Device value**|All|The assigned value of the device. The available values are **High** and **Low**.|
139+
|**Discovery sources**|All|The source reporting on the device.|
139140
|**Exclusion state**|All|The available values are **Not excluded** and **Excluded**. For more information, see [Exclude devices](exclude-devices.md).|
140141
|**Exposure level**|All|The exposure level of the device based on pending security recommendations. The available values are: <ul><li>**High**</li><li>**Medium**</li><li>**Low**: Devices are less vulnerable to exploitation.</li><li>**No data available**: Possible causes for this value include: <ul><li>The device is inactive (stopped reporting for more than 30 days).</li><li>The OS on the device isn't supported. For more information, see [minimum requirements for Microsoft Defender for Endpoint](minimum-requirements.md).</li><li>The agent software on the device is stale (unlikely).</li></ul></li></ul>|
141142
|**First seen**|All tabs except **Network devices**|How long ago the device was first seen on the network or when it was first reported by the Microsoft Defender for Endpoint sensor. The available values are **Last 7 days** or **Over 7 days ago**.|
@@ -178,6 +179,7 @@ You can sort the entries by clicking on an available column header. Select :::im
178179
- **OS version**<sup\*</sup>
179180
- **Sensor health state**<sup\*</sup>
180181
- **Onboarding status**<sup\*</sup>
182+
- **Discovery sources**
181183
- **First seen**
182184
- **Last device update**<sup\*</sup>
183185
- **Tags**<sup\*</sup>
@@ -204,6 +206,7 @@ You can sort the entries by clicking on an available column header. Select :::im
204206
- **Criticality level**<sup\*</sup>
205207
- **Sensor health state**<sup\*</sup>
206208
- **Onboarding status**<sup\*</sup>
209+
- **Discovery sources**
207210
- **Last device update**<sup\*</sup>
208211
- **First seen**
209212
- **Tags**<sup\*</sup>
@@ -219,6 +222,7 @@ You can sort the entries by clicking on an available column header. Select :::im
219222
- **Vendor**<sup>\*</sup>
220223
- **Model**<sup>\*</sup>
221224
- **Name**<sup>\*</sup>
225+
- **Discovery sources**
222226
- **Domain**
223227
- **Device type**
224228
- **Device subtype**
@@ -241,6 +245,7 @@ You can sort the entries by clicking on an available column header. Select :::im
241245
- **Model**<sup>\*</sup>
242246
- **Risk level**<sup>\*</sup>
243247
- **Exposure level**<sup>\*</sup>
248+
- **Discovery sources**
244249
- **OS distribution**<sup>\*</sup>
245250
- **OS version**<sup>\*</sup>
246251
- **First seen**
@@ -253,6 +258,7 @@ You can sort the entries by clicking on an available column header. Select :::im
253258
- **Name**<sup>\*</sup>
254259
- **Vendor**<sup>\*</sup>
255260
- **IP**<sup>\*</sup>
261+
- **Discovery sources**
256262
- **MAC address**
257263
- **Risk level**
258264
- **Exposure level**

defender-xdr/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,8 @@
154154
href: dlp-investigate-alerts-defender.md
155155
- name: Investigate data loss prevention alerts with Microsoft Sentinel
156156
href: dlp-investigate-alerts-sentinel.md
157+
- name: Investigate and respond to container threats
158+
href: investigate-respond-container-threats.md
157159
- name: Alerts
158160
href: investigate-alerts.md
159161
- name: Alert classification playbooks

defender-xdr/activate-defender-rbac.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.collection:
1212
- tier3
1313
ms.custom:
1414
ms.topic: how-to
15-
ms.date: 09/30/2024
15+
ms.date: 11/17/2024
1616
ms.reviewer:
1717
search.appverid: met150
1818
---
@@ -29,6 +29,8 @@ search.appverid: met150
2929
- [Microsoft Defender for Office 365 P2](https://go.microsoft.com/fwlink/?LinkID=2158212)
3030
- [Microsoft Defender Vulnerability Management](/defender-vulnerability-management/defender-vulnerability-management)
3131
- [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
32+
- [Microsoft Defender for Cloud Apps](/defender-cloud-apps/)
33+
- [Microsoft Security Exposure Management](/security-exposure-management/)
3234

3335
For the Microsoft Defender XDR security portal to start enforcing the permissions and assignments configured in your new [custom roles](create-custom-rbac-roles.md) or [imported roles](import-rbac-roles.md), you must activate the Microsoft Defender XDR Unified RBAC model for some or all of your workloads.
3436

@@ -54,20 +56,19 @@ You can activate your workloads in two ways from the Permissions and roles page:
5456
:::image type="content" source="/defender/media/defender/m365-defender-rbac-activate-workloads1.png" alt-text="Screenshot of the activate workloads page" lightbox="/defender/media/defender/m365-defender-rbac-activate-workloads1.png":::
5557

5658
1. **Activate workloads**
57-
- Select **Activate workloads** on the banner above the list of roles to go directly to the **Activate workloads** screen.
58-
- You must activate each workload one by one. Once you select the individual toggle, you activate (or deactivate) that workload.
5959

60-
:::image type="content" source="/defender/media/defender/defender-rbac-select-workload.png" alt-text="Screenshot of the choose workloads to activate screen":::
60+
- Select **Activate workloads** on the banner above the list of roles to go directly to the **Activate workloads** screen.
61+
- You must activate each workload one by one. Once you select the individual toggle, you activate (or deactivate) that workload.
62+
63+
:::image type="content" source="/defender/media/defender/defender-activate-workloads.png" alt-text="Screenshot of the choose workloads to activate screen.":::
6164

6265
> [!NOTE]
6366
> The **Activate workloads** button is only available when there is it at least one workload that's not active for Microsoft Defender XDR Unified RBAC.
64-
>
6567
> Microsoft Defender for Cloud is active by default with Microsoft Defender XDR Unified RBAC.
66-
>
67-
> Defender XDR Unified RBAC is automatically active for Secure Score access. Once a custom role with one of the permissions is created, it has an immediate impact on assigned users. There is no need to activate it.
68+
> Defender XDR Unified RBAC is automatically active for Exposure Management access. Once a custom role with one of the Exposure Management permissions is created, it has an immediate impact on assigned users. There is no need to activate it.
6869
>
6970
> To activate Exchange Online permissions in Microsoft Defender XDR Unified RBAC, Defender for Office 365 permissions must be active.
70-
71+
7172
2. **Workload settings**
7273
- Select **Workload settings**.
7374
- This brings you to the Microsoft Defender XDR **Permission and roles** page.

defender-xdr/create-custom-rbac-roles.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@ search.appverid: met150
2929
- [Microsoft Defender for Office 365 P2](https://go.microsoft.com/fwlink/?LinkID=2158212)
3030
- [Microsoft Defender Vulnerability Management](/defender-vulnerability-management/defender-vulnerability-management)
3131
- [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
32+
- [Microsoft Security Exposure Management](/security-exposure-management/)
3233

3334
## Create a custom role
3435

defender-xdr/custom-permissions-details.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ In Microsoft Defender XDR Unified role-based access control (RBAC) you can selec
3131
- [Microsoft Defender for Office 365 P2](https://go.microsoft.com/fwlink/?LinkID=2158212)
3232
- [Microsoft Defender Vulnerability Management](/defender-vulnerability-management/defender-vulnerability-management)
3333
- [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
34+
- [Microsoft Security Exposure Management](/security-exposure-management/)
3435

3536
<a name='microsoft-365-defender-unified-rbac-permission-details'></a>
3637

@@ -74,7 +75,7 @@ Permissions for managing the organization's security posture and performing vuln
7475
|Remediation handling|Manage|Create remediation tickets, submit new requests, and manage remediation activities in Defender Vulnerability Management.|
7576
|Application handling|Manage|Manage vulnerable applications and software, including blocking and unblocking them in Defender Vulnerability Management.|
7677
|Security baseline assessment|Manage|Create and manage profiles so you can assess if your devices comply to security industry baselines.|
77-
|Exposure Management|Read / Manage|View or manage Secure Score recommendations from all products included in Secure Score.|
78+
|Exposure Management|Read / Manage|View or manage Exposure Management insights, including Microsoft Secure Score recommendations from all products that are covered by Secure Score.|
7879

7980
### Authorization and settings
8081

defender-xdr/edit-delete-rbac-roles.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@ search.appverid: met150
2929
- [Microsoft Defender for Office 365 P2](https://go.microsoft.com/fwlink/?LinkID=2158212)
3030
- [Microsoft Defender Vulnerability Management](/defender-vulnerability-management/defender-vulnerability-management)
3131
- [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
32+
- [Microsoft Security Exposure Management](/security-exposure-management/)
3233

3334
In Microsoft Defender XDR Unified role-based access control (RBAC), you can edit and delete custom roles or roles that were imported from Defender for Endpoint, Defender for Identity, or Defender for Office 365.
3435

defender-xdr/investigate-incidents.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Investigate incidents in Microsoft Defender XDR
3-
description: Investigate incidents related to devices, users, and mailboxes.
2+
title: Investigate incidents in the Microsoft Defender portal
3+
description: Investigate incidents on various assets from correlated signals of various Defender services and other Microsoft security products like Microsoft Sentinel.
44
ms.service: defender-xdr
55
f1.keywords:
66
- NOCSH
@@ -16,20 +16,19 @@ ms.topic: conceptual
1616
search.appverid:
1717
- MOE150
1818
- MET150
19-
ms.date: 12/04/2023
19+
ms.date: 11/13/2024
20+
appliesto:
21+
- Microsoft Defender XDR
22+
- Microsoft Sentinel in the Microsoft Defender portal
2023
---
2124

22-
# Investigate incidents in Microsoft Defender XDR
25+
# Investigate incidents in the Microsoft Defender portal
2326

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

26-
**Applies to:**
27-
28-
- Microsoft Defender XDR
29+
The Microsoft Defender portal presents correlated alerts, assets, investigations, and evidence from across all your assets into an incident to give you a comprehensive look into the entire breadth of an attack.
2930

30-
Microsoft Defender XDR aggregates all related alerts, assets, investigations, and evidence from across your devices, users, and mailboxes into an incident to give you a comprehensive look into the entire breadth of an attack.
31-
32-
Within an incident, you analyze the alerts that affect your network, understand what they mean, and collate the evidence so that you can devise an effective remediation plan.
31+
Within an incident, you analyze the alerts, understand what they mean, and collate the evidence so that you can devise an effective remediation plan.
3332

3433
## Initial investigation
3534

@@ -84,7 +83,9 @@ From the graph, you can:
8483

8584
- Hunt for entity information of a device, file, IP address, or URL.
8685

87-
The *go hunt* option takes advantage of the [advanced hunting](advanced-hunting-go-hunt.md) feature to find relevant information about an entity. The *go hunt* query checks relevant schema tables for any events or alerts involving the specific entity you're investigating. You can select any of the options to find relevant information about the entity:
86+
### Go hunt
87+
88+
The ***go hunt*** action takes advantage of the [advanced hunting](advanced-hunting-go-hunt.md) feature to find relevant information about an entity. The *go hunt* query checks relevant schema tables for any events or alerts involving the specific entity you're investigating. You can select any of the options to find relevant information about the entity:
8889

8990
- See all available queries – the option returns all available queries for the entity type you're investigating.
9091
- All Activity – the query returns all activities associated with an entity, providing you with a comprehensive view of the incident's context.
@@ -96,7 +97,7 @@ The resulting logs or alerts can be linked to an incident by selecting a results
9697

9798
:::image type="content" source="/defender/media/investigate-incidents/fig2-gohunt-attackstory.png" alt-text="Highlighting the link to incident option in go hunt query results" lightbox="/defender/media/investigate-incidents/fig2-gohunt-attackstory.png":::
9899

99-
If the incident or related alerts were the result of an analytics rule you've set, you can also select **Run query** to see other related results.
100+
If the incident or related alerts were the result of an analytics rule you've set, you can also select ***Run query*** to see other related results.
100101

101102
## Summary
102103

0 commit comments

Comments
 (0)