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: CloudAppSecurityDocs/tutorial-dlp.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,6 @@ Our approach to information protection can be split into the following phases th
79
79
1. Under **Inspection method**, choose and configure one of the following classification services:
80
80
81
81
-**[Data Classification Services](dcs-inspection.md)**: Uses classification decisions you've made across Microsoft 365, Microsoft Purview Information Protection, and Defender for Cloud Apps to provide a unified labeling experience. This is the preferred content inspection method as it provides a consistent and unified experience across Microsoft products.
82
-
-**[Built-in DLP](content-inspection-built-in.md)**: Inspects files for sensitive information using our built-in DLP content inspection engine.
83
82
84
83
1. For highly sensitive files, select **Create an alert** and choose the alerts you require, so that you're informed when there are files with unprotected sensitive information in your organization.
Copy file name to clipboardExpand all lines: defender-endpoint/detect-block-potentially-unwanted-apps-microsoft-defender-antivirus.md
+25-13Lines changed: 25 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: emmwalshh
7
7
ms.author: ewalsh
8
8
ms.custom: nextgen
9
9
audience: ITPro
10
-
ms.reviewer: mimilone, julih
10
+
ms.reviewer: yongrhee, mimilone, julih
11
11
manager: deniseb
12
12
ms.subservice: ngp
13
13
ms.topic: conceptual
@@ -16,7 +16,7 @@ ms.collection:
16
16
- tier2
17
17
- mde-ngp
18
18
search.appverid: met150
19
-
ms.date: 05/17/2024
19
+
ms.date: 03/04/2025
20
20
---
21
21
22
22
# Detect and block potentially unwanted applications
@@ -36,6 +36,7 @@ ms.date: 05/17/2024
36
36
37
37
Microsoft Defender Antivirus is available in the following editions/versions of Windows and Windows Server:
38
38
39
+
- Windows Server 2025
39
40
- Windows Server 2022
40
41
- Windows Server 2019
41
42
- Windows Server, version 1803 or later
@@ -81,21 +82,21 @@ Although potentially unwanted application protection in Microsoft Edge (Chromium
81
82
3. Under the **Security** section, turn on **Block potentially unwanted apps**.
82
83
83
84
> [!TIP]
84
-
> If you are running Microsoft Edge (Chromium-based), you can safely explore the URL-blocking feature of PUA protection by testing it out on one of our [Microsoft Defender SmartScreen demo pages](https://demo.smartscreen.msft.net/).
85
+
> If you're running Microsoft Edge (Chromium-based), you can safely explore the URL-blocking feature of PUA protection by testing it out on one of our [Microsoft Defender SmartScreen demo pages](https://demo.smartscreen.msft.net/).
85
86
86
87
### Block URLs with Microsoft Defender SmartScreen
87
88
88
89
In Chromium-based Microsoft Edge with PUA protection turned on, Microsoft Defender SmartScreen protects you from PUA-associated URLs.
89
90
90
-
Security admins can [configure](/DeployEdge/configure-microsoft-edge) how Microsoft Edge and Microsoft Defender SmartScreen work together to protect groups of users from PUA-associated URLs. There are several [group policy settings](/DeployEdge/microsoft-edge-policies#smartscreen-settings) explicitly for Microsoft Defender SmartScreen available, including [one for blocking PUA](/DeployEdge/microsoft-edge-policies#smartscreenpuaenabled). In addition, admins can [configure Microsoft Defender SmartScreen](/microsoft-edge/deploy/available-policies?source=docs#configure-windows-defender-smartscreen) as a whole, using group policy settings to turn Microsoft Defender SmartScreen on or off.
91
+
Security administrators can [configure](/DeployEdge/configure-microsoft-edge) how Microsoft Edge and Microsoft Defender SmartScreen work together to protect groups of users from PUA-associated URLs. There are several [group policy settings](/DeployEdge/microsoft-edge-policies#smartscreen-settings) explicitly for Microsoft Defender SmartScreen available, including [one for blocking PUA](/DeployEdge/microsoft-edge-policies#smartscreenpuaenabled). In addition, admins can [configure Microsoft Defender SmartScreen](/microsoft-edge/deploy/available-policies?source=docs#configure-windows-defender-smartscreen) as a whole, using group policy settings to turn Microsoft Defender SmartScreen on or off.
91
92
92
93
Although Microsoft Defender for Endpoint has its own blocklist based upon a data set managed by Microsoft, you can customize this list based on your own threat intelligence. If you [create and manage indicators](indicators-overview.md) in the Microsoft Defender for Endpoint portal, Microsoft Defender SmartScreen respects the new settings.
93
94
94
95
## Microsoft Defender Antivirus and PUA protection
95
96
96
97
The potentially unwanted application (PUA) protection feature in Microsoft Defender Antivirus can detect and block PUA on endpoints in your network.
97
98
98
-
Microsoft Defender Antivirus blocks detected PUA files and any attempts to download, move, run, or install them. Blocked PUA files are then moved to quarantine. When a PUA file is detected on an endpoint, Microsoft Defender Antivirus sends a notification to the user ([unless notifications have been disabled](configure-notifications-microsoft-defender-antivirus.md) in the same format as other threat detections. The notification is prefaced with `PUA:` to indicate its content.
99
+
Microsoft Defender Antivirus blocks detected PUA files and any attempts to download, move, run, or install them. Blocked PUA files are then moved to quarantine. When a PUA file is detected on an endpoint, Microsoft Defender Antivirus sends a notification to the user ([unless notifications are disabled](configure-notifications-microsoft-defender-antivirus.md) in the same format as other threat detections. The notification is prefaced with `PUA:` to indicate its content.
99
100
100
101
The notification appears in the usual [quarantine list within the Windows Security app](microsoft-defender-security-center-antivirus.md).
101
102
@@ -122,7 +123,7 @@ See the following articles:
122
123
123
124
PUA protection is enabled by default in the Microsoft Configuration Manager (Current Branch).
124
125
125
-
See [How to create and deploy antimalware policies: Scheduled scans settings](/configmgr/protect/deploy-use/endpoint-antimalware-policies#real-time-protection-settings) for details on configuring Microsoft Configuration Manager (Current Branch).
126
+
See [How to create and deploy anti-malware policies: Scheduled scans settings](/configmgr/protect/deploy-use/endpoint-antimalware-policies#real-time-protection-settings) for details on configuring Microsoft Configuration Manager (Current Branch).
126
127
127
128
For System Center 2012 Configuration Manager, see [How to Deploy Potentially Unwanted Application Protection Policy for Endpoint Protection in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/hh508770(v=technet.10)#BKMK_PUA).
128
129
@@ -155,7 +156,7 @@ For System Center 2012 Configuration Manager, see [How to Deploy Potentially Unw
155
156
Set-MpPreference -PUAProtection Enabled
156
157
```
157
158
158
-
Setting the value for this cmdlet to `Enabled` turns on the feature if it has been disabled.
159
+
Setting the value for this cmdlet to `Enabled` turns on the feature if it is disabled.
Setting the value for this cmdlet to `Disabled` turns off the feature if it has been enabled.
177
178
179
+
#### To query the PUA status
180
+
181
+
182
+
```powershell
183
+
get-mpPreference | ft PUAProtection
184
+
```
185
+
186
+
|Value | Description|
187
+
| -------- | -------- |
188
+
|`0`| PUA Protection off (Default). Microsoft Defender Antivirus won't protect against potentially unwanted applications. |
189
+
|`1`| PUA Protection on. Detected items are blocked. They will show in history along with other threats.|
190
+
|`2`| Audit mode. Microsoft Defender Antivirus will detect potentially unwanted applications but take no action. You can review information about the applications Windows Defender would've taken action against by searching for events created by Windows Defender in the Event Viewer.|
191
+
178
192
For more information, see [Use PowerShell cmdlets to configure and run Microsoft Defender Antivirus](use-powershell-cmdlets-microsoft-defender-antivirus.md) and [Defender Antivirus cmdlets](/powershell/module/defender/index).
179
193
180
194
## Test and make sure that PUA blocking works
@@ -224,16 +238,14 @@ Sometimes a file is erroneously blocked by PUA protection, or a feature of a PUA
224
238
225
239
For more information, see [Configure and validate exclusions based on file extension and folder location](configure-extension-file-exclusions-microsoft-defender-antivirus.md).
226
240
227
-
> [!TIP]
228
-
> If you're looking for Antivirus related information for other platforms, see:
229
-
> -[Microsoft Defender for Endpoint on Mac](microsoft-defender-endpoint-mac.md)
230
-
> -[Microsoft Defender for Endpoint on Linux](microsoft-defender-endpoint-linux.md)
231
-
> -[Configure Defender for Endpoint on Android features](android-configure.md)
232
-
> -[Configure Microsoft Defender for Endpoint on iOS features](ios-configure-features.md)
Copy file name to clipboardExpand all lines: defender-endpoint/indicator-file.md
+11-20Lines changed: 11 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
6
6
ms.author: deniseb
7
7
author: denisebmsft
8
8
ms.localizationpriority: medium
9
-
ms.date: 02/06/2025
9
+
ms.date: 03/04/2025
10
10
manager: deniseb
11
11
audience: ITPro
12
12
ms.collection:
@@ -29,9 +29,6 @@ search.appverid: met150
29
29
-[Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
30
30
-[Microsoft Defender for Business](/defender-business/mdb-overview)
31
31
32
-
> [!TIP]
33
-
> Want to experience Defender for Endpoint? [Sign up for a free trial.](https://www.microsoft.com/WindowsForBusiness/windows-atp?ocid=docs-wdatp-automationexclusionlist-abovefoldlink)
34
-
35
32
> [!IMPORTANT]
36
33
> In Defender for Endpoint Plan 1 and Defender for Business, you can create an indicator to block or allow a file. In Defender for Business, your indicator is applied across your environment and cannot be scoped to specific devices.
37
34
@@ -52,37 +49,33 @@ There are three ways you can create indicators for files:
52
49
Understand the following prerequisites before you create indicators for files:
53
50
54
51
-[Behavior Monitoring is enabled](behavior-monitor.md)
55
-
56
52
-[Cloud-based protection is turned on](/defender-endpoint/enable-cloud-protection-microsoft-defender-antivirus).
57
-
58
53
-[Cloud Protection network connectivity is functional](configure-network-connections-microsoft-defender-antivirus.md)
59
-
60
54
- To start blocking files, [turn on the "block or allow" feature](advanced-features.md) in Settings (in the [Microsoft Defender portal](https://security.microsoft.com), go to **Settings** > **Endpoints** > **General** > **Advanced features** > **Allow or block file**).
61
55
62
56
### Windows prerequisites
63
57
64
58
- This feature is available if your organization uses [Microsoft Defender Antivirus](microsoft-defender-antivirus-windows.md) (in active mode)
65
-
66
-
- The Antimalware client version must be `4.18.1901.x` or later. See [Monthly platform and engine versions](microsoft-defender-antivirus-updates.md#platform-and-engine-releases)
67
-
59
+
- The antimalware client version must be `4.18.1901.x` or later. See [Monthly platform and engine versions](microsoft-defender-antivirus-updates.md#platform-and-engine-releases)
68
60
- This feature is supported on devices running Windows 10, version 1703 or later, Windows 11, Windows Server 2012 R2, Windows Server 2016 or later, Windows Server 2019, or Windows Server 2022.
69
-
70
61
- File hash computation is enabled, by setting `Computer Configuration\Administrative Templates\Windows Components\Microsoft Defender Antivirus\MpEngine\` to **Enabled**
71
62
72
63
> [!NOTE]
73
64
> File indicators support portable executable (PE) files, including `.exe` and `.dll` files only.
74
65
75
66
### macOS prerequisites
76
67
77
-
-[File hash computation is enabled](/defender-endpoint/mac-resources#configuring-from-the-command-line) by running `mdatp config enable-file-hash-computation --value enabled`
78
-
79
-
### Linux prerequisites
68
+
- Real-time protection (RTP) needs to be active.
69
+
-[File hash computation must be enabled](/defender-endpoint/mac-resources#configuring-from-the-command-line). Run the following command: `mdatp config enable-file-hash-computation --value enabled`
80
70
81
-
- Available in Defender for Endpoint version 101.85.27 or later.
71
+
> [!NOTE]
72
+
> On Mac, file indicators support Mach-O files (akin to `.exe` and `.dll` in Windows) scripts, such as sh/bash and AppleScript File (`.scpt`) files only.
82
73
83
-
-[File hash computation is enabled](/defender-endpoint/linux-preferences#configure-file-hash-computation-feature) in the Microsoft Defender portal or in the managed JSON
74
+
### Linux prerequisites
84
75
85
-
- Behavior monitoring is preferred, but this will work with any other scan (RTP or Custom).
76
+
- Available in Defender for Endpoint version `101.85.27` or later.
77
+
-[File hash computation must be enabled](/defender-endpoint/linux-preferences#configure-file-hash-computation-feature) in the Microsoft Defender portal or in the managed JSON
78
+
- Behavior monitoring enabled is preferred, but this feature works with any other scan (RTP or Custom).
86
79
87
80
## Create an indicator for files from the settings page
88
81
@@ -95,9 +88,7 @@ Understand the following prerequisites before you create indicators for files:
95
88
4. Specify the following details:
96
89
97
90
- Indicator: Specify the entity details and define the expiration of the indicator.
98
-
99
91
- Action: Specify the action to be taken and provide a description.
100
-
101
92
- Scope: Define the scope of the device group (scoping isn't available in [Defender for Business](/defender-business/mdb-overview)).
102
93
103
94
> [!NOTE]
@@ -156,7 +147,7 @@ Timestamp > ago(30d)
156
147
157
148
For more information about advanced hunting, see [Proactively hunt for threats with advanced hunting](/defender-xdr/advanced-hunting-overview).
158
149
159
-
Below are other thread names that can be used in the sample query from above:
150
+
Here are other thread names that can be used in the sample query:
Copy file name to clipboardExpand all lines: defender-endpoint/linux-install-manually.md
+34-35Lines changed: 34 additions & 35 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/14/2025
18
+
ms.date: 03/04/2025
19
19
---
20
20
21
21
# Deploy Microsoft Defender for Endpoint on Linux manually
@@ -391,96 +391,95 @@ Download the onboarding package from the [Microsoft Defender portal](https://sec
391
391
392
392
> [!NOTE]
393
393
> Initially the client device isn't associated with an organization and the *orgId* attribute is blank.
394
-
394
+
395
395
```bash
396
396
mdatp health --field org_id
397
397
```
398
-
399
-
2. Run `MicrosoftDefenderATPOnboardingLinuxServer.py`.
398
+
399
+
1. Run one of the below scenarios.
400
400
401
401
> [!NOTE]
402
402
> 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).
403
403
>
404
404
> To onboard a device that was previously offboard, you must remove the mdatp_offboard.json file located at /etc/opt/microsoft/mdatp.
405
-
406
-
If you're running RHEL 8.x or Ubuntu 20.04 or higher, you need to use `python3`.
407
-
405
+
406
+
If you're running RHEL 8.x or Ubuntu 20.04 or higher, you need to use `python3`. Run the following command:
3. Verify that the device is now associated with your organization and reports a valid organization identifier:
417
+
418
+
1. Verify that the device is now associated with your organization and reports a valid organization identifier:
419
419
420
420
```bash
421
421
mdatp health --field org_id
422
422
```
423
-
424
-
4. Check the health status of the product by running the following command. A return value of `true` denotes that the product is functioning as expected:
423
+
424
+
1. Check the health status of the product by running the following command. A return value of `true` denotes that the product is functioning as expected:
425
425
426
426
```bash
427
427
mdatp health --field healthy
428
428
```
429
-
429
+
430
430
> [!IMPORTANT]
431
431
> 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:
432
-
>
432
+
>
433
433
> ```bash
434
434
> mdatp health --field definitions_status
435
435
> ```
436
-
>
437
436
> 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).
438
-
439
-
5. Run an antivirus detection test to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
437
+
438
+
1. Run an antivirus detection test to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
440
439
441
440
1. Ensure that real-time protection is enabled (denoted by a result of `true` from running the following command):
442
-
441
+
443
442
```bash
444
443
mdatp health --field real_time_protection_enabled
445
444
```
446
-
445
+
447
446
If it isn't enabled, execute the following command:
448
-
447
+
449
448
```bash
450
449
mdatp config real-time-protection --value enabled
451
450
```
452
-
453
-
2. Open a Terminal window and execute the following command to run a detection test:
451
+
452
+
1. To run a detection test, open a Terminal window. and then run the following command:
The files should be quarantined by Defender for Endpoint on Linux.
467
466
468
-
4. Use the following command to list all the detected threats:
467
+
1. Use the following command to list all the detected threats:
469
468
470
469
```bash
471
470
mdatp threat list
472
471
```
473
-
474
-
6. Run an EDR detection test and simulate a detection to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
472
+
473
+
1. Run an EDR detection test and simulate a detection to verify that the device is properly onboarded and reporting to the service. Perform the following steps on the newly onboarded device:
475
474
476
475
1. Verify that the onboarded Linux server appears in Microsoft Defender XDR. If this is the first onboarding of the machine, it can take up to 20 minutes until it appears.
477
-
478
-
2. Download and extract the [script file](https://aka.ms/MDE-Linux-EDR-DIY) to an onboarded Linux server, and then run the following command: `./mde_linux_edr_diy.sh`
479
-
476
+
477
+
1. Download and extract the [script file](https://aka.ms/MDE-Linux-EDR-DIY) to an onboarded Linux server, and then run the following command: `./mde_linux_edr_diy.sh`
478
+
480
479
After a few minutes, a detection should be raised in Microsoft Defender XDR.
481
-
482
-
3. Look at the alert details, machine timeline, and perform your typical investigation steps.
483
-
480
+
481
+
1. Look at the alert details, machine timeline, and perform your typical investigation steps.
482
+
484
483
## Microsoft Defender for Endpoint package external package dependencies
485
484
486
485
The following external package dependencies exist for the `mdatp` package:
0 commit comments