Skip to content

Commit 004fa91

Browse files
authored
Merge branch 'main' into docs-editor/fixed-reported-inaccuracies-1744100267
2 parents bc929cb + cfd245b commit 004fa91

37 files changed

+361
-291
lines changed

CloudAppSecurityDocs/activity-filters-queries.md

Lines changed: 1 addition & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ Defender for Cloud Apps also provides you with **Suggested queries**. Suggested
135135
- Successful log in - Filters all your activities to display only those activities that involve successful sign-ins, including impersonate action, impersonate sign-in, single sign-o sign-ins, and sign-in from a new device.
136136

137137
![query activities.](media/queries-activity.png)
138-
138+
139139
Additionally, you can use the suggested queries as a starting point for a new query. First, select one of the suggested queries. Then, make changes as needed and finally select **Save as** to create a new **Saved query**.
140140

141141
### Query activities six months back
@@ -184,37 +184,6 @@ Reports that include private activities are marked with an Eye icon in the repor
184184

185185
![eye-icon](media/activity-filters-queries/eye-icon-to-indicate-private-report.png)
186186

187-
> [!NOTE]
188-
>Exporting and viewing activity data up to six months back is restricted to specific roles with elevated permissions.
189-
190-
The following roles are supported:
191-
192-
- `INVITED_ADMIN`
193-
194-
- `GLOBAL_ADMINISTRATOR`
195-
196-
- `SECURITY_ADMINISTRATOR`
197-
198-
- `MCAS_ADMINISTRATOR`
199-
200-
- `DISCOVERY_ADMIN`
201-
202-
- `SECURITY_OPERATOR`
203-
204-
- `COMPLIANCE_ADMIN`
205-
206-
- `SECURITY_READER`
207-
208-
- `GLOBAL_READER`
209-
210-
- `URBAC_ROLES_GLOBAL_ADMINISTRATOR`
211-
212-
- `URBAC_ROLES_COMPLIANCE_ADMINISTRATOR`
213-
214-
- `URBAC_ROLES_SECURITY_READER`
215-
216-
- `URBAC_ROLES_SECURITY_OPERATOR`
217-
218187
## Next steps
219188

220189
> [!div class="nextstepaction"]

CloudAppSecurityDocs/attack-paths.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,6 @@ ms.date: 03/23/2025
1010
[Microsoft Security Exposure Management](/security-exposure-management/microsoft-security-exposure-management) helps you to manage your company's attack surface and exposure risk effectively. By combining assets and techniques, [attack paths](/security-exposure-management/review-attack-paths) illustrate the end-to-end paths that attackers can use to move from an entry point within your organization to your critical assets.
1111
Microsoft Defender for Cloud Apps observed an increase in attackers using OAuth applications to access sensitive data in business-critical applications like Microsoft Teams, SharePoint, Outlook, and more. To support investigation and mitigation, these applications are integrated into the attack path and attack surface map views in Microsoft Security Exposure Management.
1212

13-
### Critical Asset Management - Service Principals
14-
15-
Microsoft Defender for Cloud Apps defines a set of critical privilege OAuth permissions. OAuth applications with these permissions are considered high-value assets. If compromised, an attacker can gain high privileges to SaaS applications. To reflect this risk, attack paths treat service principals with these permissions as target goals.
1613

1714
### Prerequisites
1815

@@ -44,21 +41,26 @@ Alternatively, you can use one of the following **Entra ID roles**:
4441
>[!NOTE]
4542
> Currently available in commercial cloud environments only. Microsoft Security Exposure Management data and capabilities are currently unavailable in U.S Government clouds - GCC, GCC High, DoD, and China Gov.
4643
47-
## View permissions for critical assets
44+
### Critical Asset Management - Service Principals
45+
46+
Microsoft Defender for Cloud Apps defines a set of critical privilege OAuth permissions. OAuth applications with these permissions are considered high-value assets. If compromised, an attacker can gain high privileges to SaaS applications. To reflect this risk, attack paths treat service principals with these permissions as target goals.
47+
48+
#### View permissions for critical assets
4849

