Configure use of hardware-based encryption for operating system drives

This policy setting allows you to manage BitLocker’s use of hardware-based encryption on operating system drives and specify which encryption algorithms it can use with hardware-based encryption. Using hardware-based encryption can improve performance of drive operations that involve frequent reading or writing of data to the drive. If you enable this policy setting you can specify additional options that control whether BitLocker software-based encryption is used instead of hardware-based encryption on computers that do not support hardware-based encryption and whether you want to restrict the encryption algorithms and cipher suites used with hardware-based encryption. If you disable this policy setting BitLocker cannot use hardware-based encryption with operating system drives and BitLocker software-based encryption will be used by default when the drive is encrypted. If you do not configure this policy setting BitLocker will use hardware-based encryption with the encryption algorithm set for the drive. If hardware-based encryption is not available BitLocker software-based encryption will be used instead. Note: The “Choose drive encryption method and cipher strength” policy setting does not apply to hardware-based encryption. The encryption algorithm used by hardware-based encryption is set when the drive is partitioned. By default BitLocker uses the algorithm configured on the drive to encrypt the drive. The “Restrict encryption algorithms and cipher suites allowed for hardware-based encryption” option enables you to restrict the encryption algorithms that BitLocker can use with hardware encryption. If the algorithm set for the drive is not available BitLocker will disable the use of hardware-based encryption. Encryption algorithms are specified by object identifiers (OID). For example:- AES 128 in CBC mode OID: 2. 16. 840. 1. 101. 3. 4. 1. 2- AES 256 in CBC mode OID: 2. 16. 840. 1. 101. 3. 4. 1. 42

Enable use of BitLocker authentication requiring preboot keyboard input on slates

This policy setting allows users to turn on authentication options that require user input from the pre-boot environment even if the platform lacks pre-boot input capability. The Windows touch keyboard (such as that used by tablets) isn’t available in the pre-boot environment where BitLocker requires additional information such as a PIN or Password. If you enable this policy setting devices must have an alternative means of pre-boot input (such as an attached USB keyboard). If this policy is not enabled the Windows Recovery Environment must be enabled on tablets to support the entry of the BitLocker recovery password. When the Windows Recovery Environment is not enabled and this policy is not enabled you cannot turn on BitLocker on a device that uses the Windows touch keyboard. Note that if you do not enable this policy setting options in the “Require additional authentication at startup” policy might not be available on such devices. These options include:- Configure TPM startup PIN: Required/Allowed- Configure TPM startup key and PIN: Required/Allowed- Configure use of passwords for operating system drives.

Allow Secure Boot for integrity validation

This policy setting allows you to configure whether Secure Boot will be allowed as the platform integrity provider for BitLocker operating system drives. Secure Boot ensures that the PC’s pre-boot environment only loads firmware that is digitally signed by authorized software publishers. Secure Boot also provides more flexibility for managing pre-boot configuration than legacy BitLocker integrity checks. If you enable or do not configure this policy setting BitLocker will use Secure Boot for platform integrity if the platform is capable of Secure Boot-based integrity validation. If you disable this policy setting BitLocker will use legacy platform integrity validation even on systems capable of Secure Boot-based integrity validation. When this policy is enabled and the hardware is capable of using Secure Boot for BitLocker scenarios the “Use enhanced Boot Configuration Data validation profile” group policy setting is ignored and Secure Boot verifies BCD settings according to the Secure Boot policy setting which is configured separately from BitLocker. Note: If the group policy setting “Configure TPM platform validation profile for native UEFI firmware configurations” is enabled and has PCR 7 omitted Bitlocker will be prevented from using Secure Boot for platform or Boot Configuration Data (BCD) integrity validation. Warning: Disabling this policy may result in BitLocker recovery when firmware is updated. If you disable this policy suspend BitLocker prior to applying firmware updates.

Choose how BitLocker-protected fixed drives can be recovered

