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
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,16 @@ For news about earlier releases, see [Archive of past updates for Microsoft Defe
21
21
22
22
## March 2025
23
23
24
+
### Enhanced Identity Inventory (Preview)
25
+
26
+
The Identities page under *Assets* has been updated to provide better visibility and management of identities across your environment. The updated Identities Inventory page now includes the following tabs:
27
+
28
+
- Identities: A consolidated view of identities across Active Directory, Entra ID. This Identities tab highlights key details, including identity types, and user's information.
29
+
30
+
- Cloud application accounts: Provides insights into accounts from connected applications via Defender for Cloud Apps, allowing investigation of account permissions, group memberships, aliases, and the applications in use.
31
+
32
+
For more information, see [Identity inventory details](/defender-for-identity/identity-inventory), [Cloud application accounts](/defender-cloud-apps/accounts).
33
+
24
34
### Role-Based Access Control scoping for "Behaviors" (Preview)
25
35
26
36
Defender for Cloud Apps customers can now configure Role-Based Access Control (RBAC) scoping for 'Behaviors.' This new capability allows administrators to define and manage access permissions more precisely. Administrators can ensure that users have the appropriate level of access to specific application data based on their roles and responsibilities. By using RBAC scoping, organizations can enhance their security posture, streamline operations, and reduce the risk of unauthorized access.
Copy file name to clipboardExpand all lines: defender-endpoint/cloud-protection-microsoft-antivirus-sample-submission.md
+17-23Lines changed: 17 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.reviewer: mkaminska, yongrhee
9
9
manager: deniseb
10
10
ms.subservice: ngp
11
11
ms.topic: conceptual
12
-
ms.date: 08/20/2024
12
+
ms.date: 03/18/2025
13
13
ms.collection:
14
14
- m365-security
15
15
- tier2
@@ -21,15 +21,15 @@ search.appverid: met150
21
21
22
22
**Applies to:**
23
23
24
-
-[Microsoft Defender for Endpoint Plan 1](microsoft-defender-endpoint.md)
25
-
-[Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
24
+
- Microsoft Defender for Endpoint Plan 1 and Plan 2
25
+
- Microsoft Defender for Endpoint for servers
26
26
- Microsoft Defender Antivirus
27
27
28
28
**Platforms**
29
+
29
30
- Windows
30
31
- macOS
31
32
- Linux
32
-
33
33
- Windows Server
34
34
35
35
Microsoft Defender Antivirus uses many intelligent mechanisms for detecting malware. One of the most powerful capabilities is the ability to apply the power of the cloud to detect malware and perform rapid analysis. Cloud protection and automatic sample submission work together with Microsoft Defender Antivirus to help protect against new and emerging threats.
@@ -54,24 +54,24 @@ Microsoft Defender Antivirus and cloud protection automatically block most new,
54
54
55
55
3. High-precision antivirus, detecting common malware through generic and heuristic techniques.
56
56
57
-
4. Advanced cloud-based protection is provided for cases when Microsoft Defender Antivirus running on the endpoint needs more intelligence to verify the intent of a suspicious file.
57
+
1. Advanced cloud-based protection is provided for cases when Microsoft Defender Antivirus running on the endpoint needs more intelligence to verify the intent of a suspicious file.
58
58
59
59
1. In the event Microsoft Defender Antivirus can't make a clear determination, file metadata is sent to the cloud protection service. Often within milliseconds, the cloud protection service can determine based on the metadata as to whether the file is malicious or not a threat.
60
60
61
61
- The cloud query of file metadata can be a result of behavior, mark of the web, or other characteristics where a clear verdict isn't determined.
62
62
- A small metadata payload is sent, with the goal of reaching a verdict of malware or not a threat. The metadata doesn't include personal data, such as personally identifiable information (PII). Information such as filenames, are hashed.
63
-
- Can be synchronous or asynchronous. For synchronous, the file won't open until the cloud renders a verdict. For asynchronous, the file opens while cloud protection performs its analysis.
63
+
- Can be synchronous or asynchronous. For synchronous, the file doesn't open until the cloud renders a verdict. For asynchronous, the file opens while cloud protection performs its analysis.
64
64
- Metadata can include PE attributes, static file attributes, dynamic and contextual attributes, and more (see [Examples of metadata sent to the cloud protection service](#examples-of-metadata-sent-to-the-cloud-protection-service)).
65
65
66
66
2. After examining the metadata, if Microsoft Defender Antivirus cloud protection can't reach a conclusive verdict, it can request a sample of the file for further inspection. This request honors the setting configuration for sample submission, as described in the following table:
67
-
67
+
68
68
| Setting | Description |
69
69
|---|---|
70
70
|**Send safe samples automatically**| - Safe samples are samples considered to not commonly contain PII data. Examples include `.bat`, `.scr`, `.dll`, and `.exe`. <br/>- If file is likely to contain PII, the user gets a request to allow file sample submission.<br/>- This option is the default configuration on Windows, macOS, and Linux. |
71
71
|**Always Prompt**| - If configured, the user is always prompted for consent before file submission<br/>- This setting isn't available in macOS and Linux cloud protection |
72
-
|**Send all samples automatically**| - If configured, all samples are sent automatically<br/>- If you would like sample submission to include macros embedded in Word docs, you must choose **Send all samples automatically**<br/>- This setting isn't available on macOS cloud protection|
72
+
|**Send all samples automatically**| - If configured, all samples are sent automatically<br/>- If you would like sample submission to include macros embedded in Word docs, you must choose **Send all samples automatically**<br/>- "Send all samples automatically" is the equivalent to "All" setting in macOS policy|
73
73
|**Do not send**| - Prevents "block at first sight" based on file sample analysis<br/>- "Don't send" is the equivalent to the "Disabled" setting in macOS policy and "None" setting in Linux policy.<br/>- Metadata is sent for detections even when sample submission is disabled |
74
-
74
+
75
75
3. After files are submitted to cloud protection, the submitted files can be **scanned**, **detonated**, and processed through **big data analysis****machine-learning** models to reach a verdict. Turning off cloud-delivered protection limits analysis to only what the client can provide through local machine-learning models, and similar functions.
76
76
77
77
> [!IMPORTANT]
@@ -107,9 +107,9 @@ The following table lists examples of metadata sent for analysis by cloud protec
107
107
108
108
## Samples are treated as customer data
109
109
110
-
Just in case you're wondering what happens with sample submissions, Defender for Endpoint treats all file samples as customer data. Microsoft honors both the geographical and data retention choices your organization selected when onboarding to Defender for Endpoint.
110
+
If you're wondering what happens with sample submissions, Defender for Endpoint treats all file samples as customer data. Microsoft honors both the geographical and data retention choices your organization selected when onboarding to Defender for Endpoint.
111
111
112
-
In addition, Defender for Endpoint has received multiple compliance certifications, demonstrating continued adherence to a sophisticated set of compliance controls:
112
+
In addition, Defender for Endpoint received multiple compliance certifications, demonstrating continued adherence to a sophisticated set of compliance controls:
113
113
114
114
- ISO 27001
115
115
- ISO 27018
@@ -129,21 +129,15 @@ There are two more scenarios where Defender for Endpoint might request a file sa
129
129
| Scenario | Description |
130
130
|:---|:---|
131
131
|Manual file sample collection in the Microsoft Defender portal | When onboarding devices to Defender for Endpoint, you can configure settings for [endpoint detection and response (EDR)](overview-endpoint-detection-response.md). For example, there's a setting to enable sample collections from the device, which can easily be confused with the sample submission settings described in this article. <br/><br/>The EDR setting controls file sample collection from devices when requested through the Microsoft Defender portal, and is subject to the roles and permissions already established. This setting can allow or block file collection from the endpoint for features such as deep analysis in the Microsoft Defender portal. If this setting isn't configured, the default is to enable sample collection. <br/><br/>Learn about Defender for Endpoint configuration settings, see: [Onboarding tools and methods for Windows 10 devices in Defender for Endpoint](onboard-windows-client.md)|
132
-
| Automated investigation and response content analysis | When [automated investigations](automated-investigations.md) are running on devices (when configured to run automatically in response to an alert or manually run), files that are identified as suspicious can be collected from the endpoints for further inspection. If necessary, the file content analysis feature for automated investigations can be disabled in the Microsoft Defender portal. <br/><br/> The file extension names can also be modified to add or remove extensions for other file types that will be automatically submitted during an automated investigation. <br/><br/> To learn more, see [Manage automation file uploads](manage-automation-file-uploads.md). |
132
+
| Automated investigation and response content analysis | When [automated investigations](automated-investigations.md) are running on devices (when configured to run automatically in response to an alert or manually run), files that are identified as suspicious can be collected from the endpoints for further inspection. If necessary, the file content analysis feature for automated investigations can be disabled in the Microsoft Defender portal. <br/><br/> The file extension names can also be modified to add or remove extensions for other file types that are automatically submitted during an automated investigation. <br/><br/> To learn more, see [Manage automation file uploads](manage-automation-file-uploads.md). |
133
133
134
-
> [!TIP]
135
-
> If you're looking for Antivirus related information for other platforms, see:
136
-
> -[Set preferences for Microsoft Defender for Endpoint on macOS](mac-preferences.md)
137
-
> -[Microsoft Defender for Endpoint on Mac](microsoft-defender-endpoint-mac.md)
138
-
> -[macOS Antivirus policy settings for Microsoft Defender Antivirus for Intune](/mem/intune/protect/antivirus-microsoft-defender-settings-macos)
139
-
> -[Set preferences for Microsoft Defender for Endpoint on Linux](linux-preferences.md)
140
-
> -[Microsoft Defender for Endpoint on Linux](microsoft-defender-endpoint-linux.md)
141
-
> -[Configure Defender for Endpoint on Android features](android-configure.md)
142
-
> -[Configure Microsoft Defender for Endpoint on iOS features](ios-configure-features.md)
With the increased use of collaboration tools like Microsoft Teams, the possibility of malicious attacks using chat messages has also increased. Microsoft Defender for Office 365 already provides time of click protection for URLs and files in Teams messages through [Safe Links for Microsoft Teams](safe-links-about.md#safe-links-settings-for-microsoft-teams) and [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](safe-attachments-for-spo-odfb-teams-about.md).
30
+
With the increased use of collaboration tools like Microsoft Teams, the possibility of malicious attacks using chat messages has also increased. Microsoft Defender for Office 365 already provides time of click protection for URLs and files in Teams messages through [Safe Links for Microsoft Teams](safe-links-about.md#safe-links-settings-for-microsoft-teams) and [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](safe-attachments-for-spo-odfb-teams-about.md). You can allow/block [URLs] (tenant-allow-block-list-urls-configure.md) and [files](tenant-allow-block-list-files-configure.md) inside Teams using Tenant Allow Block Lists.
31
31
32
32
In Microsoft 365 E5 and Defender for Office 365 Plan 2, we've extended Teams protection with a set of capabilities that are designed to disrupt the attack chain:
33
33
@@ -160,3 +160,5 @@ For detailed syntax and parameter information, see [Set-TeamsProtectionPolicyRul
-[Managing Teams quarantined messages](quarantine-admin-manage-messages-files.md#use-the-microsoft-defender-portal-to-manage-microsoft-teams-quarantined-messages)
162
162
-[Get started using Attack simulation training in Defender for Office 365](attack-simulation-training-get-started.md)
163
+
-[Get started with Defender for Cloud Apps for Microsoft Teams] (/defender-cloud-apps/what-is-defender-for-cloud-apps)
164
+
-[Get started with Compliance and DLP protection for Microsoft Teams ] (/microsoftteams/security-compliance-overview)
Copy file name to clipboardExpand all lines: defender-office-365/scc-permissions.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,8 +196,8 @@ Roles that aren't assigned to the Organization Management role group by default
196
196
|<sup>\*</sup>**Manage Review Set Tags**|This role lets users create, edit, and delete review set tags for cases they can access.|eDiscovery Manager|
197
197
|**Organization Configuration**|Run, view, and export audit reports and manage compliance policies for DLP, devices, and preservation.|Compliance Administrator <br/><br/> Compliance Data Administrator <br/><br/> Organization Management|
198
198
|<sup>\*</sup>**Preview**|View a list of items that are returned from content searches, and open each item from the list to view its contents.|Data Investigator <br/><br/> eDiscovery Manager|
|**Priority Cleanup Admin**|Access Priority Cleanup tab within Data Lifecycle Management to create, update and delete policies and modify Priority Cleanup settings for the tenant |Organization Management|
200
+
|**Priority Cleanup Viewer**|Access Priority Cleanup tab within Data Lifecycle Management to view policies|Organization Management|
201
201
|<sup>\*</sup>**Privacy Management Admin**|Manage policies in Privacy Management and has access to all functionality of the solution.|Privacy Management <br/><br/> Privacy Management Administrators|
202
202
|<sup>\*</sup>**Privacy Management Analysis**|Perform investigation and remediation of the message violations in Privacy Management. Can only view messages metadata.|Privacy Management <br/><br/> Privacy Management Analysts|
203
203
|<sup>\*</sup>**Privacy Management Investigation**|Perform investigation, remediation, and review message violations in Privacy Management. Can view message metadata and the full message.|Privacy Management <br/><br/> Privacy Management Investigators|
@@ -209,7 +209,7 @@ Roles that aren't assigned to the Organization Management role group by default
|**RecordManagement**|View and edit the configuration of the records management feature.|Compliance Administrator <br/><br/> Compliance Data Administrator <br/><br/> Organization Management <br/><br/> Records Management|
211
211
|**Retention Management**|Manage retention policies, retention labels, and retention label policies. Includes permissions to add and remove adaptive scopes from these policies, and to create, delete, and modify adaptive scopes.|Compliance Administrator <br/><br/> Compliance Data Administrator <br/><br/> Organization Management <br/><br/> Records Management|
212
-
|<sup>\*</sup>**Review**|This role lets users access review sets in eDiscovery (Premium) cases. Users who are assigned this role can see and open the list of cases on the **eDiscovery \> Advanced** page in the Microsoft Purview compliance portal that they're members of. After the user accesses an eDiscovery (Premium) case, they can select **Review sets** to access case data. This role doesn't allow the user to preview the results of a collection search that's associated with the case or do other search or case management tasks. Users with this role can only access the data in a review set.|Data Investigator <br/><br/> eDiscovery Manager <br/><br/> Insider Risk Management <br/><br/> Insider Risk Management Investigators <br/><br/> Reviewer|
212
+
|<sup>\*</sup>**Review**|This role lets users access review sets in eDiscovery (Premium) cases. Users who are assigned this role can see and open the list of cases on the **eDiscovery > Advanced** page in the Microsoft Purview compliance portal that they're members of. After the user accesses an eDiscovery (Premium) case, they can select **Review sets** to access case data. This role doesn't allow the user to preview the results of a collection search that's associated with the case or do other search or case management tasks. Users with this role can only access the data in a review set.|Data Investigator <br/><br/> eDiscovery Manager <br/><br/> Insider Risk Management <br/><br/> Insider Risk Management Investigators <br/><br/> Reviewer|
|**Role Management**|Manage role group membership and create or delete custom role groups.|Organization Management <br/><br/> Purview Administrators|
215
215
|<sup>\*</sup>**Scan Reader**|Read the different scans created in the tenant.|Compliance Administrator <br/><br/> Data Source Administrators <br/><br/> Information Protection <br/><br/> Information Protection Admins <br/><br/> Information Protection Investigators|
0 commit comments