Skip to content

Commit dcbb80a

Browse files
Merge branch 'main' into repo_sync_working_branch
2 parents fba2be5 + 608e4ac commit dcbb80a

40 files changed

+286
-136
lines changed

CloudAppSecurityDocs/tutorial-dlp.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,6 @@ Our approach to information protection can be split into the following phases th
7979
1. Under **Inspection method**, choose and configure one of the following classification services:
8080

8181
- **[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.
8382

8483
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.
8584
1. Select **Create**.

defender-endpoint/detect-block-potentially-unwanted-apps-microsoft-defender-antivirus.md

Lines changed: 25 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: emmwalshh
77
ms.author: ewalsh
88
ms.custom: nextgen
99
audience: ITPro
10-
ms.reviewer: mimilone, julih
10+
ms.reviewer: yongrhee, mimilone, julih
1111
manager: deniseb
1212
ms.subservice: ngp
1313
ms.topic: conceptual
@@ -16,7 +16,7 @@ ms.collection:
1616
- tier2
1717
- mde-ngp
1818
search.appverid: met150
19-
ms.date: 05/17/2024
19+
ms.date: 03/04/2025
2020
---
2121

2222
# Detect and block potentially unwanted applications
@@ -36,6 +36,7 @@ ms.date: 05/17/2024
3636

3737
Microsoft Defender Antivirus is available in the following editions/versions of Windows and Windows Server:
3838

39+
- Windows Server 2025
3940
- Windows Server 2022
4041
- Windows Server 2019
4142
- Windows Server, version 1803 or later
@@ -81,21 +82,21 @@ Although potentially unwanted application protection in Microsoft Edge (Chromium
8182
3. Under the **Security** section, turn on **Block potentially unwanted apps**.
8283

8384
> [!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/).
8586
8687
### Block URLs with Microsoft Defender SmartScreen
8788

8889
In Chromium-based Microsoft Edge with PUA protection turned on, Microsoft Defender SmartScreen protects you from PUA-associated URLs.
8990

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.
9192

9293
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.
9394

9495
## Microsoft Defender Antivirus and PUA protection
9596

9697
The potentially unwanted application (PUA) protection feature in Microsoft Defender Antivirus can detect and block PUA on endpoints in your network.
9798

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.
99100

100101
The notification appears in the usual [quarantine list within the Windows Security app](microsoft-defender-security-center-antivirus.md).
101102

@@ -122,7 +123,7 @@ See the following articles:
122123

123124
PUA protection is enabled by default in the Microsoft Configuration Manager (Current Branch).
124125

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).
126127

127128
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).
128129

@@ -155,7 +156,7 @@ For System Center 2012 Configuration Manager, see [How to Deploy Potentially Unw
155156
Set-MpPreference -PUAProtection Enabled
156157
```
157158

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.
159160

160161
#### To set PUA protection to audit mode
161162

@@ -175,6 +176,19 @@ Set-MpPreference -PUAProtection Disabled
175176

176177
Setting the value for this cmdlet to `Disabled` turns off the feature if it has been enabled.
177178

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+
178192
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).
179193

180194
## 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
224238

225239
For more information, see [Configure and validate exclusions based on file extension and folder location](configure-extension-file-exclusions-microsoft-defender-antivirus.md).
226240

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)
233241

234242
## See also
235243

236244
- [Next-generation protection](microsoft-defender-antivirus-windows.md)
237245
- [Configure behavioral, heuristic, and real-time protection](configure-protection-features-microsoft-defender-antivirus.md)
246+
- [Microsoft Defender for Endpoint on Mac](microsoft-defender-endpoint-mac.md)
247+
- [Microsoft Defender for Endpoint on Linux](microsoft-defender-endpoint-linux.md)
248+
- [Configure Defender for Endpoint on Android features](android-configure.md)
249+
- [Configure Microsoft Defender for Endpoint on iOS features](ios-configure-features.md)
238250

239251
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/indicator-file.md

Lines changed: 11 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
66
ms.author: deniseb
77
author: denisebmsft
88
ms.localizationpriority: medium
9-
ms.date: 02/06/2025
9+
ms.date: 03/04/2025
1010
manager: deniseb
1111
audience: ITPro
1212
ms.collection:
@@ -29,9 +29,6 @@ search.appverid: met150
2929
- [Microsoft Defender for Endpoint Plan 2](microsoft-defender-endpoint.md)
3030
- [Microsoft Defender for Business](/defender-business/mdb-overview)
3131

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-
3532
> [!IMPORTANT]
3633
> 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.
3734
@@ -52,37 +49,33 @@ There are three ways you can create indicators for files:
5249
Understand the following prerequisites before you create indicators for files:
5350

5451
- [Behavior Monitoring is enabled](behavior-monitor.md)
55-
5652
- [Cloud-based protection is turned on](/defender-endpoint/enable-cloud-protection-microsoft-defender-antivirus).
57-
5853
- [Cloud Protection network connectivity is functional](configure-network-connections-microsoft-defender-antivirus.md)
59-
6054
- 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**).
6155

6256
### Windows prerequisites
6357

6458
- 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)
6860
- 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-
7061
- File hash computation is enabled, by setting `Computer Configuration\Administrative Templates\Windows Components\Microsoft Defender Antivirus\MpEngine\` to **Enabled**
7162

7263
> [!NOTE]
7364
> File indicators support portable executable (PE) files, including `.exe` and `.dll` files only.
7465
7566
### macOS prerequisites
7667

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`
8070

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.
8273
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
8475

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).
8679

