Skip to content

Commit e494fe4

Browse files
committed
new module on irm alerts
1 parent 5a6abcf commit e494fe4

File tree

8 files changed

+182
-0
lines changed

8 files changed

+182
-0
lines changed
Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
The Alert dashboard in Microsoft Purview Insider Risk Management helps investigators and analysts view, prioritize, and take action on potentially risky user activity. Each alert is based on policy-defined conditions and provides a summary of the user's actions, associated risks, and relevant context. Effective alert triage ensures that high-risk behavior is addressed quickly, while low-risk activity can be dismissed to reduce noise.
2+
3+
## Overview of the Alert dashboard
4+
5+
The Alert dashboard provides a centralized view of all alerts generated by insider risk policies. Each alert is tied to a single user and includes:
6+
7+
- **Alert summary**: Displays the risk severity level, alert score, activity that triggered the alert, and triggering event.
8+
- **User details and history**: Shows general user information and past alerts, including unresolved or repeated risk patterns.
9+
- **Tabs for deeper analysis**: Includes tabs for **All risk factors**, **User activity**, and **Activity explorer** to review specific behavior in detail.
10+
11+
Alerts are automatically categorized by severity (low, medium, high) and can be filtered by status, policy, risk factor, or other criteria. Each new insight related to a user is added to their existing alert instead of generating a new one.
12+
13+
> [!NOTE]
14+
> Only unrestricted administrators or users with proper role assignments can view alerts, depending on how administrative units are scoped.
15+
16+
## Filtering and customizing views
17+
18+
When working with a high volume of alerts, filtering and customizing your view can improve efficiency:
19+
20+
- **Add filters** to narrow results by attributes like risk factor, severity, policy, assigned analyst, or triggering event.
21+
- **Save custom filter views** to quickly return to commonly used alert queues.
22+
- **Customize columns** to show or hide fields like policy name, time detected, or alert status.
23+
- **Search by keyword** such as user principal name (UPN), alert ID, or assigned admin.
24+
25+
These tools help reduce investigation time and support consistency across teams.
26+
27+
## Triage and take action on alerts
28+
29+
Once you've identified an alert that needs review, you can triage and take action directly from the Alert details page:
30+
31+
- **Dismiss** the alert if it was triggered by expected or non-risky behavior.
32+
- **Confirm and create a case** to escalate the alert for deeper investigation.
33+
- **Assign** the alert to another analyst or investigator.
34+
35+
Each alert is assigned a risk severity score based on multiple factors, including frequency of activity, user history, and the presence of risk indicators. If an alert remains untriaged and more risky behavior occurs, its severity level might increase.
36+
37+
> [!TIP]
38+
> You can select and dismiss multiple low-priority alerts in bulk using the command bar. Up to 400 alerts can be dismissed at once.
39+
40+
## Use Copilot to accelerate triage
41+
42+
If enabled, Security Copilot embedded in Microsoft Purview can summarize an alert to help you triage faster. Without opening the alert, you can select **Summarize with Copilot** to generate an overview that includes:
43+
44+
- Policy name and triggering event
45+
- Activity that generated the alert
46+
- Key user attributes
47+
- Top risk factors
48+
49+
Copilot can also suggest questions to help refine your summary, such as:
50+
51+
- What actions did the user perform in the last 10 days?
52+
- List all sequential activities involving this user.
53+
- Did the user engage in any unusual behavior?
54+
55+
These insights make it easier to prioritize the most important alerts and dismiss those that don't require follow-up.
56+
57+
## Retention and alert limits
58+
59+
Alerts in a "Needs review" state are retained for 120 days. After this period, they're automatically deleted unless linked to an active case. Active and unresolved cases are retained indefinitely. Organizations can have up to 100 active cases at any given time.
60+
61+
The Alert dashboard is the central hub for reviewing and triaging insider risk alerts in Microsoft Purview. It allows investigators to:
62+
63+
- Quickly assess risk severity and context
64+
- Filter and organize large volumes of alerts
65+
- Use Copilot to streamline triage
66+
- Assign, dismiss, or escalate alerts as needed
67+
68+
By combining automated insights with manual review tools, the Alert dashboard supports efficient, accurate investigation workflows aligned with your organization's risk management goals.
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
Balancing alert volume is an important part of maintaining an efficient insider risk program. If your policies generate too few alerts, you might miss meaningful signals. If they generate too many, investigators might become overwhelmed, making it harder to focus on high-risk activity. Microsoft Purview Insider Risk Management includes several tools and settings to help you fine-tune alert volume and ensure your environment supports consistent, focused investigations.
2+
3+
## When you're receiving too few alerts
4+
5+
Receiving fewer alerts than expected might indicate that your policies are too narrow or that thresholds are set too high. To increase alert volume:
6+
7+
- **Enable more risk indicators** in the **Policy indicators** settings. This expands the types of activities that policies detect.
8+
- **Include more users** in policy scope by editing the **Users and groups** section of the policy.
9+
- **Lower trigger thresholds** to start evaluating users earlier based on specific events, such as resignation or access to sensitive content.
10+
- **Lower indicator thresholds** to generate alerts based on less frequent or less severe activity.
11+
- **Adjust the alert volume slider** under **Settings > Intelligent detections**. Moving the slider toward "More alerts" increases overall alert generation, including medium- and low-severity alerts.
12+
13+
> [!TIP]
14+
> Policies based on certain templates, like _Data leaks_ and _Risky browser usage_, allow custom thresholds that can be lowered to help generate more alerts.
15+
16+
## When you're receiving too many alerts
17+
18+
High alert volume can overwhelm analysts and reduce the effectiveness of your investigation process. To reduce alert volume:
19+
20+
- **Enable analytics** in **Settings > Analytics** to identify high-risk areas and adjust your approach accordingly.
21+
- **Use real-time insights** to update thresholds and indicator selections based on recommended values.
22+
- **Refine policy scope and content** by narrowing the list of in-scope users or prioritizing only the most sensitive files and communication channels.
23+
- **Enable inline alert customization** to allow analysts to adjust thresholds during triage.
24+
- **Dismiss multiple low-priority alerts in bulk** to reduce noise in the alert queue.
25+
26+
## Configuration options for alert management
27+
28+
Beyond basic tuning, Microsoft Purview provides several configuration options to help manage alert volume more effectively:
29+
30+
- **Use appropriate policy templates** to target specific risk scenarios.
31+
- **Configure global exclusions** to prevent benign activity from triggering alerts.
32+
- **Define detection groups** to apply different policies to different user populations.
33+
- **Create indicator variants** to refine detection logic.
34+
- **Adjust policy timeframes** to control how far back activity is evaluated.
35+
- **Assign appropriate roles** to ensure only qualified users can make sensitive configuration changes.
36+
37+
Effective alert volume management requires both upfront planning and ongoing tuning. Use built-in analytics and threshold recommendations to maintain a manageable signal-to-noise ratio. When alert volume is tuned effectively, your investigation process becomes more focused, efficient, and aligned with organizational risk priorities.
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
Alerts in Microsoft Purview Insider Risk Management aren't generated randomly. They follow a defined sequence of actions that begins with policy settings and ends with a triggered alert. Understanding how alerts are generated is critical to reviewing and interpreting them accurately during investigations. This understanding allows investigators to identify relevant activity, determine why it was evaluated, and assess whether it meets the defined risk criteria.
2+
3+
## Why alert generation matters
4+
5+
Knowing how an alert was generated helps investigators:
6+
7+
- Identify what triggered the alert
8+
- Understand which activities were evaluated
9+
- Determine appropriate next steps
10+
- Align alert evaluation with policy criteria
11+
12+
This context supports more consistent triage decisions and helps reduce time spent on irrelevant or low-risk activity.
13+
14+
## Alert generation process
15+
16+
Alerts are generated through a five-step process:
17+
18+
:::image type="content" source="../media/insider-risk-management-alert-generation-chart.png" alt-text="Diagram illustrating the process of how alerts are generated in Insider Risk Management." lightbox=" ../media/insider-risk-management-alert-generation-chart.png":::
19+
20+
1. **Settings configured**: Organizations configure policy settings to align with their insider risk management strategy. This includes defining which risk indicators to monitor, identifying sensitive domains, and setting privacy preferences.
21+
22+
1. **Policy created**: Policies define whose activity to evaluate, what activity to detect, and which events should trigger active monitoring. For example, a policy might monitor users in finance for data exfiltration after a resignation is submitted.
23+
24+
1. **Triggering event occurs**: A triggering event activates the policy for a specific user. This could include events such as a resignation date being set or a risky website being accessed. It might also include detection of exfiltration behavior.
25+
26+
1. **User activity evaluated and scored**: The system begins monitoring the user's actions. Activities are assigned risk scores based on the type of activity, configured thresholds, and the user’s history.
27+
28+
1. **Alert generated**: An alert is generated if the user's risk score exceeds the policy-defined threshold.
29+
30+
This process ensures that alerts are based on defined conditions and relevant context. Not all activity results in an alert. For example, a user downloading files might not trigger an alert unless other risk factors are present.
31+
32+
Each alert is the result of a defined policy, a triggering event, and risk-based evaluation of user activity. Understanding how alerts are generated helps investigators assess their relevance and determine whether further action is needed. This insight supports more accurate, timely, and consistent handling of insider risk alerts.

