Decrypting BitLocker volumes or images is challenging due to the various encryption options offered by BitLocker that require different information for decryption.
This article explains BitLocker protectors and talks about the best ways to get the data decrypted, even for computers that are turned off.
BitLocker Encryption Options
Protectors that can be used to encrypt a BitLocker volume include:
- TPM (Trusted Platform Module chip)
- Startup key (on a USB drive)
- TPM+PIN+Startup key
- TPM+Startup key
- Recovery key (numerical password; on a USB drive)
- Recovery password (on a USB drive)
- Active Directory Domain Services (AD DS) account
To list the protectors of a given BitLocker volume, type the following command in command-line prompt (cmd):
manage-bde -protectors -get C: (where C: is the name of the mounted BitLocker-encrypted volume)
The list of protectors will be displayed as follows:
Detailed information on each protector type, in accordance with Microsoft documentation, is provided below:
- TPM. BitLocker uses the computer’s TPM to protect the encryption key. If you specify this protector, users can access the encrypted drive as long as it is connected to the system board that hosts the TPM and the system boot integrity is intact. In general, TPM-based protectors can only be associated to an operating system volume.
- TPM+PIN. BitLocker uses a combination of the TPM and a user-supplied Personal Identification Number (PIN). A PIN is four to twenty digits or if you allow enhanced PINs, four to twenty letters, symbols, spaces, or numbers.
- Startup key. BitLocker uses input from a USB memory device that contains the external key. It is a binary file with a .BEK extension.
- TPM+PIN+Startup key. BitLocker uses a combination of the TPM, a user-supplied PIN, and input from a USB memory device that contains an external key.
- TPM+Startup key. BitLocker uses a combination of the TPM and input from a USB memory device that contains an external key.
- Password. A user-supplied password is used to access the volume.
- Recovery key. A recovery key also called a numerical password, is stored as a specified file in a USB memory device. It is a sequence of 48 digits divided by dashes.
- Active Directory Domain Services account. BitLocker uses domain authentication to unlock data volumes. Operating system volumes cannot use this type of key protector.
Any of these protectors encrypt a BitLocker Volume Master Key (VMK) to generate a Full Volume Encryption Key (FVEK), which is then used to encrypt the volume.
Using Memory Images for Instant Decryption of BitLocker Volumes
If a given BitLocker volume is mounted, the VMK resides in RAM.
When Windows displays a standard Windows user login screen, as above, this means that the system BitLocker volume is mounted and the VMK resides in memory. Once a live memory image has been created using warm-boot method *, it is possible to use Passware Kit to extract the VMK and decrypt the volume.
When you turn on a computer configured with the default BitLocker settings, Windows reads the encryption key from the TPM chip, mounts the system drive and proceeds with the boot process. In this case, the VMK resides in memory as well.
Passware Kit extracts the VMK (base64 format) from the memory image (or hibernation file), converts it to FVEK, and decrypts the BitLocker volume. It also recovers the Recovery key and Startup key protectors, if available. A sample result is displayed below:
As shown on the screenshot above, Passware Kit Forensic displays both the Encryption/Recovery key and Startup key (file) protectors, as well as creates a decrypted copy of the volume.
To summarize, if the memory image contains the VMK, the volume gets decrypted, regardless of the protector type used to encrypt the volume. By extracting this VMK, it is also possible to recover the protectors (Recovery Key and Startup Key).
However, if the memory image does not contain the VMK (the volume was not mounted during the live memory acquisition, the hibernation file had been overwritten, etc.), it is only possible to decrypt the volume with the Password protector, i.e. to recover the original password (using brute-force or dictionary attacks).
The password recovery process is time-consuming and depends on the password complexity, any knowledge about the password, and your hardware resources available for password recovery, such as GPUs and availability of distributed computing. As a result, the recovered original password can be used to mount the BitLocker volume.
For some volumes, Password might not be among protectors used and the volume might be protected with other protectors (e.g. Startup key or TPM + PIN). In this case it is impossible to decrypt the volume without a memory image acquired while the volume was mounted or a hibernation file, which contains the VMK.
* It is important to acquire a live memory image correctly in order to preserve residing encryption keys. A warm boot can be performed using a Windows Secure Boot compatible Linux distributive, such as Passware Bootable Memory Imager available in Passware Kit Forensic.
Hi Yana, you mention in this article that 'When Windows displays a standard Windows user login screen, this means that the system BitLocker volume is mounted and the VMK resides in memory. Once a live memory image has been created *, it is possible to use Passware Kit to extract the VMK and decrypt the volume'
You are implying here that a RAM capture/live memory image can occur from the login screen with the tools suggested, however this does not seem to be the case. You need to have the login password/PIN in this case to extract the VMK from the RAM Capture so that you can run a RAM Capture tool executable from a USB.
Please do let me know if you know of any tools that have the ability to capture RAM from a locked screen.
Dear Lars Lincoln
We have explored your request with our Research team and have updated the note as follows:
It is important to acquire a live memory image correctly in order to preserve residing encryption keys. A warm boot can be performed using a Windows Secure Boot compatible Linux distributive.
I hope this answers your question.
How reliable is the Passware Bootable Memory Imager on a system with a BitLocker-enabled boot drive? I am surprised that the keys reside in memory and are not wiped from RAM. It looks to me that unless the following registry key is set: https://docs.microsoft.com/en-us/mem/configmgr/protect/tech-ref/bitlocker/settings#prevent-memory-overwrite-on-restart, the method would not be successful, as the system will wipe memory on restart. Best wishes.
Adam Walker we had many successful cases, but it is important to note that this is possible only in case of reboot made with hardware button. Any reboot performed via the software option will most likely erase the keys from the memory.
Please sign in to leave a comment.