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: defender-endpoint/api/get-assessment-software-vulnerabilities.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -395,7 +395,7 @@ Each returned record contains all the data from the full export software vulnera
395
395
|ExploitabilityLevel|String|The exploitability level of this vulnerability (NoExploit, ExploitIsPublic, ExploitIsVerified, ExploitIsInKit)|ExploitIsInKit|
396
396
|FirstSeenTimestamp|String|First time the CVE of this product was seen on the device.|2020-11-03 10:13:34.8476880|
397
397
|ID|String|Unique identifier for the record.|123ABG55_573AG&mnp!|
398
-
|LastSeenTimestamp|String|Last time the CVE was reported on the device.|2020-11-03 10:13:34.8476880|
398
+
|LastSeenTimestamp|String|Last time the software was reported on the device.|2020-11-03 10:13:34.8476880|
399
399
|OSPlatform|String|Platform of the operating system running on the device; specific operating systems with variations within the same family, such as Windows 10 and Windows 11. See Microsoft Defender Vulnerability Management supported operating systems and platforms for details.|Windows10 and Windows 11|
400
400
|RbacGroupName|String|The role-based access control (RBAC) group. If this device isn't assigned to any RBAC group, the value is "Unassigned." If the organization doesn't contain any RBAC groups, the value is "None."|Servers|
401
401
|RecommendationReference|string|A reference to the recommendation ID related to this software.|va--microsoft--silverlight|
Copy file name to clipboardExpand all lines: defender-endpoint/linux-install-manually.md
+53-20Lines changed: 53 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
title: Deploy Microsoft Defender for Endpoint on Linux manually
3
3
description: Describes how to deploy Microsoft Defender for Endpoint on Linux manually from the command line.
4
4
ms.service: defender-endpoint
5
-
ms.author: deniseb
6
-
author: denisebmsft
5
+
ms.author: ewalsh
6
+
author: emmwalshh
7
7
ms.reviewer: gopkr
8
8
ms.localizationpriority: medium
9
9
manager: deniseb
@@ -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/10/2025
18
+
ms.date: 02/11/2025
19
19
---
20
20
21
21
# Deploy Microsoft Defender for Endpoint on Linux manually
@@ -50,10 +50,6 @@ In order to preview new features and provide early feedback, it's recommended th
50
50
> [!WARNING]
51
51
> Switching the channel after the initial installation requires the product to be reinstalled. To switch the product channel: uninstall the existing package, reconfigure your device to use the new channel, and follow the steps in this document to install the package from the new location.
52
52
53
-
## Installer script
54
-
55
-
To use the installer script method, see [Use the installer script to deploy Microsoft Defender for Endpoint on Linux](linux-installer-script.md).
56
-
57
53
## Application installation
58
54
59
55
### RHEL and variants (CentOS, Fedora, Oracle Linux, Amazon Linux 2, Rocky, and Alma)
@@ -198,7 +194,7 @@ Download the onboarding package from Microsoft Defender portal.
198
194
> To run this command, you must have `python` or `python3` installed on the device depending on the distro and version. If needed, see [Step-by-step Instructions for Installing Python on Linux](https://opensource.com/article/20/4/install-python-linux).
199
195
200
196
> [!NOTE]
201
-
> To onboard a device that was previously offboarded you must remove the mdatp_offboard.json file located at /etc/opt/microsoft/mdatp.
197
+
> To onboard a device that was previously offboard, you must remove the mdatp_offboard.json file located at /etc/opt/microsoft/mdatp.
202
198
203
199
If you're running RHEL 8.x or Ubuntu 20.04 or higher, you need to use `python3`.
204
200
@@ -225,11 +221,11 @@ Download the onboarding package from Microsoft Defender portal.
225
221
```
226
222
227
223
> [!IMPORTANT]
228
-
> When the product starts for the first time, it downloads the latest anti-malware definitions. This process may take up to a few minutes depending on the network connectivity. During this time, the command mentioned earlier returns a value of `false`. You can check the status of the definition update using the following command:
224
+
> When the product starts for the first time, it downloads the latest anti-malware definitions. This process might take up to a few minutes depending on the network connectivity. During this time, the command mentioned earlier returns a value of `false`. You can check the status of the definition update using the following command:
229
225
>
230
226
> `mdatp health --field definitions_status`
231
227
>
232
-
> Note that you may also need to configure a proxy after completing the initial installation. See [Configure Defender for Endpoint on Linux for static proxy discovery: Post-installation configuration](linux-static-proxy-configuration.md#post-installation-configuration).
228
+
> You might also need to configure a proxy after completing the initial installation. See [Configure Defender for Endpoint on Linux for static proxy discovery: Post-installation configuration](linux-static-proxy-configuration.md#post-installation-configuration).
233
229
234
230
1. Run an AV detection test to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
235
231
@@ -284,7 +280,7 @@ The following external package dependencies exist for the mdatp package:
284
280
285
281
> [!NOTE]
286
282
> Starting 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.
287
-
> If eBPF is not 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 lower, the following other dependencies on the auditd package exist for mdatp:
283
+
> 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 lower, the following other dependencies on the auditd package exist for mdatp:
288
284
> - The mdatp RPM package requires `audit`, `semanage`.
289
285
> - For DEBIAN, the mdatp package requires `auditd`.
290
286
> - For Mariner, the mdatp package requires `audit`.
@@ -298,19 +294,32 @@ The `mde-netfilter` package also has the following package dependencies:
298
294
If the Microsoft Defender for Endpoint installation fails due to missing dependencies errors, you can manually download the prerequisite dependencies.
299
295
300
296
301
-
## Log installation issues
297
+
## Troubleshoot installation issues
298
+
299
+
- For details on how to find the log that's generated when an installation error occurs, see [Log installation issues](/defender-endpoint/linux-resources#log-installation-issues).
300
+
301
+
- For information about common installation issues, see [Installation issues](/defender-endpoint/linux-support-install).
302
+
303
+
- If the health of the device is false, see [Investigate agent health issues](health-status.md).
302
304
303
-
See [Log installation issues](linux-resources.md#log-installation-issues) for more information on how to find the automatically generated log that is created by the installer when an error occurs.
305
+
- For product performance issues, see [Troubleshoot performance issues for Microsoft Defender for Endpoint on Linux](linux-support-perf.md).
304
306
305
-
## How to migrate from Insiders-Fast to Production channel
307
+
- For proxy and connectivity issues, see [Troubleshoot cloud connectivity issues for Microsoft Defender for Endpoint on Linux](linux-support-connectivity.md).
308
+
309
+
- To get support from Microsoft, open a support ticket, and provide the log files created by using the [Microsoft Defender for Endpoint client analyzer tool](run-analyzer-linux.md).
310
+
311
+
312
+
## How to switch between channels
313
+
314
+
For example, to change channel from Insiders-Fast to Production, do the following:
306
315
307
316
1. Uninstall the `Insiders-Fast channel` version of Defender for Endpoint on Linux.
308
317
309
318
```bash
310
319
sudo yum remove mdatp
311
320
```
312
321
313
-
1. Disable the Defender for Endpoint on Linux Insiders-Fast repo
322
+
2. Disable the Defender for Endpoint on Linux Insiders-Fast repo.
314
323
315
324
```bash
316
325
sudo yum repolist
@@ -323,14 +332,38 @@ See [Log installation issues](linux-resources.md#log-installation-issues) for mo
1. Redeploy Microsoft Defender for Endpoint on Linux using the Production channel.
335
+
3. Redeploy Microsoft Defender for Endpoint on Linux using the Production channel.
336
+
337
+
Defender for Endpoint on Linux can be deployed from one of the following channels (denoted as [channel]):
338
+
339
+
- `insiders-fast`
340
+
- `insiders-slow`
341
+
- `prod`
342
+
343
+
Each of these channels corresponds to a Linux software repository. This article describes how to configure your device to use one of these repositories.
344
+
345
+
The choice of channel determines the type and frequency of updates that are offered to your device. Devices in insiders-fast are the first to receive updates and new features, followed later by insiders-slow and lastly by prod.
346
+
347
+
In order to preview new features and provide early feedback, it's recommended that you configure some devices in your enterprise to use either `insiders-fast` or `insiders-slow`.
348
+
349
+
> [!WARNING]
350
+
> Switching channels after the initial installation requires the product to be reinstalled. To switch the product channel: uninstall the existing package, reconfigure your device to use the new channel, and follow the steps in this document to install the package from the new location.
351
+
352
+
## How to configure policies for Microsoft Defender for Endpoint on Linux
353
+
354
+
You can configure antivirus and EDR settings on your endpoints. For more information, see the following articles:
355
+
356
+
- [Set preferences for Microsoft Defender for Endpoint on Linux](/defender-endpoint/linux-preferences) describes the available settings
357
+
- [Security settings management](/mem/intune/protect/mde-security-integration) describes how to configure settings in the Microsoft Defender portal.
327
358
328
-
## Uninstallation
359
+
## Uninstall Microsoft Defender for Endpoint on Linux
329
360
330
-
See [Uninstall](linux-resources.md#uninstall-defender-for-endpoint-on-linux) for details on how to remove Defender for Endpoint on Linux from client devices.
361
+
For manual uninstallation, execute the below command as per your Linux distribution.
331
362
332
-
## See also
363
+
- `sudo yum remove mdatp` for RHEL and variants(CentOS and Oracle Linux).
364
+
- `sudo zypper remove mdatp` for SLES and variants.
365
+
- `sudo apt-get purge mdatp` for Ubuntu and Debian systems.
366
+
- `sudo dnf remove mdatp` for Mariner
333
367
334
-
- [Investigate agent health issues](health-status.md)
335
368
336
369
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]
0 commit comments