mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-18 08:17:23 +00:00
Merge pull request #4326 from MicrosoftDocs/master
Publish 12/1/2020 10:30 AM PT
This commit is contained in:
commit
cd7a1482c4
@ -20,7 +20,7 @@ The enrollment into Intune is triggered by a group policy created on your local
|
||||
Requirements:
|
||||
- AD-joined PC running Windows 10, version 1709 or later
|
||||
- The enterprise has configured a mobile device management (MDM) service
|
||||
- The enterprise AD must be [registered with Azure Active Directory (Azure AD)](azure-active-directory-integration-with-mdm.md)
|
||||
- The on-premises AD must be [integrated with Azure AD (via Azure AD Connect)](https://docs.microsoft.com/azure/architecture/reference-architectures/identity/azure-ad)
|
||||
- The device should not already be enrolled in Intune using the classic agents (devices managed using agents will fail enrollment with `error 0x80180026`)
|
||||
- The minimum Windows Server version requirement is based on the Hybrid Azure AD join requirement. See [How to plan your hybrid Azure Active Directory join implementation](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan) for more information.
|
||||
|
||||
|
@ -75,9 +75,6 @@ Here are examples of data fields. The encoded 0xF000 is the standard delimiter/s
|
||||
|
||||
If you use Intune custom profiles to assign UserRights policies, you must use the CDATA tag (`<![CDATA[...]]>`) to wrap the data fields. You can specify one or more user groups within the CDATA tag by using 0xF000 as the delimiter/separator.
|
||||
|
||||
> [!NOTE]
|
||||
> There is currently a reporting issue in the Microsoft Endpoint Manager (MEM) console which results in the setting reporting back a 'Remediation failed' (0x87d1fde8) error, even when the setting is successfully applied. To verify whether the setting has applied successfully, check the local Windows 10 device: Event Viewer>Applications and Services Logs<Microsoft>Windows>DeviceManagement-Enterprise-Diagnostics-Provider>Admin>Event ID 814. This issue is the result of the use of the CDATA tags, which are neccesary when more than a single entry is required. If there is only a single entry, the CDATA tags can be omitted - which will resolve the reporting false positive.
|
||||
|
||||
> [!NOTE]
|
||||
> `` is the entity encoding of 0xF000.
|
||||
|
||||
@ -87,7 +84,7 @@ For example, the following syntax grants user rights to Authenticated Users and
|
||||
<![CDATA[Authenticated UsersReplicator]]>
|
||||
```
|
||||
|
||||
For example, the following syntax grants user rights to two specific users from Contoso, user1 and user2:
|
||||
For example, the following syntax grants user rights to two specific Azure Active Directory (AAD) users from Contoso, user1 and user2:
|
||||
|
||||
```xml
|
||||
<![CDATA[AzureAD\user1@contoso.comAzureAD\user2@contoso.com]]>
|
||||
|
@ -21,7 +21,7 @@ ms.localizationpriority: medium
|
||||
|
||||
- Windows 10
|
||||
|
||||
>Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/WindowsForBusiness/Compare).
|
||||
> Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/WindowsForBusiness/Compare).
|
||||
|
||||
To help protect your company from attacks which may originate from untrusted or attacker controlled font files, we’ve created the Blocking Untrusted Fonts feature. Using this feature, you can turn on a global setting that stops your employees from loading untrusted fonts processed using the Graphics Device Interface (GDI) onto your network. Untrusted fonts are any font installed outside of the `%windir%/Fonts` directory. Blocking untrusted fonts helps prevent both remote (web-based or email-based) and local EOP attacks that can happen during the font file-parsing process.
|
||||
|
||||
@ -85,8 +85,8 @@ To turn this feature on, off, or to use audit mode:
|
||||
|
||||
- **To audit with this feature.** Type **3000000000000**.
|
||||
|
||||
>[!Important]
|
||||
>Your existing **MitigationOptions** values should be saved during your update. For example, if the current value is *1000*, your updated value should be *1000000001000*.
|
||||
> [!Important]
|
||||
> Your existing **MitigationOptions** values should be saved during your update. For example, if the current value is *1000*, your updated value should be *1000000001000*.
|
||||
|
||||
5. Restart your computer.
|
||||
|
||||
@ -105,8 +105,8 @@ After you turn this feature on, or start using Audit mode, you can look at your
|
||||
FontPath:<br>
|
||||
Blocked: true
|
||||
|
||||
>[!NOTE]
|
||||
>Because the **FontType** is *Memory*, there’s no associated **FontPath**.
|
||||
> [!NOTE]
|
||||
> Because the **FontType** is *Memory*, there’s no associated **FontPath**.
|
||||
|
||||
**Event Example 2 - Winlogon**<br>
|
||||
Winlogon.exe attempted loading a font that is restricted by font-loading policy.<br>
|
||||
@ -114,8 +114,8 @@ After you turn this feature on, or start using Audit mode, you can look at your
|
||||
FontPath: `\??\C:\PROGRAM FILES (X86)\COMMON FILES\MICROSOFT SHARED\EQUATION\MTEXTRA.TTF`<br>
|
||||
Blocked: true
|
||||
|
||||
>[!NOTE]
|
||||
>Because the **FontType** is *File*, there’s also an associated **FontPath**.
|
||||
> [!NOTE]
|
||||
> Because the **FontType** is *File*, there’s also an associated **FontPath**.
|
||||
|
||||
**Event Example 3 - Internet Explorer running in Audit mode**<br>
|
||||
Iexplore.exe attempted loading a font that is restricted by font-loading policy.<br>
|
||||
@ -123,8 +123,8 @@ After you turn this feature on, or start using Audit mode, you can look at your
|
||||
FontPath:<br>
|
||||
Blocked: false
|
||||
|
||||
>[!NOTE]
|
||||
>In Audit mode, the problem is recorded, but the font isn’t blocked.
|
||||
> [!NOTE]
|
||||
> In Audit mode, the problem is recorded, but the font isn’t blocked.
|
||||
|
||||
## Fix apps having problems because of blocked fonts
|
||||
Your company may still need apps that are having problems because of blocked fonts, so we suggest that you first run this feature in Audit mode to determine which fonts are causing the problems.
|
||||
@ -144,10 +144,4 @@ After you figure out the problematic fonts, you can try to fix your apps in 2 wa
|
||||
|
||||
## Related content
|
||||
|
||||
- [Dropping the “Untrusted Font Blocking” setting](https://blogs.technet.microsoft.com/secguide/2017/06/15/dropping-the-untrusted-font-blocking-setting/)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Dropping the “Untrusted Font Blocking” setting](https://techcommunity.microsoft.com/t5/microsoft-security-baselines/dropping-the-quot-untrusted-font-blocking-quot-setting/ba-p/701068/)
|
||||
|
@ -11,7 +11,7 @@ author: denisebmsft
|
||||
ms.author: deniseb
|
||||
ms.custom: nextgen
|
||||
audience: ITPro
|
||||
ms.date:
|
||||
ms.date: 11/30/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
@ -31,72 +31,73 @@ manager: dansimp
|
||||
|
||||
Potentially unwanted applications (PUA) are not considered viruses, malware, or other types of threats, but they might perform actions on endpoints which adversely affect endpoint performance or use. _PUA_ can also refer to an application that has a poor reputation, as assessed by Microsoft Defender for Endpoint, due to certain kinds of undesirable behavior.
|
||||
|
||||
For example:
|
||||
Here are some examples:
|
||||
|
||||
* **Advertising software**: Software that displays advertisements or promotions, including software that inserts advertisements to webpages.
|
||||
* **Bundling software**: Software that offers to install other software that is not digitally signed by the same entity. Also, software that offers to install other software that qualify as PUA.
|
||||
* **Evasion software**: Software that actively tries to evade detection by security products, including software that behaves differently in the presence of security products.
|
||||
- **Advertising software** that displays advertisements or promotions, including software that inserts advertisements to webpages.
|
||||
- **Bundling software** that offers to install other software that is not digitally signed by the same entity. Also, software that offers to install other software that qualify as PUA.
|
||||
- **Evasion software** that actively tries to evade detection by security products, including software that behaves differently in the presence of security products.
|
||||
|
||||
For more examples and a discussion of the criteria we use to label applications for special attention from security features, see [How Microsoft identifies malware and potentially unwanted applications](../intelligence/criteria.md).
|
||||
> [!TIP]
|
||||
> For more examples and a discussion of the criteria we use to label applications for special attention from security features, see [How Microsoft identifies malware and potentially unwanted applications](../intelligence/criteria.md).
|
||||
|
||||
Potentially unwanted applications can increase the risk of your network being infected with actual malware, make malware infections harder to identify, or waste IT resources in cleaning them up.
|
||||
|
||||
## How it works
|
||||
PUA protection is supported on Windows 10, Windows Server 2019, and Windows Server 2016.
|
||||
|
||||
### Microsoft Edge
|
||||
## Microsoft Edge
|
||||
|
||||
The next major version of Microsoft Edge, which is Chromium-based, blocks potentially unwanted application downloads and associated resource URLs. This feature is provided via [Microsoft Defender SmartScreen](../microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md).
|
||||
The [new Microsoft Edge](https://support.microsoft.com/microsoft-edge/get-to-know-microsoft-edge-3f4bb0ff-58de-2188-55c0-f560b7e20bea), which is Chromium-based, blocks potentially unwanted application downloads and associated resource URLs. This feature is provided via [Microsoft Defender SmartScreen](../microsoft-defender-smartscreen/microsoft-defender-smartscreen-overview.md).
|
||||
|
||||
#### Enable PUA protection in Chromium-based Microsoft Edge
|
||||
### Enable PUA protection in Chromium-based Microsoft Edge
|
||||
|
||||
Although potentially unwanted application protection in Microsoft Edge (Chromium-based, version 80.0.361.50) is turned off by default, it can easily be turned on from within the browser.
|
||||
|
||||
1. Select the ellipses, and then choose **Settings**.
|
||||
2. Select **Privacy and services**.
|
||||
3. Under the **Services** section, turn on **Block potentially unwanted apps**.
|
||||
2. Select **Privacy, search, and services**.
|
||||
3. Under the **Security** section, turn on **Block potentially unwanted apps**.
|
||||
|
||||
> [!TIP]
|
||||
> 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 Windows Defender SmartScreen [demo pages](https://demo.smartscreen.msft.net/).
|
||||
> 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/).
|
||||
|
||||
#### Blocking URLs with Windows Defender SmartScreen
|
||||
### Blocking URLs with Microsoft Defender SmartScreen
|
||||
|
||||
In Chromium-based Edge with PUA protection turned on, Windows Defender SmartScreen will protect you from PUA-associated URLs.
|
||||
In Chromium-based Edge with PUA protection turned on, Microsoft Defender SmartScreen will protect you from PUA-associated URLs.
|
||||
|
||||
Admins can [configure](https://docs.microsoft.com/DeployEdge/configure-microsoft-edge) how Microsoft Edge and Windows Defender SmartScreen work together to protect groups of users from PUA-associated URLs. There are several group policy [settings](https://docs.microsoft.com/DeployEdge/microsoft-edge-policies#smartscreen-settings) explicitly for Windows
|
||||
Admins can [configure](https://docs.microsoft.com/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](https://docs.microsoft.com/DeployEdge/microsoft-edge-policies#smartscreen-settings) explicitly for Microsoft
|
||||
Defender SmartScreen available, including [one for blocking PUA](https://docs.microsoft.com/DeployEdge/microsoft-edge-policies#smartscreenpuaenabled). In addition, admins can
|
||||
[configure Windows Defender SmartScreen](https://docs.microsoft.com/microsoft-edge/deploy/available-policies?source=docs#configure-windows-defender-smartscreen) as a whole, using group policy settings to turn Windows Defender SmartScreen on or off.
|
||||
[configure Microsoft Defender SmartScreen](https://docs.microsoft.com/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.
|
||||
|
||||
Although Microsoft Defender for Endpoint has its own block list, 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](../microsoft-defender-atp/manage-indicators.md) in the Microsoft Defender for Endpoint portal, Windows Defender SmartScreen will respect the new settings.
|
||||
Although Microsoft Defender for Endpoint has its own block list 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](../microsoft-defender-atp/manage-indicators.md) in the Microsoft Defender for Endpoint portal, Microsoft Defender SmartScreen will respect the new settings.
|
||||
|
||||
### Microsoft Defender Antivirus
|
||||
## Microsoft Defender Antivirus
|
||||
|
||||
The potentially unwanted application (PUA) protection feature in Microsoft Defender Antivirus can detect and block PUAs on endpoints in your network.
|
||||
|
||||
> [!NOTE]
|
||||
> This feature is only available in Windows 10.
|
||||
> This feature is available in Windows 10, Windows Server 2019, and Windows Server 2016.
|
||||
|
||||
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 will be prefaced with _PUA:_ to indicate its content.
|
||||
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.
|
||||
|
||||
The notification appears in the usual [quarantine list within the Windows Security app](microsoft-defender-security-center-antivirus.md#detection-history).
|
||||
|
||||
#### Configure PUA protection in Microsoft Defender Antivirus
|
||||
### Configure PUA protection in Microsoft Defender Antivirus
|
||||
|
||||
You can enable PUA protection with Microsoft Intune, Microsoft Endpoint Configuration Manager, Group Policy, or via PowerShell cmdlets.
|
||||
You can enable PUA protection with [Microsoft Intune](https://docs.microsoft.com/mem/intune/protect/device-protect), [Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/mem/configmgr/protect/deploy-use/endpoint-protection), [Group Policy](https://docs.microsoft.com/azure/active-directory-domain-services/manage-group-policy), or via [PowerShell cmdlets](https://docs.microsoft.com/powershell/module/defender/?view=win10-ps&preserve-view=true).
|
||||
|
||||
You can also use the PUA audit mode to detect PUAs without blocking them. The detections will be captured in the Windows event log.
|
||||
You can also use PUA protection in audit mode to detect potentially unwanted applications without blocking them. The detections will be captured in the Windows event log.
|
||||
|
||||
> [!TIP]
|
||||
> You can visit the Microsoft Defender for Endpoint demo website at [demo.wd.microsoft.com](https://demo.wd.microsoft.com/Page/UrlRep) to confirm that the feature is working, and see it in action.
|
||||
> Visit the Microsoft Defender for Endpoint demo website at [demo.wd.microsoft.com](https://demo.wd.microsoft.com/Page/UrlRep) to confirm that the feature is working, and see it in action.
|
||||
|
||||
PUA audit mode is useful if your company is conducting an internal software security compliance check and you'd like to avoid any false positives.
|
||||
PUA protection in audit mode is useful if your company is conducting an internal software security compliance check and you'd like to avoid any false positives.
|
||||
|
||||
##### Use Intune to configure PUA protection
|
||||
#### Use Intune to configure PUA protection
|
||||
|
||||
See [Configure device restriction settings in Microsoft Intune](https://docs.microsoft.com/intune/device-restrictions-configure) and [Microsoft Defender Antivirus device restriction settings for Windows 10 in Intune](https://docs.microsoft.com/intune/device-restrictions-windows-10#microsoft-defender-antivirus) for more details.
|
||||
|
||||
##### Use Configuration Manager to configure PUA protection
|
||||
#### Use Configuration Manager to configure PUA protection
|
||||
|
||||
PUA protection is enabled by default in the Microsoft Endpoint Configuration Manager (Current Branch).
|
||||
|
||||
@ -107,37 +108,39 @@ For System Center 2012 Configuration Manager, see [How to Deploy Potentially Unw
|
||||
> [!NOTE]
|
||||
> PUA events blocked by Microsoft Defender Antivirus are reported in the Windows Event Viewer and not in Microsoft Endpoint Configuration Manager.
|
||||
|
||||
##### Use Group Policy to configure PUA protection
|
||||
#### Use Group Policy to configure PUA protection
|
||||
|
||||
1. On your Group Policy management computer, open the [Group Policy Management Console](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)), right-click the Group Policy Object you want to configure, and select **Edit**.
|
||||
|
||||
2. In the **Group Policy Management Editor**, go to **Computer configuration** and select **Administrative templates**.
|
||||
|
||||
3. Expand the tree to **Windows components > Microsoft Defender Antivirus**.
|
||||
3. Expand the tree to **Windows Components** > **Microsoft Defender Antivirus**.
|
||||
|
||||
4. Double-click **Configure protection for potentially unwanted applications**.
|
||||
4. Double-click **Configure detection for potentially unwanted applications**.
|
||||
|
||||
5. Select **Enabled** to enable PUA protection.
|
||||
|
||||
6. In **Options**, select **Block** to block potentially unwanted applications, or select **Audit Mode** to test how the setting will work in your environment. Select **OK**.
|
||||
|
||||
##### Use PowerShell cmdlets to configure PUA protection
|
||||
7. Deploy your Group Policy object as you usually do.
|
||||
|
||||
###### To enable PUA protection
|
||||
#### Use PowerShell cmdlets to configure PUA protection
|
||||
|
||||
##### To enable PUA protection
|
||||
|
||||
```PowerShell
|
||||
Set-MpPreference -PUAProtection enable
|
||||
```
|
||||
Setting the value for this cmdlet to `Enabled` will turn the feature on if it has been disabled.
|
||||
|
||||
###### To set PUA protection to audit mode
|
||||
##### To set PUA protection to audit mode
|
||||
|
||||
```PowerShell
|
||||
Set-MpPreference -PUAProtection auditmode
|
||||
```
|
||||
Setting `AuditMode` will detect PUAs without blocking them.
|
||||
|
||||
###### To disable PUA protection
|
||||
##### To disable PUA protection
|
||||
|
||||
We recommend keeping PUA protection turned on. However, you can turn it off by using the following cmdlet:
|
||||
|
||||
@ -148,7 +151,7 @@ Setting the value for this cmdlet to `Disabled` will turn the feature off if it
|
||||
|
||||
See [Use PowerShell cmdlets to configure and run Microsoft Defender Antivirus](use-powershell-cmdlets-microsoft-defender-antivirus.md) and [Defender cmdlets](https://docs.microsoft.com/powershell/module/defender/index) for more information on how to use PowerShell with Microsoft Defender Antivirus.
|
||||
|
||||
#### View PUA events
|
||||
### View PUA events
|
||||
|
||||
PUA events are reported in the Windows Event Viewer, but not in Microsoft Endpoint Configuration Manager or in Intune.
|
||||
|
||||
@ -156,9 +159,11 @@ You can turn on email notifications to receive mail about PUA detections.
|
||||
|
||||
See [Troubleshoot event IDs](troubleshoot-microsoft-defender-antivirus.md) for details on viewing Microsoft Defender Antivirus events. PUA events are recorded under event ID **1160**.
|
||||
|
||||
#### Allow-listing apps
|
||||
### Allow-listing apps
|
||||
|
||||
Sometimes a file is erroneously blocked by PUA protection, or a feature of a PUA is required to complete a task. In these cases, a file can be allow-listed. See [How to Configure Endpoint Protection in Configuration Manager](https://docs.microsoft.com/previous-versions/system-center/system-center-2012-R2/hh508770(v=technet.10)#to-exclude-specific-files-or-folders) for information on allowing files which are currently blocked by PUA protection in Microsoft Defender Antivirus.
|
||||
Sometimes a file is erroneously blocked by PUA protection, or a feature of a PUA is required to complete a task. In these cases, a file can be allow-listed.
|
||||
|
||||
For more information, see [Recommended antivirus exclusions for Configuration Manager site servers, site systems, and clients](https://docs.microsoft.com/troubleshoot/mem/configmgr/recommended-antivirus-exclusions#exclusions).
|
||||
|
||||
## Related articles
|
||||
|
||||
|
Binary file not shown.
After Width: | Height: | Size: 102 KiB |
Binary file not shown.
After Width: | Height: | Size: 97 KiB |
Binary file not shown.
After Width: | Height: | Size: 107 KiB |
@ -43,7 +43,7 @@ It's important to understand the following requirements prior to creating indica
|
||||
- The Antimalware client version must be 4.18.1901.x or later.
|
||||
- Supported on machines on Windows 10, version 1703 or later, Windows server 2016 and 2019.
|
||||
- The virus and threat protection definitions must be up-to-date.
|
||||
- This feature currently supports entering .CER or .PEM file extensions.
|
||||
- This feature currently supports entering .CER or .PEM (Base64 ASCII) encoding based certificates.
|
||||
|
||||
>[!IMPORTANT]
|
||||
> - A valid leaf certificate is a signing certificate that has a valid certification path and must be chained to the Root Certificate Authority (CA) trusted by Microsoft. Alternatively, a custom (self-signed) certificate can be used as long as it's trusted by the client (Root CA certificate is installed under the Local Machine 'Trusted Root Certification Authorities').
|
||||
|
@ -27,6 +27,42 @@ ms.topic: conceptual
|
||||
> [!NOTE]
|
||||
> Defender for Endpoint for iOS would use a VPN in order to provide the Web Protection feature. This is not a regular VPN and is a local/self-looping VPN that does not take traffic outside the device.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **PUBLIC PREVIEW EDITION**
|
||||
>
|
||||
> This documentation is for a pre-release solution. The guidelines and the solution are subject to change between now and its general availability.
|
||||
>
|
||||
> As with any pre-release solution, remember to exercise caution when determining the target population for your deployments.
|
||||
|
||||
|
||||
## Configure compliance policy against jailbroken devices
|
||||
|
||||
To protect corporate data from being accessed on jailbroken iOS devices, we recommend that you setup the following compliance policy on Intune.
|
||||
|
||||
> [!NOTE]
|
||||
> Currently Defender for Endpoint for iOS does not provide protection against jailbreak scenarios. Some data like your corporate email id and corporate profile picture (if available) will be exposed to the attacker on the jailbroken device.
|
||||
|
||||
Follow the steps below to create a compliance policy against jailbroken devices.
|
||||
|
||||
1. In [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), go to **Devices** -> **Compliance policies** -> click on **Create Policy**. Select "iOS/iPadOS" as platform and click **Create**.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
1. Specify a name of the policy, example "Compliance Policy for Jailbreak".
|
||||
1. In the compliance settings page, click to expand **Device Health** section and click **Block** for **Jailbroken devices** field.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
1. In the *Action for noncompliance* section, select the actions as per your requirements and click **Next**.
|
||||
|
||||
> [!div class="mx-imgBorder"]
|
||||
> 
|
||||
|
||||
1. In the *Assignments* section, select the user groups that you want to include for this policy and then click **Next**.
|
||||
1. In the **Review+Create** section, verify that all the information entered is correct and then select **Create**.
|
||||
|
||||
## Configure custom indicators
|
||||
|
||||
Defender for Endpoint for iOS enables admins to configure custom indicators on iOS devices as well. Refer to [Manage indicators](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/manage-indicators) on how to configure custom indicators.
|
||||
@ -37,4 +73,3 @@ Defender for Endpoint for iOS enables admins to configure custom indicators on i
|
||||
## Web Protection
|
||||
|
||||
By default, Defender for Endpoint for iOS includes and enables the web protection feature. [Web protection](web-protection-overview.md) helps to secure devices against web threats and protect users from phishing attacks.
|
||||
|
||||
|
@ -54,7 +54,7 @@ The following steps can be used to troubleshoot and mitigate these issues:
|
||||
> [!NOTE]
|
||||
> This feature is available in version 100.90.70 or newer.
|
||||
|
||||
This feature is enabled by default on the `Dogfood` and `InsisderFast` channels. If you're using a different update channel, this feature can be enabled from the command line:
|
||||
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
|
||||
@ -78,16 +78,63 @@ The following steps can be used to troubleshoot and mitigate these issues:
|
||||
To collect current statistics, run:
|
||||
|
||||
```bash
|
||||
mdatp diagnostic real_time_protection_statistics # you can use ‘> stat.log’ to redirect to file
|
||||
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.
|
||||
|
||||
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
|
||||
--2020-11-14 11:27:27-- https://raw.githubusercontent.com/microsoft.mdatp-xplat/master/linus/diagnostic/high_cpu_parser.py
|
||||
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.xxx.xxx
|
||||
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)| 151.101.xxx.xxx| :443... connected.
|
||||
HTTP request sent, awaiting response... 200 OK
|
||||
Length: 1020 [text/plain]
|
||||
Saving to: 'high_cpu_parser.py'
|
||||
|
||||
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 this command will show all processes and their associated scan activity. 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).
|
||||
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.
|
||||
|
||||
> [!NOTE]
|
||||
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
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
3. Use the `top` command-line tool and analyze which applications are using the resources on your system. Typical examples include software updaters and compilers.
|
||||
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).
|
||||
|
||||
4. Configure Defender for Endpoint for Linux with exclusions for the processes or disk locations that contribute to the performance issues and re-enable real-time protection.
|
||||
|
||||
For more details, see [Configure and validate exclusions for Defender for Endpoint for Linux](linux-exclusions.md).
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Intune-based deployment for Microsoft Defender ATP for Mac
|
||||
description: Install Microsoft Defender ATP for Mac, using Microsoft Intune.
|
||||
description: Install Microsoft Defender for Endpoint for Mac, using Microsoft Intune.
|
||||
keywords: microsoft, defender, atp, mac, installation, deploy, uninstallation, intune, jamf, macos, catalina, mojave, high sierra
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
@ -42,7 +42,7 @@ This topic describes how to deploy Microsoft Defender for Endpoint for Mac throu
|
||||
|
||||
## Prerequisites and system requirements
|
||||
|
||||
Before you get started, see [the main MIcrosoft Defender for EndpointP for Mac page](microsoft-defender-atp-mac.md) for a description of prerequisites and system requirements for the current software version.
|
||||
Before you get started, see [the main Microsoft Defender for Endpoint for Mac page](microsoft-defender-atp-mac.md) for a description of prerequisites and system requirements for the current software version.
|
||||
|
||||
## Overview
|
||||
|
||||
|
@ -91,6 +91,12 @@ The [DisableAntiSpyware](https://docs.microsoft.com/windows-hardware/customize/d
|
||||
|
||||
`Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender` <br/>
|
||||
|
||||
> [!NOTE]
|
||||
> When using the DISM command within a task sequence running PS, the following path to cmd.exe is required.
|
||||
> Example:<br/>
|
||||
> `c:\windows\sysnative\cmd.exe /c Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender-Features`<br/>
|
||||
> `c:\windows\sysnative\cmd.exe /c Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender`<br/>
|
||||
|
||||
3. To verify Microsoft Defender Antivirus is running, use the following PowerShell cmdlet: <br/>
|
||||
|
||||
`Get-Service -Name windefend`
|
||||
|
@ -139,7 +139,7 @@ You can prevent further propagation of an attack in your organization by banning
|
||||
|
||||
>[!IMPORTANT]
|
||||
>
|
||||
>- This feature is available if your organization uses Microsoft Defender Antivirus and Cloud–based protection is enabled. For more information, see [Manage cloud–based 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.
|
||||
|
@ -87,6 +87,12 @@ The [DisableAntiSpyware](https://docs.microsoft.com/windows-hardware/customize/d
|
||||
|
||||
`Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender` <br/>
|
||||
|
||||
> [!NOTE]
|
||||
> When using the DISM command within a task sequence running PS, the following path to cmd.exe is required.
|
||||
> Example:<br/>
|
||||
> `c:\windows\sysnative\cmd.exe /c Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender-Features`<br/>
|
||||
> `c:\windows\sysnative\cmd.exe /c Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender`<br/>
|
||||
|
||||
3. To verify Microsoft Defender Antivirus is running, use the following PowerShell cmdlet: <br/>
|
||||
|
||||
`Get-Service -Name windefend`
|
||||
|
@ -18,7 +18,7 @@ ms.collection:
|
||||
- M365-security-compliance
|
||||
- m365solution-symantecmigrate
|
||||
ms.topic: article
|
||||
ms.date: 09/24/2020
|
||||
ms.date: 11/30/2020
|
||||
ms.custom: migrationguides
|
||||
ms.reviewer: depicker, yongrhee, chriggs
|
||||
---
|
||||
@ -68,6 +68,12 @@ Now that you're moving from Symantec to Microsoft Defender for Endpoint, you'll
|
||||
`Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender-Features` <br/>
|
||||
`Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender` <br/>
|
||||
|
||||
> [!NOTE]
|
||||
> When using the DISM command within a task sequence running PS, the following path to cmd.exe is required.
|
||||
> Example:<br/>
|
||||
> `c:\windows\sysnative\cmd.exe /c Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender-Features`<br/>
|
||||
> `c:\windows\sysnative\cmd.exe /c Dism /online /Get-FeatureInfo /FeatureName:Windows-Defender`<br/>
|
||||
|
||||
3. To verify Microsoft Defender Antivirus is running, use the following PowerShell cmdlet: <br/>
|
||||
`Get-Service -Name windefend`
|
||||
|
||||
|
@ -67,12 +67,12 @@ When submitting Microsoft Defender SmartScreen products, make sure to select **M
|
||||
## Viewing Microsoft Defender SmartScreen anti-phishing events
|
||||
|
||||
> [!NOTE]
|
||||
> No Smartscreen events will be logged when using Microsoft Edge version 77 or later.
|
||||
> No SmartScreen events will be logged when using Microsoft Edge version 77 or later.
|
||||
|
||||
When Microsoft Defender SmartScreen warns or blocks a user from a website, it's logged as [Event 1035 - Anti-Phishing](https://technet.microsoft.com/scriptcenter/dd565657(v=msdn.10).aspx).
|
||||
When Microsoft Defender SmartScreen warns or blocks a user from a website, it's logged as [Event 1035 - Anti-Phishing](https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/compatibility/dd565657(v=vs.85)).
|
||||
|
||||
## Viewing Windows event logs for Microsoft Defender SmartScreen
|
||||
Microsoft Defender SmartScreen events appear in the Microsoft-Windows-SmartScreen/Debug login Event Viewer.
|
||||
Microsoft Defender SmartScreen events appear in the Microsoft-Windows-SmartScreen/Debug log, in the Event Viewer.
|
||||
|
||||
Windows event log for SmartScreen is disabled by default, users can use Event Viewer UI to enable the log or use the command line to enable it:
|
||||
|
||||
|
@ -30,7 +30,7 @@ The **Passwords must meet complexity requirements** policy setting determines wh
|
||||
1. Passwords may not contain the user's samAccountName (Account Name) value or entire displayName (Full Name value). Both checks are not case sensitive.
|
||||
|
||||
The samAccountName is checked in its entirety only to determine whether it is part of the password. If the samAccountName is fewer than three characters long, this check is skipped.
|
||||
The displayName is parsed for delimiters: commas, periods, dashes or hyphens, underscores, spaces, pound signs, and tabs. If any of these delimiters are found, the displayName is split and all parsed sections (tokens) are confirmed not to be included in the password. Tokens that are shorter than three characters are ignored, and substrings of the tokens are not checked. For example, the name "Erin M. Hagens" is split into three tokens: "Erin", "M", and "Havens". Because the second token is only one character long, it is ignored. Therefore, this user could not have a password that included either "grin" or "hagens" as a substring anywhere in the password.
|
||||
The displayName is parsed for delimiters: commas, periods, dashes or hyphens, underscores, spaces, pound signs, and tabs. If any of these delimiters are found, the displayName is split and all parsed sections (tokens) are confirmed not to be included in the password. Tokens that are shorter than three characters are ignored, and substrings of the tokens are not checked. For example, the name "Erin M. Hagens" is split into three tokens: "Erin", "M", and "Havens". Because the second token is only one character long, it is ignored. Therefore, this user could not have a password that included either "erin" or "havens" as a substring anywhere in the password.
|
||||
|
||||
2. The password contains characters from three of the following categories:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user