This is a post about enabling BitLocker on non-HSTI devices with Windows 10 version 1809 and standard user permissions.
First of all a little background on HSTI. HSTI is a Hardware Security Testability Interface. It is an interface to report the results of security-related self-tests. Its purpose is to provide high assurance validation of proper security configuration.
The enhancement with Windows 10 version 1809 is that we are able to activate BitLocker with a MDM policy (Intune), even for non-HSTI devices and on Windows 10 Pro Edition. This was not working with Windows 10 version 1803 or lower and the community came up with custom solutions to handle this like custom PowerShell scripts deployed via Intune Management Extension. If we wanted to use Intune native MDM policies via the BitLocker CSP we needed HSTI compliant devices like the Surface devices or newer hardware devices which are mostly delivered as HSTI compliant devices now. To successful start the encryption as a standard user, a Windows 10 version 1803 was the minimum as the feature was introduced with this version.
The prerequisites for Intune BitLocker configuration are
- Windows 10 version 1809 Enterprise and Pro
- Azure Active Directory joined devices
- Microsoft Intune
- non-HSTI device
Older devices can be protected by Intune BitLocker policy now?
Yes, as long as they are running Windows 10 version 1809. The most common problem is that we do not replace all devices in every Windows 10 project to have only latest HSTI compliant devices in the environment. We have to support older devices purchased maybe not long ago but not HSTI compliant. These devices can now be managed by an Intune device configuration policy to turn on BitLocker silently without administrative permissions as long as the device is a Windows 10 version 1809 device.
What do we need to do?
Currently at the time of writing we need two configuration policies. One endpoint protection profile and a custom profile.
The endpoint protection profile configures the silent BitLocker enforcement and other parameters like encryption strength. Go to Microsoft Intune > Device configuration – Profiles > yourpolicyname – Properties > Endpoint protection > Windows Encryption
Set Encrypt devices to Require
Set Warning for other disk encryption to Block
Sure you can set other parameters like encryption methods as well, but for a functional test this is enough.
These two settings make sure the encryption starts and it starts silently as we block the warning dialog for other disk encryption software.
Example shown below:
The second profile is a custom profile (at time of writing it was not available in the UI) and it configures the ability to enforce the BitLocker encryption even when standard users are logging in. For example when the Windows 10 device is enrolled with an Autopilot profile where the user account type is set to standard user. AllowStandardUserEncryption is a new setting introduced with Windows 10 version 1809 BitLocker CSP and must be used in conjunction with the setting “Warning for other disk encryption set to Block” otherwise it is not functional!
The custom OMA-URI configuration must be configured like this:
OMA-URI: ./Vendor/MSFT/BitLocker/AllowStandardUserEncryption Data type: integer Value: 1
Example shown below:
The two policies must be assigned to a user group or device group to test the new policies. To force the user type to a standard user after enrollment we need an Autopilot profile and assign it to our device.
If we now enroll a new Windows 10 version 1809 non-HSTI device it must be encrypted silently and the recovery key must be backed up to Azure AD.
How can I easily verify this?
I used a Hyper-V VM Generation 2 with an enabled TPM module:
To test if the VM is reporting as a non-HSTI compliant device I downloaded the Device Guard and Credential Guard hardware readiness tool and verified the HSTI status with the following PowerShell command:
The result is displayed like this:
During my test I had to make sure that after the first restart, the Windows 10 version 1809 ISO is ejected, otherwise silent BitLocker encryption will fail. This is because the system does not have the normal start parameters during the BitLocker and TPM provisioning. The platform would take into account the additional media as the normal platform verification parameter. Which means after ejecting the ISO it would have prompted us for the recovery key. Microsoft takes care of this situation and does not start the BitLocker provisioning process at all. So, the generation of the platform default configuration parameters for later verification to unlock the TPM is prevented, as long as a removable media is inserted. See the failure event here:
Without an ISO it will successfully starts the encryption and key backup to Azure AD. A success event is shown below:
The BitLocker state can be verified with the PowerShell command on the client:
Get-BitLockerVolume | fl
In the Intune portal we can see the recovery key appended to the AAD device object:
What’s new in Windows 10, version 1809 for IT Pros
Device Guard and Credential Guard hardware readiness tool
Hardware Security Testability Specification
Go ahead and start encrypting all your Windows 10 devices to strengthen your security level 👍
Oliver started as a System Engineer and is now a Lead Cloud Architect and has been working in the IT industry for the past 15+ years specializing in Enterprise Mobility and Security, Deployment and Automation. Oliver has been awarded Enterprise Mobility MVP in August 2018. Currently working for Glück & Kanja Consulting AG and is engaged in enterprise projects with up to 100k endpoints. Most recent focus has been on Modern Management projects, helping customers to solve actual challenges there. In 2017, Oliver has founded https://oliverkieselbach.com blog and is blogging on SCConfigMgr.