Skip to content

Commit c31dbf6

Browse files
authored
Merge pull request #97356 from MicrosoftDocs/master
11/27 PM Publish
2 parents b5d59c6 + bd840c7 commit c31dbf6

File tree

110 files changed

+791
-433
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

110 files changed

+791
-433
lines changed

articles/active-directory/devices/concept-azure-managed-workstation.md

Lines changed: 23 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: devices
88
ms.topic: conceptual
9-
ms.date: 05/28/2019
9+
ms.date: 11/18/2019
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -17,12 +17,11 @@ ms.reviewer: frasim
1717

1818
ms.collection: M365-identity-device-management
1919
---
20-
2120
# Understand secure, Azure-managed workstations
2221

2322
Secured, isolated workstations are critically important for the security of sensitive roles like administrators, developers, and critical service operators. If client workstation security is compromised, many security controls and assurances can fail or be ineffective.
2423

25-
This document explains what you need for building a secure workstation, often known as a privileged access workstation (PAW). The article also contains detailed instructions to set up initial security controls. This guidance describes how cloud-based technology can manage the service. It relies on security capabilities that were introduced in Windows 10RS5, Microsoft Defender Advanced Threat Protection (ATP), Azure Active Directory, and Intune.
24+
This document explains what you need for building a secure workstation, often known as a privileged access workstation (PAW). The article also contains detailed instructions to set up initial security controls. This guidance describes how cloud-based technology can manage the service. It relies on security capabilities that were introduced in Windows 10RS5, Microsoft Defender Advanced Threat Protection (ATP), Azure Active Directory, and Microsoft Intune.
2625

2726
> [!NOTE]
2827
> This article explains the concept of a secure workstation and its importance. If you are already familiar with the concept and would like to skip to deployment, visit [Deploy a Secure Workstation](howto-azure-managed-workstation.md).
@@ -52,6 +51,7 @@ This document describes a solution that can help protect your computing devices
5251
* Windows 10 (current version) for device health attestation and user experience
5352
* Defender ATP for cloud-managed endpoint protection, detection, and response
5453
* Azure AD PIM for managing authorization and just-in-time (JIT) privileged access to resources
54+
* Log Analytics, and Sentinel for monitoring and alerting
5555

5656
## Who benefits from a secure workstation?
5757

@@ -63,7 +63,7 @@ All users and operators benefit when using a secure workstation. An attacker who
6363
* Highly sensitive workstation, such as a SWIFT payment terminal
6464
* Workstation handling trade secrets
6565

