Jump to content

BitLocker

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 122.106.249.198 (talk) at 10:55, 12 November 2015 (→Security concerns). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Infobox Windows component BitLocker (codenamed Cornerstone[1][2] and formerly known as Secure Startup[3]) is a full disk encryption feature included with select editions of Windows Vista and later. 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) mode with a 128-bit or 256-bit key, and also (on Windows Vista and Windows 7) the Elephant diffuser for additional disk encryption-specific security not provided by AES.[4][5] CBC is not used over the whole disk, only for each individual disk sector.

History

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 in the event that 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.[1] 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.[3][6] BitLocker was briefly called Secure Startup prior to Windows Vista being released to manufacturing.[3][6]

Availability

BitLocker is available on the Ultimate and Enterprise editions of Windows Vista and Windows 7, the Pro and Enterprise editions of Windows 8 and later,[7][8] and Windows Server 2008 and later. Initially, the graphical BitLocker interface in Windows Vista could only encrypt the operating system volume; encrypting other volumes could be achieved through an included command-line tool.[9] 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.[10]

The latest version of BitLocker, first 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.[11]

Bitlocker is also compatible with the portable instances of Windows 8 Enterprise edition installed through Windows To Go.[12]

Microsoft eDrive is a specification for storage devices to allow compliant storage devices to use its built-in encryption.

Device encryption

Windows Mobile 6.5, Windows RT and core edition of Windows 8.1 include device encryption, a feature-limited version of BitLocker that encrypts the whole system.[13][14][15] 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,[15] which requires solid-state drives, non-removable RAM (to protect against cold boot attacks) and a TPM 2.0 chip.[13][16]

Encryption modes

There are three authentication mechanisms that can be used as building blocks to implement BitLocker encryption:[17]

  • Transparent operation mode: This mode uses the capabilities of TPM 1.2 hardware to provide for a transparent user experience—the user powers up and logs into Windows as normal. 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.
  • 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 USB key may be provided by a CCID device 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, thus preventing the key file from being stolen on a compromised system by simply copying the key file from the USB drive and stealing it.

The following combinations of the above authentication mechanisms are supported, all with an optional escrow recovery key:[18]

Operation

BitLocker is a logical volume encryption system. A volume may or may not be an entire hard disk drive, or it can span one or more physical drives. Also, when enabled, TPM and BitLocker can ensure the integrity of the trusted boot path (e.g. BIOS, boot sector, etc.), in order to prevent most offline physical attacks, boot sector malware, etc.

In order for BitLocker to operate, at least two NTFS-formatted volumes are required: one for the operating system (usually C:) and another with a minimum size of 100 MB[24] from which the operating system boots. BitLocker requires the boot volume to remain unencrypted—on Windows Vista this volume must be assigned a drive letter, while on Windows 7 that is not required. Unlike previous versions of Windows, Vista's "diskpart" command-line tool includes the ability to shrink the size of an NTFS volume so that the system volume for BitLocker 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;[25] Windows 7 creates the secondary boot volume by default, even if BitLocker is not used initially.

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 kernel 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.[26]

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 bootmanager. 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 PCR check to fail, and thereby generate a false warning.)[27]

To use BitLocker on the primary system device, Compatibility Support Module (CSM) needs to be disabled in UEFI.

Security concerns

According to Microsoft sources,[28] BitLocker does not contain an intentionally built-in backdoor; without a backdoor 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. The lack of any backdoor has been a concern to the UK Home Office,[29] which 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.[30] 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.[31] 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.[citation needed]

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.[32]

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.[33] 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. Use of a TPM alone does not offer any protection, as the keys are held in memory while Windows is running, although two-factor authentication, i.e. using TPM together with a PIN, offers better protection for machines that are not powered on when physical access to them is obtained.[citation needed] Similar full disk encryption mechanisms of other vendors and other operating systems, including Linux and Mac OS X, are vulnerable to the same attack.[33] The authors recommend that computers be powered down when not in physical control of the owner (rather than be left in a "sleep" state) 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 is able to access physical memory, for example, through a 1394 or Thunderbolt DMA channel.[34] Any cryptographic material in memory is at risk from this attack, which therefore is not specific to BitLocker.

Starting with Windows 8 and Windows Server 2012 Microsoft removed the Elephant Diffuser from the BitLocker scheme for no declared reason.[35] 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.[36]

MS15-122 closed a security vulnerability in Bitlocker that allowed authentication to be bypassed by employing a malicious Kerberos KDC.[37]

See also

