IT tutorials
 
Technology
 

Managing Windows Server 2012 Storage and File Systems : TPM and BitLocker Drive Encryption (part 5) - Hardware encrypted drives, Optimizing encryption

11/14/2013 2:49:57 AM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

4. Using hardware encryption, secure boot, and Network Unlock

BitLocker Drive Encryption has other enhancements for Windows 8 and Windows Server 2012 as well. You can manage most of these enhancements using the Administrative Templates policies for Computer Configuration under Windows Components\BitLocker Drive Encryption.

4.1 Hardware encrypted drives

Windows 8 and Windows Server 2012 add support for disk drives with hardware encryption (referred to as encrypted hard drives). Encryption in hardware is faster and moves the processing burden from the computer’s processor to the hardware processor on the hard disk. By default, if a computer has hardware encryption, Windows 8 will use it with BitLocker. To use encrypted hard drives with Windows Server 2012, you must add the Enhanced Storage feature.

When the operating system initializes an encrypted hard drive, it activates a security mode that allows the drive controller to generate a media key for every volume created on the encrypted hard drive. This media key set is used to encrypt every byte of data written to the drive and decrypt every byte of data read from the drive. The key set consists of the following:

  • A data-encryption key This key is used to encrypt all data on the drive. The key is stored in an encrypted format in a random location on the drive.

  • An authentication key This key is used to unlock data on the drive. A hash of the authentication key is stored on the drive and used to decrypt the data-encryption key.

An encrypted drive is locked and inaccessible when it is in a powered-off state. When the drive is powered on (as part of the computer startup), the drive remains locked until the authentication key is used to decrypt the data-encryption key. All data read from or written to the drive passes through the encryption engine. If the data-encryption key needs to be changed or erased, the drive doesn’t need to be re-encrypted. Instead, the encryption engine creates a new authentication key and then re-encrypts the data-encryption key. Afterward, the data-encryption key can be unlocked with the new authentication key and data can be read from and written to the drive as before.

Before you enable hardware encryption there are some important caveats. With data drives, the drive must be in an uninitialized state and in a security-inactive state. With system drives, the drive must be in an uninitialized state and in a security-inactive state, and the computer must always boot natively from Unified Extensible Firmware Interface (UEFI). Further, neither data drives nor system drives can be attached to RAID controllers. Although future updates or service packs could change or remove these restrictions, these are the restrictions as of the time I wrote this.

Important

System drives must boot natively from UEFI 2.3.1 or later and have a defined EFI_STORAGE_SECURITY_COMMAND_PROTOCOL. System drives must also have the Compatibility Support Module (CSM) disabled in UEFI.

4.2 Optimizing encryption

In Group Policy, you can precisely control whether to permit software-based encryption when hardware encryption is not available and whether to restrict encryption to those algorithms and cipher strengths supported by hardware. To do this, use Group Policy to enable hardware-based encryption for system drives, data drives, or both.

You can enable hardware-based encryption for data drives using the Configure Use Of Hardware-Based Encryption For Fixed Data Drives policy, shown in Figure 11. When the policy is enabled, you must specifically allow software-based encryption when hardware-based encryption isn’t available. You also have the option of restricting the encryption algorithms used to a specific subset. Keep in mind that the encryption algorithm is set when a drive is partitioned and that the Choose Drive Encryption Method And Cipher Strength policy doesn’t apply to hardware-based encryption.

Enable and configure the use of hardware-based encryption for fixed data drives.
Figure 11. Enable and configure the use of hardware-based encryption for fixed data drives.

You can enable hardware-based encryption for system drives using the Configure Use Of Hardware-Based Encryption For Operating System Drives policy, shown in Figure 12. As with data drives, when the policy is enabled, you must keep in mind the following:

  • You must specifically allow software-based encryption when hardware-based encryption isn’t available.

  • You have the option of restricting the encryption algorithms used to a specific subset.

  • You know the Choose Drive Encryption Method And Cipher Strength policy doesn’t apply to hardware-based encryption.

Finally, as necessary, use the Configure Use Of Hardware-Based Encryption For Removable Data Drives policy to control whether software-based encryption is permitted when hardware encryption is not available and whether to restrict encryption to those algorithms and cipher strengths supported by hardware.

Enable and configure the use of hardware-based encryption for operating system drives.

Figure 12. Enable and configure the use of hardware-based encryption for operating system drives.
 
Others
 
- Managing Windows Server 2012 Storage and File Systems : TPM and BitLocker Drive Encryption (part 4) - Introducing BitLocker Drive Encryption
- Managing Windows Server 2012 Storage and File Systems : TPM and BitLocker Drive Encryption (part 3) - Clearing the TPM, Changing the TPM owner password
- Managing Windows Server 2012 Storage and File Systems : TPM and BitLocker Drive Encryption (part 2) - Preparing and initializing a TPM for first use
- Managing Windows Server 2012 Storage and File Systems : TPM and BitLocker Drive Encryption (part 1) - Understanding TPM states and tools
- Dynamics AX 2009 Monitoring Tools (part 3) - Code Profiler Tool
- Dynamics AX 2009 Monitoring Tools (part 2) - Monitoring Database Activity
- Dynamics AX 2009 Monitoring Tools (part 1) - Tracing Options and Other Tracing Activities
- Troubleshooting Exchange Server 2010 : Troubleshooting Mailbox Servers
- Troubleshooting Exchange Server 2010 : General Server Troubleshooting Tools (part 2) - Test-ServiceHealth,
- Troubleshooting Exchange Server 2010 : General Server Troubleshooting Tools (part 1) - Event Viewer, Test-SystemHealth
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us