66-
To reduce risk, you should implement elevated security controls for privileged workstations that make use of these accounts. For more information, see the [Azure Active Directory feature deployment guide](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-deployment-checklist-p2), [Office 365 roadmap](https://aka.ms/o365secroadmap), and [Securing Privileged Access roadmap](https://aka.ms/sparoadmap)).
66+
To reduce risk, you should implement elevated security controls for privileged workstations that make use of these accounts. For more information, see the [Azure Active Directory feature deployment guide](../fundamentals/active-directory-deployment-checklist-p2.md), [Office 365 roadmap](https://aka.ms/o365secroadmap), and [Securing Privileged Access roadmap](https://aka.ms/sparoadmap)).
6767

6868
## Why use dedicated workstations?
6969

@@ -78,16 +78,29 @@ Containment strategies tighten security by increasing the number and type of con
7878

7979
## Supply chain management
8080

81-
Essential to a secured workstation is a supply chain solution where you use a trusted workstation called the 'root of trust'. For this solution, the root of trust uses [Microsoft Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot) technology. To secure a workstation, Autopilot lets you leverage Microsoft OEM-optimized Windows 10 devices. These devices come in a known good state from the manufacturer. Instead of reimaging a potentially insecure device, Autopilot can transform a Windows device into a “business-ready” state. It applies settings and policies, installs apps, and even changes the edition of Windows 10. For example, Autopilot might change a device's Windows installation from Windows 10 Pro to Windows 10 Enterprise so that it can use advanced features.
81+
Essential to a secured workstation is a supply chain solution where you use a trusted workstation called the 'root of trust'. Technology that must be considered in the selection of the root of trust hardware should include the following technologies included in modern laptops:
82+
83+
* [Trusted Platform Module (TPM) 2.0](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-tpm)
84+
* [BitLocker Drive Encryption](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-bitlocker)
85+
* [UEFI Secure Boot](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-secure-boot)
86+
* [Drivers and Firmware Distributed through Windows Update](https://docs.microsoft.com/windows-hardware/drivers/dashboard/understanding-windows-update-automatic-and-optional-rules-for-driver-distribution)
87+
* [Virtualization and HVCI Enabled](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-vbs)
88+
* [Drivers and Apps HVCI-Ready](https://docs.microsoft.com/windows-hardware/test/hlk/testref/driver-compatibility-with-device-guard)
89+
* [Windows Hello](https://docs.microsoft.com/windows-hardware/design/device-experiences/windows-hello-biometric-requirements)
90+
* [DMA I/O Protection](https://docs.microsoft.com/windows/security/information-protection/kernel-dma-protection-for-thunderbolt)
91+
* [System Guard](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-system-guard/system-guard-how-hardware-based-root-of-trust-helps-protect-windows)
92+
* [Modern Standby](https://docs.microsoft.com/windows-hardware/design/device-experiences/modern-standby)
93+
94+
For this solution, root of trust will be deployed using [Microsoft Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot) technology with hardware that meets the modern technical requirements. To secure a workstation, Autopilot lets you leverage Microsoft OEM-optimized Windows 10 devices. These devices come in a known good state from the manufacturer. Instead of reimaging a potentially insecure device, Autopilot can transform a Windows device into a “business-ready” state. It applies settings and policies, installs apps, and even changes the edition of Windows 10. For example, Autopilot might change a device's Windows installation from Windows 10 Pro to Windows 10 Enterprise so that it can use advanced features.
8295

8396
![Secure workstation Levels](./media/concept-azure-managed-workstation/supplychain.png)
8497

8598
## Device roles and profiles
8699

87-
This guidance references several security profiles and roles that can help you create more secure solutions for users, developers, and IT personnel. These profiles balance usability and risks for common users that can benefit from an enhanced or secure workstation. The settings configurations provided here are based on industry accepted standards. This guidance shows how to harden Windows 10 and reduce the risks associated with device or user compromise. It does so by using policy and technology to help manage security features and risks.
100+
This guidance references several security profiles and roles that can help you create more secure solutions for users, developers, and IT personnel. These profiles balance usability and risks for common users that can benefit from an enhanced or secure workstation. The settings configurations provided here are based on industry accepted standards. This guidance shows how to harden Windows 10 and reduce the risks associated with device or user compromise. To take advantage of the modern hardware technology and root of trust device, we will use [Device Health Attestation](https://techcommunity.microsoft.com/t5/Intune-Customer-Success/Support-Tip-Using-Device-Health-Attestation-Settings-as-Part-of/ba-p/282643), which is enabled starting at the **High Security** profile. This capability is present to ensure the attackers cannot be persistent during the early boot of a device. It does so by using policy and technology to help manage security features and risks.
88101
![Secure workstation Levels](./media/concept-azure-managed-workstation/seccon-levels.png)
89102

90-
* **Low Security** – A managed, standard workstation provides a good starting point for most home and small business use. These devices are registered in Azure AD and managed with Intune. This profile permits users to run any applications and browse any website. An anti-malware solution like [Microsoft Defender](https://www.microsoft.com/windows/comprehensive-security) should be enabled.
103+
* **Basic Security** – A managed, standard workstation provides a good starting point for most home and small business use. These devices are registered in Azure AD and managed with Intune. This profile permits users to run any applications and browse any website. An anti-malware solution like [Microsoft Defender](https://www.microsoft.com/windows/comprehensive-security) should be enabled.
91104

92105
* **Enhanced Security** – This entry-level, protected solution is good for home users, small business users, and general developers.
93106

@@ -99,16 +112,16 @@ This guidance references several security profiles and roles that can help you c
99112

100113
* **Specialized** – Attackers target developers and IT administrators because they can alter systems of interest to the attackers. The specialized workstation expands on the policies of the high security workstation by managing local applications and limiting websites. It also restricts high-risk productivity capabilities such as ActiveX, Java, browser plugins, and other Windows controls. You deploy this profile with the DeviceConfiguration_NCSC - Windows10 (1803) SecurityBaseline script.
101114

102-
* **Secured** – An attacker who compromises an administrative account can cause significant business damage by data theft, data alteration, or service disruption. In this hardened state, the workstation enables all the security controls and policies that restrict direct control of local application management. A secured workstation has no productivity tools so the device more difficult to compromise. It blocks the most common vector for phishing attacks: email and social media. The secured workstation can be deployed with the Secure Workstation - Windows10 (1809) SecurityBaseline script.
115+
* **Secured** – An attacker who compromises an administrative account can cause significant business damage by data theft, data alteration, or service disruption. In this hardened state, the workstation enables all the security controls and policies that restrict direct control of local application management. A secured workstation has no productivity tools so the device more difficult to compromise. It blocks the most common vector for phishing attacks: email and social media. The secured workstation can be deployed with the Secure Workstation - Windows10 (1809) SecurityBaseline script.
103116

104117
![Secured workstation](./media/concept-azure-managed-workstation/secure-workstation.png)
105118

106119
A secure workstation provides an administrator with a hardened workstation that has clear application control and application guard. The workstation uses credential guard, device guard, and exploit guard to protect the host from malicious behavior. All local disks are also encrypted with BitLocker.
107120

108121
* **Isolated** – This custom, offline scenario represents the extreme end of the spectrum. No installation scripts are provided for this case. You might need to manage a business-critical function that requires an unsupported or unpatched legacy operating system. For example, a high value production line or a life-support system. Because security is critical and cloud services are unavailable, you can manage and update these computers manually or with an isolated Active Directory forest architecture such as the Enhanced Security Admin Environment (ESAE). In these circumstances, consider removing all access except basic Intune and ATP health checks.
109122

110-
* [Intune network communications requirement](https://docs.microsoft.com/intune/network-bandwidth-use)
111-
* [ATP network communications requirement](https://docs.microsoft.com/azure-advanced-threat-protection/configure-proxy)
123+
* [Intune network communications requirement](https://docs.microsoft.com/intune/network-bandwidth-use)
124+
* [ATP network communications requirement](https://docs.microsoft.com/azure-advanced-threat-protection/configure-proxy)
112125

113126
## Next steps
114127

0 commit comments

Comments
 (0)