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: CloudAppSecurityDocs/release-notes.md
+27-3Lines changed: 27 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,30 @@ For more information on what's new with other Microsoft Defender security produc
20
20
For news about earlier releases, see [Archive of past updates for Microsoft Defender for Cloud Apps](release-note-archive.md).
21
21
22
22
23
+
## October 2024
24
+
25
+
### New anomaly data in advanced hunting CloudAppEvents table
26
+
27
+
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal, can now utilize the new *LastSeenForUser* and *UncommonForUser* columns for queries and detections rules.
28
+
The new columns are designed to assist you to better __identify uncommon activities__ that may appear suspicious, and allow you to create more accurate custom detections, as well as investigate any suspicious activities that arise.
29
+
30
+
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
31
+
32
+
### New Conditional Access app control / inline data in advanced hunting CloudAppEvents table
33
+
34
+
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new *AuditSource* and *SessionData* columns for queries and detection rules.
35
+
Using this data allows for queries that consider specific audit sources, including access and session control, and queries by specific inline sessions.
36
+
37
+
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
38
+
39
+
### New data in advanced hunting CloudAppEvents table - OAuthAppId
40
+
41
+
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new _OAuthAppId_ column for queries and detection rules.
42
+
43
+
Using _OAuthAppId_ allows the queries that consider specific OAuth applications, making queries and detection rules more accurate.
44
+
45
+
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
46
+
23
47
## September 2024
24
48
25
49
### Enforce Edge in-browser when accessing business apps
@@ -28,7 +52,7 @@ Administrators who understand the power of Edge in-browser protection, can now r
28
52
A primary reason is security, since the barrier to circumventing session controls using Edge is much higher than with reverse proxy technology.
29
53
30
54
For more information see:
31
-
[Enforce Edge in-browser protection when accessing business apps](https://learn.microsoft.com/defender-cloud-apps/in-browser-protection#enforce-edge-in-browser-when-accessing-business-apps)
55
+
[Enforce Edge in-browser protection when accessing business apps](/defender-cloud-apps/in-browser-protection)
32
56
33
57
### Connect Mural to Defender for Cloud Apps (Preview)
34
58
@@ -146,7 +170,7 @@ Microsoft Defender for Cloud Apps log collector now supports [Azure Kubernetes S
146
170
147
171
For more information, see [Configure automatic log upload using Docker on Azure Kubernetes Service (AKS)](discovery-kubernetes.md).
148
172
149
-
### New Conditional Access app control / inline data for the advanced hunting CloudAppEvents table
173
+
### New Conditional Access app control / inline data for the advanced hunting CloudAppEvents table (Preview)
150
174
151
175
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new *AuditSource* and *SessionData* columns for queries and detection rules. Using this data allows for queries that consider specific audit sources, including access and session control, and queries by specific inline sessions.
152
176
@@ -224,7 +248,7 @@ Automatic log collection is supported using a Docker container on multiple opera
224
248
225
249
For more information, see [Configure automatic log upload using Podman](discovery-linux-podman.md).
226
250
227
-
### New anomaly data for the advanced hunting CloudAppEvents table
251
+
### New anomaly data for the advanced hunting CloudAppEvents table (Preview)
228
252
229
253
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal can now use the new *LastSeenForUser* and *UncommonForUser* columns for queries and detections rules. Using this data helps to rule out false positives and find anomalies.
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-get-started.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ The following social engineering techniques are available:
102
102
103
103
-**How-to Guide**: A teaching guide that contains instructions for users (for example, how to report phishing messages).
104
104
105
-
<sup>\*</sup> The link can be a URL or a QR code. QR code support in Attack simulation training is currently in preview.
105
+
<sup>\*</sup> The link can be a URL or a QR code.
106
106
107
107
The URLs that are used by Attack simulation training are listed in the following table:
108
108
@@ -180,9 +180,6 @@ In simulations that use **Credential Harvest** or **Link in Attachment** social
180
180
181
181
The best training experience for simulated phishing messages is to make them as close as possible to real phishing attacks that your organization might experience. What if you could capture and use harmless versions of real-world phishing messages that were detected in Microsoft 365 and use them in simulated phishing campaigns? You can, with _payload automations_ (also known as _payload harvesting_). To create payload automations, see [Payload automations for Attack simulation training](attack-simulation-training-payload-automations.md).
182
182
183
-
> [!TIP]
184
-
> QR code payloads are currently in Preview, aren't available in all organizations, and are subject to change.
185
-
186
183
Attack simulation training also supports using QR codes in payloads. You can choose from the list of built-in QR code payloads, or you can create custom QR code payloads. For more information, see [QR code payloads in Attack simulation training](attack-simulation-training-payloads.md#qr-code-payloads).
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-insights.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -281,9 +281,6 @@ For more information about the **Users** and **Details** tabs, see the following
281
281
282
282
### Reporting for QR code simulations
283
283
284
-
> [!TIP]
285
-
> QR code payloads are currently in Preview, aren't available in all organizations, and are subject to change.
286
-
287
284
You can select QR code payloads to use in simulations. The QR code replaces the phishing URL as the payload that's used in the simulation email message. For more information, see [QR code payloads](attack-simulation-training-payloads.md#qr-code-payloads).
288
285
289
286
Because QR codes are a different type of a phishing URL, user events around read, delete, compromise, and click events remain the same. For example, scanning the QR code opens the phishing URL, so the event is tracked as a click event. The existing mechanisms for tracking compromise, deletes, and report events remain the same.
@@ -426,7 +423,7 @@ When you export information from the reports, the CSV file contains more informa
426
423
|EmailLinkClicked_Browser|The web browser that was used to click the link payload in **Credential Harvest**, **Link to Malware**, **Drive-by-url**, and **OAuth Consent Grant** simulations. This information comes from UserAgent.|
427
424
|EmailLinkClicked_IP|The IP address where the link payload was clicked in **Credential Harvest**, **Link to Malware**, **Drive-by-url**, and **OAuth Consent Grant** simulations. This information comes from UserAgent.|
428
425
|EmailLinkClicked_Device|The device where the link payload was clicked in **Credential Harvest**, **Link to Malware**, **Drive-by-url**, and **OAuth Consent Grant** simulations. This information comes from UserAgent.|
429
-
|EmailLinkClicked_ClickSource|Whether the payload link was selected by clicking on a URL or scanning a QR Code in **Credential Harvest**, **Link to Malware**, **Drive-by-url**, and **OAuth Consent Grant** simulations. Values are `PhishingURL` or `QRCode`. QR code support is currently in Preview.|
426
+
|EmailLinkClicked_ClickSource|Whether the payload link was selected by clicking on a URL or scanning a QR Code in **Credential Harvest**, **Link to Malware**, **Drive-by-url**, and **OAuth Consent Grant** simulations. Values are `PhishingURL` or `QRCode`.|
430
427
|CredSupplied_TimeStamp(Compromised)|When the user entered their credentials.|
431
428
|CredSupplied_Browser|The web browser that was used when the user entered their credentials. This information comes from UserAgent.|
432
429
|CredSupplied_IP|The IP address where the user entered their credentials. This information comes from UserAgent.|
@@ -472,7 +469,7 @@ How user activity signals are captured is described in the following table.
472
469
|Deleted message|The user 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.|
473
470
|Permissions granted|The user shared permissions in an **OAuth Consent Grant** simulation.||
474
471
475
-
¹ The clicked link can be a selected URL or a scanned QR code (QR code support in Attack simulation training is currently in Preview).
472
+
¹ The clicked link can be a selected URL or a scanned QR code.
In Attack simulation training in Microsoft 365 E5 or Microsoft Defender for Office 365 Plan 2, a _payload_ is the link, QR code (currently in Preview), or attachment in the simulated phishing email message that's presented to users. Attack simulation training offers a robust built-in payload catalog for the available social engineering techniques. However, you might want to create custom payloads that work better for your organization.
25
+
In Attack simulation training in Microsoft 365 E5 or Microsoft Defender for Office 365 Plan 2, a _payload_ is the link, QR code, or attachment in the simulated phishing email message that's presented to users. Attack simulation training offers a robust built-in payload catalog for the available social engineering techniques. However, you might want to create custom payloads that work better for your organization.
26
26
27
27
For getting started information about Attack simulation training, see [Get started using Attack simulation training](attack-simulation-training-get-started.md).
28
28
@@ -133,9 +133,6 @@ To see payloads that have been archived (the **Status** value is **Archive**), u
133
133
134
134
## QR code payloads
135
135
136
-
> [!TIP]
137
-
> QR code payloads are currently in Preview, aren't available in all organizations, and are subject to change.
138
-
139
136
On the **Global payloads** tab of **Content library**\>**Payloads** at <https://security.microsoft.com/attacksimulator?viewid=contentlibrary&source=global>, you can see the built-in, unmodifiable QR code payloads by typing **QR** in the :::image type="icon" source="media/m365-cc-sc-search-icon.png" border="false"::: **Search** box, and then pressing the ENTER key.
140
137
141
138
QR code payloads are available in five languages to address real-world scenarios that involve QR code attacks.
@@ -178,7 +175,7 @@ You can also create custom payloads that use QR codes as phishing links as descr
178
175
-**OAuth Consent Grant**<sup>\*</sup>
179
176
-**How-to Guide**
180
177
181
-
<sup>\*</sup> This social engineering technique allows you to use QR codes (currently in Preview).
178
+
<sup>\*</sup> This social engineering technique allows you to use QR codes.
182
179
183
180
For more information about the different social engineering techniques, see [Simulations](attack-simulation-training-get-started.md#simulations).
184
181
@@ -239,7 +236,7 @@ You can also create custom payloads that use QR codes as phishing links as descr
239
236
-**Text** tab: A rich text editor is available to create the payload. To see the typical font and formatting settings, toggle **Formatting controls** to :::image type="icon" source="media/scc-toggle-on.png" border="false"::: **On**.
240
237
241
238
> [!TIP]
242
-
> The **Formatting controls** bar contains an **Insert QR code** action that you can use instead of selecting **Insert QR code** control from the **Dynamic tag** dropdown list for applicable social engineering techniques (currently in Preview):
239
+
> The **Formatting controls** bar contains an **Insert QR code** action that you can use instead of selecting **Insert QR code** control from the **Dynamic tag** dropdown list for applicable social engineering techniques:
243
240
>
244
241
> :::image type="content" source="media/attack-sim-training-payloads-formatting-controls-insert-qr-code.png" alt-text="The Insert QR code action in the formatting controls on the Configure payload page of the new payload creation wizard.":::
245
242
>
@@ -262,7 +259,7 @@ You can also create custom payloads that use QR codes as phishing links as descr
262
259
|**Insert City**|`${city}`|
263
260
|**Insert Date**|`${date|MM/dd/yyyy|offset}`|
264
261
265
-
- The **Insert QR code** control (currently in Preview) is available only in the **Credential Harvest**, **Drive-by URL**, **OAuth Consent Grant**, or **How-to Guide** techniques.
262
+
- The **Insert QR code** control is available only in the **Credential Harvest**, **Drive-by URL**, **OAuth Consent Grant**, or **How-to Guide** techniques.
266
263
267
264
Instead of using a link as the phishing payload in the message, you can use a QR code. Selecting the **Insert QR code** control opens the **Insert QR code** flyout where you configure the following information:
Copy file name to clipboardExpand all lines: defender-office-365/attack-simulation-training-simulations.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ On the **Select technique** page, select an available social engineering techniq
54
54
-**OAuth Consent Grant**<sup>\*</sup>
55
55
-**How-to Guide**<sup>\*</sup>
56
56
57
-
<sup>\*</sup> This social engineering technique allows you to use QR codes (currently in Preview). For more information, see the [QR code simulations and training](#qr-code-simulations-and-training) section later in this article.
57
+
<sup>\*</sup> This social engineering technique allows you to use QR codes. For more information, see the [QR code simulations and training](#qr-code-simulations-and-training) section later in this article.
58
58
59
59
If you select the **View details** link in the description, a details flyout opens that describes the technique and the simulation steps that result from the technique.
60
60
@@ -632,9 +632,6 @@ Back on the **Simulations** tab, the simulation that you created is now listed.
632
632
633
633
## QR code simulations and training
634
634
635
-
> [!TIP]
636
-
> QR code payloads are currently in Preview, aren't available in all organizations, and are subject to change.
637
-
638
635
You can select payloads with QR codes to use in simulations. The QR code replaces the phishing URL as the payload that's used in the simulation email message in the following social engineering techniques:
0 commit comments