This policy setting allows you to control how BitLocker-protected fixed data drives are recovered in the absence of the required credentials. This policy setting is applied when you turn on BitLocker. The “Allow data recovery agent” check box is used to specify whether a data recovery agent can be used with BitLocker-protected fixed data drives. Before a data recovery agent can be used it must be added from the Public Key Policies item in either the Group Policy Management Console or the Local Group Policy Editor. Consult the BitLocker Drive Encryption Deployment Guide on Microsoft TechNet for more information about adding data recovery agents. In “Configure user storage of BitLocker recovery information” select whether users are allowed required or not allowed to generate a 48-digit recovery password or a 256-bit recovery key. Select “Omit recovery options from the BitLocker setup wizard” to prevent users from specifying recovery options when they turn on BitLocker on a drive. This means that you will not be able to specify which recovery option to use when you turn on BitLocker instead BitLocker recovery options for the drive are determined by the policy setting. In “Save BitLocker recovery information to Active Directory Domain Services” choose which BitLocker recovery information to store in AD DS for fixed data drives. If you select “Backup recovery password and key package” both the BitLocker recovery password and key package are stored in AD DS. Storing the key package supports recovering data from a drive that has been physically corrupted. If you select “Backup recovery password only” only the recovery password is stored in AD DS. Select the “Do not enable BitLocker until recovery information is stored in AD DS for fixed data drives” check box if you want to prevent users from enabling BitLocker unless the computer is connected to the domain and the backup of BitLocker recovery information to AD DS succeeds. Note: If the “Do not enable BitLocker until recovery information is stored in AD DS for fixed data drives” check box is selected a recovery password is automatically generated. If you enable this policy setting you can control the methods available to users to recover data from BitLocker-protected fixed data drives. If this policy setting is not configured or disabled the default recovery options are supported for BitLocker recovery. By default a DRA is allowed the recovery options can be specified by the user including the recovery password and recovery key and recovery information is not backed up to AD DS

Configure use of passwords for fixed data drives

This policy setting specifies whether a password is required to unlock BitLocker-protected fixed data drives. If you choose to permit the use of a password you can require that a password be used enforce complexity requirements on the password and configure a minimum length for the password. For the complexity requirement setting to be effective the Group Policy setting “Password must meet complexity requirements” located in Computer Configuration -> Windows Settings -> Security Settings -> Account Policies -> Password Policy -> must be also enabled. Note: These settings are enforced when turning on BitLocker not when unlocking a volume. BitLocker will allow unlocking a drive with any of the protectors available on the drive. If you enable this policy setting users can configure a password that meets the requirements you define. To require the use of a password select “Require password for fixed data drive”. To enforce complexity requirements on the password select “Require complexity”. When set to “Require complexity” a connection to a domain controller is necessary when BitLocker is enabled to validate the complexity the password. When set to “Allow complexity” a connection to a domain controller will be attempted to validate the complexity adheres to the rules set by the policy but if no domain controllers are found the password will still be accepted regardless of actual password complexity and the drive will be encrypted using that password as a protector. When set to “Do not allow complexity” no password complexity validation will be done. Passwords must be at least 8 characters. To configure a greater minimum length for the password enter the desired number of characters in the “Minimum password length” box. If you disable this policy setting the user is not allowed to use a password. If you do not configure this policy setting passwords will be supported with the default settings which do not include password complexity requirements and require only 8 characters. Note: Passwords cannot be used if FIPS-compliance is enabled. The “System cryptography: Use FIPS-compliant algorithms for encryption hashing and signing” policy setting in Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options specifies whether FIPS-compliance is enabled.

Deny write access to fixed drives not protected by BitLocker

This policy setting determines whether BitLocker protection is required for fixed data drives to be writable on a computer. This policy setting is applied when you turn on BitLocker. If you enable this policy setting all fixed data drives that are not BitLocker-protected will be mounted as read-only. If the drive is protected by BitLocker it will be mounted with read and write access. If you disable or do not configure this policy setting all fixed data drives on the computer will be mounted with read and write access.

Allow access to BitLocker-protected fixed data drives from earlier versions of Windows

