You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can manage Microsoft Purview Data Loss Prevention (DLP) alerts in the Microsoft Defender portal. Open **Incidents & alerts**\>**Incidents** on the quick launch of the <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a>. From this page, you can:
29
+
You can manage and respond to Microsoft Purview Data Loss Prevention (DLP) alerts and incidents in the Microsoft Defender portal. Open **Incidents & alerts**\>**Incidents** on the quick launch of the <ahref="https://go.microsoft.com/fwlink/p/?linkid=2077139"target="_blank">Microsoft Defender portal</a>. From this page, you can:
31
30
32
31
- View all your DLP alerts grouped under incidents in the Microsoft Defender XDR incident queue.
33
-
- View intelligent inter-solution (DLP-MDE, DLP-MDO) and intra-solution (DLP-DLP) correlated alerts under a single incident.
34
-
- Hunt for compliance logs along with security under Advanced Hunting.
35
-
-In-place admin remediation actions on user, file, and device.
32
+
- View DLP alerts correlated with other DLP alerts, or with alerts from other solutions (Defender for Endpoint, Defender for Office 365, Microsoft Sentinel, and so on), under a single incident.
33
+
- Hunt for security threats, using queries combining compliance logs with security logs, under Advanced Hunting.
34
+
-Take remediation actions in-place on users, files, and devices.
36
35
- Associate custom tags to DLP incidents and filter by them.
37
-
- Filter by DLP policy name, tag, Date, service source, incident status, and user on the unified incident queue.
36
+
- Filter the unified incident queue by DLP policy name, tag, date, service source, incident status, and user.
38
37
39
-
> [!TIP]
40
-
> You can also pull DLP incidents along with events and evidence into Microsoft Sentinel for investigation and remediation with the Microsoft Defender XDR connector in Microsoft Sentinel.
38
+
## Prerequisites
41
39
42
-
## Licensing requirements
40
+
###Licensing requirements
43
41
44
42
To investigate Microsoft Purview Data Loss Prevention incidents in the Microsoft Defender portal, you need a license from one of the following subscriptions:
45
43
@@ -51,17 +49,18 @@ To investigate Microsoft Purview Data Loss Prevention incidents in the Microsoft
51
49
> [!NOTE]
52
50
> When you are licensed and eligible for this feature, DLP alerts will automatically flow into Microsoft Defender XDR. If you don't want DLP alerts to flow into Defender, open a support case to disable this feature. If you disable this feature DLP alerts will surface in the Defender portal as Microsoft Defender for Office alerts.
53
51
54
-
## Roles
52
+
###Roles
55
53
56
54
It's best practice to only grant minimal permissions to alerts in the Microsoft Defender portal. You can create a custom role with these roles and assign it to the users who need to investigate DLP alerts.
57
55
58
-
|Permission |Defender Alert Access |
59
-
|---------|---------|
60
-
|Manage Alerts | DLP + Security |
61
-
|View-Only Manage Alerts |DLP + Security |
62
-
|Information Protection Analyst |DLP only |
63
-
|DLP Compliance Management |DLP only |
64
-
|View-Only DLP Compliance Management |DLP only |
56
+
| Permission | Defender Alert Access |
57
+
| ---------- | --------- |
58
+
| Manage Alerts | DLP + Security |
59
+
| View-Only Manage Alerts | DLP + Security |
60
+
| Information Protection Analyst | DLP only |
61
+
| DLP Compliance Management | DLP only |
62
+
| View-Only DLP Compliance Management | DLP only |
63
+
65
64
66
65
## Before you start
67
66
@@ -70,15 +69,15 @@ It's best practice to only grant minimal permissions to alerts in the Microsoft
70
69
> [!NOTE]
71
70
> [Administrative units](/microsoft-365/compliance/microsoft-365-compliance-center-permissions#administrative-units) restrictions flow from data loss prevention (DLP) into the Defender portal. If you are an administrative unit restricted admin, you'll only see the DLP alerts for your administrative unit.
## Investigate DLP alerts in the Microsoft Defender portal
76
77
77
78
1. Go to the Microsoft Defender portal, and select **Incidents** in the left hand navigation menu to open the incidents page.
78
79
79
-
1. Select **Filters** on the top right, and choose **Service Source : Data Loss Prevention** to view all incidents with DLP alerts. Here's a few examples of the subfilters that are available in preview:
80
-
1. by user and device names
81
-
1. (in preview) In the **Entities** filter, you can search on file names, user, device names, and file paths.
80
+
1. Select **Add filter** on the toolbar, and choose the **Service/detection sources** filter. Then select that filter and choose **Microsoft Data Loss Prevention** to view all incidents with DLP alerts. You can also filter the queue by user and device names (using the **Entities** filter) and by policies, using the **Policy/policy rule** filter, you can search on file names, user, device names, and file paths.
82
81
1. (in preview) In the **Incidents** queue > **Alert policies** > Alert policy title. You can search on the DLP policy name.
83
82
84
83
1. Search for the DLP policy name of the alerts and incidents you're interested in.
@@ -99,7 +98,7 @@ The **CloudAppEvents** table contains all audit logs across all locations like S
99
98
100
99
If you're new to advanced hunting, you should review [Get started with advanced hunting](advanced-hunting-overview.md).
101
100
102
-
Before you can use advance hunting you must have [access to the **CloudAppEvents** table](/defender-cloud-apps/protect-office-365#connect-microsoft-365-to-microsoft-defender-for-cloud-apps) that contains the Microsoft Purview data.
101
+
Before you can use advanced hunting you must have [access to the **CloudAppEvents** table](/defender-cloud-apps/protect-office-365#connect-microsoft-365-to-microsoft-defender-for-cloud-apps) that contains the Microsoft Purview data.
0 commit comments