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
We've extended the device information we send to Defender for Cloud Apps including device names, IP addresses, account UPNs and used port. For more information about our integration with Defender for Cloud Apps, see [Using Azure ATP with Defender for Cloud Apps](/defender-for-identity/deploy-defender-identity).
909
909
910
910
- Version includes improvements and bug fixes for internal sensor infrastructure.
Copy file name to clipboardExpand all lines: CloudAppSecurityDocs/release-notes.md
+23-14Lines changed: 23 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,14 @@ For news about earlier releases, see [Archive of past updates for Microsoft Defe
29
29
30
30
## May 2025
31
31
32
+
33
+
### New Applications inventory page now available in Defender XDR
34
+
35
+
The new Applications page in Microsoft Defender XDR provides a unified inventory of all SaaS and connected OAuth applications across your environment. This view helps streamline application discovery, monitoring, and risk assessment.
36
+
37
+
For more information, see [Application inventory overview](applications-inventory.md).
38
+
39
+
32
40
### Changes to Microsoft Defender for Cloud Apps SIEM agent availability
33
41
34
42
As part of our ongoing convergence process across Microsoft Defender workloads, [Microsoft Defender for Cloud Apps SIEM agents](siem.md) will be deprecated starting November 2025.
@@ -41,6 +49,7 @@ To ensure continuity and access to data currently available through Microsoft De
41
49
42
50
For detailed guidance see: [Migrate from Defender for Cloud Apps SIEM agent to supported APIs](migrate-to-supported-api-solutions.md)
43
51
52
+
44
53
### New and improved Cloud App Catalog page
45
54
46
55
The Cloud app catalog page has been revamped to meet security standards. The new design includes improved navigation, making it easier for you to discover and manage your cloud applications.
@@ -100,7 +109,7 @@ For more information, see:
100
109
101
110
The new *Permissions filter and export capabilities allow you to quickly identify apps with specific permissions to access Microsoft 365.
102
111
103
-
You can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights enable you to get deeper visibility into apps accessing emails using legacy EWS API.
112
+
You can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights enables you to get deeper visibility into apps accessing emails using legacy EWS API.
104
113
105
114
We're also expanding the coverage of privilege level feature for all popular Microsoft first-party API permissions. The enhanced coverage of privilege level classification enables you to view and monitor apps with powerful permissions into legacy and other non-Graph APIs that have access to Microsoft 365.
106
115
@@ -157,7 +166,7 @@ For more information, see:
157
166
158
167
The Enterprise application 'Microsoft Defender for Cloud Apps – Session Controls' is used internally by the Conditional Access App Control service.
159
168
Ensure there's no CA policy restricting access to this application.
160
-
For policies that restrict all or certain applications, please ensure this application is listed as an exception or confirm that the blocking policy is deliberate.
169
+
For policies that restrict all or certain applications, ensure this application is listed as an exception or confirm that the blocking policy is deliberate.
161
170
162
171
For more information, see [Sample: Create Microsoft Entra ID Conditional Access policies for use with Defender for Cloud Apps](session-policy-aad.md#sample-create-microsoft-entra-id-conditional-access-policies-for-use-with-defender-for-cloud-apps).
163
172
@@ -173,7 +182,7 @@ For more information, see:
173
182
### SaaS Security initiative in Exposure Management
174
183
175
184
[Microsoft Security Exposure Management](/security-exposure-management/) offers a focused, metric-driven way of tracking exposure in specific security areas using security [initiatives](/security-exposure-management/initiatives). The "SaaS security initiative" provides a centralized location for all best practices related to SaaS security, categorized into 12 measurable metrics. These metrics are designed to assist in effectively managing and prioritizing the large number of security recommendations.
176
-
This capability is General Availability (Worldwide) - Note Microsoft Security Exposure Management data and capabilities are currently unavailable in U.S Government clouds - GCC, GCC High and DoD
185
+
This capability is General Availability (Worldwide) - Note Microsoft Security Exposure Management data and capabilities are currently unavailable in U.S Government clouds - GCC, GCC High, and DoD
177
186
178
187
For more information, see [SaaS security initiative](saas-security-initiative.md).
179
188
@@ -191,13 +200,13 @@ For more information, see [filters on app governance](/defender-cloud-apps/app-g
191
200
192
201
### Visibility into privilege level for popular Microsoft first-party APIs (Preview)
193
202
194
-
Defender for Cloud Apps users who use app governance can now gain visibility into privilege level for all popular Microsoft first-party API permissions. The enhanced coverage of privilege level classification will enable you to view and monitor apps with powerful permissions into legacy and other non-Graph APIs that have access to Microsoft 365.
203
+
Defender for Cloud Apps users who use app governance can now gain visibility into privilege level for all popular Microsoft first-party API permissions. The enhanced coverage of privilege level classification enables you to view and monitor apps with powerful permissions into legacy and other non-Graph APIs that have access to Microsoft 365.
195
204
196
205
For more information, see [OAuth app permission related details on app governance](/defender-cloud-apps/app-governance-visibility-insights-view-apps#getting-detailed-information-on-an-app).
197
206
198
207
### Granular data usage insights into EWS API access (Preview)
199
208
200
-
Defender for Cloud Apps users who use app governance can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights will enable you to get deeper visibility into apps accessing emails using legacy EWS API.
209
+
Defender for Cloud Apps users who use app governance can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights enable you to get deeper visibility into apps accessing emails using legacy EWS API.
201
210
202
211
For more information, see [OAuth app data usage insights on app governance](/defender-cloud-apps/app-governance-visibility-insights-view-apps#getting-detailed-information-on-an-app).
203
212
@@ -206,7 +215,7 @@ For more information, see [OAuth app data usage insights on app governance](/def
206
215
### New anomaly data in advanced hunting CloudAppEvents table
207
216
208
217
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.
209
-
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.
218
+
The new columns are designed to assist you to better __identify uncommon activities__ that might appear suspicious, and allow you to create more accurate custom detections, and investigate any suspicious activities that arise.
210
219
211
220
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
212
221
@@ -227,13 +236,13 @@ For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/micro
227
236
228
237
## September 2024
229
238
230
-
### Enforce Edge in-browser when accessing business apps
239
+
### Enforce Microsoft Edge in-browser when accessing business apps
231
240
232
-
Administrators who understand the power of Edge in-browser protection, can now require their users to use Edge when accessing corporate resources.
241
+
Administrators who understand the power of Microsoft Edge in-browser protection, can now require their users to use Microsoft Edge when accessing corporate resources.
233
242
234
-
A primary reason is security, since the barrier to circumventing session controls using Edge is much higher than with reverse proxy technology.
243
+
A primary reason is security, since the barrier to circumventing session controls using Microsoft Edge is higher than with reverse proxy technology.
235
244
236
-
For more information, see [Enforce Edge in-browser protection when accessing business apps](in-browser-protection.md#enforce-microsoft-edge-browser-protection-when-accessing-business-apps).
245
+
For more information, see [Enforce Microsoft Edge in-browser protection when accessing business apps](in-browser-protection.md#enforce-microsoft-edge-browser-protection-when-accessing-business-apps).
237
246
238
247
### Connect Mural to Defender for Cloud Apps (Preview)
239
248
@@ -248,13 +257,13 @@ For more information, see:
248
257
249
258
### Removing the ability to email end users about blocked actions
250
259
251
-
Effective October 1st, 2024, we will discontinue the feature that notifies end users via email when their action is blocked by session policies.
260
+
Effective October 1, 2024, we'll discontinue the feature that notifies end users via email when their action is blocked by session policies.
252
261
253
262
This option ensures that if a user's action is blocked, they get both a browser message and an email notification.
254
263
255
264
Admins can no longer configure this setting when creating new session policies.
256
265
257
-
Existing session policies with this setting will not trigger email notifications to end users when a block action occurs.
266
+
Existing session policies with this setting won't trigger email notifications to end users when a block action occurs.
258
267
259
268
End users will continue to receive the block message directly through the browser and will stop receiving block notification via email.
260
269
@@ -293,7 +302,7 @@ For more information, see [Configure custom URL for MDA block pages](mde-govern.
293
302
294
303
### In-browser protection for macOS users and newly supported policies (Preview)
295
304
296
-
Edge browser users from macOS who are scoped to session policies are now protected with in-browser protection.
305
+
Microsoft Edge browser users from macOS who are scoped to session policies are now protected with in-browser protection.
297
306
298
307
The following session policies are now supported:
299
308
@@ -304,7 +313,7 @@ The following session policies are now supported:
304
313
305
314
See [In-browser protection](in-browser-protection.md).
306
315
307
-
In-browser protection is supported with the last 2 stable versions of Edge (for example, if the newest Edge is 126, in-browser protection works for v126 and v125).
316
+
In-browser protection is supported with the last two stable versions of Microsoft Edge (for example, if the newest Microsoft Edge is 126, in-browser protection works for v126 and v125).
308
317
309
318
See [Microsoft Edge releases](/deployedge/microsoft-edge-release-schedule#microsoft-edge-releases).
Copy file name to clipboardExpand all lines: defender-endpoint/attack-surface-reduction-rules-reference.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,7 @@ The following table lists the supported operating systems for rules that are cur
131
131
|[Block rebooting machine in Safe Mode](#block-rebooting-machine-in-safe-mode)| Y | Y | Y |
132
132
|[Block untrusted and unsigned processes that run from USB](#block-untrusted-and-unsigned-processes-that-run-from-usb)| Y | Y | Y |
133
133
|[Block use of copied or impersonated system tools](#block-use-of-copied-or-impersonated-system-tools)| Y | Y | Y |
134
-
|[Block Webshell creation for Servers](#block-webshell-creation-for-servers)| N | Y <br>Exchange role only| Y <br>Exchange role only |
134
+
|[Block Webshell creation for Servers](#block-webshell-creation-for-servers)| N | Y <br>Exchange role only|Y on Windows Server 2016 <br>Exchange role only <br>N on Windows Server 2012 R2|
135
135
|[Block Win32 API calls from Office macros](#block-win32-api-calls-from-office-macros)| Y | N | N |
136
136
|[Use advanced protection against ransomware](#use-advanced-protection-against-ransomware)| Y <br> version 1803 or later | Y | Y |
Copy file name to clipboardExpand all lines: defender-xdr/advanced-hunting-oauthappinfo-table.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,9 +37,9 @@ The `OAuthAppInfo` table might not include all the app or service principal-rela
37
37
38
38
## Prerequisites
39
39
40
-
This advanced hunting table is populated by app governance records from Microsoft Defender for Cloud Apps. To turn on app governance, follow the steps in [Turn on app governance](/defender-cloud-apps/app-governance-get-started).
40
+
This advanced hunting table is populated by app governance records from Microsoft Defender for Cloud Apps.
41
41
42
-
If your organization hasn’t deployed Microsoft Defender for Cloud Apps in Microsoft Defender XDR nor turned on app governance, you can't view the `OAuthAppInfo` table in advanced hunting.
42
+
You need to turn on app governance to view the `OAuthAppInfo` table in advanced hunting. To turn on app governance, follow the steps in [Turn on app governance](/defender-cloud-apps/app-governance-get-started).
Copy file name to clipboardExpand all lines: defender-xdr/data-privacy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ Customer data stored by integrated services might also be stored in the followin
56
56
57
57
Microsoft Defender XDR data is retained for 180 days, and is visible across the Microsoft Defender portal during that time, except for in **Advanced hunting** queries.
58
58
59
-
In the Microsoft Defender portal's **Advanced hunting** page, data is accessible via queries for only 30 days, unless it's streamed through [Microsoft Sentinel with Microsoft's unified security operations platform](/azure/sentinel/microsoft-365-defender-sentinel-integration?toc=%2Fdefender-xdr%2Ftoc.json&bc=%2Fdefender-xdr%2Fbreadcrumb%2Ftoc.json&tabs=defender-portal), where retention periods may be longer.
59
+
In the Microsoft Defender portal's **Advanced hunting** page, data is accessible via queries for only 30 days, unless it's streamed through [Microsoft Sentinel](/azure/sentinel/microsoft-365-defender-sentinel-integration?toc=%2Fdefender-xdr%2Ftoc.json&bc=%2Fdefender-xdr%2Fbreadcrumb%2Ftoc.json&tabs=defender-portal), where retention periods may be longer.
60
60
61
61
Data continues to be retained and visible, even when a license is under a grace period or in suspended mode. At the end of any grace period or suspension, and no later than 180 days from a contract termination or expiration, data is deleted from Microsoft's systems and is unrecoverable.
Copy file name to clipboardExpand all lines: defender-xdr/incidents-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ appliesto:
27
27
28
28
# Incidents and alerts in the Microsoft Defender portal
29
29
30
-
Microsoft's unified SecOps platform in the Microsoft Defender portal brings together a unified set of security services to reduce your exposure to security threats, improve your organizational security posture, detect security threats, and investigate and respond to breaches. These services collect and produce signals that are displayed in the portal. The two main kinds of signals are:
30
+
The Microsoft Defender portal brings together a unified set of security services to reduce your exposure to security threats, improve your organizational security posture, detect security threats, and investigate and respond to breaches. These services collect and produce signals that are displayed in the portal. The two main kinds of signals are:
31
31
32
32
**Alerts**: Signals that result from various threat detection activities. These signals indicate the occurrence of malicious or suspicious events in your environment.
Copy file name to clipboardExpand all lines: defender-xdr/investigate-incidents.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ If the incident or related alerts were the result of an analytics rule you've se
107
107
108
108
> [!NOTE]
109
109
> To view the details of an attack path, you must have read access permissions in the Microsoft Defender portal and the license for [Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management). </br></br>
110
-
> To view attack path details with Microsoft Sentinel in the unified security operations platform, a *Sentinel Reader* role is required. To create new attack paths, the *Security Administrator* role is required.
110
+
> To view attack path details with Microsoft Sentinel in the Defender portal, a *Sentinel Reader* role is required. To create new attack paths, the *Security Administrator* role is required.
111
111
112
112
The incident graph also contains information about **attack paths**. These paths allow security analysts to identify what other entities an attacker is likely to target next. To view an attack path, you can click on an entity in the incident graph and select **View attack paths**. The top attack paths are shown within the incident graph. Here's an example.
|False positive </br> Includes not malicious, not enough data to validate, etc.|Dismissed|
137
137
138
138
For more information about alert statuses and classifications in Microsoft Defender XDR, see [Manage alerts in Microsoft Defender](investigate-alerts.md#manage-alerts).
@@ -213,4 +213,4 @@ If you are using automation on Microsoft Sentinel incidents, note that automatio
213
213
After investigating an insider risk incident or alert, you can do any of the following:
214
214
215
215
- Continue to respond to the alert in the Microsoft Purview portal.
216
-
- Use advanced hunting to investigate other insider risk management events in the Microsoft Defender portal.
216
+
- Use advanced hunting to investigate other insider risk management events in the Microsoft Defender portal.
0 commit comments