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
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://go.microsoft.com/fwlink/p/?linkid=2225630)
31
31
32
-
## Overview of settings and policies to configure
32
+
## Configure your security settings
33
33
34
-
Microsoft Defender for Endpoint on Linux includes antivirus, anti-malware protection, endpoint detection, and response capabilities. This article summarizes important settings to configure, with links to additional resources.
34
+
Microsoft Defender for Endpoint on Linux includes antivirus, anti-malware protection, endpoint detection, and response capabilities. This article summarizes important security settings to configure and includes links to additional resources.
35
35
36
36
| Settings | Description|
37
37
|--|--|
@@ -44,22 +44,22 @@ Microsoft Defender for Endpoint on Linux includes antivirus, anti-malware protec
44
44
| 7. Deploy updates. | Microsoft regularly publishes software updates to improve performance, security, and to deliver new features. <br/><br/>See [Deploy updates for Microsoft Defender for Endpoint on Linux](linux-updates.md). |
45
45
| 8. Configure network protection (preview) | Network protection helps prevent employees from using any application to access dangerous domains that might host phishing scams, exploits, and other malicious content on the Internet. <br/><br/>See [Network protection for Linux](network-protection-linux.md). |
46
46
47
-
## Options for configuring security policies and settings
47
+
## Options for configuring security settings
48
48
49
-
To configure your security policies and settings for Defender for Endpoint on Linux, you have two main options:
49
+
To configure your security settings in Defender for Endpoint on Linux, you have two main options:
50
50
51
51
- Use the Microsoft Defender portal (Defender for Endpoint Security Settings Management); or
52
52
- Use a configuration profile
53
53
54
-
If you prefer to use command line to configure your security settings, you can use that to configure certain settings, gather diagnostics, run scans, and more. See [Resources](linux-resources.md#configure-from-the-command-line).
54
+
If you prefer to use command line, you can use that to configure certain settings, gather diagnostics, run scans, and more. See [Linux resources: Configure using command line](linux-resources.md#configure-from-the-command-line).
55
55
56
56
### Defender for Endpoint Security Settings Management
57
57
58
-
You can configure Defender for Endpoint on Linux in the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)) through functionality known as Security Settings Management. For more information, including how to create, edit, and verify your security policies, see [Use Microsoft Defender for Endpoint Security Settings Management to manage Microsoft Defender Antivirus](mde-security-settings-management.md).
58
+
You can configure Defender for Endpoint on Linux in the Microsoft Defender portal ([https://security.microsoft.com](https://security.microsoft.com)) through functionality known as Defender for Endpoint Security Settings Management. For more information, including how to create, edit, and verify security policies, see [Use Microsoft Defender for Endpoint Security Settings Management to manage Microsoft Defender Antivirus](mde-security-settings-management.md).
59
59
60
60
### Configuration profile
61
61
62
-
You can configure Defender for Endpoint on Linux through a configuration profile that uses a `.json` file. After you have set up your profile, you can deploy it by using your management tool of choice. Preferences managed by the enterprise take precedence over the ones set locally on the device. In other words, users in your enterprise aren't able to change preferences that are set through this configuration profile. If exclusions were added through the managed configuration profile, they can only be removed through the managed configuration profile. The command line works for exclusions that were added locally.
62
+
You can configure settings in Defender for Endpoint on Linux through a configuration profile that uses a `.json` file. After you have set up your profile, you can deploy it by using your management tool of choice. Preferences managed by the enterprise take precedence over the ones set locally on the device. In other words, users in your enterprise aren't able to change preferences that are set through this configuration profile. If exclusions were added through the managed configuration profile, they can only be removed through the managed configuration profile. The command line works for exclusions that were added locally.
63
63
64
64
This article describes the structure of this profile (including a recommended profile that you can use to get started) and instructions on how to deploy the profile.
65
65
@@ -456,6 +456,7 @@ By default, NFS and Fuse are unmonitored from RTP, Quick, and Full scans. Howeve
456
456
}
457
457
}
458
458
```
459
+
459
460
To remove both NFS and Fuse from unmonitored list of filesystems, use the following snippet:
Copy file name to clipboardExpand all lines: defender-endpoint/linux-support-connectivity.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: linux
17
17
search.appverid: met150
18
-
ms.date: 03/12/2025
18
+
ms.date: 03/28/2025
19
19
---
20
20
21
21
# Troubleshoot cloud connectivity issues for Microsoft Defender for Endpoint on Linux
@@ -56,7 +56,7 @@ Testing connection with https://uk-v20.events.data.microsoft.com/ping ... [OK]
56
56
Testing connection with https://v20.events.data.microsoft.com/ping ... [OK]
57
57
```
58
58
59
-
If the connectivity test fails, check if the device has Internet access and if [network connections](mde-linux-prerequisites.md#network-connections) are blocked by a proxy or firewall.
59
+
If the connectivity test fails, check if the device has Internet access. Also check to see if network connections are blocked by a proxy or firewall. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-that-devices-can-connect-to-defender-for-endpoint-cloud-services).
60
60
61
61
Failures with curl error 35 or 60, indicate certificate pinning rejection. Check to see if the connection is under SSL or HTTPS inspection. If so, add Microsoft Defender for Endpoint to the allowlist.
62
62
@@ -96,7 +96,6 @@ To set the proxy for mdatp, use the following command:
96
96
mdatp config proxy set --value http://address:port
97
97
```
98
98
99
-
100
99
Upon success, attempt another connectivity test from the command line:
Copy file name to clipboardExpand all lines: defender-endpoint/mde-linux-deployment-on-sap.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: linux
17
17
search.appverid: met150
18
-
ms.date: 02/04/2025
18
+
ms.date: 03/28/2025
19
19
ms.custom:
20
20
- partner-contribution
21
21
---
@@ -65,7 +65,7 @@ Here are some important point about SAP applications on Linux Server:
65
65
66
66
- Microsoft Defender for Endpoint [Build: 101.24082.0004 | Release version: 30.124082.0004.0](/defender-endpoint/linux-whatsnew#oct-2024-build-101240820004--release-version-3012408200040) or later must be deployed.
67
67
- Microsoft Defender for Endpoint on Linux supports [Linux releases](/defender-endpoint/mde-linux-prerequisites) used by SAP applications.
68
-
- Microsoft Defender for Endpoint on Linux requires connectivity to specific Internet endpoints from VMs to update antivirus definitions. For more information, see [Network connections](mde-linux-prerequisites.md#network-connections).
68
+
- Microsoft Defender for Endpoint on Linux requires connectivity to specific Internet endpoints from VMs to update antivirus definitions. For more information, see [Verify that devices can connect to Defender for Endpoint cloud services](mde-linux-prerequisites.md#verify-that-devices-can-connect-to-defender-for-endpoint-cloud-services).
69
69
- Microsoft Defender for Endpoint on Linux requires some `crontab` (or other task scheduler) entries to schedule scans, log rotation, and Microsoft Defender for Endpoint updates. Enterprise security teams normally manage these entries. For more information, see [How to schedule an update for Microsoft Defender for Endpoint on Linux](linux-update-mde-linux.md).
70
70
71
71
As of December 2024, Defender for Endpoint on Linux can safely be configured with real-time protection enabled.
Copy file name to clipboardExpand all lines: defender-endpoint/mde-linux-prerequisites.md
+29-25Lines changed: 29 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.collection:
15
15
ms.topic: conceptual
16
16
ms.subservice: linux
17
17
search.appverid: met150
18
-
ms.date: 03/14/2025
18
+
ms.date: 03/31/2025
19
19
---
20
20
21
21
# Prerequisites for Microsoft Defender for Endpoint on Linux
@@ -53,9 +53,10 @@ For detailed licensing information, see [Product Terms: Microsoft Defender for E
53
53
54
54
## Software requirements
55
55
56
-
- Linux server endpoints should be able to access the [Microsoft Defender portal](https://security.microsoft.com). If necessary, [configure static proxy discovery](linux-static-proxy-configuration.md).
56
+
- Linux server endpoints should be able to access the `*.endpoint.security.microsoft.com`. If necessary, [configure static proxy discovery](linux-static-proxy-configuration.md).
57
57
- Linux server endpoints should have systemd (system manager) installed.
58
58
- Administrative privileges on the Linux server endpoint are required for installation.
59
+
- An appropriate role assigned in Defender for Endpoint. See [Role-based access control](/defender-endpoint/prepare-deployment#role-based-access-control).
59
60
60
61
> [!NOTE]
61
62
> Linux distributions using system manager support both SystemV and Upstart.
@@ -94,8 +95,14 @@ The following Linux server distributions and x64 (AMD64/EM64T) versions are supp
94
95
95
96
- Ubuntu 20.04 Arm64
96
97
- Ubuntu 22.04 Arm64
98
+
- Ubuntu 24.04 ARM64
97
99
- Amazon Linux 2 Arm64
98
100
- Amazon Linux 2023 Arm64
101
+
- RHEL 8.x ARM64
102
+
- RHEL 9.x ARM64
103
+
- Oracle Linux 8.x ARM64
104
+
- Oracle Linux 9.x ARM64
105
+
- SUSE Linux Enterprise Server 15 (SP5, SP6) ARM64
99
106
100
107
Support for [Microsoft Defender for Endpoint on Linux for Arm64-based devices](/defender-endpoint/mde-linux-arm) is now in preview.
101
108
@@ -136,13 +143,12 @@ Support for [Microsoft Defender for Endpoint on Linux for Arm64-based devices](/
136
143
> NFS v3 mount points to be scanned thoroughly and are required to set the `no_root_squash` export option on these mount points.
137
144
> Without this option, scanning NFS v3 can potentially fail due to lack of permissions.
138
145
139
-
## Network connections
146
+
## Verify that devices can connect to Defender for Endpoint cloud services
140
147
141
-
- Verify that your devices can connect to Microsoft Defender for Endpoint cloud services.
142
148
- Prepare your environment, as described in Step 1 of the following article [Configure your network environment to ensure connectivity with Defender for Endpoint service](/defender-endpoint/configure-environment)
143
149
- Connect Defender for Endpoint on Linux through a proxy server by using the following discovery methods:
- Permit anonymous traffic in the previously listed URLs, if a proxy or firewall blocks traffic.
147
153
148
154
> [!NOTE]
@@ -159,10 +165,23 @@ For troubleshooting steps, see [Troubleshoot cloud connectivity issues for Micro
159
165
160
166
## External package dependency
161
167
162
-
For information on external package dependencies, see the following articles:
168
+
If the Microsoft Defender for Endpoint installation fails due to missing dependencies errors, you can manually download the prerequisite dependencies. The following external package dependencies exist for the mdatp package:
163
169
164
-
-[Microsoft Defender for Endpoint on Linux](/defender-endpoint/microsoft-defender-endpoint-linux)
165
-
-[Configure security settings and policies for Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-preferences)
170
+
- The mdatp RPM package requires `glibc >= 2.17`, `policycoreutils`, `selinux-policy-targeted`, and `mde-netfilter`.
171
+
- For RHEL6 the mdatp RPM package requires `policycoreutils`, `libselinux`, and `mde-netfilter`.
172
+
- For DEBIAN the mdatp package requires `libc6 >= 2.23`, `uuid-runtime`, and `mde-netfilter`.
173
+
174
+
> [!NOTE]
175
+
> Beginning with version `101.24082.0004`, Defender for Endpoint on Linux no longer supports the `Auditd` event provider. We're transitioning completely to the more efficient eBPF technology.
176
+
> If eBPF isn't supported on your machines, or if there are specific requirements to remain on Auditd, and your machines are using Defender for Endpoint on Linux version `101.24072.0001` or older, the following additional dependency on the auditd package exists for mdatp:
177
+
> - The mdatp RPM package requires `audit`, `semanage`.
178
+
> - For DEBIAN, the mdatp package requires `auditd`.
179
+
> - For Mariner, the mdatp package requires `audit`.
180
+
181
+
The `mde-netfilter` package also has the following package dependencies:
182
+
183
+
- For DEBIAN, the mde-netfilter package requires `libnetfilter-queue1` and `libglib2.0-0`
184
+
- For RPM, the mde-netfilter package requires `libmnl`, `libnfnetlink`, `libnetfilter_queue`, and `glib2`
166
185
167
186
## Installation instructions
168
187
@@ -179,30 +198,15 @@ There are several methods and tools that you can use to deploy Microsoft Defende
179
198
-[Guidance for Defender for Endpoint on Linux Server with SAP](/defender-endpoint/mde-linux-deployment-on-sap)
180
199
181
200
> [!IMPORTANT]
182
-
> Installing Microsoft Defender for Endpoint in any location other than the default install path isn't supported. On Linux, Microsoft Defender for Endpoint creates an mdatp user with random UID and GID values. If you want to control these values, create an mdatp user before installation using the /usr/sbin/nologin shell option. Here's an example: `mdatp:x:UID:GID::/home/mdatp:/usr/sbin/nologin`.
183
-
184
-
### Troubleshoot installation issues
185
-
186
-
If you experience any installation issues, for self-troubleshooting, follow these steps:
187
-
188
-
1. For information on how to find the log that's generated automatically when an installation error occurs, see [Log installation issues](linux-resources.md#log-installation-issues).
189
-
190
-
2. For information about common installation issues, see [Installation issues](/defender-endpoint/linux-support-install).
191
-
192
-
3. If health of the device is `false`, see [Defender for Endpoint agent health issues](/defender-endpoint/health-status).
193
-
194
-
4. For product performance issues, see [Troubleshoot performance issues](/defender-endpoint/linux-support-perf).
195
-
196
-
5. For proxy and connectivity issues, see [Troubleshoot cloud connectivity issues](/defender-endpoint/linux-support-connectivity).
201
+
> Installing Microsoft Defender for Endpoint in any location other than the default install path isn't supported. On Linux, Microsoft Defender for Endpoint creates an mdatp user with random UID and GID values. If you want to control these values, create an mdatp user before installation using the `/usr/sbin/nologin` shell option. Here's an example: `mdatp:x:UID:GID::/home/mdatp:/usr/sbin/nologin`.
197
202
198
-
To get support from Microsoft, open a support ticket, and provide the log files created by using the [client analyzer](/defender-endpoint/overview-client-analyzer).
203
+
If you experience any installation issues, self-troubleshooting resources are available. See the links in the [See also](#see-also) section.
199
204
200
205
## Next steps
201
206
202
207
-[Deploy Defender for Endpoint on Linux](/defender-endpoint/linux-installer-script)
203
208
-[Configure Defender for Endpoint on Linux](/defender-endpoint/linux-preferences)
204
209
-[Deploy updates for Defender for Endpoint on Linux](/defender-endpoint/linux-updates)
205
-
-[Run the client analyzer on Linux](run-analyzer-linux.md)
0 commit comments