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
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-insights.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.collection:
13
13
ms.custom:
14
14
description: Admins can learn how Attack simulation training in the Microsoft Defender portal affects users and can gain insights from simulation and training outcomes.
15
15
search.appverid: met150
16
-
ms.date: 08/14/2024
16
+
ms.date: 10/18/2024
17
17
appliesto:
18
18
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 2</a>
19
19
---
@@ -220,16 +220,18 @@ If you hover over a data point in the chart, the actual values are shown.
220
220
221
221
The details table below the chart shows the following information. You can sort the information by clicking on an available column header. Select :::image type="icon" source="media/m365-cc-sc-customize-icon.png" border="false"::: **Customize columns** to change the columns that are shown. By default, all available columns are selected.
222
222
223
-
-**User**: Name of the user
224
-
-**Simulation types**: Type of simulations where the user was involved
225
-
-**Simulations**: Name of simulations where the user was involved
226
-
-**Email address**: Email address of the user
227
-
-**Latest repeat count**: This is the latest count of compromises for users categorized as repeat offender. As an example, if the repeat offender’s threshold is set to 3, and a user has been compromised in 3 consecutive simulations, then the latest repeat count is 3. If the user has been compromised in 4 consecutive simulations, then the latest repeat count is 4. If the user has been compromised in 2 consecutive simulations, then this value shows N/A. The latest repeat count sets to 0 (N/A), every time a repeat offender flag is reset (meaning the user passes a simulation).
228
-
-**Repeat offences**: This will include the number of times a user has been classified as a repeat offender. As an example, if a user:
229
-
- Was classified as a repeat offender in first few simulations (they were compromised 3 consecutive times, where repeat offender threshold is 2)
230
-
- Was classified as ‘clean’ after passing a simulation
231
-
- Was classified as a repeat offender in the next few simulations (they were compromised 4 consecutive times, where repeat offender threshold is 2)
232
-
In such a case, the number of repeat offences would be set to 2. The count updates every time a user is considered a repeat offender.
223
+
-**User**: Name of the user.
224
+
-**Simulation types**: Type of simulations where the user was involved.
225
+
-**Simulations**: Name of simulations where the user was involved.
226
+
-**Email address**: Email address of the user.
227
+
-**Latest repeat count**: Latest count of compromises for users categorized as repeat offenders. For example, if the repeat offender threshold is set to 3, and a user was compromised in 3 consecutive simulations, then the latest repeat count is 3. If the user was compromised in 4 consecutive simulations, then the latest repeat count is 4. If the user was compromised in 2 consecutive simulations, then the value N/A. The latest repeat count sets to 0 (N/A), every time a repeat offender flag is reset (meaning the user passes a simulation).
228
+
-**Repeat offences**: Includes the number of times a user was classified as a repeat offender. For example:
229
+
- The user was classified as a repeat offender in first few simulations (they were compromised 3 consecutive times, where repeat offender threshold is 2).
230
+
- The user was classified as 'clean' after passing a simulation.
231
+
- The user was classified as a repeat offender in the next few simulations (they were compromised 4 consecutive times, where repeat offender threshold is 2).
232
+
233
+
In these cases, the number of repeat offences is set to 2. The count updates every time a user is considered a repeat offender.
0 commit comments