Skip to content

Commit 1cd8d6c

Browse files
committed
Merge branch 'main' into Teams-chrisda
2 parents 6912980 + 56a0585 commit 1cd8d6c

File tree

2 files changed

+19
-25
lines changed

2 files changed

+19
-25
lines changed

defender-endpoint/cloud-protection-microsoft-antivirus-sample-submission.md

Lines changed: 17 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.reviewer: mkaminska, yongrhee
99
manager: deniseb
1010
ms.subservice: ngp
1111
ms.topic: conceptual
12-
ms.date: 08/20/2024
12+
ms.date: 03/18/2025
1313
ms.collection:
1414
- m365-security
1515
- tier2
@@ -21,15 +21,15 @@ search.appverid: met150
2121

2222
**Applies to:**
2323

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
2626
- Microsoft Defender Antivirus
2727

2828
**Platforms**
29+
2930
- Windows
3031
- macOS
3132
- Linux
32-
3333
- Windows Server
3434

3535
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,
5454

5555
3. High-precision antivirus, detecting common malware through generic and heuristic techniques.
5656

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.
5858

5959
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.
6060

6161
- 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.
6262
- 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.
6464
- 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)).
6565

6666
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+
6868
| Setting | Description |
6969
|---|---|
7070
| **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. |
7171
| **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 |
7373
| **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+
7575
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.
7676

7777
> [!IMPORTANT]
@@ -107,9 +107,9 @@ The following table lists examples of metadata sent for analysis by cloud protec
107107

108108
## Samples are treated as customer data
109109

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.
111111

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:
113113

114114
- ISO 27001
115115
- ISO 27018
@@ -129,21 +129,15 @@ There are two more scenarios where Defender for Endpoint might request a file sa
129129
| Scenario | Description |
130130
|:---|:---|
131131
|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). |
133133

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)
143134

144135
## See also
145136

146-
[Next-generation protection overview](next-generation-protection.md)
137+
- [Next-generation protection overview](next-generation-protection.md)
138+
- [Microsoft Defender for Endpoint on Linux](microsoft-defender-endpoint-linux.md)
139+
- [Microsoft Defender for Endpoint on Mac](microsoft-defender-endpoint-mac.md)
140+
- [Microsoft Defender for Endpoint - Mobile Threat Defense](mtd.md)
141+
- [Configure remediation for Microsoft Defender Antivirus detections](configure-remediation-microsoft-defender-antivirus.md)
147142

148-
[Configure remediation for Microsoft Defender Antivirus detections.](configure-remediation-microsoft-defender-antivirus.md)
149143
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/schedule-antivirus-scans-group-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.localizationpriority: medium
66
author: emmwalshh
77
ms.author: ewalsh
88
ms.custom: nextgen
9-
ms.date: 02/18/2025
9+
ms.date: 03/18/2025
1010
ms.reviewer: pauhijbr, ksarens
1111
manager: deniseb
1212
ms.subservice: ngp
@@ -87,7 +87,7 @@ For more information, see the [Manage when protection updates should be download
8787

8888
| Location | Setting | Description | Default setting (if not configured)|
8989
|:---|:---|:---|:---|
90-
| Signature updates | Turn on scan after Security intelligence update | A scan will occur immediately after a new protection update is downloaded | Enabled |
90+
| Signature updates | Turn on scan after Security intelligence update | A process scan will occur immediately after a new protection update is downloaded | Enabled |
9191

9292
> [!TIP]
9393
> If you're looking for Antivirus related information for other platforms, see:

0 commit comments

Comments
 (0)