4950
To view the full list of permissions, go to the [Microsoft Defender portal](https://security.microsoft.com) and navigate to Settings > Microsoft Defender XDR > Rules > Critical asset management.
5051

5152
:::image type="content" source="media/saas-securty-initiative/screenshot-of-the-critical-asset-management-page.png" alt-text="Screenshot of the Critical asset management page in the Defender XDR portal." lightbox="media/saas-securty-initiative/Screenshot-of-the-critical-asset-management-page.png":::
5253

53-
> [!NOTE]
54-
> OAuth apps appear in the attack path surface map only when specific conditions are detected.
55-
> For example, an OAuth app may appear in the attack path only if a vulnerable component with an easily exploitable entry point is detected that allows lateral movement to service principals with high privileges.
5654

5755
## Investigation user flow: View attack paths involving OAuth applications
5856

5957
Once you understand which permissions represent high-value targets, use the following steps to investigate how these applications appear in your environment’s attack paths.
6058
For smaller organizations with a manageable number of attack paths, we recommend following this structured approach to investigate each attack path:
6159

60+
> [!NOTE]
61+
> OAuth apps show in the attack path surface map only when specific conditions are detected.
62+
> For example, an OAuth app might appear in the attack path if a vulnerable component with an easily exploitable entry point is detected. This entry point allows lateral movement to service principals with high privileges.
63+
6264
1. Go to Exposure Management > Attack surface > Attack paths.
6365

6466
1. Filter by 'Target type: AAD Service principal'

CloudAppSecurityDocs/caac-known-issues.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,9 @@ For example, assume that a session policy is configured to prevent downloading f
5151

5252
Session policies don't protect external business-to-business (B2B) collaboration users in Microsoft Teams applications.
5353

54+
## Session Controls with Non-Interactive Tokens
55+
Some applications utilize non-interactive access tokens to facilitate seamless redirection between apps within the same suite or realm. When one application is onboarded to Conditional Access App Control and the other is not, session controls may not be enforced as expected. For example, if the Teams client retrieves a non-interactive token for SharePoint Online (SPO), it can initiate an active session in SPO without prompting the user for reauthentication. As a result, the session control mechanism cannot intercept or enforce policies on these sessions. To ensure consistent enforcement, it's recommended to onboard all relevant applications, such as Teams, alongside SPO.
56+
5457
## Limitations for sessions that the reverse proxy serves
5558

5659
The following limitations apply only on sessions that the reverse proxy serves. Users of Microsoft Edge can benefit from in-browser protection instead of using the reverse proxy, so these limitations don't affect them.

defender-endpoint/configure-endpoints-gp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Onboard Windows devices to Microsoft Defender for Endpoint via Group Policy
2+
title: Onboard Windows Servers to Microsoft Defender for Endpoint via Group Policy
33
description: Use Group Policy to deploy the configuration package on Windows devices so that they are onboarded to the service.
44
ms.service: defender-endpoint
55
ms.author: deniseb

defender-endpoint/configure-endpoints-script.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Onboard Windows devices using a local script
2+
title: Onboard Windows Servers using a local script
33
description: Use a local script to deploy the configuration package on devices to enable onboarding of the devices to the service.
44
search.appverid: met150
55
ms.service: defender-endpoint

defender-endpoint/device-health-microsoft-defender-antivirus-health.md

Lines changed: 12 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
66
ms.author: ewalsh
77
author: emmwalshh
88
ms.localizationpriority: medium
9-
ms.date: 03/13/2025
9+
ms.date: 04/08/2025
1010
manager: deniseb
1111
audience: ITPro
1212
ms.collection:
@@ -36,7 +36,7 @@ The Device Health report provides information about the devices in your organiza
3636
>
3737
> - Device is onboarded to Microsoft Defender for Endpoint
3838
> - OS: Windows 10, Windows 11, Windows Server 2012 R2/, 2016 R2/ 2019/2022 (non MMA), MacOS, Linux
39-
> - Sense (MsSense.exe): **10.8210.** \*+. See [Prerequisites](#prerequisites) section for related details.
39+
> - Sense (MsSense.exe): **10.8210.** \*+.
4040
>
4141
> For Windows Server 2012 R2 and Windows Server 2016 to appear in device health reports, these devices must be onboarded using the modern unified solution package. For more information, see [New functionality in the modern unified solution for Windows Server 2012 R2 and 2016](onboard-windows-server-2012r2-2016.md#functionality-in-the-modern-unified-solution).
4242
@@ -48,7 +48,6 @@ In the Microsoft Defender portal, in the navigation pane, select **Reports**, an
4848
- [View device health cards](#view-device-health-cards)
4949
- [Report access permissions](#report-access-permissions)
5050
- [Microsoft Defender Antivirus health tab](#microsoft-defender-antivirus-health-tab)
51-
- [Prerequisites](#prerequisites)
5251
- [Card functionality](#card-functionality)
5352
- [New Microsoft Defender Antivirus filter definitions](#new-microsoft-defender-antivirus-filter-definitions)
5453
- [Export report](#export-report)
@@ -119,20 +118,6 @@ For the three `updates` cards (also known as up-to-date reporting cards), "**No
119118
- Cloud protection isn't enabled.
120119
- Device doesn't meet pre-requisites for Antivirus engine or platform version.
121120

122-
### Prerequisites
123-
124-
Up-to-date reporting generates information for devices that meet the following criteria:
125-
126-
* **Windows:**
127-
* OS - Windows 10 1809 or later
128-
* Engine version: 1.1.19300.2+
129-
* Platform version: 4.8.2202.1+
130-
* Sense (MsSense.exe): 10.8210.*+
131-
132-
* **Linux and Mac:**
133-
* Platform version: 101.23112.*+
134-
135-
* **Cloud Protection enabled**
136121

137122
:::image type="content" source="media/device-health-defender-antivirus-health-tab.png" alt-text="Shows the Microsoft Defender Antivirus Health tab." lightbox="media/device-health-defender-antivirus-health-tab.png":::
138123

@@ -174,7 +159,7 @@ There are two different export csv functionalities through the portal:
174159

175160
- **Top level export**. You can use the top-level **Export** button to gather an all-up Microsoft Defender Antivirus health report (500-K limit).
176161

177-
:::image type="content" source="media/device-health-defender-antivirus-health-tab-export.png" alt-text="Screenshot that shows the top-level export report button." lightbox="media/device-health-defender-antivirus-health-tab-export.png":::
162+
:::image type="content" source="media/device-health-defender-antivirus-health-tab-export.png" alt-text="Screenshot that shows the top-level export report button." lightbox="media/device-health-defender-antivirus-health-tab-export.png":::
178163

179164
- **Flyout level export**. You can use the **Export** button within the flyouts to export a report to an Excel spreadsheet (100-K limit).
180165

@@ -288,14 +273,15 @@ For more information about the aforementioned terms, refer back to the section:
288273

289274
> [!NOTE]
290275
>
291-
> Up to date reporting generates information for devices that meet the following criteria:
292-
>
293-
> - Engine version: `1.1.19300.2` or later
294-
> - Platform version: `4.18.2202.1` or later
295-
> - Cloud protection enabled
296-
> - Windows OS
297-
>
298-
> Currently up to date reporting is only available for Windows devices. Cross platform devices such as Mac and Linux are listed under `no data available`.>
276+
> Up-to-date reporting generates information for devices that meet the following criteria:
277+
> * **Windows:**
278+
> * OS - Windows 10 1809 or later
279+
> * Engine version: 1.1.19300.2+
280+
> * Platform version: 4.8.2202.1+
281+
> * Sense (MsSense.exe): 10.8210.*+
282+
> * **Linux and Mac:**
283+
> * Platform version: 101.23112.*+
284+
> * **Cloud Protection enabled**
299285
300286
##### Up-to-date definitions
301287

0 commit comments

Comments
 (0)