diff --git a/windows/security/TOC.yml b/windows/security/TOC.yml index 133027057d..c479c94205 100644 --- a/windows/security/TOC.yml +++ b/windows/security/TOC.yml @@ -149,6 +149,14 @@ href: information-protection/bitlocker/ts-bitlocker-tpm-issues.md - name: Decode Measured Boot logs to track PCR changes href: information-protection/bitlocker/ts-bitlocker-decode-measured-boot-logs.md + - name: Personal Data Encryption (PDE) + items: + - name: Personal Data Encryption (PDE) overview + href: information-protection/personal-data-encryption/overview-pde.md + - name: Personal Data Encryption (PDE) (FAQ) + href: information-protection/personal-data-encryption/faq-pde.yml + - name: Configure Personal Data Encryption (PDE) in Intune + href: information-protection/personal-data-encryption/configure-pde-in-intune.md - name: Configure S/MIME for Windows href: identity-protection/configure-s-mime.md - name: Network security diff --git a/windows/security/encryption-data-protection.md b/windows/security/encryption-data-protection.md index 782617bafe..48738d546a 100644 --- a/windows/security/encryption-data-protection.md +++ b/windows/security/encryption-data-protection.md @@ -2,17 +2,17 @@ title: Encryption and data protection in Windows description: Get an overview encryption and data protection in Windows 11 and Windows 10 search.appverid: MET150 -author: denisebmsft -ms.author: deniseb -manager: dansimp -ms.topic: conceptual -ms.date: 09/08/2021 -ms.prod: m365-security -ms.technology: windows-sec +author: frankroj +ms.author: frankroj +manager: aaroncz +ms.topic: overview +ms.date: 09/22/2022 +ms.prod: windows-client +ms.technology: itpro-security ms.localizationpriority: medium ms.collection: ms.custom: -ms.reviewer: deepakm, rafals +ms.reviewer: rafals --- # Encryption and data protection in Windows client @@ -32,8 +32,8 @@ Encrypted hard drives provide: - Better performance: Encryption hardware, integrated into the drive controller, allows the drive to operate at full data rate with no performance degradation. - Strong security based in hardware: Encryption is always "on" and the keys for encryption never leave the hard drive. User authentication is performed by the drive before it will unlock, independently of the operating system. -- Ease of use: Encryption is transparent to the user, and the user does not need to enable it. Encrypted hard drives are easily erased using on-board encryption key; there is no need to re-encrypt data on the drive. -- Lower cost of ownership: There is no need for new infrastructure to manage encryption keys, since BitLocker uses your existing infrastructure to store recovery information. Your device operates more efficiently because processor cycles do not need to be used for the encryption process. +- Ease of use: Encryption is transparent to the user, and the user doesn't need to enable it. Encrypted hard drives are easily erased using on-board encryption key; there's no need to re-encrypt data on the drive. +- Lower cost of ownership: There's no need for new infrastructure to manage encryption keys, since BitLocker uses your existing infrastructure to store recovery information. Your device operates more efficiently because processor cycles don't need to be used for the encryption process. Encrypted hard drives are a new class of hard drives that are self-encrypted at a hardware level and allow for full disk hardware encryption. @@ -45,8 +45,14 @@ BitLocker provides encryption for the operating system, fixed data, and removabl Windows consistently improves data protection by improving existing options and providing new strategies. +## Personal Data Encryption (PDE) + +(*Applies to: Windows 11, version 22H2 and later*) + +[!INCLUDE [Personal Data Encryption (PDE) description](information-protection/personal-data-encryption/includes/pde-description.md)] ## See also - [Encrypted Hard Drive](information-protection/encrypted-hard-drive.md) - [BitLocker](information-protection/bitlocker/bitlocker-overview.md) +- [Personal Data Encryption (PDE)](information-protection/personal-data-encryption/overview-pde.md) diff --git a/windows/security/information-protection/personal-data-encryption/configure-pde-in-intune.md b/windows/security/information-protection/personal-data-encryption/configure-pde-in-intune.md new file mode 100644 index 0000000000..0151546bcc --- /dev/null +++ b/windows/security/information-protection/personal-data-encryption/configure-pde-in-intune.md @@ -0,0 +1,124 @@ +--- +title: Configure Personal Data Encryption (PDE) in Intune +description: Configuring and enabling Personal Data Encryption (PDE) required and recommended policies in Intune + +author: frankroj +ms.author: frankroj +ms.reviewer: rafals +manager: aaroncz +ms.topic: how-to +ms.prod: windows-client +ms.technology: itpro-security +ms.localizationpriority: medium +ms.date: 09/22/2022 +--- + + + +# Configure Personal Data Encryption (PDE) policies in Intune + +## Required prerequisites + +### Enable Personal Data Encryption (PDE) + +1. Sign into the Intune +2. Navigate to **Devices** > **Configuration Profiles** +3. Select **Create profile** +4. Under **Platform**, select **Windows 10 and later** +5. Under **Profile type**, select **Templates** +6. Under **Template name**, select **Custom**, and then select **Create** +7. On the ****Basics** tab: + 1. Next to **Name**, enter **Personal Data Encryption** + 2. Next to **Description**, enter a description +8. Select **Next** +9. On the **Configuration settings** tab, select **Add** +10. In the **Add Row** window: + 1. Next to **Name**, enter **Personal Data Encryption** + 2. Next to **Description**, enter a description + 3. Next to **OMA-URI**, enter in **./User/Vendor/MSFT/PDE/EnablePersonalDataEncryption** + 4. Next to **Data type**, select **Integer** + 5. Next to **Value**, enter in **1** +11. Select **Save**, and then select **Next** +12. On the **Assignments** tab: + 1. Under **Included groups**, select **Add groups** + 2. Select the groups that the PDE policy should be deployed to + 3. Select **Select** + 4. Select **Next** +13. On the **Applicability Rules** tab, configure if necessary and then select **Next** +14. On the **Review + create** tab, review the configuration to make sure everything is configured correctly, and then select **Create** + +#### Disable Winlogon automatic restart sign-on (ARSO) + +1. Sign into the Intune +2. Navigate to **Devices** > **Configuration Profiles** +3. Select **Create profile** +4. Under **Platform**, select **Windows 10 and later** +5. Under **Profile type**, select **Templates** +6. Under **Template name**, select **Administrative templates**, and then select **Create** +7. On the ****Basics** tab: + 1. Next to **Name**, enter **Disable ARSO** + 2. Next to **Description**, enter a description +8. Select **Next** +9. On the **Configuration settings** tab, under **Computer Configuration**, navigate to **Windows Components** > **Windows Logon Options** +10. Select **Sign-in and lock last interactive user automatically after a restart** +11. In the **Sign-in and lock last interactive user automatically after a restart** window that opens, select **Disabled**, and then select **OK** +12. Select **Next** +13. On the **Scope tags** tab, configure if necessary and then select **Next** +12. On the **Assignments** tab: + 1. Under **Included groups**, select **Add groups** + 2. Select the groups that the ARSO policy should be deployed to + 3. Select **Select** + 4. Select **Next** +13. On the **Review + create** tab, review the configuration to make sure everything is configured correctly, and then select **Create** + +## Recommended prerequisites + +#### Disable crash dumps + +1. Sign into the Intune +2. Navigate to **Devices** > **Configuration Profiles** +3. Select **Create profile** +4. Under **Platform**, select **Windows 10 and later** +5. Under **Profile type**, select **Settings catalog**, and then select **Create** +6. On the ****Basics** tab: + 1. Next to **Name**, enter **Disable Hibernation** + 2. Next to **Description**, enter a description +7. Select **Next** +8. On the **Configuration settings** tab, select **Add settings** +9. In the **Settings picker** windows, select **Memory Dump** +10. When the settings appear in the lower pane, under **Setting name**, select both **Allow Crash Dump** and **Allow Live Dump**, and then select the **X** in the top right corner of the **Settings picker** window to close the window +11. Change both **Allow Live Dump** and **Allow Crash Dump** to **Block**, and then select **Next** +12. On the **Scope tags** tab, configure if necessary and then select **Next** +13. On the **Assignments** tab: + 1. Under **Included groups**, select **Add groups** + 2. Select the groups that the crash dumps policy should be deployed to + 3. Select **Select** + 4. Select **Next** +14. On the **Review + create** tab, review the configuration to make sure everything is configured correctly, and then select **Create** + +#### Disable hibernation + +1. Sign into the Intune +2. Navigate to **Devices** > **Configuration Profiles** +3. Select **Create profile** +4. Under **Platform**, select **Windows 10 and later** +5. Under **Profile type**, select **Settings catalog**, and then select **Create** +6. On the ****Basics** tab: + 1. Next to **Name**, enter **Disable Hibernation** + 2. Next to **Description**, enter a description +7. Select **Next** +8. On the **Configuration settings** tab, select **Add settings** +9. In the **Settings picker** windows, select **Power** +10. When the settings appear in the lower pane, under **Setting name**, select **Allow Hibernate**, and then select the **X** in the top right corner of the **Settings picker** window to close the window +11. Change **Allow Hibernate** to **Block**, and then select **Next** +12. On the **Scope tags** tab, configure if necessary and then select **Next** +13. On the **Assignments** tab: + 1. Under **Included groups**, select **Add groups** + 2. Select the groups that the hibernation policy should be deployed to + 3. Select **Select** + 4. Select **Next** +14. On the **Review + create** tab, review the configuration to make sure everything is configured correctly, and then select **Create** + +## See also +- [Personal Data Encryption (PDE)](overview-pde.md) +- [Personal Data Encryption (PDE) FAQ](faq-pde.yml) \ No newline at end of file diff --git a/windows/security/information-protection/personal-data-encryption/faq-pde.yml b/windows/security/information-protection/personal-data-encryption/faq-pde.yml new file mode 100644 index 0000000000..49b38650ce --- /dev/null +++ b/windows/security/information-protection/personal-data-encryption/faq-pde.yml @@ -0,0 +1,74 @@ +### YamlMime:FAQ + +metadata: + title: Frequently asked questions for Personal Data Encryption (PDE) + description: Answers to common questions regarding Personal Data Encryption (PDE). + author: frankroj + ms.author: frankroj + ms.reviewer: rafals + manager: aaroncz + ms.topic: faq + ms.prod: windows-client + ms.technology: itpro-security + ms.localizationpriority: medium + ms.date: 09/22/2022 + +title: Frequently asked questions for Personal Data Encryption (PDE) +summary: | + Here are some answers to common questions regarding Personal Data Encryption (PDE) + +sections: + - name: Single section - ignored + questions: + - question: Can PDE encrypt entire volumes or drives? + answer: | + No. PDE only encrypts specified files. + + - question: Is PDE a replacement for BitLocker? + answer: | + No. It's still recommended to encrypt all volumes with BitLocker Drive Encryption for increased security. + + - question: Can an IT admin specify which files should be encrypted? + answer: | + Yes, but it can only be done using the PDE APIs. + + - question: Do I need to use OneDrive as my backup provider? + answer: | + No. PDE doesn't have a requirement for a backup provider including OneDrive. However, backups are strongly recommended in case the encryption keys used by PDE are lost. OneDrive is a recommended backup provider. + + - question: What is the relation between Windows Hello for Business and PDE? + answer: | + Windows Hello for Business unlocks PDE encryption keys during user sign on. + + - question: Can a file be encrypted with both PDE and EFS at the same time? + answer: | + No. PDE and EFS are mutually exclusive. + + - question: Can a PDE encrypted files be accessed after signing on via a Remote Desktop connection (RDP)? + answer: | + No. Accessing PDE encrypted files over RDP isn't currently supported. + + - question: Can a PDE encrypted files be access via a network share? + answer: | + No. PDE encrypted files can only be accessed after signing on locally to Windows with Windows Hello for Business credentials. + + - question: How can it be determined if a file is encrypted with PDE? + answer: | + Encrypted files will show a padlock on the file's icon. Additionally, `cipher.exe` can be used to show the encryption state of the file. + + - question: Can users manually encrypt and decrypt files with PDE? + answer: | + Currently users can decrypt files manually but they can't encrypt files manually. + + - question: If a user signs into Windows with a password instead of Windows Hello for Business, will they be able to access their PDE encrypted files? + answer: | + No. PDE encryption keys are protected Windows Hello for Business credentials and will only be unlocked when signing on with Windows Hello for Business PIN or biometrics. + + - question: What encryption method and strength does PDE use? + answer: | + PDE uses AES-256 to encrypt files + +additionalContent: | + ## See also + - [Personal Data Encryption (PDE)](overview-pde.md) + - [Configure Personal Data Encryption (PDE) polices in Intune](configure-pde-in-intune.md) \ No newline at end of file diff --git a/windows/security/information-protection/personal-data-encryption/includes/pde-description.md b/windows/security/information-protection/personal-data-encryption/includes/pde-description.md new file mode 100644 index 0000000000..7ca7334657 --- /dev/null +++ b/windows/security/information-protection/personal-data-encryption/includes/pde-description.md @@ -0,0 +1,27 @@ +--- +title: Personal Data Encryption (PDE) description +description: Personal Data Encryption (PDE) description include file + +author: frankroj +ms.author: frankroj +ms.reviewer: rafals +manager: aaroncz +ms.topic: how-to +ms.prod: windows-client +ms.technology: itpro-security +ms.localizationpriority: medium +ms.date: 09/22/2022 +--- + + + +Personal data encryption (PDE) is a security feature introduced in Windows 11, version 22H2 that provides additional encryption features to Windows. PDE differs from BitLocker in that it encrypts individual files instead of whole volumes and disks. PDE occurs in addition to other encryption methods such as BitLocker. + +PDE utilizes Windows Hello for Business to link data encryption keys with user credentials. This feature can minimize the number of credentials the user has to remember to gain access to files. For example, when using BitLocker with PIN, a user would need to authenticate twice - once with the BitLocker PIN and a second time with Windows credentials. This requirement requires users to remember two different credentials. With PDE, users only need to enter one set of credentials via Windows Hello for Business. + +PDE is also accessibility friendly. For example, The BitLocker PIN entry screen doesn't have accessibility options. PDE however uses Windows Hello for Business, which does have accessibility features. + +Unlike BitLocker that releases data encryption keys at boot, PDE doesn't release data encryption keys until a user signs in using Windows Hello for Business. Users will only be able to access their PDE encrypted files once they've signed into Windows using Windows Hello for Business. Additionally, PDE has the ability to also discard the encryption keys when the device is locked. + +> [!NOTE] +> PDE is currently only available to developers via [PDE APIs](/uwp/api/windows.security.dataprotection.userdataprotectionmanager). There is no user interface in Windows to either enable PDE or encrypt files via PDE. Also, although there is an MDM policy that can enable PDE, there are no MDM policies that can be used to encrypt files via PDE. diff --git a/windows/security/information-protection/personal-data-encryption/overview-pde.md b/windows/security/information-protection/personal-data-encryption/overview-pde.md new file mode 100644 index 0000000000..90896a5bd7 --- /dev/null +++ b/windows/security/information-protection/personal-data-encryption/overview-pde.md @@ -0,0 +1,142 @@ +--- +title: Personal Data Encryption (PDE) +description: Personal Data Encryption unlocks user encrypted files at user sign in instead of at boot. + +author: frankroj +ms.author: frankroj +ms.reviewer: rafals +manager: aaroncz +ms.topic: how-to +ms.prod: windows-client +ms.technology: itpro-security +ms.localizationpriority: medium +ms.date: 09/22/2022 +--- + + + +# Personal Data Encryption (PDE) + +(*Applies to: Windows 11, version 22H2 and later Enterprise and Education editions*) + +[!INCLUDE [Personal Data Encryption (PDE) description](includes/pde-description.md)] + +## Prerequisites + +### **Required** + - [Azure AD joined device](/azure/active-directory/devices/concept-azure-ad-join) + - [Windows Hello for Business](../../identity-protection/hello-for-business/hello-overview.md) + - Windows 11, version 22H2 and later Enterprise and Education editions + +### **Not supported with PDE** + - [FIDO/security key authentication](../../identity-protection/hello-for-business/microsoft-compatible-security-key.md) + - [Winlogon automatic restart sign-on (ARSO)](/windows-server/identity/ad-ds/manage/component-updates/winlogon-automatic-restart-sign-on--arso-) + - For information on disabling ARSO via Intune, see [Disable Winlogon automatic restart sign-on (ARSO)](configure-pde-in-intune.md#disable-winlogon-automatic-restart-sign-on-arso)). + - [Windows Information Protection (WIP)](../windows-information-protection/protect-enterprise-data-using-wip.md) + - [Hybrid Azure AD joined devices](/azure/active-directory/devices/concept-azure-ad-join-hybrid) + - Remote Desktop connections + +### **Highly recommended** + - [BitLocker Drive Encryption](../bitlocker/bitlocker-overview.md) enabled + - Although PDE will work without BitLocker, it's recommended to also enable BitLocker. PDE is meant to supplement BitLocker and not replace it. + - Backup solution such as [OneDrive](/onedrive/onedrive) + - In certain scenarios such as TPM resets or destructive PIN resets, the PDE encryption keys can be lost. In such scenarios, any file encrypted with PDE will no longer be accessible. The only way to recover such files would be from backup. + - [Windows Hello for Business PIN reset service](../../identity-protection/hello-for-business/hello-feature-pin-reset.md) + - Destructive PIN resets will cause PDE encryption keys to be lost. The destructive PIN reset will make any file encrypted with PDE no longer accessible after a destructive PIN reset. Files encrypted with PDE will need to be recovered from a backup after a destructive PIN reset. For this reason Windows Hello for Business PIN reset service is recommended since it provides non-destructive PIN resets. + - [Windows Hello Enhanced Sign-in Security](/windows-hardware/design/device-experiences/windows-hello-enhanced-sign-in-security) + - Provides additional security when authenticating with Windows Hello for Business via biometrics or PIN + - [Kernel and user mode crash dumps disabled](/windows/client-management/mdm/policy-csp-memorydump) + - Crash dumps can potentially cause the PDE encryption keys to be exposed. For greatest security, disable kernel and user mode crash dumps. For information on disabling crash dumbs via Intune, see [Disable crash dumps](configure-pde-in-intune.md#disable-crash-dumps). + - [Hibernation disabled](/windows/client-management/mdm/policy-csp-power#power-allowhibernate) + - Hibernation files can potentially cause the PDE encryption keys to be exposed. For greatest security, disable hibernation. For information on disabling crash dumbs via Intune, see [Disable hibernation](configure-pde-in-intune.md#disable-hibernation). + +## PDE protection levels + +PDE uses AES-256 to encrypt files and offers two levels of protection. The level of protection is determined based on the organizational needs. These levels can be set via the PDE APIs. + +| Item | Level 1 | Level 2 | +|---|---|---| +| Data is accessible when user is signed in | Yes | Yes | +| Data is accessible when user has locked their device | Yes | No | +| Data is accessible after user signs out | No | No | +| Data is accessible when device is shut down | No | No | +| Decryption keys discarded | After user signs out | After user locks device or signs out | + +## PDE encrypted files accessibility + +When a file is encrypted with PDE, its icon will show a padlock. If the user hasn't signed in locally with Windows Hello for Business or an unauthorized user attempts to access a PDE encrypted file, they'll be denied access to the file. + +Scenarios where a user will be denied access to a PDE encrypted file include: + +- User has signed into Windows via a password instead of signing in with Windows Hello for Business biometric or PIN. +- If specified via level 2 protection, when the device is locked. +- When trying to access files on the device remotely. For example, UNC network paths. +- Remote Desktop sessions. +- Other users on the device who aren't owners of the file, even if they're signed in via Windows Hello for Business and have permissions to navigate to the PDE encrypted files. + +## How to enable PDE + +To enable PDE on devices, push an MDM policy to the devices with the following parameters: + +- Name: **Personal Data Encryption** +- OMA-URI: **./User/Vendor/MSFT/PDE/EnablePersonalDataEncryption** +- Data type: **Integer** +- Value: **1** + +There's also a [PDE CSP](/windows/client-management/mdm/personaldataencryption-csp) available for MDM solutions that support it. + +> [!NOTE] +> Enabling the PDE policy on devices only enables the PDE feature. It does not encrypt any files. To encrypt files, use the [PDE APIs](/uwp/api/windows.security.dataprotection.userdataprotectionmanager) to create custom applications and scripts to specify which files to encrypt and at what level to encrypt the files. Additionally, files will not encrypt via the APIs until this policy has been enabled. + +For information on enabling PDE via Intune, see [Enable Personal Data Encryption (PDE)](configure-pde-in-intune.md#enable-personal-data-encryption-pde). + +## Differences between PDE and BitLocker + +| Item | PDE | BitLocker | +|--|--|--| +| Release of encryption keys | At user sign in via Windows Hello for Business | At boot | +| Encryption keys discarded | At user sign out | At reboot | +| Files encrypted | Individual specified files | Entire volume/drive | +| Authentication to access encrypted file | Windows Hello for Business | When BitLocker with PIN is enabled, BitLocker PIN plus Windows sign in | +| Accessibility | Windows Hello for Business is accessibility friendly | BitLocker with PIN doesn't have accessibility features | + +## Differences between PDE and EFS + +The main difference between encrypting files with PDE instead of EFS is the method they use to encrypt the file. PDE uses Windows Hello for Business to secure the encryption keys that encrypts the files. EFS uses certificates to secure and encrypt the files. + +To see if a file is encrypted with PDE or EFS: + +1. Open the properties of the file +2. Under the **General** tab, select **Advanced...** +3. In the **Advanced Attributes** windows, select **Details** + +For PDE encrypted files, under **Protection status:** there will be an item listed as **Personal Data Encryption is:** and it will have the attribute of **On**. + +For EFS encrypted files, under **Users who can access this file:**, there will be a **Certificate thumbprint** next to the users with access to the file. There will also be a section at the bottom labeled **Recovery certificates for this file as defined by recovery policy:**. + +Encryption information including what encryption method is being used can be obtained with the command line `cipher.exe /c` command. + +## Disable PDE and decrypt files + +Currently there's no method to disable PDE via MDM policy. However, PDE can be disabled locally and files can be decrypted using `cipher.exe`. + +In certain scenarios a user may be able to manually decrypt a file using the following steps: + +1. Open the properties of the file +2. Under the **General** tab, select **Advanced...** +3. Uncheck the option **Encrypt contents to secure data** +4. Select **OK**, and then **OK** again + +> [!Important] +> Once a user selects to manually decrypt a file, they will not be able to manually encrypt the file again. + +## Windows out of box applications that support PDE + +Certain Windows applications support PDE out of the box. If PDE is enabled on a device, these applications will utilize PDE. + +- Mail + - Supports encrypting both email bodies and attachments + +## See also +- [Personal Data Encryption (PDE) FAQ](faq-pde.yml) +- [Configure Personal Data Encryption (PDE) polices in Intune](configure-pde-in-intune.md) \ No newline at end of file