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-faq.md
+52-13Lines changed: 52 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ ms.custom:
19
19
- seo-marvel-apr2020
20
20
description: Admins can learn about deployment considerations and frequently asked questions regarding Attack simulation and training in Microsoft 365 E5 or Microsoft Defender for Office 365 Plan 2 organizations.
21
21
ms.service: defender-office-365
22
-
ms.date: 6/22/2023
22
+
ms.date: 06/14/2024
23
23
appliesto:
24
24
- ✅ <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>
25
25
---
@@ -144,8 +144,17 @@ There are no built-in options to add safety tips to payloads, but you can use th
144
144
145
145
Yes. For more information, see [Training campaigns in Attack simulation training](attack-simulation-training-training-campaigns.md).
146
146
147
+
### How do I find out about simulation messages that weren't delivered?
148
+
149
+
The [Users tab](attack-simulation-training-simulations.md#users-tab) for the simulation is filterable by **Simulation message delivery: Failed to deliver**.
150
+
151
+
If you won the sender domain, the undelivered simulation report is returned in a non-delivery report (also known as an NDR or bounce message). For more information about the codes in the NDR, see [Email non-delivery reports and SMTP errors in Exchange Online](/exchange/troubleshoot/email-delivery/ndr/non-delivery-reports-in-exchange-online).
152
+
147
153
## Issues with Attack simulation training reporting
148
154
155
+
> [!TIP]
156
+
> Simulation data recording start a few minutes after the simulation is launched and after users begin interacting with the simulation messages. There's no fixed start time. Events are still captured after the simulation ends.
157
+
149
158
### Differences in user activity data from Attack simulation training reports and other reports
150
159
151
160
For reporting on user activity related to simulation messages, we recommend using the [built-in simulation reports](attack-simulation-training-insights.md). Reports from other sources (for example, [Advanced hunting](/defender-xdr/advanced-hunting-overview)) might not be accurate.
@@ -177,6 +186,9 @@ Attack simulation training supports on-premises mailboxes, but with reduced repo
177
186
- Data on whether users read, forwarded, or deleted the simulation email isn't available for on-premises mailboxes.
178
187
- The number of users who reported the simulation email isn't available for on-premises mailboxes.
179
188
189
+
> [!TIP]
190
+
> Other than the simulation messages being sent via the transport pipeline vs. direct injection in Microsoft 365, the training, automation, and content management experiences are the same for on-premises mailboxes.
191
+
180
192
### Simulation reports aren't updated immediately
181
193
182
194
Detailed simulation reports aren't updated immediately after you launch a campaign. Don't worry; this behavior is expected.
@@ -251,6 +263,12 @@ Managing a large CSV file or adding many individual recipients can be cumbersome
251
263
252
264
> [!TIP]
253
265
> Currently, shared mailboxes aren't supported in Attack simulation training. Simulations should target user mailboxes or groups containing user mailboxes.
266
+
>
267
+
> Distribution groups are expanded and the list of users is generated at the time of saving the simulation or simulation automation.
268
+
269
+
### Q: Are the limits for the number of simulations that can be deployed during a specific time interval?
270
+
271
+
A. No, although you might experience slowness if you launch many parallel simulations. Message rates (including simulation message rates) are constrained by the [message rate limits of the service](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#receiving-and-sending-limits).
254
272
255
273
### Q: Does Microsoft provide payloads in other languages?
256
274
@@ -293,27 +311,40 @@ At 9:00 AM on the same day, the simulation message is sent to UserB. With region
293
311
294
312
So, on the initial run of a campaign with region aware delivery enabled, it might appear that the simulation message was sent only to users in a specific time zone. But, as time passes and more users come into scope, the targeted users increase.
295
313
314
+
If you don't use region aware delivery, the campaign starts based on the time zone of the user who's setting it up.
315
+
296
316
### Q: Does Microsoft collect or store any information that users enter at the Credential Harvest sign-in page, used in the Credential Harvest simulation technique?
297
317
298
318
A: No. Any information entered at the credential harvest sign-in page is discarded silently. Only the 'click' is recorded to capture the compromise event. Microsoft doesn't collect, log or store any details that users enter at this step.
299
319
300
320
### Q: How long is simulation information retained? Can I delete simulation data?
301
321
302
-
A: Simulation data is retained for 18 months from the date of generation. Data includes:
303
-
304
-
- Simulation metadata
305
-
- User activity
306
-
- Aggregate reports
307
-
308
-
The following data is retained until you [delete the simulation](attack-simulation-training-simulations.md#remove-simulations):
309
-
310
-
- Tenant payloads
311
-
- Notifications
312
-
- Login pages
322
+
A: See the following table:
323
+
324
+
|Data type|Retention|
325
+
|---|---|
326
+
|Simulation metadata|18 months unless the [simulation is deleted sooner by an admin](attack-simulation-training-simulations.md#remove-simulations).|
327
+
|Simulation automation|18 months unless the [simulation automation is deleted sooner by an admin](attack-simulation-training-simulation-automations.md#remove-simulation-automations).|
328
+
|Payload automation|18 months unless the [payload automation is deleted sooner by an admin](attack-simulation-training-payload-automations.md#remove-payload-automations).|
329
+
|User activity in simulation metadata|18 months unless deleted by an admin.|
330
+
|Global payloads|Persisted unless deleted by Microsoft.|
331
+
|Tenant payloads|18 months unless the [archived payload is deleted sooner by an admin](attack-simulation-training-payloads.md#remove-archived-payloads).|
332
+
|User activity in training metadata|18 months unless the [simulation is deleted sooner by an admin](attack-simulation-training-simulations.md#remove-simulations).|
333
+
|MDO recommended payloads|6 months.|
334
+
|Global end user notifications|Persisted unless deleted by Microsoft.|
335
+
|Tenant end user notifications|18 months unless the [notification is deleted sooner by an admin](attack-simulation-training-end-user-notifications.md#remove-end-user-notifications).|
336
+
|Global login pages|Persisted unless deleted by the service.|
337
+
|Tenant login pages|18 months unless the [login page is deleted sooner by an admin](attack-simulation-training-login-pages.md#remove-login-pages).|
338
+
|Global landing pages|Persisted unless deleted by Microsoft|
339
+
|Tenant landing pages|18 months unless the [landing page is deleted sooner by an admin](attack-simulation-training-landing-pages.md#remove-landing-pages).|
340
+
341
+
If the entire tenant is deleted, attack simulation training data is deleted after 90 days.
342
+
343
+
For more information, see [Data retention information for Microsoft Defender for Office 365](mdo-data-retention.md).
313
344
314
345
### Q: Can I create, view, and manage simulations using an API?
315
346
316
-
A: Read and write scenarios are supported using the Microsoft Graph API:
347
+
A: Yes. Read and write scenarios are supported using the Microsoft Graph API:
317
348
318
349
-`AttackSimulation.Read.All`:
319
350
- Read simulation metadata
@@ -323,3 +354,11 @@ A: Read and write scenarios are supported using the Microsoft Graph API:
323
354
-`AttackSimulation.ReadWrite.All`: Run simulations using the specified payloads, notifications, and login pages.
324
355
325
356
For more information, see [List simulations](/graph/api/attacksimulationroot-list-simulations) and [Reports API overview for attack simulation training as part of Microsoft Defender for Office 365](/graph/api/resources/report-m365defender-reports-overview).
357
+
358
+
### Q: Can I delete custom payloads?
359
+
360
+
A: Yes. First you archive the payload, then you delete the archived payload. For instructions, see [Archive payloads](attack-simulation-training-payloads.md#archive-payloads).
361
+
362
+
### Q: Can I modify the built-in payloads?
363
+
364
+
A: Not directly. You can copy the payload and then modify the copy. For instructions, see [Copy payloads](attack-simulation-training-payloads.md#copy-payloads).
@@ -313,7 +313,7 @@ The **Delivery status** section on **Report** tab** for a simulation shows the n
313
313
314
314
-**Successfully received message**
315
315
-**Positive reinforcement message delivered**
316
-
-**Just simulation message delivered
316
+
-**Just simulation message delivered**
317
317
318
318
Select **View users to whom message delivery failed** to go to the [Users tab](attack-simulation-training-simulations.md#users-tab) tab in the report where the results are filtered by **Simulation message delivery: Failed to deliver**.
319
319
@@ -380,6 +380,71 @@ You can hover over a section in the chart to see the actual numbers in each cate
380
380
381
381
:::image type="content" source="media/attack-sim-report-training-campaign-report-tab-all-user-activity.png" alt-text="The All user activity section on the Report tab in the Training campaign report in Attack simulation training." lightbox="media/attack-sim-report-training-campaign-report-tab-all-user-activity.png":::
382
382
383
+
## Appendix
384
+
385
+
When you export information from the reports, the CSV file contains more information than what's shown in the report, even if you have all column shown. The fields are described in the following table.
386
+
387
+
> [!TIP]
388
+
> For maximum information, verify that all available columns in the report are visible before you export.
389
+
390
+
|Field Name|Description|
391
+
|---|---|
392
+
|UserName|Username of the user who did the activity.|
393
+
|UserMail|Email address of the user who did the activity.|
394
+
|Compromised|Indicates if the user was compromised. Values are Yes or No.|
395
+
|AttachmentOpened_TimeStamp|When the attachment was opened.|
396
+
|AttachmentOpened_Browser|When the attachment was opened in a web browser. This information comes from UserAgent.|
397
+
|AttachmentOpened_IP|The IP address where the attachment was opened. This information comes from UserAgent.|
398
+
|AttachmentOpened_Device|The device where the attachment was opened. This information comes from UserAgent.|
399
+
|AttachmentLinkClicked_TimeStamp|When the attachment link was clicked.|
400
+
|AttachmentLinkClicked_Browser|The web browser that was used to click the attachment link. This information comes from UserAgent.|
401
+
|AttachmentLinkClicked_IP|The IP address where the attachment link was clicked. This information comes from UserAgent.|
402
+
|AttachmentLinkClicked_Device|The device where the attachment link was clicked. This information comes from UserAgent.|
403
+
|CredSupplied_TimeStamp(Compromised)|When the user entered their credentials.|
404
+
|CredSupplied_Browser|The web browser that was used when the user entered their credentials. This information comes from UserAgent.|
405
+
|CredSupplied_IP|The IP address where the user entered their credentials. This information comes from UserAgent.|
406
+
|CredSupplied_Device|The device where the user entered their credentials. This information comes from UserAgent.|
407
+
|SuccessfullyDeliveredEmail_TimeStamp|When the simulation email message was delivered to the user.|
408
+
|MessageRead_TimeStamp|When the simulation message was read.|
409
+
|MessageDeleted_TimeStamp|When the simulation message was deleted.|
410
+
|MessageReplied_TimeStamp|When the user replied to the simulation message.|
411
+
|MessageForwarded_TimeStamp|When the user forwarded the simulation message.|
412
+
|OutOfOfficeDays|Determines whether the user is out of office. This information comes from the Automatic replies setting in Outlook.|
413
+
|PositiveReinforcementMessageDelivered_TimeStamp|When the positive reinforcement message was delivered to the user.|
414
+
|PositiveReinforcementMessageFailed_TimeStamp|When the positive reinforcement message failed to be delivered to the user.|
415
+
|JustSimulationMessageDelivered_TimeStamp|When the simulation message was delivered to the user as part of a simulation with no trainings assigned (**No training** was selected on the **Assign training** page of the new simulation wizard).|
416
+
|JustSimulationMessageFailed_TimeStamp|When the simulation email message failed to be delivered to the user, and the simulation had no trainings assigned.|
417
+
|TrainingAssignmentMessageDelivered_TimeStamp|When the training assignment message was delivered to the user. This value is empty if no trainings were assigned in the simulation.|
418
+
|TrainingAssignmentMessageFailed_TimeStamp|When the training assignment message failed to be delivered to the user. This value is empty if no trainings were assigned in the simulation.|
419
+
|FailedToDeliverEmail_TimeStamp|When the simulation email message failed to be delivered to the user.|
420
+
|Last Simulation Activity|The last simulation activity of the user (whether they passed or were compromised).|
421
+
|Assigned Trainings|The list of trainings assigned to the user as part of the simulation.|
422
+
|Completed Trainings|The list of trainings completed by the user as part of the simulation..|
423
+
|Training Status|The current status of trainings for the user as part of the simulation.|
424
+
|Phishing Reported On|When the user reported the simulation message as phishing.|
425
+
|Department|The user's Department property value in Microsoft Entra ID at the time of simulation.|
426
+
|Company|The user's Company property value in Microsoft Entra ID at the time of simulation.|
427
+
|Title|The user's Title property value in Microsoft Entra ID at the time of simulation.|
428
+
|Office|The user's Office property value in Microsoft Entra ID at the time of simulation.|
429
+
|City|The user's City property value in Microsoft Entra ID at the time of simulation.|
430
+
|Country|The user's Country property value in Microsoft Entra ID at the time of simulation.|
431
+
|Manager|The user's Manager property value in Microsoft Entra ID at the time of simulation.|
432
+
433
+
How user activity signals are captured is described in the following table.
434
+
435
+
|Field|Description|Calculation logic|
436
+
|---|---|---|
437
+
|DownloadAttachment|A user downloaded the attachment.|The signal comes from the client (for example, Outlook or Word).|
438
+
|Opened Attachment|A user opened the attachment.|The signal comes from the client (for example, Outlook or Word).|
439
+
|Read Message|The user read the simulation message.|Message read signals might experience issues in the following scenarios: <ul><li>The user reported the message as phishing in Outlook without leaving the reading pane, and **Mark items as read when viewed in the Reading Pane** wasn't configured (default).</li><li>The user reported the unread message as phishing in Outlook, the message was deleted, and **Mark messages as read when deleted** wasn't configured (default).</li></ul>|
440
+
|Out of Office|Determines whether the user is out of office.|Currently calculated by the Automatic replies setting from Outlook.|
441
+
|Compromised User|Indicates if a user been compromised. The compromise signals can vary based on the attack type.|<ul><li>**Credential Harvest**: The user enters their credentials in the login page (credentials aren't stored by Microsoft).</li><li>**Malware Attachment**: The user opens the file and enables editing in protected view.</li><li>**Link in attachment**: The user opens the attachment, and clicks on the link.</li><li>**Link to Malware**: The user clicks on the link and enters their credentials.</li><li>**Drive by URL**: The user clicks on the link (entering credentials isn't required).</li><li>**OAuth**: The user clicks on the link and accepts to share permissions.</li></ul>|
442
+
|Clicked Message Link|Indicates if a user clicked on the message .|The URL in the simulation is unique for each user, which allows individual user activity tracking. Third-party filtering services or email forwarding can lead to false positives. For more information, see [I see clicks or compromise events from users who insist they didn't click the link in the simulation message](attack-simulation-training-faq.md#i-see-clicks-or-compromise-events-from-users-who-insist-they-didnt-click-the-link-in-the-simulation-message).|
443
+
|Forwarded Message|Indicates if a user forwarded on the message .||
444
+
|Replied to Message|Indicates if an end users has replied on the message.||
445
+
|Deleted message|Indicates if an end users has deleted the message.|The signal comes from the Outlook activity of the user. If the user reports the message as phishing, the message might be moved to the Deleted Items folder, which is identified as a deletion.|
446
+
|Permissions granted|Indicates if a user shared permissions in an Oauth-based attack.||
447
+
383
448
## Related Links
384
449
385
450
[Get started using Attack simulation training](attack-simulation-training-get-started.md)
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-login-pages.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,6 +121,13 @@ When you select a login page from the list by clicking anywhere in the row other
121
121
122
122
-**Code** tab: You can view and modify the HTML code directly.
123
123
124
+
> [!TIP]
125
+
> To avoid sending passwords in plain text from custom login pages, avoid using the variable **name** in HTML code. Instead, use **type**, **id**, or **class**. For example:
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-payloads.md
+11-4Lines changed: 11 additions & 4 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 to create and manage payloads for Attack simulation training in Microsoft Defender for Office 365 Plan 2.
15
15
search.appverid: met150
16
-
ms.date: 06/12/2024
16
+
ms.date: 06/14/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
---
@@ -377,15 +377,15 @@ The create payload wizard opens with the settings and values of the selected pay
377
377
378
378
## Archive payloads
379
379
380
-
You can't delete custom payloads from the **Tenant payloads** tab, but you can archive them.
381
-
382
380
To archive an existing payload on the **Tenant payloads** tab, select the payload by clicking **⋮** (**Actions**) at the end of the row, and then select :::image type="icon" source="media/m365-cc-sc-archive-icon.png" border="false"::: **Archive**.
383
381
384
382
The **Status** value of the payload changes to **Archive**, and the payload is no longer visible on the **Tenant payloads** table when **Show archived payloads** is toggled off :::image type="icon" source="media/scc-toggle-off.png" border="false":::.
385
383
386
384
To see archived payloads on the **Tenant payloads** tab, toggle **Show archived payloads** to on :::image type="icon" source="media/scc-toggle-on.png" border="false":::.
387
385
388
-
## Restore archived payloads
386
+
After you archive a payload, you can restore it or remove it as described in the following subsections.
387
+
388
+
### Restore archived payloads
389
389
390
390
To restore an archive payload on the **Tenant payloads** tab, do the following steps:
391
391
@@ -394,6 +394,13 @@ To restore an archive payload on the **Tenant payloads** tab, do the following s
394
394
395
395
After you restore the archived payload, the **Status** value changes to **Draft**. Toggle **Show archived payloads** to off :::image type="icon" source="media/scc-toggle-off.png" border="false"::: to see the restored payload. To return the payload to the **Status** value **Ready**, [edit the payload](#modify-payloads), review or change the settings, and then select **Submit**.
396
396
397
+
### Remove archived payloads
398
+
399
+
To remove an archived payload from the **Tenant payloads** tab, do the following steps:
400
+
401
+
1. Set the **Show archived payloads** toggle to on :::image type="icon" source="media/scc-toggle-on.png" border="false":::.
402
+
2. Select the payload by clicking **⋮** (**Actions**) at the end of the row, select :::image type="icon" source="media/m365-cc-sc-delete-icon.png" border="false"::: **Delete**, and then select **Confirm** in the confirmation dialog.
403
+
397
404
## Send a test
398
405
399
406
On the **Tenant payloads** or **Global payloads** tabs, you can send a copy of the payload email to yourself (the currently logged in user) for inspection.
0 commit comments