BitLocker Decryption Explained

Dmitry Sumin
Passware
Published in
3 min readFeb 4, 2021

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:

  1. TPM (Trusted Platform Module chip)
  2. Startup key (on a USB drive)
  3. TPM+PIN+Startup key
  4. TPM+Startup key
  5. Recovery key (numerical password; on a USB drive)
  6. Recovery password (on a USB drive)
  7. 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:

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 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.

SUMMARY

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, ). 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 Password might not be among protectors used and the volume might be protected with other protectors (e.g. Startup key or TPM + PINVMK.

* 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.

Originally published at https://blog.passware.com.

--

--