mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 19:33:37 +00:00
Merge pull request #8787 from illfated/patch-1
Update respond-file-alerts.md
This commit is contained in:
jcaparas
GitHub
@ -13,7 +13,7 @@ author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection: M365-security-compliance
|
||||
ms.collection: M365-security-compliance
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
@ -25,10 +25,10 @@ ms.topic: article
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender for Endpoint](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
>Want to experience Defender for Endpoint? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-responddile-abovefoldlink)
|
||||
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-responddile-abovefoldlink)
|
||||
|
||||
Quickly respond to detected attacks by stopping and quarantining files or blocking a file. After taking action on files, you can check activity details in the Action center.
|
||||
|
||||
@ -46,12 +46,12 @@ You can also submit files for deep analysis, to run the file in a secure cloud s
|
||||
|
||||
Some actions require certain permissions. The following table describes what action certain permissions can take on portable executable (PE) and non-PE files:
|
||||
|
||||
Permission | PE files | Non-PE files
|
||||
:---|:---|:---
|
||||
View data | X | X
|
||||
Alerts investigation | ☑ | X
|
||||
Live response basic | X | X
|
||||
Live response advanced | ☑ |☑
|
||||
| Permission | PE files | Non-PE files |
|
||||
| :--------------------- | :------: | :----------: |
|
||||
| View data | X | X |
|
||||
| Alerts investigation | ☑ | X |
|
||||
| Live response basic | X | X |
|
||||
| Live response advanced | ☑ | ☑ |
|
||||
|
||||
For more information on roles, see [Create and manage roles for role-based access control](user-roles.md).
|
||||
|
||||
@ -60,8 +60,8 @@ For more information on roles, see [Create and manage roles for role-based acces
|
||||
|
||||
You can contain an attack in your organization by stopping the malicious process and quarantining the file where it was observed.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You can only take this action if:
|
||||
> [!IMPORTANT]
|
||||
> You can only take this action if:
|
||||
>
|
||||
> - The device you're taking the action on is running Windows 10, version 1703 or later
|
||||
> - The file does not belong to trusted third-party publishers or not signed by Microsoft
|
||||
@ -71,35 +71,35 @@ The **Stop and Quarantine File** action includes stopping running processes, qua
|
||||
|
||||
This action takes effect on devices with Windows 10, version 1703 or later, where the file was observed in the last 30 days.
|
||||
|
||||
>[!NOTE]
|
||||
>You’ll be able to restore the file from quarantine at any time.
|
||||
> [!NOTE]
|
||||
> You’ll be able to restore the file from quarantine at any time.
|
||||
|
||||
### Stop and quarantine files
|
||||
|
||||
1. Select the file you want to stop and quarantine. You can select a file from any of the following views or use the Search box:
|
||||
|
||||
- **Alerts** - click the corresponding links from the Description or Details in the Artifact timeline
|
||||
- **Search box** - select **File** from the drop–down menu and enter the file name
|
||||
- **Alerts** - click the corresponding links from the Description or Details in the Artifact timeline
|
||||
- **Search box** - select **File** from the drop–down menu and enter the file name
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>The stop and quarantine file action is limited to a maximum of 1000 devices. To stop a file on a larger number of devices, see [Add indicator to block or allow file](#add-indicator-to-block-or-allow-a-file).
|
||||
> [!NOTE]
|
||||
> The stop and quarantine file action is limited to a maximum of 1000 devices. To stop a file on a larger number of devices, see [Add indicator to block or allow file](#add-indicator-to-block-or-allow-a-file).
|
||||
|
||||
2. Go to the top bar and select **Stop and Quarantine File**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Specify a reason, then click **Confirm**.
|
||||
|
||||
|
||||
|
||||
|
||||
The Action center shows the submission information:
|
||||
|
||||
The Action center shows the submission information:
|
||||
|
||||
|
||||
- **Submission time** - Shows when the action was submitted.
|
||||
- **Success** - Shows the number of devices where the file has been stopped and quarantined.
|
||||
- **Failed** - Shows the number of devices where the action failed and details about the failure.
|
||||
- **Pending** - Shows the number of devices where the file is yet to be stopped and quarantined from. This can take time for cases when the device is offline or not connected to the network.
|
||||
- **Submission time** - Shows when the action was submitted.
|
||||
- **Success** - Shows the number of devices where the file has been stopped and quarantined.
|
||||
- **Failed** - Shows the number of devices where the action failed and details about the failure.
|
||||
- **Pending** - Shows the number of devices where the file is yet to be stopped and quarantined from. This can take time for cases when the device is offline or not connected to the network.
|
||||
|
||||
4. Select any of the status indicators to view more information about the action. For example, select **Failed** to see where the action failed.
|
||||
|
||||
@ -118,9 +118,9 @@ You can roll back and remove a file from quarantine if you’ve determined that
|
||||
|
||||
1. Open an elevated command–line prompt on the device:
|
||||
|
||||
a. Go to **Start** and type _cmd_.
|
||||
a. Go to **Start** and type _cmd_.
|
||||
|
||||
b. Right–click **Command prompt** and select **Run as administrator**.
|
||||
b. Right–click **Command prompt** and select **Run as administrator**.
|
||||
|
||||
2. Enter the following command, and press **Enter**:
|
||||
|
||||
@ -130,26 +130,26 @@ You can roll back and remove a file from quarantine if you’ve determined that
|
||||
|
||||
> [!NOTE]
|
||||
> In some scenarios, the **ThreatName** may appear as: EUS:Win32/CustomEnterpriseBlock!cl.
|
||||
>
|
||||
>
|
||||
> Defender for Endpoint will restore all custom blocked files that were quarantined on this device in the last 30 days.
|
||||
|
||||
> [!Important]
|
||||
> A file that was quarantined as a potential network threat might not be recoverable. If a user attempts to restore the file after quarantine, that file might not be accessible. This can be due to the system no longer having network credentials to access the file. Typically, this is a result of a temporary log on to a system or shared folder and the access tokens expired.
|
||||
> [!IMPORTANT]
|
||||
> A file that was quarantined as a potential network threat might not be recoverable. If a user attempts to restore the file after quarantine, that file might not be accessible. This can be due to the system no longer having network credentials to access the file. Typically, this is a result of a temporary log on to a system or shared folder and the access tokens expired.
|
||||
|
||||
## Add indicator to block or allow a file
|
||||
|
||||
You can prevent further propagation of an attack in your organization by banning potentially malicious files or suspected malware. If you know a potentially malicious portable executable (PE) file, you can block it. This operation will prevent it from being read, written, or executed on devices in your organization.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
>- This feature is available if your organization uses Microsoft Defender Antivirus and Cloud–delivered protection is enabled. For more information, see [Manage cloud–delivered protection](../microsoft-defender-antivirus/deploy-manage-report-microsoft-defender-antivirus.md).
|
||||
> - This feature is available if your organization uses Microsoft Defender Antivirus and Cloud–delivered protection is enabled. For more information, see [Manage cloud–delivered protection](../microsoft-defender-antivirus/deploy-manage-report-microsoft-defender-antivirus.md).
|
||||
>
|
||||
>- The Antimalware client version must be 4.18.1901.x or later.
|
||||
>- This feature is designed to prevent suspected malware (or potentially malicious files) from being downloaded from the web. It currently supports portable executable (PE) files, including _.exe_ and _.dll_ files. The coverage will be extended over time.
|
||||
>- This response action is available for devices on Windows 10, version 1703 or later.
|
||||
>- The allow or block function cannot be done on files if the file's classification exists on the device's cache prior to the allow or block action.
|
||||
> - The Antimalware client version must be 4.18.1901.x or later.
|
||||
> - This feature is designed to prevent suspected malware (or potentially malicious files) from being downloaded from the web. It currently supports portable executable (PE) files, including _.exe_ and _.dll_ files. The coverage will be extended over time.
|
||||
> - This response action is available for devices on Windows 10, version 1703 or later.
|
||||
> - The allow or block function cannot be done on files if the file's classification exists on the device's cache prior to the allow or block action.
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
> The PE file needs to be in the device timeline for you to be able to take this action.
|
||||
>
|
||||
> There may be a couple of minutes of latency between the time the action is taken and the actual file being blocked.
|
||||
@ -157,14 +157,14 @@ You can prevent further propagation of an attack in your organization by banning
|
||||
### Enable the block file feature
|
||||
|
||||
To start blocking files, you first need to [turn the **Block or allow** feature on](advanced-features.md) in Settings.
|
||||
|
||||
|
||||
### Allow or block file
|
||||
|
||||
When you add an indicator hash for a file, you can choose to raise an alert and block the file whenever a device in your organization attempts to run it.
|
||||
|
||||
Files automatically blocked by an indicator won't show up in the files's Action center, but the alerts will still be visible in the Alerts queue.
|
||||
|
||||
See [manage indicators](manage-indicators.md) for more details on blocking and raising alerts on files.
|
||||
See [manage indicators](manage-indicators.md) for more details on blocking and raising alerts on files.
|
||||
|
||||
To stop blocking a file, remove the indicator. You can do so via the **Edit Indicator** action on the file's profile page. This action will be visible in the same position that the **Add Indicator** action was, before you added the indicator.
|
||||
|
||||
@ -215,10 +215,10 @@ The Deep analysis summary includes a list of observed *behaviors*, some of which
|
||||
|
||||
Results of deep analysis are matched against threat intelligence and any matches will generate appropriate alerts.
|
||||
|
||||
Use the deep analysis feature to investigate the details of any file, usually during an investigation of an alert or for any other reason where you suspect malicious behavior. This feature is available within the **Deep analysis** tab, on the file's profile page.
|
||||
Use the deep analysis feature to investigate the details of any file, usually during an investigation of an alert or for any other reason where you suspect malicious behavior. This feature is available within the **Deep analysis** tab, on the file's profile page.<br/>
|
||||
<br/>
|
||||
|
||||
>[!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4aAYy?rel=0]
|
||||
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4aAYy?rel=0]
|
||||
|
||||
**Submit for deep analysis** is enabled when the file is available in the Defender for Endpoint backend sample collection, or if it was observed on a Windows 10 device that supports submitting to deep analysis.
|
||||
|
||||
@ -232,7 +232,7 @@ You can also manually submit a sample through the [Microsoft Security Center Por
|
||||
|
||||
When the sample is collected, Defender for Endpoint runs the file in is a secure environment and creates a detailed report of observed behaviors and associated artifacts, such as files dropped on devices, communication to IPs, and registry modifications.
|
||||
|
||||
**Submit files for deep analysis:**
|
||||
#### Submit files for deep analysis
|
||||
|
||||
1. Select the file that you want to submit for deep analysis. You can select or search a file from any of the following views:
|
||||
|
||||
@ -242,17 +242,17 @@ When the sample is collected, Defender for Endpoint runs the file in is a secure
|
||||
|
||||
2. In the **Deep analysis** tab of the file view, click **Submit**.
|
||||
|
||||
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> Only PE files are supported, including _.exe_ and _.dll_ files.
|
||||
> [!NOTE]
|
||||
> Only PE files are supported, including _.exe_ and _.dll_ files.
|
||||
|
||||
A progress bar is displayed and provides information on the different stages of the analysis. You can then view the report when the analysis is done.
|
||||
|
||||
> [!NOTE]
|
||||
> Depending on device availability, sample collection time can vary. There is a 3–hour timeout for sample collection. The collection will fail and the operation will abort if there is no online Windows 10 device reporting at that time. You can re–submit files for deep analysis to get fresh data on the file.
|
||||
|
||||
**View deep analysis reports**
|
||||
#### View deep analysis reports
|
||||
|
||||
View the deep analysis report that Defender for Endpoint provides to see the details of the deep analysis that was conducted on the file you submitted. This feature is available in the file view context.
|
||||
|
||||
@ -268,7 +268,7 @@ The details provided can help you investigate if there are indications of a pote
|
||||
|
||||
|
||||
|
||||
**Troubleshoot deep analysis**
|
||||
#### Troubleshoot deep analysis
|
||||
|
||||
If you encounter a problem when trying to submit a file, try each of the following troubleshooting steps.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user