Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


05:20 PM
Rob Enderle
Rob Enderle

TCG Drive Encryption Goes Mainstream

The Trusted Computing Group's newly released specifications for the management of hard drive encryption are now being adopted by a number of vendors -- Seagate arguably the most prominent, but also including Fujitsu, Toshiba, Hitachi, Wave Systems, CryptoMill, WinMagic, Secude, and McAfee.

The Trusted Computing Group's newly released specifications for the management of hard drive encryption are now being adopted by a number of vendors -- Seagate arguably the most prominent, but also including Fujitsu, Toshiba, Hitachi, Wave Systems, CryptoMill, WinMagic, Secude, and McAfee.These specifications (PDF) focus on how the drives are managed by host-side applications, and should provide the dual benefit of increased performance with encrypted drives, driving a wider implementation of this security technology. What this enables is vastly lowered barriers to entry for related products because the standards allow hardware-encrypted drives from a wide variety of conforming vendors to be plug-compatible.

This, in turn, has the dual benefit of lowering costs through competitive standardization and increasing adoption of the related technology. The National Security Agency, which participated in this effort, has issued a letter of acceptance for one of the participating vendors, demonstrating that it's also behind this effort.

Standard Advantages Advantages to this TCG Hard Drive encryption approach include improved setup time, enhanced scalability, interoperability, increased security over keys, portability, and platform breadth. Let's take a look at each.

Setup Time: With this class of encryption product, data is encrypted from the time the drive is manufactured. Turning on the security is nearly instantaneous because the drive is already encrypted. With other forms of encryption, the drive must first become encrypted when the feature is turned on, requiring the encryption of the then-resident drive contents (which can be very time-consuming).

Scalability: For more traditional CPU-based solutions, when multiple drives are introduced, they will bottleneck once the capacity of the CPU and chipset is reached. With drive- based encryption, the restricting function is handled by the drive and scales up in performance with each drive added.

Interoperability: Chipsets vary greatly between processor vendors, and have since the late '90s. Processor/chipset-based approaches tend to tie the drives to the chipset and processor solution, and have difficulty moving between solutions (if at all) without performance impact. The TCG approach is plug-compatible across vendors, virtually eliminating this problem.

Key Security: With CPU/chipset solutions, the keys for each hard drive need to be managed by the host-side application. They are generally stored in memory so they can be made accessible to the CPU. This leaves the keys vulnerable to kernel-level attacks and others, like the Princeton cold-boot attack. With the TCG method, the keys are sent to the hard drive during the preboot -- typically using a security-hardened application. This makes them more difficult to compromise.

Portability: Drives based on the TCG specification can be moved between PCs because, unlike other methods, there is no system-level dependency. This is because the encryption engine is inside the drive and not dependent on the unique aspects of any one PC configuration.

RAID Performance: Chipset/CPU configurations are particularly painful on servers or multiple-drive desktops because they shift the encryption load to the processor and chipset, which generally is already running at a high-level load in such a configuration. That typically leads to a significant bottleneck.

Wrapping Up The TCG's new specifications, as well as drives from the vendors now supporting them, have been needed for some time and address a number of high-performance, interoperability, and security concerns. This change represents a significant improvement in an industry (storage) that doesn't have many of them in any given year.

-- Rob Enderle is president and founder of Enderle Group. Special to Dark Reading.

Comment  | 
Print  | 
More Insights
Threaded  |  Newest First  |  Oldest First
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-12-04
An Ubuntu-specific patch in PulseAudio created a race condition where the snap policy module would fail to identify a client connection from a snap as coming from a snap if SCM_CREDENTIALS were missing, allowing the snap to connect to PulseAudio without proper confinement. This could be exploited by...
PUBLISHED: 2020-12-03
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
PUBLISHED: 2020-12-03
In the PrestaShop module "productcomments" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
PUBLISHED: 2020-12-03
HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.
PUBLISHED: 2020-12-03
An issue was discovered in the Linux kernel before 5.9.3. io_uring takes a non-refcounted reference to the files_struct of the process that submitted a request, causing execve() to incorrectly optimize unshare_fd(), aka CID-0f2122045b94.