mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-25 11:47:23 +00:00
Merge branch 'master' into v-smandalika-bl-dply-winserv
This commit is contained in:
commit
000a38e004
@ -26,7 +26,7 @@ For details about Microsoft mobile device management protocols for Windows 10 s
|
||||
|
||||
|New or updated article|Description|
|
||||
|-----|-----|
|
||||
| [Policy CSP](policy-configuration-service-provider.md) | Added the following new policies in Windows 10, version 20H2:<br>- [LocalUsersAndGroups/Configure](policy-csp-localusersandgroups.md#localusersandgroups-configure)<br>- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays)<br>- [MixedReality/BrightnessButtonDisabled](policy-csp-mixedreality.md#mixedreality-brightnessbuttondisabled)<br>- [MixedReality/FallbackDiagnostics](policy-csp-mixedreality.md#mixedreality-fallbackdiagnostics)<br>- [MixedReality/MicrophoneDisabled](policy-csp-mixedreality.md#mixedreality-microphonedisabled)<br>- [MixedReality/VolumeButtonDisabled](policy-csp-mixedreality.md#mixedreality-volumebuttondisabled)<br>- [WindowsSandbox/AllowAudioInput](policy-csp-windowssandbox.md#windowssandbox-allowaudioinput)<br>- [WindowsSandbox/AllowClipboardRedirection](policy-csp-windowssandbox.md#windowssandbox-allowclipboardredirection)<br>- [WindowsSandbox/AllowNetworking](policy-csp-windowssandbox.md#windowssandbox-allownetworking)<br>- [WindowsSandbox/AllowPrinterRedirection](policy-csp-windowssandbox.md#windowssandbox-allowprinterredirection)<br>- [WindowsSandbox/AllowVGPU](policy-csp-windowssandbox.md#windowssandbox-allowvgpu)<br>- [WindowsSandbox/AllowVideoInput](policy-csp-windowssandbox.md#windowssandbox-allowvideoinput) |
|
||||
| [Policy CSP](policy-configuration-service-provider.md) | Added the following new policies in Windows 10, version 20H2:<br>- [LocalUsersAndGroups/Configure](policy-csp-localusersandgroups.md#localusersandgroups-configure)<br>- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#mixedreality-aadgroupmembershipcachevalidityindays)<br>- [MixedReality/BrightnessButtonDisabled](policy-csp-mixedreality.md#mixedreality-brightnessbuttondisabled)<br>- [MixedReality/FallbackDiagnostics](policy-csp-mixedreality.md#mixedreality-fallbackdiagnostics)<br>- [MixedReality/MicrophoneDisabled](policy-csp-mixedreality.md#mixedreality-microphonedisabled)<br>- [MixedReality/VolumeButtonDisabled](policy-csp-mixedreality.md#mixedreality-volumebuttondisabled) |
|
||||
| [WindowsDefenderApplicationGuard CSP](windowsdefenderapplicationguard-csp.md) | Updated the description of the following node:<br>- Settings/AllowWindowsDefenderApplicationGuard |
|
||||
|
||||
## What’s new in MDM for Windows 10, version 2004
|
||||
|
@ -48,6 +48,8 @@ ms.date: 10/14/2020
|
||||
<!--Policy-->
|
||||
<a href="" id="windowssandbox-allowaudioinput"></a>**WindowsSandbox/AllowAudioInput**
|
||||
|
||||
Available in the latest Windows 10 insider preview build.
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
@ -60,7 +62,7 @@ ms.date: 10/14/2020
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Business</td>
|
||||
@ -68,11 +70,11 @@ ms.date: 10/14/2020
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -134,6 +136,8 @@ The following are the supported values:
|
||||
<!--Policy-->
|
||||
<a href="" id="windowssandbox-allowclipboardredirection"></a>**WindowsSandbox/AllowClipboardRedirection**
|
||||
|
||||
Available in the latest Windows 10 insider preview build.
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
@ -146,7 +150,7 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Business</td>
|
||||
@ -154,11 +158,11 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -217,6 +221,8 @@ The following are the supported values:
|
||||
<!--Policy-->
|
||||
<a href="" id="windowssandbox-allownetworking"></a>**WindowsSandbox/AllowNetworking**
|
||||
|
||||
Available in the latest Windows 10 insider preview build.
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
@ -229,7 +235,7 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Business</td>
|
||||
@ -237,11 +243,11 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -298,6 +304,8 @@ The following are the supported values:
|
||||
<!--Policy-->
|
||||
<a href="" id="windowssandbox-allowprinterredirection"></a>**WindowsSandbox/AllowPrinterRedirection**
|
||||
|
||||
Available in the latest Windows 10 insider preview build.
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
@ -310,7 +318,7 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Business</td>
|
||||
@ -318,11 +326,11 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -380,6 +388,8 @@ The following are the supported values:
|
||||
<!--Policy-->
|
||||
<a href="" id="windowssandbox-allowvgpu"></a>**WindowsSandbox/AllowVGPU**
|
||||
|
||||
Available in the latest Windows 10 insider preview build.
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
@ -392,7 +402,7 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Business</td>
|
||||
@ -400,11 +410,11 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -465,6 +475,8 @@ The following are the supported values:
|
||||
<!--Policy-->
|
||||
<a href="" id="windowssandbox-allowvideoinput"></a>**WindowsSandbox/AllowVideoInput**
|
||||
|
||||
Available in the latest Windows 10 insider preview build.
|
||||
|
||||
<!--SupportedSKUs-->
|
||||
<table>
|
||||
<tr>
|
||||
@ -477,7 +489,7 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Pro</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Business</td>
|
||||
@ -485,11 +497,11 @@ The following are the supported values:
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Enterprise</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Education</td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /><sup>9</sup></td>
|
||||
<td><img src="images/checkmark.png" alt="check mark" /></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -546,16 +558,4 @@ The following are the supported values:
|
||||
|
||||
<hr/>
|
||||
|
||||
Footnotes:
|
||||
|
||||
- 1 - Available in Windows 10, version 1607.
|
||||
- 2 - Available in Windows 10, version 1703.
|
||||
- 3 - Available in Windows 10, version 1709.
|
||||
- 4 - Available in Windows 10, version 1803.
|
||||
- 5 - Available in Windows 10, version 1809.
|
||||
- 6 - Available in Windows 10, version 1903.
|
||||
- 7 - Available in Windows 10, version 1909.
|
||||
- 8 - Available in Windows 10, version 2004.
|
||||
- 9 - Available in Windows 10, version 20H2.
|
||||
|
||||
<!--/Policies-->
|
||||
|
@ -67,6 +67,7 @@
|
||||
##### [Software inventory](microsoft-defender-atp/tvm-software-inventory.md)
|
||||
##### [Vulnerabilities in my organization](microsoft-defender-atp/tvm-weaknesses.md)
|
||||
##### [Event timeline](microsoft-defender-atp/threat-and-vuln-mgt-event-timeline.md)
|
||||
##### [Vulnerable devices report](microsoft-defender-atp/tvm-vulnerable-devices-report.md)
|
||||
##### [Hunt for exposed devices](microsoft-defender-atp/tvm-hunt-exposed-devices.md)
|
||||
|
||||
|
||||
@ -274,6 +275,7 @@
|
||||
|
||||
#### [Configure]()
|
||||
##### [Configure iOS features](microsoft-defender-atp/ios-configure-features.md)
|
||||
#### [Privacy](microsoft-defender-atp/microsoft-defender-atp-ios-privacy-information.md)
|
||||
|
||||
|
||||
### [Microsoft Defender Advanced Threat Protection for Linux]()
|
||||
@ -456,6 +458,7 @@
|
||||
##### [Onboard devices using Mobile Device Management tools](microsoft-defender-atp/configure-endpoints-mdm.md)
|
||||
##### [Onboard devices using a local script](microsoft-defender-atp/configure-endpoints-script.md)
|
||||
##### [Onboard non-persistent virtual desktop infrastructure (VDI) devices](microsoft-defender-atp/configure-endpoints-vdi.md)
|
||||
##### [Onboard Windows 10 multi-session devices in Windows Virtual Desktop](microsoft-defender-atp/Onboard-Windows-10-multi-session-device.md)
|
||||
|
||||
#### [Onboard Windows servers](microsoft-defender-atp/configure-server-endpoints.md)
|
||||
#### [Onboard non-Windows devices](microsoft-defender-atp/configure-endpoints-non-windows.md)
|
||||
@ -1340,3 +1343,5 @@
|
||||
### [Windows 10 Mobile security guide](windows-10-mobile-security-guide.md)
|
||||
|
||||
## [Change history for Threat protection](change-history-for-threat-protection.md)
|
||||
|
||||
|
||||
|
@ -43,8 +43,8 @@ We've seen macro malware download threats from the following families:
|
||||
|
||||
* Delete any emails from unknown people or with suspicious content. Spam emails are the main way macro malware spreads.
|
||||
|
||||
* Enterprises can prevent macro malware from running executable content using [ASR rules](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction#enable-and-audit-attack-surface-reduction-rules)
|
||||
* Enterprises can prevent macro malware from running executable content using [ASR rules](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/attack-surface-reduction)
|
||||
|
||||
For more tips on protecting yourself from suspicious emails, see [phishing](phishing.md).
|
||||
For more tips on protecting yourself from suspicious emails, see [phishing](phishing.md).
|
||||
|
||||
For more general tips, see [prevent malware infection](prevent-malware-infection.md).
|
||||
For more general tips, see [prevent malware infection](prevent-malware-infection.md).
|
||||
|
@ -0,0 +1,131 @@
|
||||
---
|
||||
title: "Onboard Windows 10 multi-session devices in Windows Virtual Desktop"
|
||||
description: "Read more in this article about Onboarding Windows 10 multi-session devices in Windows Virtual Desktop"
|
||||
keywords: Windows Virtual Desktop, WVD, microsoft defender, endpoint, onboard
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.localizationpriority: medium
|
||||
audience: ITPro
|
||||
ms.topic: article
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.custom: nextgen
|
||||
ms.date: 09/10/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
---
|
||||
|
||||
# Onboard Windows 10 multi-session devices in Windows Virtual Desktop
|
||||
6 minutes to read
|
||||
|
||||
Applies to:
|
||||
- Windows 10 multi-session running on Windows Virtual Desktop (WVD)
|
||||
> [!IMPORTANT]
|
||||
> Welcome to Microsoft Defender for Endpoint, the new name for Microsoft Defender Advanced Threat Protection. Read more about this and other updates here. We'll be updating names in products and in the docs in the near future.
|
||||
|
||||
> [!WARNING]
|
||||
> Microsoft Defender for Endpoint support for Windows Virtual Desktop multi-session scenarios is currently in Preview and limited up to 25 concurrent sessions per host/VM. However, single session scenarios on Windows Virtual Desktop are fully supported.
|
||||
|
||||
Microsoft Defender for Endpoint supports monitoring both VDI as well as Windows Virtual Desktop sessions. Depending on your organization's needs, you might need to implement VDI or Windows Virtual Desktop sessions to help your employees access corporate data and apps from an unmanaged device, remote location, or similar scenario. With Microsoft Defender for Endpoint, you can monitor these virtual machines for anomalous activity.
|
||||
|
||||
## Before you begin
|
||||
Familiarize yourself with the [considerations for non-persistent VDI](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi#onboard-non-persistent-virtual-desktop-infrastructure-vdi-devices-1). While [Windows Virtual Desktop](https://docs.microsoft.com/azure/virtual-desktop/overview) does not provide non-persistence options, it does provide ways to use a golden Windows image that can be used to provision new hosts and redeploy machines. This increases volatility in the environment and thus impacts what entries are created and maintained in the Microsoft Defender for Endpoint portal, potentially reducing visibility for your security analysts.
|
||||
|
||||
> [!NOTE]
|
||||
> Depending on your choice of onboarding method, devices can appear in Microsoft Defender for Endpoint portal as either:
|
||||
> - Single entry for each virtual desktop
|
||||
> - Multiple entries for each virtual desktop
|
||||
|
||||
Microsoft recommends onboarding Windows Virtual Desktop as a single entry per virtual desktop. This ensures that the investigation experience in the Microsoft Defender Endpoint portal is in the context of one device based on the machine name. Organizations that frequently delete and re-deploy WVD hosts should strongly consider using this method as it prevents multiple objects for the same machine from being created in the Microsoft Defender for Endpoint portal. This can lead to confusion when investigating incidents. For test or non-volatile environments, you may opt to choose differently.
|
||||
|
||||
Microsoft recommends adding the Microsoft Defender for Endpoint onboarding script to the WVD golden image. This way, you can be sure that this onboarding script runs immediately at first boot. It is executed as a startup script at first boot on all the WVD machines that are provisioned from the WVD golden image. However, if you are using one of the gallery images without modification, place the script in a shared location and call it from either local or domain group policy.
|
||||
|
||||
> [!NOTE]
|
||||
> The placement and configuration of the VDI onboarding startup script on the WVD golden image configures it as a startup script that runs when the WVD starts. It is NOT recommended to onboard the actual WVD golden image. Another consideration is the method used to run the script. It should run as early in the startup/provisioning process as possible to reduce the time between the machine being available to receive sessions and the device onboarding to the service. Below scenarios 1 & 2 take this into account.
|
||||
|
||||
### Scenarios
|
||||
There are several ways to onboard a WVD host machine:
|
||||
|
||||
- Run the script in the golden image (or from a shared location) during startup.
|
||||
- Use a management tool to run the script.
|
||||
|
||||
#### *Scenario 1: Using local group policy*
|
||||
This scenario requires placing the script in a golden image and uses local group policy to run early in the boot process.
|
||||
|
||||
Use the instructions in [Onboard non-persistent virtual desktop infrastructure VDI devices](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-vdi#onboard-non-persistent-virtual-desktop-infrastructure-vdi-devices-1).
|
||||
|
||||
Follow the instructions for a single entry for each device.
|
||||
|
||||
#### *Scenario 2: Using domain group policy*
|
||||
This scenario uses a centrally located script and runs it using a domain-based group policy. You can also place the script in the golden image and run it in the same way.
|
||||
|
||||
**Download the WindowsDefenderATPOnboardingPackage.zip file from the Windows Defender Security Center**
|
||||
1. Open the VDI configuration package .zip file (WindowsDefenderATPOnboardingPackage.zip)
|
||||
- In the Microsoft Defender Security Center navigation pane, select **Settings** > **Onboarding**.
|
||||
- Select Windows 10 as the operating system.
|
||||
- In the **Deployment method** field, select VDI onboarding scripts for non-persistent endpoints.
|
||||
- Click **Download package** and save the .zip file.
|
||||
2. Extract the contents of the .zip file to a shared, read-only location that can be accessed by the device. You should have a folder called **OptionalParamsPolicy** and the files **WindowsDefenderATPOnboardingScript.cmd** and **Onboard-NonPersistentMachine.ps1**.
|
||||
|
||||
**Use Group Policy management console to run the script when the virtual machine starts**
|
||||
1. Open the Group Policy Management Console (GPMC), right-click the Group Policy Object (GPO) you want to configure and click **Edit**.
|
||||
1. In the Group Policy Management Editor, go to **Computer configuration** \> **Preferences** \> **Control panel settings**.
|
||||
1. Right-click **Scheduled tasks**, click **New**, and then click **Immediate Task** (At least Windows 7).
|
||||
1. In the Task window that opens, go to the **General** tab. Under **Security options** click **Change User or Group** and type SYSTEM. Click **Check Names** and then click OK. NT AUTHORITY\SYSTEM appears as the user account the task will run as.
|
||||
1. Select **Run whether user is logged on or not** and check the **Run with highest privileges** check box.
|
||||
1. Go to the **Actions** tab and click **New**. Ensure that **Start a program** is selected in the Action field.
|
||||
Enter the following:
|
||||
|
||||
> Action = "Start a program" <br>
|
||||
> Program/Script = C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe <br>
|
||||
> Add Arguments (optional) = -ExecutionPolicy Bypass -command "& \\Path\To\Onboard-NonPersistentMachine.ps1"
|
||||
|
||||
Click **OK** and close any open GPMC windows.
|
||||
|
||||
#### *Scenario 3: Onboarding using management tools*
|
||||
|
||||
If you plan to manage your machines using a management tool, you can onboard devices with Microsoft Endpoint Configuration Manager.
|
||||
|
||||
For more information, see: [Onboard Windows 10 devices using Configuration Manager](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-sccm)
|
||||
|
||||
> [!WARNING]
|
||||
> If you plan to use [Attack Surface reduction Rules](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/attack-surface-reduction), please note that rule “[Block process creations originating from PSExec and WMI commands](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/attack-surface-reduction#block-process-creations-originating-from-psexec-and-wmi-commands)" should not be used as it is incompatible with management through Microsoft Endpoint Configuration Manager because this rule blocks WMI commands the Configuration Manager client uses to function correctly.
|
||||
|
||||
> [!TIP]
|
||||
> After onboarding the device, you can choose to run a detection test to verify that the device is properly onboarded to the service. For more information, see [Run a detection test on a newly onboarded Microsoft Defender for Endpoint device](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/run-detection-test).
|
||||
|
||||
#### Tagging your machines when building your golden image
|
||||
|
||||
As part of your onboarding, you may want to consider setting a machine tag to be able to differentiate WVD machines more easily in the Microsoft Security Center. For more information, see
|
||||
[Add device tags by setting a registry key value](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/machine-tags#add-device-tags-by-setting-a-registry-key-value).
|
||||
|
||||
#### Other recommended configuration settings
|
||||
|
||||
When building your golden image, you may want to configure initial protection settings as well. For more information, see [Other recommended configuration settings](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/configure-endpoints-gp#other-recommended-configuration-settings).
|
||||
|
||||
In addition, if you are using FSlogix user profiles, we recommend you exclude the following files from always-on protection:
|
||||
|
||||
**Exclude Files:**
|
||||
|
||||
> %ProgramFiles%\FSLogix\Apps\frxdrv.sys <br>
|
||||
> %ProgramFiles%\FSLogix\Apps\frxdrvvt.sys <br>
|
||||
> %ProgramFiles%\FSLogix\Apps\frxccd.sys <br>
|
||||
> %TEMP%\*.VHD <br>
|
||||
> %TEMP%\*.VHDX <br>
|
||||
> %Windir%\TEMP\*.VHD <br>
|
||||
> %Windir%\TEMP\*.VHDX <br>
|
||||
> \\storageaccount.file.core.windows.net\share\*\*.VHD <br>
|
||||
> \\storageaccount.file.core.windows.net\share\*\*.VHDX <br>
|
||||
|
||||
**Exclude Processes:**
|
||||
|
||||
> %ProgramFiles%\FSLogix\Apps\frxccd.exe <br>
|
||||
> %ProgramFiles%\FSLogix\Apps\frxccds.exe <br>
|
||||
> %ProgramFiles%\FSLogix\Apps\frxsvc.exe <br>
|
||||
|
||||
#### Licensing requirements
|
||||
|
||||
Windows 10 Multi-session is a client OS. Licensing requirements for Microsoft Defender for endpoint can be found at: [Licensing requirements](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/minimum-requirements#licensing-requirements).
|
Binary file not shown.
After Width: | Height: | Size: 49 KiB |
Binary file not shown.
After Width: | Height: | Size: 42 KiB |
Binary file not shown.
After Width: | Height: | Size: 62 KiB |
Binary file not shown.
After Width: | Height: | Size: 40 KiB |
Binary file not shown.
After Width: | Height: | Size: 46 KiB |
@ -27,8 +27,6 @@ ms.topic: article
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
To benefit from Microsoft Defender Advanced Threat Protection (ATP) cloud app discovery signals, turn on Microsoft Cloud App Security integration.
|
||||
|
||||
>[!NOTE]
|
||||
|
@ -0,0 +1,97 @@
|
||||
---
|
||||
title: Microsoft Defender ATP for iOS - Privacy information
|
||||
ms.reviewer:
|
||||
description: Describes privacy information for Microsoft Defender ATP for iOS
|
||||
keywords: microsoft, defender, atp, ios, policy, overview
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: macapara
|
||||
author: mjcaparas
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection:
|
||||
- m365-security-compliance
|
||||
- m365initiative-defender-endpoint
|
||||
ms.topic: conceptual
|
||||
---
|
||||
|
||||
# Privacy information - Microsoft Defender ATP for iOS
|
||||
|
||||
>[!NOTE]
|
||||
> Microsoft Defender ATP for iOS uses a VPN to provide the Web Protection feature. This is not a regular VPN and is a local or self-looping VPN that does not take traffic outside the device. Microsoft or your organization, does not see your browsing activity.
|
||||
|
||||
Microsoft Defender ATP for iOS collects information from your configured iOS devices and stores it in the same tenant where you have Microsoft Defender ATP. The information is collected to help keep Microsoft Defender ATP for iOS secure, up-to-date, performing as expected, and to support the service.
|
||||
|
||||
## Required data
|
||||
|
||||
Required data consists of data that is necessary to make Microsoft Defender ATP for iOS work as expected. This data is essential to the operation of the service and can include data related to the end user, organization, device, and apps.
|
||||
|
||||
Here is a list of the types of data being collected:
|
||||
|
||||
### Web page or Network information
|
||||
|
||||
- Connection information only when a malicious connection or web page is detected.
|
||||
|
||||
- Protocol type (such as HTTP, HTTPS, etc.) only when a malicious connection or web page is detected.
|
||||
|
||||
### Device and account information
|
||||
|
||||
- Device information such as date & time, iOS version, CPU info, and Device identifier, where Device identifier is one of the following:
|
||||
|
||||
- Wi-Fi adapter MAC address
|
||||
|
||||
- Randomly generated globally unique identifier (GUID)
|
||||
|
||||
- Tenant, Device and User information
|
||||
|
||||
- Azure Active Directory (AD) Device ID and Azure User ID - Uniquely identifies the device, User respectively at Azure Active directory.
|
||||
|
||||
- Azure tenant ID - GUID that identifies your organization within Azure Active Directory.
|
||||
|
||||
- Microsoft Defender ATP org ID - Unique identifier associated with the enterprise that the device belongs to. Allows Microsoft to identify whether issues are impacting a select set of enterprises and how many enterprises are impacted.
|
||||
|
||||
- User Principal Name – Email ID of the user.
|
||||
|
||||
### Product and service usage data
|
||||
|
||||
The following information is collected only for Microsoft Defender ATP app installed on the device.
|
||||
|
||||
- App package info, including name, version, and app upgrade status.
|
||||
|
||||
- Actions performed in the app.
|
||||
|
||||
- Crash report logs generated by iOS.
|
||||
|
||||
- Memory usage data.
|
||||
|
||||
## Optional Data
|
||||
|
||||
Optional data includes diagnostic data and feedback data from the client. Optional diagnostic data is additional data that helps us make product improvements and provides enhanced information to help us detect, diagnose, and fix issues. This data is only for diagnostic purposes and is not required for the service itself.
|
||||
|
||||
Optional diagnostic data includes:
|
||||
|
||||
- App, CPU, and network usage for Microsoft Defender ATP.
|
||||
|
||||
- Features configured by the admin.
|
||||
|
||||
- Basic information about the browsers on the device.
|
||||
|
||||
Feedback Data is collected through in-app feedback provided by the user.
|
||||
|
||||
- The user’s email address, if they choose to provide it.
|
||||
|
||||
- Feedback type (smile, frown, idea) and any feedback comments submitted by the user.
|
||||
|
||||
For more information, see [More on Privacy](https://aka.ms/mdatpiosprivacystatement).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -29,8 +29,6 @@ ms.topic: conceptual
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-portaloverview-abovefoldlink)
|
||||
|
||||
[!include[Prerelease information](../../includes/prerelease.md)]
|
||||
|
||||
Cybersecurity weaknesses identified in your organization are mapped to actionable security recommendations and prioritized by their impact. Prioritized recommendations help shorten the time to mitigate or remediate vulnerabilities and drive compliance.
|
||||
|
||||
Each security recommendation includes actionable remediation steps. To help with task management, the recommendation can also be sent using Microsoft Intune and Microsoft Endpoint Configuration Manager. When the threat landscape changes, the recommendation also changes as it continuously collects information from your environment.
|
||||
|
@ -22,7 +22,6 @@ ms.topic: article
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
|
@ -0,0 +1,84 @@
|
||||
---
|
||||
title: Vulnerable devices report - threat and vulnerability management
|
||||
description: A report showing vulnerable device trends and current statistics. The goal is for you to understand the breath and scope of your device exposure.
|
||||
keywords: mdatp-tvm vulnerable devices, mdatp, tvm, reduce threat & vulnerability exposure, reduce threat and vulnerability, monitor security configuration
|
||||
search.product: eADQiWindows 10XVcnh
|
||||
search.appverid: met150
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
ms.author: ellevin
|
||||
author: levinec
|
||||
ms.localizationpriority: medium
|
||||
manager: dansimp
|
||||
audience: ITPro
|
||||
ms.collection:
|
||||
- m365-security-compliance
|
||||
- m365initiative-defender-endpoint
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Vulnerable devices report - threat and vulnerability management
|
||||
|
||||
[!INCLUDE [Microsoft 365 Defender rebranding](../../includes/microsoft-defender.md)]
|
||||
|
||||
> [!IMPORTANT]
|
||||
> **Vulnerable devices report is currently in public preview**<br>
|
||||
> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
|
||||
> For more information, see [Microsoft Defender ATP preview features](preview.md).
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2146631)
|
||||
- [Threat and vulnerability management](next-gen-threat-and-vuln-mgt.md)
|
||||
|
||||
>Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/microsoft-365/windows/microsoft-defender-atp?ocid=docs-wdatp-portaloverview-abovefoldlink)
|
||||
|
||||
The report shows graphs and bar charts with vulnerable device trends and current statistics. The goal is for you to understand the breath and scope of your device exposure.
|
||||
|
||||
Access the report in the Microsoft Defender Security Center by going to **Reports > Vulnerable devices**
|
||||
|
||||
There are two columns:
|
||||
|
||||
- Trends (over time). Can show the past 30 days, 3 months, 6 months, or a custom date range.
|
||||
- Today (current information)
|
||||
|
||||
**Filter**: You can filter the data by vulnerability severity levels, exploit availability, vulnerability age, operating system platform, Windows 10 version, or device group.
|
||||
|
||||
**Drill down**: If there is an insight you want to explore further, select the relevant bar chart to view a filtered list of devices in the Device inventory page. From there, you can export the list.
|
||||
|
||||
## Severity level graphs
|
||||
|
||||
Each device is counted only once according to the most severe vulnerability found on that device.
|
||||
|
||||

|
||||
|
||||
## Exploit availability graphs
|
||||
|
||||
Each device is counted only once based on the highest level of known exploit.
|
||||
|
||||

|
||||
|
||||
## Vulnerability age graphs
|
||||
|
||||
Each device is counted only once under the oldest vulnerability publication date. Older vulnerabilities have a higher chance of being exploited.
|
||||
|
||||

|
||||
|
||||
## Vulnerable devices by operating system platform graphs
|
||||
|
||||
The number of devices on each operating system that are exposed due to software vulnerabilities.
|
||||
|
||||

|
||||
|
||||
## Vulnerable devices by Windows 10 version graphs
|
||||
|
||||
The number of devices on each Windows 10 version that are exposed due to vulnerable applications or OS.
|
||||
|
||||

|
||||
|
||||
## Related topics
|
||||
|
||||
- [Threat and vulnerability management overview](next-gen-threat-and-vuln-mgt.md)
|
||||
- [Security recommendations](tvm-security-recommendation.md)
|
@ -112,12 +112,12 @@ View related weaknesses information in the device page.
|
||||
1. Go to the Microsoft Defender Security Center navigation menu bar, then select the device icon. The **Devices list** page opens.
|
||||
2. In the **Devices list** page, select the device name that you want to investigate.
|
||||
|
||||

|
||||

|
||||
|
||||
3. The device page will open with details and response options for the device you want to investigate.
|
||||
4. Select **Discovered vulnerabilities**.
|
||||
|
||||

|
||||

|
||||
|
||||
5. Select the vulnerability that you want to investigate to open up a flyout panel with the CVE details, such as: vulnerability description, threat insights, and detection logic.
|
||||
|
||||
@ -143,4 +143,5 @@ Report a false positive when you see any vague, inaccurate, or incomplete inform
|
||||
- [Threat and vulnerability management overview](next-gen-threat-and-vuln-mgt.md)
|
||||
- [Security recommendations](tvm-security-recommendation.md)
|
||||
- [Software inventory](tvm-software-inventory.md)
|
||||
- [Dashboard insights](tvm-dashboard-insights.md)
|
||||
- [View and organize the Microsoft Defender ATP Devices list](machines-view-overview.md)
|
||||
|
Loading…
x
Reference in New Issue
Block a user