References

  1. ^ a b Biddle, Peter (2004). "Next-Generation Secure Computing Base". Microsoft. Archived from the original (PPT) on August 27, 2006. Retrieved January 30, 2015.
  2. ^ Thurrott, Paul (September 9, 2005). "Pre-PDC Exclusive: Windows Vista Product Editions". Supersite for Windows. Penton. Retrieved March 14, 2015.
  3. ^ a b c Microsoft (April 22, 2005). "Secure Startup - Full Volume Encryption: Technical Overview" (DOC). Retrieved March 14, 2015.
  4. ^ "Windows BitLocker Drive Encryption Frequently Asked Questions". TechNet Library. Microsoft. March 22, 2012. Retrieved September 5, 2007.
  5. ^ Ferguson, Niels (August 2006). "AES-CBC + Elephant Diffuser: A Disk Encryption Algorithm for Windows Vista" (PDF). Microsoft. Retrieved February 22, 2008. {{cite journal}}: Cite journal requires |journal= (help)
  6. ^ a b Microsoft (April 21, 2005). "Secure Startup - Full Volume Encryption: Executive Overview" (DOC). Retrieved June 9, 2015.
  7. ^ "What's New in BitLocker for Windows 8 and Windows Server 2012". TechNet Library. Microsoft. February 15, 2012. Retrieved March 2, 2012.
  8. ^ "Windows BitLocker Drive Encryption Frequently Asked Questions". TechNet Library. Microsoft. March 22, 2012. Retrieved September 5, 2007.
  9. ^ "BitLocker Drive Encryption Provider". MSDN Library. Microsoft. February 19, 2008. Retrieved February 22, 2008.
  10. ^ Hynes, Byron (June 2008). "Advances in BitLocker Drive Encryption". Technet Magazine. Microsoft. Retrieved July 18, 2008.
  11. ^ "Description of BitLocker To Go Reader". Microsoft. Retrieved September 7, 2013.
  12. ^ Windows To Go: Frequently Asked Questions - Can I use BitLocker to protect my Windows To Go drive?
  13. ^ a b "Device Encryption". Windows Mobile 6.5 Dev Center. Microsoft. April 8, 2010. Retrieved July 6, 2014.
  14. ^ Cunningham, Andrew (October 17, 2013). "Windows 8.1 includes seamless, automatic disk encryption—if your PC supports it". Ars Technica. Condé Nast. Retrieved July 6, 2014.
  15. ^ a b "Help protect your files with device encryption". Windows Help portal. Microsoft. Retrieved July 6, 2014.
  16. ^ Thurrott, Paul (June 4, 2013). "In Blue: Device Encryption". Paul Thurrott's SuperSite for Windows. Penton Media. Retrieved June 10, 2013.
  17. ^ "BitLocker Drive Encryption". Data Encryption Toolkit for Mobile PCs: Security Analysis. Microsoft. April 4, 2007. Retrieved September 5, 2007.
  18. ^ "ProtectKeyWithNumericalPassword method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. February 19, 2008. Retrieved July 18, 2008.
  19. ^ "ProtectKeyWithTPM method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. February 19, 2008. Retrieved July 18, 2008.
  20. ^ "ProtectKeyWithTPMAndPIN method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. February 19, 2008. Retrieved July 18, 2008.
  21. ^ "ProtectKeyWithTPMAndPINAndStartupKey method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. February 19, 2008. Retrieved July 18, 2008.
  22. ^ "ProtectKeyWithTPMAndStartupKey method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. February 19, 2008. Retrieved July 18, 2008.
  23. ^ "ProtectKeyWithExternalKey method of the Win32_EncryptableVolume class". MSDN Library. Microsoft. February 19, 2008. Retrieved July 18, 2008.
  24. ^ "BitLocker Drive Encryption in Windows 7: Frequently Asked Questions". TechNet Library. Microsoft. March 22, 2012. Retrieved April 7, 2012.
  25. ^ "Description of the BitLocker Drive Preparation Tool". Microsoft. September 7, 2007. Archived from the original on February 19, 2008. Retrieved February 22, 2008.
  26. ^ Ou, George (June 8, 2007). "Prevent data theft with Windows Vista's Encrypted File System (EFS) and BitLocker". TechRepublic. CBS Interactive. Retrieved September 7, 2013.
  27. ^ "BitLocker Drive Encryption in Windows 7: Frequently Asked Questions". TechNet Library. Microsoft. March 22, 2012. Retrieved March 16, 2013.
  28. ^ "Back-door nonsense". System Integrity Team Blog. Microsoft. March 2, 2006. Retrieved June 19, 2006.
  29. ^ Stone-Lee, Ollie (February 16, 2006). "UK holds Microsoft security talks". BBC. Retrieved June 12, 2009.
  30. ^ Evers, Joris (March 3, 2006). "Microsoft: Vista won't get a backdoor". CNET. CBS Interactive. Retrieved May 1, 2008.
  31. ^ Did the FBI Lean On Microsoft for Access to Its Encryption Software?
  32. ^ Byron, Hynes. "Keys to Protecting Data with BitLocker Drive Encryption". TechNet Magazine. Microsoft. Retrieved August 21, 2007.
  33. ^ a b 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). Princeton University. Retrieved February 22, 2008. {{cite journal}}: Cite journal requires |journal= (help)
  34. ^ "Blocking the SBP-2 driver and Thunderbolt controllers to reduce 1394 DMA and Thunderbolt DMA threats to BitLocker". Microsoft. March 4, 2011. Retrieved March 15, 2011.
  35. ^ http://technet.microsoft.com/en-us/library/hh831713.aspx
  36. ^ http://spi.unob.cz/presentations/23-May/07-Rosendorf%20The%C2%A0BitLocker%C2%A0Schema.pdf
  37. ^ https://technet.microsoft.com/library/security/MS15-122
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=BitLocker&oldid=690275116"