8780
## Create an indicator for files from the settings page
8881

@@ -95,9 +88,7 @@ Understand the following prerequisites before you create indicators for files:
9588
4. Specify the following details:
9689

9790
- Indicator: Specify the entity details and define the expiration of the indicator.
98-
9991
- Action: Specify the action to be taken and provide a description.
100-
10192
- Scope: Define the scope of the device group (scoping isn't available in [Defender for Business](/defender-business/mdb-overview)).
10293

10394
> [!NOTE]
@@ -156,7 +147,7 @@ Timestamp > ago(30d)
156147

157148
For more information about advanced hunting, see [Proactively hunt for threats with advanced hunting](/defender-xdr/advanced-hunting-overview).
158149

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:
160151

161152
Files:
162153

defender-endpoint/linux-install-manually.md

Lines changed: 34 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: conceptual
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 02/14/2025
18+
ms.date: 03/04/2025
1919
---
2020

2121
# Deploy Microsoft Defender for Endpoint on Linux manually
@@ -391,96 +391,95 @@ Download the onboarding package from the [Microsoft Defender portal](https://sec
391391
392392
> [!NOTE]
393393
> Initially the client device isn't associated with an organization and the *orgId* attribute is blank.
394-
394+
395395
```bash
396396
mdatp health --field org_id
397397
```
398-
399-
2. Run `MicrosoftDefenderATPOnboardingLinuxServer.py`.
398+
399+
1. Run one of the below scenarios.
400400

401401
> [!NOTE]
402402
> 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).
403403
>
404404
> 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:
407+
408408
```bash
409409
sudo python3 MicrosoftDefenderATPOnboardingLinuxServer.py
410410
```
411-
412-
For the rest of distros and versions, you need to use `python`.
413-
411+
412+
For the rest of distros and versions, you need to use `python`. Run the following command:
413+
414414
```bash
415415
sudo python MicrosoftDefenderATPOnboardingLinuxServer.py
416416
```
417-
418-
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:
419419
420420
```bash
421421
mdatp health --field org_id
422422
```
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:
425425
426426
```bash
427427
mdatp health --field healthy
428428
```
429-
429+
430430
> [!IMPORTANT]
431431
> 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+
>
433433
> ```bash
434434
> mdatp health --field definitions_status
435435
> ```
436-
>
437436
> 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:
440439
441440
1. Ensure that real-time protection is enabled (denoted by a result of `true` from running the following command):
442-
441+
443442
```bash
444443
mdatp health --field real_time_protection_enabled
445444
```
446-
445+
447446
If it isn't enabled, execute the following command:
448-
447+
449448
```bash
450449
mdatp config real-time-protection --value enabled
451450
```
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:
454453

455454
``` bash
456455
curl -o /tmp/eicar.com.txt https://secure.eicar.org/eicar.com.txt
457456
```
458-
459-
3. You can run more detection tests on zip files using either of the following commands:
460457

458+
1. You can run more detection tests on zip files using either of the following commands:
459+
461460
```bash
462461
curl -o /tmp/eicar_com.zip https://secure.eicar.org/eicar_com.zip
463462
curl -o /tmp/eicarcom2.zip https://secure.eicar.org/eicarcom2.zip
464463
```
465464

466465
The files should be quarantined by Defender for Endpoint on Linux.
467466

468-
4. Use the following command to list all the detected threats:
467+
1. Use the following command to list all the detected threats:
469468

470469
```bash
471470
mdatp threat list
472471
```
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:
475474

476475
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+
480479
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+
484483
## Microsoft Defender for Endpoint package external package dependencies
485484

486485
The following external package dependencies exist for the `mdatp` package:

0 commit comments

Comments
 (0)