learn-pr/wwl-sci/purview-insider-risk-investigate-alerts/index.yml

Whitespace-only changes.
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.purview-insider-risk-investigate-alerts.investigate-triage-alerts
3+
title: Investigate and triage insider risk alerts in Microsoft Purview
4+
metadata:
5+
title: Investigate and triage insider risk alerts in Microsoft Purview
6+
description: "Investigate and triage insider risk alerts in Microsoft Purview."
7+
ms.date: 04/15/2025
8+
author: wwlpublish
9+
ms.author: riswinto
10+
ms.topic: unit
11+
azureSandbox: false
12+
labModal: false
13+
durationInMinutes: 6
14+
content: |
15+
[!include[](includes/investigate-triage-alerts.md)]
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.purview-insider-risk-investigate-alerts.manage-alert-volume
3+
title: Manage alert volume in insider risk management
4+
metadata:
5+
title: Manage alert volume in insider risk management
6+
description: "Manage alert volume in insider risk management."
7+
ms.date: 04/15/2025
8+
author: wwlpublish
9+
ms.author: riswinto
10+
ms.topic: unit
11+
azureSandbox: false
12+
labModal: false
13+
durationInMinutes: 4
14+
content: |
15+
[!include[](includes/manage-alert-volume.md)]
81.3 KB
Loading
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.purview-insider-risk-investigate-alerts.understand-insider-risk-alerts
3+
title: Understand insider risk alerts and investigations
4+
metadata:
5+
title: Understand insider risk alerts and investigations
6+
description: "Understand insider risk alerts and investigations."
7+
ms.date: 04/15/2025
8+
author: wwlpublish
9+
ms.author: riswinto
10+
ms.topic: unit
11+
azureSandbox: false
12+
labModal: false
13+
durationInMinutes: 3
14+
content: |
15+
[!include[](includes/understand-insider-risk-alerts.md)]

0 commit comments

Comments
 (0)