mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merge pull request #4497 from MicrosoftDocs/master
Publish 01/04/2021, 3:30 PM
This commit is contained in:
Gary Moore
GitHub
commit
ba863f2d84
@ -302,6 +302,7 @@
|
||||
##### [Troubleshoot installation issues](microsoft-defender-atp/linux-support-install.md)
|
||||
##### [Troubleshoot cloud connectivity issues](microsoft-defender-atp/linux-support-connectivity.md)
|
||||
##### [Troubleshoot performance issues](microsoft-defender-atp/linux-support-perf.md)
|
||||
##### [Troubleshoot missing events issues](microsoft-defender-atp/linux-support-events.md)
|
||||
|
||||
|
||||
#### [Privacy](microsoft-defender-atp/linux-privacy.md)
|
||||
|
||||
@ -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
|
||||
---
|
||||
|
||||
@ -26,28 +26,30 @@ ms.topic: article
|
||||
- Azure Active Directory
|
||||
- [Microsoft Defender for Endpoint](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
|
||||
>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-basicaccess-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-basicaccess-abovefoldlink)
|
||||
|
||||
Refer to the instructions below to use basic permissions management.
|
||||
Refer to the instructions below to use basic permissions management.
|
||||
|
||||
You can use either of the following solutions:
|
||||
- Azure PowerShell
|
||||
- Azure portal
|
||||
- Azure portal
|
||||
|
||||
For granular control over permissions, [switch to role-based access control](rbac.md).
|
||||
|
||||
## Assign user access using Azure PowerShell
|
||||
|
||||
You can assign users with one of the following levels of permissions:
|
||||
- Full access (Read and Write)
|
||||
- Read-only access
|
||||
|
||||
### Before you begin
|
||||
|
||||
- Install Azure PowerShell. For more information, see, [How to install and configure Azure PowerShell](https://azure.microsoft.com/documentation/articles/powershell-install-configure/).<br>
|
||||
|
||||
> [!NOTE]
|
||||
> You need to run the PowerShell cmdlets in an elevated command-line.
|
||||
|
||||
- Connect to your Azure Active Directory. For more information, see, [Connect-MsolService](https://msdn.microsoft.com/library/dn194123.aspx).
|
||||
- Connect to your Azure Active Directory. For more information, see [Connect-MsolService](https://docs.microsoft.com/powershell/module/msonline/connect-msolservice?view=azureadps-1.0).
|
||||
|
||||
**Full access** <br>
|
||||
Users with full access can log in, view all system information and resolve alerts, submit files for deep analysis, and download the onboarding package.
|
||||
@ -61,19 +63,20 @@ Assigning read-only access rights requires adding the users to the "Security Rea
|
||||
Use the following steps to assign security roles:
|
||||
|
||||
- For **read and write** access, assign users to the security administrator role by using the following command:
|
||||
```text
|
||||
```PowerShell
|
||||
Add-MsolRoleMember -RoleName "Security Administrator" -RoleMemberEmailAddress "secadmin@Contoso.onmicrosoft.com"
|
||||
```
|
||||
- For **read-only** access, assign users to the security reader role by using the following command:
|
||||
```text
|
||||
```PowerShell
|
||||
Add-MsolRoleMember -RoleName "Security Reader" -RoleMemberEmailAddress "reader@Contoso.onmicrosoft.com"
|
||||
```
|
||||
|
||||
For more information, see, [Add, or remove group memberships](https://technet.microsoft.com/library/321d532e-407d-4e29-a00a-8afbe23008dd#BKMK_ManageGroups).
|
||||
For more information, see [Add or remove group members using Azure Active Directory](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-groups-members-azure-portal).
|
||||
|
||||
## Assign user access using the Azure portal
|
||||
For more information, see [Assign administrator and non-administrator roles to uses with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal).
|
||||
|
||||
For more information, see [Assign administrator and non-administrator roles to users with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal).
|
||||
|
||||
## Related topic
|
||||
|
||||
- [Manage portal access using RBAC](rbac.md)
|
||||
|
||||
@ -46,7 +46,7 @@ Permission type | Permission | Permission display name
|
||||
Application | Ip.Read.All | 'Read IP address profiles'
|
||||
Delegated (work or school account) | Ip.Read.All | 'Read IP address profiles'
|
||||
|
||||
>[!Note]
|
||||
>[!NOTE]
|
||||
> When obtaining a token using user credentials:
|
||||
>- The user needs to have at least the following role permission: 'View Data' (See [Create and manage roles](user-roles.md) for more information)
|
||||
|
||||
@ -95,3 +95,13 @@ Content-type: application/json
|
||||
"orgLastSeen": "2017-08-29T13:32:59Z"
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
| Name | Description |
|
||||
| :--- | :---------- |
|
||||
| Org prevalence | the distinct count of devices that opened network connection to this IP. |
|
||||
| Org first seen | the first connection for this IP in the organization. |
|
||||
| Org last seen | the last connection for this IP in the organization. |
|
||||
|
||||
> [!NOTE]
|
||||
> This statistic information is based on data from the past 30 days.
|
||||
|
||||
@ -24,7 +24,6 @@ ms.topic: conceptual
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender for Endpoint for Linux](microsoft-defender-atp-linux.md)
|
||||
@ -37,8 +36,29 @@ To test if Defender for Endpoint for Linux can communicate to the cloud with the
|
||||
mdatp connectivity test
|
||||
```
|
||||
|
||||
expected output:
|
||||
|
||||
```output
|
||||
Testing connection with https://cdn.x.cp.wd.microsoft.com/ping ... [OK]
|
||||
Testing connection with https://eu-cdn.x.cp.wd.microsoft.com/ping ... [OK]
|
||||
Testing connection with https://wu-cdn.x.cp.wd.microsoft.com/ping ... [OK]
|
||||
Testing connection with https://x.cp.wd.microsoft.com/api/report ... [OK]
|
||||
Testing connection with https://winatp-gw-cus.microsoft.com/test ... [OK]
|
||||
Testing connection with https://winatp-gw-eus.microsoft.com/test ... [OK]
|
||||
Testing connection with https://winatp-gw-weu.microsoft.com/test ... [OK]
|
||||
Testing connection with https://winatp-gw-neu.microsoft.com/test ... [OK]
|
||||
Testing connection with https://winatp-gw-ukw.microsoft.com/test ... [OK]
|
||||
Testing connection with https://winatp-gw-uks.microsoft.com/test ... [OK]
|
||||
Testing connection with https://eu-v20.events.data.microsoft.com/ping ... [OK]
|
||||
Testing connection with https://us-v20.events.data.microsoft.com/ping ... [OK]
|
||||
Testing connection with https://uk-v20.events.data.microsoft.com/ping ... [OK]
|
||||
Testing connection with https://v20.events.data.microsoft.com/ping ... [OK]
|
||||
```
|
||||
|
||||
If the connectivity test fails, check if the device has Internet access and if [any of the endpoints required by the product](microsoft-defender-atp-linux.md#network-connections) are blocked by a proxy or firewall.
|
||||
|
||||
Failures with curl error 35 or 60, indicate certificate pinning rejection. Please check if the connection is under SSL or HTTPS inspection. If so, add Microsoft Defender for Endpoint to the allow list.
|
||||
|
||||
## Troubleshooting steps for environments without proxy or with transparent proxy
|
||||
|
||||
To test that a connection is not blocked in an environment without a proxy or with a transparent proxy, run the following command in the terminal:
|
||||
|
||||
@ -0,0 +1,94 @@
|
||||
---
|
||||
title: Troubleshoot missing events or alerts issues for Microsoft Defender ATP for Linux
|
||||
description: Troubleshoot missing events or alerts issues in Microsoft Defender ATP for Linux.
|
||||
keywords: microsoft, defender, atp, linux, events
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: dansimp
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
mms.collection:
|
||||
- m365-security-compliance
|
||||
- m365initiative-defender-endpoint
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Troubleshoot missing events or alerts issues for Microsoft Defender for Endpoint for Linux
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender for Endpoint for Linux](microsoft-defender-atp-linux.md)
|
||||
|
||||
This article provides some general steps to mitigate missing events or alerts in the [security center](https://securitycenter.windows.com/) portal.
|
||||
|
||||
Once Microsoft Defender for Endpoint has been installed properly on a device, a device page will be generated in the portal and _File_, _Process_, _Network_ and other events should appear in the timeline and advanced hunting pages.
|
||||
In case events are not appearing or some types of events are missing, that could indicate some problem.
|
||||
|
||||
## Missing network and login events
|
||||
|
||||
Microsoft Defender for Endpoint utilized `audit` framework from linux to track network and login activity.
|
||||
|
||||
1. Make sure audit framework is working.
|
||||
|
||||
```bash
|
||||
service auditd status
|
||||
```
|
||||
|
||||
expected output:
|
||||
|
||||
```output
|
||||
● auditd.service - Security Auditing Service
|
||||
Loaded: loaded (/usr/lib/systemd/system/auditd.service; enabled; vendor preset: enabled)
|
||||
Active: active (running) since Mon 2020-12-21 10:48:02 IST; 2 weeks 0 days ago
|
||||
Docs: man:auditd(8)
|
||||
https://github.com/linux-audit/audit-documentation
|
||||
Process: 16689 ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE)
|
||||
Process: 16665 ExecStart=/sbin/auditd (code=exited, status=0/SUCCESS)
|
||||
Main PID: 16666 (auditd)
|
||||
Tasks: 25
|
||||
CGroup: /system.slice/auditd.service
|
||||
├─16666 /sbin/auditd
|
||||
├─16668 /sbin/audispd
|
||||
├─16670 /usr/sbin/sedispatch
|
||||
└─16671 /opt/microsoft/mdatp/sbin/mdatp_audisp_plugin -d
|
||||
```
|
||||
|
||||
2. If auditd is stopped, please start it.
|
||||
|
||||
```bash
|
||||
service auditd start
|
||||
```
|
||||
|
||||
**On SLES15** systems, SYSCALL auditing in `auditd` is disabled by default and can explain missing events.
|
||||
|
||||
1. To validate that SYSCALL auditing is not disabeld, list the current audit rules:
|
||||
|
||||
```bash
|
||||
sudo auditctl -l
|
||||
```
|
||||
|
||||
if the following line is present, please remove it or edit it to enable Microsoft Defender for Endpoint to track specific SYSCALLs.
|
||||
|
||||
```output
|
||||
-a task, never
|
||||
```
|
||||
|
||||
audit rules are located at `/etc/audit/rules.d/audit.rules`.
|
||||
|
||||
## Missing file events
|
||||
|
||||
File events are collected with `fanotify` framework. In case some or all file events are missing please make sure fanotify is enabled on the device and that the file system is [supported](microsoft-defender-atp-linux.md#system-requirements).
|
||||
|
||||
List the filesystems on the machine with:
|
||||
|
||||
```bash
|
||||
df -Th
|
||||
```
|
||||
@ -24,7 +24,6 @@ ms.topic: conceptual
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender for Endpoint for Linux](microsoft-defender-atp-linux.md)
|
||||
@ -36,9 +35,11 @@ An error in installation may or may not result in a meaningful error message by
|
||||
```bash
|
||||
sudo journalctl | grep 'microsoft-mdatp' > installation.log
|
||||
```
|
||||
|
||||
```bash
|
||||
grep 'postinstall end' installation.log
|
||||
```
|
||||
|
||||
```Output
|
||||
microsoft-mdatp-installer[102243]: postinstall end [2020-03-26 07:04:43OURCE +0000] 102216
|
||||
```
|
||||
@ -47,6 +48,20 @@ An output from the previous command with correct date and time of installation i
|
||||
|
||||
Also check the [Client configuration](linux-install-manually.md#client-configuration) to verify the health of the product and detect the EICAR text file.
|
||||
|
||||
## Make sure you have the correct package
|
||||
|
||||
Please mind that the package you are installing is matching the host distribution and version.
|
||||
|
||||
| package | distribution |
|
||||
|-------------------------------|------------------------------------------|
|
||||
| mdatp-rhel8.Linux.x86_64.rpm | Oracle, RHEL and CentOS 8.x |
|
||||
| mdatp-sles12.Linux.x86_64.rpm | SuSE Linux Enterprise Server 12.x |
|
||||
| mdatp-sles15.Linux.x86_64.rpm | SuSE Linux Enterprise Server 15.x |
|
||||
| mdatp.Linux.x86_64.rpm | Oracle, RHEL and CentOS 7.x |
|
||||
| mdatp.Linux.x86_64.deb | Debian and Ubuntu 16.04, 18.04 and 20.04 |
|
||||
|
||||
For [manual deployment](linux-install-manually.md), make sure the correct distro and version had been chosen.
|
||||
|
||||
## Installation failed
|
||||
|
||||
Check if the mdatp service is running:
|
||||
@ -54,6 +69,7 @@ Check if the mdatp service is running:
|
||||
```bash
|
||||
systemctl status mdatp
|
||||
```
|
||||
|
||||
```Output
|
||||
● mdatp.service - Microsoft Defender for Endpoint
|
||||
Loaded: loaded (/lib/systemd/system/mdatp.service; enabled; vendor preset: enabled)
|
||||
@ -69,47 +85,59 @@ systemctl status mdatp
|
||||
## Steps to troubleshoot if mdatp service isn't running
|
||||
|
||||
1. Check if "mdatp" user exists:
|
||||
|
||||
```bash
|
||||
id "mdatp"
|
||||
```
|
||||
|
||||
If there’s no output, run
|
||||
|
||||
```bash
|
||||
sudo useradd --system --no-create-home --user-group --shell /usr/sbin/nologin mdatp
|
||||
```
|
||||
|
||||
2. Try enabling and restarting the service using:
|
||||
|
||||
```bash
|
||||
sudo systemctl enable mdatp
|
||||
```
|
||||
|
||||
```bash
|
||||
sudo systemctl restart mdatp
|
||||
```
|
||||
|
||||
3. If mdatp.service isn't found upon running the previous command, run:
|
||||
|
||||
```bash
|
||||
sudo cp /opt/microsoft/mdatp/conf/mdatp.service <systemd_path>
|
||||
```
|
||||
|
||||
where ```<systemd_path>``` is
|
||||
```/lib/systemd/system``` for Ubuntu and Debian distributions and
|
||||
```/usr/lib/systemd/system``` for Rhel, CentOS, Oracle and SLES.
|
||||
```/usr/lib/systemd/system``` for Rhel, CentOS, Oracle and SLES.
|
||||
Then rerun step 2.
|
||||
|
||||
4. If the above steps don’t work, check if SELinux is installed and in enforcing mode. If so, try setting it to permissive (preferably) or disabled mode. It can be done by setting the parameter `SELINUX` to "permissive" or "disabled" in `/etc/selinux/config` file, followed by reboot. Check the man-page of selinux for more details.
|
||||
Now try restarting the mdatp service using step 2. Revert the configuration change immediately though for security reasons after trying it and reboot.
|
||||
|
||||
5. If `/opt` directory is a symbolic link, create a bind mount for `/opt/microsoft`.
|
||||
5. If `/opt` directory is a symbolic link, create a bind mount for `/opt/microsoft`.
|
||||
|
||||
6. Ensure that the daemon has executable permission.
|
||||
|
||||
```bash
|
||||
ls -l /opt/microsoft/mdatp/sbin/wdavdaemon
|
||||
```
|
||||
|
||||
```Output
|
||||
-rwxr-xr-x 2 root root 15502160 Mar 3 04:47 /opt/microsoft/mdatp/sbin/wdavdaemon
|
||||
```
|
||||
|
||||
If the daemon doesn't have executable permissions, make it executable using:
|
||||
|
||||
```bash
|
||||
sudo chmod 0755 /opt/microsoft/mdatp/sbin/wdavdaemon
|
||||
```
|
||||
|
||||
and retry running step 2.
|
||||
|
||||
7. Ensure that the file system containing wdavdaemon isn't mounted with "noexec".
|
||||
@ -117,24 +145,31 @@ Now try restarting the mdatp service using step 2. Revert the configuration chan
|
||||
## If mdatp service is running, but EICAR text file detection doesn't work
|
||||
|
||||
1. Check the file system type using:
|
||||
|
||||
```bash
|
||||
findmnt -T <path_of_EICAR_file>
|
||||
```
|
||||
|
||||
Currently supported file systems for on-access activity are listed [here](microsoft-defender-atp-linux.md#system-requirements). Any files outside these file systems won't be scanned.
|
||||
|
||||
## Command-line tool “mdatp” isn't working
|
||||
|
||||
1. If running the command-line tool `mdatp` gives an error `command not found`, run the following command:
|
||||
|
||||
```bash
|
||||
sudo ln -sf /opt/microsoft/mdatp/sbin/wdavdaemonclient /usr/bin/mdatp
|
||||
```
|
||||
|
||||
and try again.
|
||||
|
||||
If none of the above steps help, collect the diagnostic logs:
|
||||
|
||||
```bash
|
||||
sudo mdatp diagnostic create
|
||||
```
|
||||
|
||||
```Output
|
||||
Diagnostic file created: <path to file>
|
||||
```
|
||||
|
||||
Path to a zip file that contains the logs will be displayed as an output. Reach out to our customer support with these logs.
|
||||
|
||||
@ -23,7 +23,6 @@ ms.topic: conceptual
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender for Endpoint for Linux](microsoft-defender-atp-linux.md)
|
||||
@ -34,6 +33,8 @@ Real-time protection (RTP) is a feature of Defender for Endpoint for Linux that
|
||||
|
||||
Depending on the applications that you are running and your device characteristics, you may experience suboptimal performance when running Defender for Endpoint for Linux. In particular, applications or system processes that access many resources over a short timespan can lead to performance issues in Defender for Endpoint for Linux.
|
||||
|
||||
Before starting, **please make sure that other security products are not currenly running on the device**. Multilpe security products may conflict and impact the host performance.
|
||||
|
||||
The following steps can be used to troubleshoot and mitigate these issues:
|
||||
|
||||
1. Disable real-time protection using one of the following methods and observe whether the performance improves. This approach helps narrow down whether Defender for Endpoint for Linux is contributing to the performance issues.
|
||||
@ -43,19 +44,22 @@ The following steps can be used to troubleshoot and mitigate these issues:
|
||||
```bash
|
||||
mdatp config real-time-protection --value disabled
|
||||
```
|
||||
|
||||
```Output
|
||||
Configuration property updated
|
||||
```
|
||||
|
||||
If your device is managed by your organization, real-time protection can be disabled by your administrator using the instructions in [Set preferences for Defender for Endpoint for Linux](linux-preferences.md).
|
||||
|
||||
2. To find the applications that are triggering the most scans, you can use real-time statistics gathered by Defender for Endpoint for Linux.
|
||||
If the performance problem persists while real-time protection is off, the origin of the problem could be the endpoint detection and response component. In this case please contact customer support for further instructions and mitigation.
|
||||
|
||||
2. To find the applications that are triggering the most scans, you can use real-time statistics gathered by Defender for Endpoint for Linux.
|
||||
|
||||
> [!NOTE]
|
||||
> This feature is available in version 100.90.70 or newer.
|
||||
|
||||
This feature is enabled by default on the `Dogfood` and `InsiderFast` channels. If you're using a different update channel, this feature can be enabled from the command line:
|
||||
|
||||
|
||||
```bash
|
||||
mdatp config real-time-protection-statistics --value enabled
|
||||
```
|
||||
@ -71,6 +75,7 @@ The following steps can be used to troubleshoot and mitigate these issues:
|
||||
```bash
|
||||
mdatp config real-time-protection --value enabled
|
||||
```
|
||||
|
||||
```Output
|
||||
Configuration property updated
|
||||
```
|
||||
@ -80,16 +85,18 @@ The following steps can be used to troubleshoot and mitigate these issues:
|
||||
```bash
|
||||
mdatp diagnostic real-time-protection-statistics --output json > real_time_protection.json
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> Using ```--output json``` (note the double dash) ensures that the output format is ready for parsing.
|
||||
|
||||
The output of this command will show all processes and their associated scan activity.
|
||||
The output of this command will show all processes and their associated scan activity.
|
||||
|
||||
3. On your Linux system, download the sample Python parser **high_cpu_parser.py** using the command:
|
||||
3. On your Linux system, download the sample Python parser **high_cpu_parser.py** using the command:
|
||||
|
||||
```bash
|
||||
wget -c https://raw.githubusercontent.com/microsoft/mdatp-xplat/master/linux/diagnostic/high_cpu_parser.py
|
||||
```
|
||||
|
||||
The output of this command should be similar to the following:
|
||||
|
||||
```Output
|
||||
@ -102,39 +109,40 @@ The following steps can be used to troubleshoot and mitigate these issues:
|
||||
|
||||
100%[===========================================>] 1,020 --.-K/s in 0s
|
||||
```
|
||||
|
||||
4. Next, type the following commands:
|
||||
|
||||
```bash
|
||||
chmod +x high_cpu_parser.py
|
||||
```
|
||||
|
||||
```bash
|
||||
cat real_time_protection.json | python high_cpu_parser.py > real_time_protection.log
|
||||
```
|
||||
|
||||
The output of the above is a list of the top contributors to performance issues. The first column is the process identifier (PID), the second column is te process name, and the last column is the number of scanned files, sorted by impact.
|
||||
|
||||
|
||||
For example, the output of the command will be something like the below:
|
||||
|
||||
```Output
|
||||
... > python ~/repo/mdatp-xplat/linux/diagnostic/high_cpu_parser.py <~Downloads/output.json | head -n 10
|
||||
27432 None 76703
|
||||
73467 actool 1249
|
||||
73914 xcodebuild 1081
|
||||
73873 bash 1050
|
||||
27475 None 836
|
||||
1 launchd 407
|
||||
73468 ibtool 344
|
||||
549 telemetryd_v1 325
|
||||
4764 None 228
|
||||
125 CrashPlanService 164
|
||||
27432 None 76703
|
||||
73467 actool 1249
|
||||
73914 xcodebuild 1081
|
||||
73873 bash 1050
|
||||
27475 None 836
|
||||
1 launchd 407
|
||||
73468 ibtool 344
|
||||
549 telemetryd_v1 325
|
||||
4764 None 228
|
||||
125 CrashPlanService 164
|
||||
```
|
||||
|
||||
To improve the performance of Defender for Endpoint for Linux, locate the one with the highest number under the `Total files scanned` row and add an exclusion for it. For more information, see [Configure and validate exclusions for Defender for Endpoint for Linux](linux-exclusions.md).
|
||||
|
||||
|
||||
To improve the performance of Defender for Endpoint for Linux, locate the one with the highest number under the `Total files scanned` row and add an exclusion for it. For more information, see [Configure and validate exclusions for Defender for Endpoint for Linux](linux-exclusions.md).
|
||||
|
||||
>[!NOTE]
|
||||
> The application stores statistics in memory and only keeps track of file activity since it was started and real-time protection was enabled. Processes that were launched before or during periods when real time protection was off are not counted. Additionally, only events which triggered scans are counted.
|
||||
|
||||
5. Configure Microsoft Defender ATP for Linux with exclusions for the processes or disk locations that contribute to the performance issues and re-enable real-time protection.
|
||||
|
||||
For more information, see [Configure and validate exclusions for Microsoft Defender ATP for Linux](linux-exclusions.md).
|
||||
|
||||
|
||||
For more information, see [Configure and validate exclusions for Microsoft Defender ATP for Linux](linux-exclusions.md).
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user