This policy setting configures whether or not fixed data drives formatted with the FAT file system can be unlocked and viewed on computers running Windows Server 2008 Windows Vista Windows XP with Service Pack 3 (SP3) or Windows XP with Service Pack 2 (SP2) operating systems. If this policy setting is enabled or not configured fixed data drives formatted with the FAT file system can be unlocked on computers running Windows Server 2008 Windows Vista Windows XP with SP3 or Windows XP with SP2 and their content can be viewed. These operating systems have read-only access to BitLocker-protected drives. When this policy setting is enabled select the “Do not install BitLocker To Go Reader on FAT formatted fixed drives” check box to help prevent users from running BitLocker To Go Reader from their fixed drives. If BitLocker To Go Reader (bitlockertogo. exe) is present on a drive that does not have an identification field specified or if the drive has the same identification field as specified in the “Provide unique identifiers for your organization” policy setting the user will be prompted to update BitLocker and BitLocker To Go Reader will be deleted from the drive. In this situation for the fixed drive to be unlocked on computers running Windows Server 2008 Windows Vista Windows XP with SP3 or Windows XP with SP2 BitLocker To Go Reader must be installed on the computer. If this check box is not selected BitLocker To Go Reader will be installed on the fixed drive to enable users to unlock the drive on computers running Windows Server 2008 Windows Vista Windows XP with SP3 or Windows XP with SP2 that do not have BitLocker To Go Reader installed. If this policy setting is disabled fixed data drives formatted with the FAT file system that are BitLocker-protected cannot be unlocked on computers running Windows Server 2008 Windows Vista Windows XP with SP3 or Windows XP with SP2. Bitlockertogo. exe will not be installed. Note: This policy setting does not apply to drives that are formatted with the NTFS file system.

Configure use of smart cards on fixed data drives

This policy setting allows you to specify whether smart cards can be used to authenticate user access to the BitLocker-protected fixed data drives on a computer. If you enable this policy setting smart cards can be used to authenticate user access to the drive. You can require a smart card authentication by selecting the “Require use of smart cards on fixed data drives” check box. Note: These settings are enforced when turning on BitLocker not when unlocking a drive. BitLocker will allow unlocking a drive with any of the protectors available on the drive. If you disable this policy setting users are not allowed to use smart cards to authenticate their access to BitLocker-protected fixed data drives. If you do not configure this policy setting smart cards can be used to authenticate user access to a BitLocker-protected drive.

Enforce drive encryption type on fixed data drives

This policy setting allows you to configure the encryption type used by BitLocker Drive Encryption. This policy setting is applied when you turn on BitLocker. Changing the encryption type has no effect if the drive is already encrypted or if encryption is in progress. Choose full encryption to require that the entire drive be encrypted when BitLocker is turned on. Choose used space only encryption to require that only the portion of the drive used to store data is encrypted when BitLocker is turned on. If you enable this policy setting the encryption type that BitLocker will use to encrypt drives is defined by this policy and the encryption type option will not be presented in the BitLocker setup wizard. If you disable or do not configure this policy setting the BitLocker setup wizard will ask the user to select the encryption type before turning on BitLocker.

Configure use of hardware-based encryption for fixed data drives

This policy setting allows you to manage BitLocker’s use of hardware-based encryption on fixed data drives and specify which encryption algorithms it can use with hardware-based encryption. Using hardware-based encryption can improve performance of drive operations that involve frequent reading or writing of data to the drive. If you enable this policy setting you can specify additional options that control whether BitLocker software-based encryption is used instead of hardware-based encryption on computers that do not support hardware-based encryption and whether you want to restrict the encryption algorithms and cipher suites used with hardware-based encryption. If you disable this policy setting BitLocker cannot use hardware-based encryption with operating system drives and BitLocker software-based encryption will be used by default when the drive is encrypted. If you do not configure this policy setting BitLocker will use hardware-based encryption with the encryption algorithm set for the drive. If hardware-based encryption is not available BitLocker software-based encryption will be used instead. Note: The “Choose drive encryption method and cipher strength” policy setting does not apply to hardware-based encryption. The encryption algorithm used by hardware-based encryption is set when the drive is partitioned. By default BitLocker uses the algorithm configured on the drive to encrypt the drive. The “Restrict encryption algorithms and cipher suites allowed for hardware-based encryption” option enables you to restrict the encryption algorithms that BitLocker can use with hardware encryption. If the algorithm set for the drive is not available BitLocker will disable the use of hardware-based encryption. Encryption algorithms are specified by object identifiers (OID). For example:- AES 128 in CBC mode OID: 2. 16. 840. 1. 101. 3. 4. 1. 2- AES 256 in CBC mode OID: 2. 16. 840. 1. 101. 3. 4. 1. 42