Skip to content

Commit 20b66f8

Browse files
Merge pull request #1197 from batamig/roles
XDR service roles
2 parents 4ee70da + 704fb5f commit 20b66f8

File tree

3 files changed

+35
-74
lines changed

3 files changed

+35
-74
lines changed

defender-xdr/advanced-hunting-microsoft-defender.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,10 @@ Querying from a single portal across different data sets makes hunting more effi
3434
## How to access
3535

3636
### Required roles and permissions
37-
To query across Microsoft Sentinel and Microsoft Defender XDR data in the unified advanced hunting page, you must have access to Microsoft Defender XDR advanced hunting (see [Required roles and permissions](custom-roles.md#required-roles-and-permissions)) and at least Microsoft Sentinel Reader (see [Microsoft Sentinel-specific roles](/azure/sentinel/roles#microsoft-sentinel-specific-roles)).
3837

39-
In the unified portal, you can query any data in any workload that you can currently access based on the roles and permissions you have.
38+
You can query data in any workload that you can currently access based on your roles and permissions.
39+
40+
To query across Microsoft Sentinel and Microsoft Defender XDR data in the unified advanced hunting page, you'll also need at least the Microsoft Sentinel Reader role. For more information, see [Microsoft Sentinel-specific roles](/azure/sentinel/roles#microsoft-sentinel-specific-roles).
4041

4142
### Connect a workspace
4243

defender-xdr/custom-roles.md

Lines changed: 32 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ f1.keywords:
77
ms.author: dansimp
88
author: dansimp
99
ms.localizationpriority: medium
10-
ms.date: 03/04/2024
10+
ms.date: 08/22/2024
1111
manager: dansimp
1212
audience: ITPro
1313
ms.collection:
@@ -18,92 +18,52 @@ search.appverid:
1818
- MOE150
1919
- MET150
2020
---
21-
# Custom roles in role-based access control for Microsoft Defender XDR
21+
# Custom roles in role-based access control for Microsoft Defender portal services
2222

23-
> [!NOTE]
24-
> Microsoft Defender XDR users can now take advantage of a centralized permissions management solution to control user access and permissions across different Microsoft security solutions. Learn more about the [Microsoft Defender XDR Unified role-based access control (RBAC)](manage-rbac.md).
23+
By default, access to services available in the Microsoft Defender portal are managed collectively using [Microsoft Entra global roles](m365d-permissions.md). If you need greater flexibility and control over access to specific product data, and aren't yet using the [Microsoft Defender XDR Unified role-based access control (RBAC)](manage-rbac.md) for centralized permissions management, we recommend creating custom roles for each service.
2524

26-
[!INCLUDE [Prerelease](../includes/prerelease.md)]
25+
For example, create a custom role for Microsoft Defender for Endpoint to manage access to specific Defender for Endpoint data, or create a custom role for Microsoft Defender for Office to manage access to specific email and collaboration data.
2726

2827
**Applies to:**
2928

29+
- Microsoft Defender for Cloud
30+
- Microsoft Defender for Cloud Apps
31+
- Microsoft Defender for Endpoint
32+
- Microsoft Defender for Identity
33+
- Microsoft Defender for IoT
34+
- Microsoft Defender for Office 365
3035
- Microsoft Defender XDR
36+
- Microsoft Security Exposure Management (preview)
37+
- Microsoft Sentinel
3138

32-
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/microsoft-defender.md)]
33-
34-
There are two types of roles that can be used to access to Microsoft Defender XDR:
35-
36-
- **Global Microsoft Entra roles**
37-
- **Custom roles**
38-
39-
Access to Microsoft Defender XDR can be managed collectively by using [Global roles in Microsoft Entra ID](m365d-permissions.md)
40-
41-
If you need greater flexibility and control over access to specific product data, Microsoft Defender XDR access can also be managed with the creation of Custom roles through each respective security portal.
42-
43-
For example, a Custom role created through Microsoft Defender for Endpoint would allow access to the relevant product data, including Endpoint data within the Microsoft Defender portal. Similarly, a Custom role created through Microsoft Defender for Office 365 would allow access to the relevant product data, including Email & collaboration data within the Microsoft Defender portal.
44-
45-
Users with existing Custom roles can access data in the Microsoft Defender portal according to their existing workload permissions with no additional configuration required.
46-
47-
## Create and manage custom roles
48-
49-
Custom roles and permissions can be created and individually managed through each of the following security portals:
50-
51-
- Microsoft Defender for Endpoint – [Edit roles in Microsoft Defender for Endpoint](/defender-endpoint/user-roles)
52-
- Microsoft Defender for Office 365 – [Permissions in the Security & Compliance Center](/defender-office-365/scc-permissions?preserve-view=true&view=o365-worldwide)
53-
- Microsoft Defender for Cloud Apps – [Manage admin access](/cloud-app-security/manage-admins)
54-
55-
Each custom role created through an individual portal allows access to the data of the relevant product portal. For example, a custom role created through Microsoft Defender for Endpoint will only allow access to Defender for Endpoint data.
56-
57-
> [!TIP]
58-
> Permissions and roles can also be accessed through the Microsoft Defender portal by selecting Permissions & roles from the navigation pane. Access to Microsoft Defender for Cloud Apps is managed through the Defender for Cloud Apps portal and controls access to Microsoft Defender for Identity as well. See [Microsoft Defender for Cloud Apps](/cloud-app-security/manage-admins)
59-
60-
> [!NOTE]
61-
> Custom roles created in Microsoft Defender for Cloud Apps have access to Microsoft Defender for Identity data as well. Users with User group admin, or App/instance admin Microsoft Defender for Cloud Apps roles are not able to access Microsoft Defender for Cloud Apps data through the Microsoft Defender portal.
39+
[!INCLUDE [Prerelease](../includes/prerelease.md)]
6240

