|Other names||Device Encryption|
|Initial release||January 30, 2007|
|Operating system||Microsoft Windows|
|Type||Disk encryption software|
BitLocker is a full volume encryption feature included with Microsoft Windows versions starting with Windows Vista. It is designed to protect data by providing encryption for entire volumes. By default, it uses the AES encryption algorithm in cipher block chaining (CBC) or XTS mode with a 128-bit or 256-bit key. CBC is not used over the whole disk; it is applied to each individual sector.
BitLocker originated as a part of Microsoft's Next-Generation Secure Computing Base architecture in 2004 as a feature tentatively codenamed "Cornerstone" and was designed to protect information on devices, particularly if a device was lost or stolen; another feature, titled "Code Integrity Rooting", was designed to validate the integrity of Microsoft Windows boot and system files. When used in conjunction with a compatible Trusted Platform Module (TPM), BitLocker can validate the integrity of boot and system files before decrypting a protected volume; an unsuccessful validation will prohibit access to a protected system. BitLocker was briefly called Secure Startup before Windows Vista's release to manufacturing.
BitLocker is available on:
- Ultimate and Enterprise editions of Windows Vista and Windows 7
- Pro and Enterprise editions of Windows 8 and 8.1
- Pro, Enterprise, and Education editions of Windows 10
- Windows Server 2008 and later
|Initial release||January 30, 2007|
|Operating system||Microsoft Windows|
|License||Proprietary commercial software|
Initially, the graphical BitLocker interface in Windows Vista could only encrypt the operating system volume. Starting with Windows Vista with Service Pack 1 and Windows Server 2008, volumes other than the operating system volume could be encrypted using the graphical tool. Still, some aspects of the BitLocker (such as turning autolocking on or off) had to be managed through a command-line tool called
The version of BitLocker included in Windows 7 and Windows Server 2008 R2 adds the ability to encrypt removable drives. On Windows XP or Windows Vista, read-only access to these drives can be achieved through a program called BitLocker To Go Reader, if FAT16, FAT32 or exFAT filesystems are used. In addition, a new command-line tool called
manage-bde replaced the old
Starting with Windows Server 2012 and Windows 8, Microsoft has complemented BitLocker with the Microsoft Encrypted Hard Drive specification, which allows the cryptographic operations of BitLocker encryption to be offloaded to the storage device's hardware. In addition, BitLocker can now be managed through Windows PowerShell. Finally, Windows 8 introduced Windows To Go in its Enterprise edition, which BitLocker can protect.
Windows Mobile 6.5, Windows RT and core editions of Windows 8.1 include device encryption, a feature-limited version of BitLocker that encrypts the whole system. Logging in with a Microsoft account with administrative privileges automatically begins the encryption process. The recovery key is stored to either the Microsoft account or Active Directory, allowing it to be retrieved from any computer. While device encryption is offered on all versions of 8.1, unlike BitLocker, device encryption requires that the device meet the InstantGo (formerly Connected Standby) specifications, which requires solid-state drives, non-removable RAM (to protect against cold boot attacks) and a TPM 2.0 chip.
Starting with Windows 10 1703, the requirements for device encryption have changed, requiring a TPM 1.2 or 2.0 module with PCR 7 support, UEFI Secure Boot, and that the device meets Modern Standby requirements or HSTI validation.
In September 2019 a new update was released (KB4516071) changing the default setting for BitLocker when encrypting a self-encrypting hard drive. Now, the default is to use software encryption for newly encrypted drives. This is due to hardware encryption flaws and security concerns related to those issues.
Three authentication mechanisms can be used as building blocks to implement BitLocker encryption:
- Transparent operation mode: This mode uses the capabilities of TPM 1.2 hardware to provide for transparent user experience—the user powers up and logs into Windows as usual. The key used for disk encryption is sealed (encrypted) by the TPM chip and will only be released to the OS loader code if the early boot files appear to be unmodified. The pre-OS components of BitLocker achieve this by implementing a Static Root of Trust Measurement—a methodology specified by the Trusted Computing Group (TCG). This mode is vulnerable to a cold boot attack, as it allows a powered-down machine to be booted by an attacker. It is also vulnerable to a sniffing attack, as the volume encryption key is transferred in plain text from the TPM to the CPU during a successful boot.
- User authentication mode: This mode requires that the user provide some authentication to the pre-boot environment in the form of a pre-boot PIN or password.
- USB Key Mode: The user must insert a USB device that contains a startup key into the computer to be able to boot the protected OS. Note that this mode requires that the BIOS on the protected machine supports the reading of USB devices in the pre-OS environment. The key may also be provided by a CCID for reading a cryptographic smartcard. Using CCID provides additional benefits beyond just storing the key file on an external USB thumb drive because the CCID protocol hides the private key using a cryptographic processor embedded in the smartcard; this prevents the key from being stolen by simply being read off the media on which it is stored.
The following combinations of the above authentication mechanisms are supported, all with an optional escrow recovery key:
BitLocker is a logical volume encryption system. (A volume spans part of a hard disk drive, the whole drive or more than one drive.) When enabled, TPM and BitLocker can ensure the integrity of the trusted boot path (e.g. BIOS and boot sector), in order to prevent most offline physical attacks and boot sector malware.
In order for BitLocker to encrypt the volume holding the operating system, at least two NTFS-formatted volumes are required: one for the operating system (usually C:) and another with a minimum size of 100 MB, which remains unencrypted and boots the operating system. (In case of Windows Vista and Windows Server 2008, however, the volume's minimum size is 1.5 GB and must have a drive letter.) Unlike previous versions of Windows, Vista's "diskpart" command-line tool includes the ability to shrink the size of an NTFS volume so that this volume may be created from already allocated space. A tool called the BitLocker Drive Preparation Tool is also available from Microsoft that allows an existing volume on Windows Vista to be shrunk to make room for a new boot volume and for the necessary bootstrapping files to be transferred to it.
Once an alternate boot partition has been created, the TPM module needs to be initialized (assuming that this feature is being used), after which the required disk-encryption key protection mechanisms such as TPM, PIN or USB key are configured. The volume is then encrypted as a background task, something that may take a considerable amount of time with a large disk as every logical sector is read, encrypted and rewritten back to disk. The keys are only protected after the whole volume has been encrypted when the volume is considered secure. BitLocker uses a low-level device driver to encrypt and decrypt all file operations, making interaction with the encrypted volume transparent to applications running on the platform.
Encrypting File System (EFS) may be used in conjunction with BitLocker to provide protection once the operating system is running. Protection of the files from processes and users within the operating system can only be performed using encryption software that operates within Windows, such as EFS. BitLocker and EFS, therefore, offer protection against different classes of attacks.
In Active Directory environments, BitLocker supports optional key escrow to Active Directory, although a schema update may be required for this to work (i.e. if the Active Directory Services are hosted on a Windows version previous to Windows Server 2008).
BitLocker and other full disk encryption systems can be attacked by a rogue boot manager. Once the malicious bootloader captures the secret, it can decrypt the Volume Master Key (VMK), which would then allow access to decrypt or modify any information on an encrypted hard disk. By configuring a TPM to protect the trusted boot pathway, including the BIOS and boot sector, BitLocker can mitigate this threat. (Note that some non-malicious changes to the boot path may cause a Platform Configuration Register check to fail, and thereby generate a false warning.)
According to Microsoft sources, BitLocker does not contain an intentionally built-in backdoor; without which there is no way for law enforcement to have a guaranteed passage to the data on the user's drives that is provided by Microsoft. In 2006 the UK Home Office expressed concern over the lack of a backdoor and tried entering into talks with Microsoft to get one introduced, although Microsoft developer Niels Ferguson and other Microsoft spokesmen state that they will not grant the wish to have one added. Microsoft engineers have said that FBI agents also put pressure on them in numerous meetings in order to add a backdoor, although no formal, written request was ever made; Microsoft engineers eventually suggested to the FBI that agents should look for the hard copy of the key that the BitLocker program suggests its users to make. Although the AES encryption algorithm used in BitLocker is in the public domain, its implementation in BitLocker, as well as other components of the software, are proprietary; however, the code is available for scrutiny by Microsoft partners and enterprises, subject to a non-disclosure agreement.
The "Transparent operation mode" and "User authentication mode" of BitLocker use TPM hardware to detect if there are unauthorized changes to the pre-boot environment, including the BIOS and MBR. If any unauthorized changes are detected, BitLocker requests a recovery key on a USB device. This cryptographic secret is used to decrypt the Volume Master Key (VMK) and allow the bootup process to continue.
Nevertheless, in February 2008, a group of security researchers published details of a so-called "cold boot attack" that allows full disk encryption systems such as BitLocker to be compromised by booting the machine off removable media, such as a USB drive, into another operating system, then dumping the contents of pre-boot memory. The attack relies on the fact that DRAM retains information for up to several minutes (or even longer if cooled) after power has been removed. There is the Bress/Menz device described in US Patent 9,514,789 that can accomplish this type of attack. Use of a TPM alone does not offer any protection, as the keys are held in memory while Windows is running. Similar full disk encryption mechanisms of other vendors and other operating systems, including Linux and Mac OS X, are vulnerable to the same attack. The authors recommend that computers be powered down when not in physical control of the owner (rather than be left in a sleep mode) and that the encryption software be configured to require a password to boot the machine.
Once a BitLocker-protected machine is running, its keys are stored in memory where they may be susceptible to attack by a process that can access physical memory, for example, through a 1394 or Thunderbolt DMA channel. Starting with Windows 10 version 1803, Microsoft added a new feature called "Kernel DMA Protection" to BitLocker, against DMA attacks via Thunderbolt 3 ports.
Starting with Windows 8 and Windows Server 2012, Microsoft removed the Elephant Diffuser from the BitLocker scheme for no declared reason. Dan Rosendorf's research shows that removing the Elephant Diffuser had an "undeniably negative impact" on the security of BitLocker encryption against a targeted attack. Microsoft later cited performance concerns, and noncompliance with the Federal Information Processing Standards (FIPS), to justify the diffuser's removal. Starting with Windows 10 version 1511, however, Microsoft added a new FIPS-compliant XTS-AES encryption algorithm to BitLocker.
On 10 November 2015, Microsoft released a security update to mitigate a security vulnerability in BitLocker that allowed authentication to be bypassed by employing a malicious Kerberos key distribution center, if the attacker had physical access to the machine, the machine was part of a domain and had no PIN or USB protection.
In October 2017, it was reported that a flaw (ROCA vulnerability) in a code library developed by Infineon, which had been in widespread use in security products such as smartcards and TPMs, enabled private keys to be inferred from public keys. This could allow an attacker to bypass BitLocker encryption when an affected TPM chip is used. Microsoft released an updated version of the firmware for Infineon TPM chips that fixes the flaw via Windows Update.
- Features new to Windows Vista
- List of Microsoft Windows components
- Vista IO technologies
- Next-Generation Secure Computing Base
- Hakala, Trudy (January 29, 2020). "What's new in Windows 10, versions 1507 and 1511". TechNet. Microsoft. Retrieved March 7, 2020.
- "Windows BitLocker Drive Encryption Frequently Asked Questions". TechNet Library. Microsoft. March 22, 2012. Retrieved March 7, 2020.
- Ferguson, Niels (August 2006). "AES-CBC + Elephant Diffuser: A Disk Encryption Algorithm for Windows Vista" (PDF). Microsoft. Retrieved March 7, 2020. Cite journal requires
- Biddle, Peter (2004). "Next-Generation Secure Computing Base". Microsoft. Archived from the original (PPT) on August 27, 2006. Retrieved March 7, 2020.
- Thurrott, Paul (September 9, 2005). "Pre-PDC Exclusive: Windows Vista Product Editions". Supersite for Windows. Penton. Archived from the original on April 2, 2015. Retrieved March 7, 2020.
- Microsoft (April 22, 2005). "Secure Startup–Full Volume Encryption: Technical Overview" (DOC). Retrieved March 7, 2020.
- Microsoft (April 21, 2005). "Secure Startup – Full Volume Encryption: Executive Overview" (DOC). Retrieved March 7, 2020.
- "What's New in BitLocker". TechNet Library. Microsoft. August 31, 2016. Retrieved March 7, 2020.
- "Compare Windows 10 Editions". Windows for Business. Microsoft. Retrieved March 7, 2020.
- "BitLocker Drive Encryption in Windows Vista". TechNet. Microsoft. Archived from the original on November 17, 2016. Retrieved March 7, 2020.
- "BitLocker Drive Encryption Overview". TechNet. Microsoft. November 17, 2009. Retrieved March 7, 2020.
- Hynes, Byron (September 8, 2016). "Advances in BitLocker Drive Encryption". TechNet Magazine. Microsoft. Retrieved March 7, 2020.
- "Description of BitLocker To Go Reader". Microsoft. Archived from the original on September 24, 2019. Retrieved April 25, 2017.
- "Enabling BitLocker by Using the Command Line". TechNet. Microsoft. September 12, 2012. Retrieved March 7, 2020.
- "Encrypted Hard Drive". TechNet. Microsoft. August 31, 2016. Retrieved March 7, 2020.
- "Encrypted Hard Drive Device Guide". MSDN. Microsoft. June 1, 2017. Retrieved March 7, 2020.
- "BitLocker". TechNet. Microsoft. Retrieved March 7, 2020.
- "Windows To Go: Frequently Asked Questions". TechNet. Microsoft. October 23, 2013. Retrieved March 7, 2020.
- "Device Encryption". Device Encryption. Microsoft. November 18, 2015. Retrieved March 7, 2020.
- Cunningham, Andrew (October 17, 2013). "Windows 8.1 includes seamless, automatic disk encryption—if your PC supports it". Ars Technica. Condé Nast. Retrieved March 7, 2020.
- "Help protect your files with device encryption". Windows Help portal. Microsoft. Archived from the original on May 2, 2016. Retrieved March 7, 2020.
- Thurrott, Paul (June 4, 2013). "In Blue: Device Encryption". Paul Thurrott's SuperSite for Windows. Penton Media. Archived from the original on June 9, 2013. Retrieved March 7, 2020.
- "BitLocker drive encryption in Windows 10 for OEMs". docs.microsoft.com. November 16, 2018. Retrieved March 7, 2020.
- "September 24, 2019—KB4516071 (OS Build 16299.1420)". support.microsoft.com. Retrieved March 7, 2020.
- Cimpanu, Catalin (November 5, 2018). "Flaws in self-encrypting SSDs let attackers bypass disk encryption". www.zdnet.com. Retrieved March 7, 2020.
- "BitLocker Drive Encryption". Data Encryption Toolkit for Mobile PCs: Security Analysis. Microsoft. April 4, 2007. Archived from the original on October 23, 2007. Retrieved March 7, 2020.
- "ProtectKeyWithTPM method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. March 31, 2018. Retrieved March 7, 2020.
- "ProtectKeyWithTPMAndPIN method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. March 31, 2018. Retrieved March 7, 2020.
- "ProtectKeyWithTPMAndPINAndStartupKey method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. March 31, 2018. Retrieved March 7, 2020.
- "ProtectKeyWithTPMAndStartupKey method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. March 31, 2018. Retrieved March 7, 2020.
- "ProtectKeyWithExternalKey method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. March 31, 2018. Retrieved March 7, 2020.
- "ProtectKeyWithNumericalPassword method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. March 31, 2018. Retrieved March 7, 2020.
- "BitLocker Drive Encryption in Windows 7: Frequently Asked Questions". TechNet. Microsoft. September 12, 2012. Retrieved March 7, 2020.
- "Windows BitLocker Drive Encryption Step-by-Step Guide". TechNet. Microsoft. July 2, 2012. Retrieved March 7, 2020.
- "Description of the BitLocker Drive Preparation Tool". Microsoft. December 21, 2011. Retrieved March 7, 2020.
- Andrew, Bettany; Halsey, Mike (2013). Exam Ref 70-687: Configuring Windows 8 (1 ed.). Microsoft Press. p. 307. ISBN 978-0-7356-7392-2. OCLC 851209981.
- Jerry, Honeycutt (2012). Introducing Windows 8: An Overview for IT professionals. Microsoft. p. 121. ISBN 978-0-7356-7050-1. OCLC 819519777.
- Ou, George (February 28, 2007). "Prevent data theft with Windows Vista's Encrypted File System (EFS) and BitLocker". TechRepublic. CBS Interactive. Retrieved March 7, 2020.
- "Back-door nonsense". System Integrity Team Blog. Microsoft. March 2, 2006. Retrieved March 7, 2020.
- Stone-Lee, Ollie (February 16, 2006). "UK holds Microsoft security talks". BBC. Retrieved March 7, 2020.
- Evers, Joris (March 6, 2006). "Microsoft: Vista won't get a backdoor". CNET. CBS Interactive. Retrieved March 7, 2020.
- Franceschi-Bicchierai, Lorenzo (September 11, 2013). "Did the FBI Lean On Microsoft for Access to Its Encryption Software?". Mashable. Retrieved March 7, 2020.
- Thurrott, Paul (June 10, 2015). "No Back Doors: Microsoft Opens Windows Source Code to EU Governments". Petri. Retrieved March 7, 2020.
- "Shared Source Initiative". www.microsoft.com. Retrieved March 7, 2020.
- Byron, Hynes (September 7, 2016). "Keys to Protecting Data with BitLocker Drive Encryption". TechNet Magazine. Microsoft. Retrieved March 7, 2020.
- Halderman, J. Alex; Schoen, Seth D.; Heninger, Nadia; Clarkson, William; Paul, William; Calandrino, Joseph A.; Feldman, Ariel J.; Appelbaum, Jacob; Felten, Edward W (February 21, 2008). Lest We Remember: Cold Boot Attacks on Encryption Keys (PDF) (Thesis). Princeton University. Retrieved March 7, 2020.
- "Systems and methods for safely moving short term memory devices while preserving, protecting and examining their digital data". Retrieved March 7, 2020.
- "Blocking the SBP-2 driver and Thunderbolt controllers to reduce 1394 DMA and Thunderbolt DMA threats to BitLocker". Microsoft. November 7, 2018. Retrieved March 7, 2020.
- "Kernel DMA Protection for Thunderbolt™ 3". Microsoft. March 26, 2019. Retrieved March 16, 2020.
- "BitLocker Overview". technet.microsoft.com. August 31, 2016. Retrieved March 7, 2020.
- Rosendorf, Dan (May 23, 2013). "Bitlocker: A little about the internals and what changed in Windows 8" (PDF). Retrieved March 7, 2020.
- Lee, Micah (June 4, 2015). "Microsoft Gives Details About Its Controversial Disk Encryption". The Intercept. Retrieved March 7, 2020.
- "Microsoft Security Bulletin MS15-122 – Important". Security TechCenter. Microsoft. October 11, 2017. Retrieved March 7, 2020.
- Goodin, Dan (October 16, 2017). "Millions of high-security crypto keys crippled by newly discovered flaw". Ars Technica. Condé Nast. Retrieved March 7, 2020.
- Busvine, Douglas (October 16, 2017). "Infineon says has fixed encryption flaw found by researchers". Reuters. Retrieved March 7, 2020.
|Wikibooks has a book on the topic of: Guide to Windows Commands|