6341
<a name='manage-permissions-and-roles-in-the-microsoft-365-defender-portal'></a>
6442

65-
## Manage permissions and roles in the Microsoft Defender portal
66-
67-
Permissions and roles can also be managed in the Microsoft Defender portal:
68-
69-
1. Sign in to the Microsoft Defender portal at security.microsoft.com.
70-
2. In the navigation pane, select **Permissions & roles**.
71-
3. Under the **Permissions** header, select **Roles**.
72-
73-
> [!NOTE]
74-
> This only applies to Defender for Office 365 and Defender for Endpoint. Access for other workloads must be done in their relevant portals.
75-
76-
## Required roles and permissions
77-
78-
The following table outlines the roles and permissions required to access each unified experience in each workload. Roles defined in the table refer to custom roles in individual portals and aren't connected to global roles in Microsoft Entra ID, even if similarly named.
43+
## Locate custom role management settings in the Microsoft Defender portal
7944

80-
> [!NOTE]
81-
> Incident management requires management permissions for all products that are part of the incident.
45+
Each Microsoft Defender service has its own custom role management settings, with some services being represented in a central location in the Microsoft Defender portal. To locate custom role management settings in the Microsoft Defender portal:
8246

83-
> [!IMPORTANT]
84-
> Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
47+
1. Sign in to the Microsoft Defender portal at [security.microsoft.com](https://security.microsoft.com).
48+
1. In the navigation pane, select **Permissions**.
49+
1. Select the **Roles** link for the service where you want to create a custom role. For example, for Defender for Endpoint:
8550

86-
|Microsoft Defender XDR workload|One of the following roles is required for Defender for Endpoint|One of the following roles is required for Defender for Office 365|One of the following roles is required for Defender for Cloud Apps and Defender for Identity | One of the following roles is required for Microsoft Defender for Cloud |
87-
|---|---|---|---|---|
88-
|Viewing investigation data: <ul><li>Alert page</li> <li>Alerts queue</li> <li>Incidents</li> <li>Incident queue</li> <li>Action center</li></ul>|View data- security operations|<ul><li>View-only Manage alerts </li> <li>Organization configuration</li><li>Audit logs</li> <li>View-only audit logs</li> <li>Security reader</li> <li>Security admin</li><li>View-only recipients</li></ul>|<ul><li>Global admin</li> <li>Security admin</li> <li>Compliance admin</li> <li>Security operator</li> <li>Security reader</li> <li>Global reader</li></ul>|<ul><li>Global admin</li><li>Security admin</li></ul> |
89-
|Viewing hunting data, saving, editing, and deleting hunting queries and functions|View data- security operations|<ul><li>Security reader</li> <li>Security admin</li> <li>View-only recipients</li>|<ul><li>Global admin</li> <li>Security admin</li> <li>Compliance admin</li> <li>Security operator</li> <li>Security reader</li> <li>Global reader</li></ul>|<ul><li>Global admin</li><li>Security admin</li></ul> |
90-
|Managing alerts and incidents|Alerts investigation|<ul><li>Manage alerts</li> <li>Security admin</li>|<ul><li>Global admin</li> <li>Security admin</li> <li>Compliance admin</li> <li>Security operator</li> <li>Security reader</li></ul>|<ul><li>Global admin</li><li>Security admin</li></ul> |
91-
|Action center remediation|Active remediation actions – security operations|Search and purge||<ul><li>Global admin</li><li>Security admin</li></ul> |
92-
|Setting custom detections|Manage security settings|<ul><li>Manage alerts</li> <li>Security admin</li></ul>|<ul><li>Global admin</li> <li>Security admin</li> <li>Compliance admin</li> <li>Security operator</li> <li>Security reader</li> <li>Global reader</li></ul>|<ul><li>Global admin</li><li>Security admin</li></ul> |
93-
|Threat Analytics|Alerts and incidents data: <ul><li>View data- security operations</li></ul>Defender Vulnerability Management mitigations:<ul><li>View data - Threat and vulnerability management</li></ul>|Alerts and incidents data:<ul> <li>View-only Manage alerts</li> <li>Manage alerts</li> <li>Organization configuration</li><li>Audit logs</li> <li>View-only audit logs</li><li>Security reader</li> <li>Security admin</li><li>View-only recipients</li> </ul> Prevented email attempts: <ul><li>Security reader</li> <li>Security admin</li><li>View-only recipients</li>|<ul><li>Global admin</li> <li>Security admin</li> <li>Compliance admin</li> <li>Security operator</li> <li>Security reader</li> <li>Global reader</li></ul>|<ul><li>Global admin</li><li>Security admin</li></ul> |
51+
:::image type="content" source="./media/custom-roles/custom-roles-endpoint.png" alt-text="Screenshot that shows Roles link for Defender for Endpoint." lightbox="./media/custom-roles/custom-roles-endpoint.png" :::
9452

95-
For example, to view hunting data from Microsoft Defender for Endpoint, View data security operations permissions are required.
53+
In each service, custom role names aren't connected to global roles in Microsoft Entra ID, even if similarly named. For example, a custom role named *Security Admin* in Microsoft Defender for Endpoint isn't connected to the global *Security Admin* role in Microsoft Entra ID.
9654

97-
Similarly, to view hunting data from Microsoft Defender for Office 365, users would require one of the following roles:
55+
## Reference of Defender portal service content
9856

99-
- View data security operations
100-
- Security reader
101-
- Security admin
102-
- View-only recipients
57+
For information about the permissions and roles for each Microsoft Defender XDR service, see the following articles:
10358

104-
## Related articles
59+
- [Microsoft **Defender for Cloud** user roles and permissions](/azure/defender-for-cloud/permissions)
60+
- [Configure access for **Defender for Cloud Apps**](/defender-cloud-apps/manage-admins)
61+
- [Create and manage roles in **Defender for Endpoint**](/defender-endpoint/user-roles)
62+
- [Roles and permissions in **Defender for Identity**](/defender-for-identity/role-groups)
63+
- [Microsoft **Defender for IoT** user management](/azure/defender-for-iot/organizations/manage-users-overview)
64+
- [Microsoft **Defender for Office 365** permissions](/defender-office-365/mdo-portal-permissions)
65+
- [Manage access to **Microsoft Defender XDR**](m365d-permissions.md)
66+
- [**Microsoft Security Exposure Management** permissions](/security-exposure-management/prerequisites#permissions)
67+
- [Roles and permissions in **Microsoft Sentinel**](/azure/sentinel/roles)
10568

106-
- [RBAC roles](/defender-office-365/migrate-to-defender-for-office-365-onboard#rbac-roles)
107-
- [Manage access to Microsoft Defender XDR](m365d-permissions.md)
108-
- [Manage admin access for Defender for Cloud Apps](/cloud-app-security/manage-admins)
109-
[!INCLUDE [Microsoft Defender XDR rebranding](../includes/defender-m3d-techcommunity.md)]
69+
Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
371 KB
Loading

0 commit comments

Comments
 (0)