Content deleted Content added
m spelling (Wikipedia:Typo Team) |
Rescuing 1 sources and tagging 1 as dead.) #IABot (v2.0.9.5 |
||
(42 intermediate revisions by 26 users not shown) | |||
Line 1:
{{short description|Cryptographic hardware}}
{{NPOV language|date=April 2013}}
'''Hardware-based full disk encryption''' ('''FDE''') is available from many [[hard disk drive]] (HDD/[[Solid-state drive|SSD]]) vendors, including: [[Hitachi]], Integral Memory, iStorage Limited, [[Micron Technology|Micron]], [[Seagate Technology]], [[Samsung]], [[Toshiba]], [[ViaSat|Viasat UK]], and [[Western Digital]]
▲'''Hardware-based full disk encryption''' ('''FDE''') is available from many [[hard disk drive]] (HDD/[[Solid-state drive|SSD]]) vendors, including: [[Hitachi]], iStorage Limited, [[Seagate Technology]], [[Samsung]], [[Toshiba]], [[ViaSat|Viasat UK]], [[Western Digital]], [[Micron Technology|Micron]], [[OCZ Storage Solutions|OCZ]], [[SanDisk]], [[Samsung]], Integral Memory and USB vendors such as [[Yubikey]] or iStorage Limited. The [[symmetric-key algorithm|symmetric encryption key]] is maintained independently from the computer's [[Central processing unit|CPU]], thus allowing the complete data store to be encrypted and removing computer memory as a potential attack vector.
Hardware-FDE has two major components: the hardware encryptor and the data store.
Line 10 ⟶ 7:
#Hard disk drive (HDD) FDE (self-encrypting drive)
#Enclosed hard disk drive FDE
#Removable
#Bridge and [[Chipset]] (BC) FDE
Hardware designed for a particular purpose can often achieve better performance than [[disk encryption software]], and disk encryption hardware can be made more transparent to software than encryption done in software. As soon as the key has been
==
=== Hard disk drive FDE ===
Usually referred to as '''self-encrypting drive''' ('''SED''').
HDD FDE is made by HDD vendors using the [[Opal Storage Specification|OPAL]] and Enterprise standards developed by the [[Trusted Computing Group]].<ref>{{cite web |url=http://www.trustedcomputinggroup.org/solutions/data_protection |title=Trusted Computing Group Data Protection page |publisher=Trustedcomputinggroup.org |date= |access-date=2013-08-06 |url-status=dead |archive-url=https://
[[Hitachi]], [[Micron Technology|Micron]], [[Seagate Technology|Seagate]], [[Samsung]], and [[Toshiba]] are the disk drive manufacturers offering [[Trusted Computing Group
=== Enclosed hard disk drive FDE ===
Within a standard [[Harddrive#Form factors|hard drive form factor]] case the encryptor (BC), [[Cryptographic key|key]] store and a smaller form factor, commercially available, hard disk drive is enclosed.
*The enclosed hard disk drive's case can be [[tamper-evident]], so when
*The encryptors electronics including the [[Cryptographic key|key]] store and integral hard drive (if it is [[Solid-state drive|solid-state]]) can be protected by other [[Tamper resistance|tamper respondent]] measures.
*The key can be [[Crypto-shredding|purged]], allowing a user to prevent his [[Authentication factors#Authentication factors|authentication parameters]] being used without destroying the encrypted data. Later the same [[Cryptographic key|key]] can be re-loaded into the Enclosed hard disk drive FDE, to retrieve this data.
*Tampering is not an issue for SEDs as they cannot be read without the decryption key, regardless of access to the internal electronics {{Clarify|reason=see Talk page, decryption keys can be recovered from the internal electornics in several cases|date=July 2016}}.
=== Removable
The
*This is an improvement on removing [unencrypted] [[hard disk drive|hard drives]] from a [[computer]] and storing them in a [[safe]] when not in use.
*This design can be used to encrypt multiple [[hard disk drive|drives]] using the same [[Cryptographic key|key]].
*Generally they are not securely locked<ref>{{cite web |title=Sapphire Cipher Snap-In |url=https://www.addonics.com/products/ssna256eu.php |website=Addonics.com |publisher=Addonics |accessdate=2020-05-15 |archive-date=2020-12-01 |archive-url=https://web.archive.org/web/20201201214820/https://www.addonics.com/products/ssna256eu.php |url-status=dead }}</ref> so the drive's interface is open to attack.
=== Chipset FDE ===
The encryptor bridge and chipset (BC) is placed between the computer and the standard hard disk drive, encrypting every sector written to it.
Line 45 ⟶ 43:
Hardware-based encryption when built into the drive or within the drive enclosure is notably transparent to the user. The drive, except for bootup authentication, operates just like any drive, with no degradation in performance. There is no complication or performance overhead, unlike [[disk encryption software]], since all the encryption is invisible to the [[operating system]] and the host [[Central processing unit|computer's processor]].
The two main use cases are [[Data at
==={{anchor|Crypto erase}}Disk
[[Crypto-shredding]] is the practice of 'deleting' data by (only) deleting or overwriting the encryption keys.
When a cryptographic disk erasure (or crypto erase) command is given (with proper authentication credentials), the drive self-generates a new media encryption key and goes into a 'new drive' state.<ref>{{cite web |title=10 Reasons to Buy Self-Encrypting Drives
When [[Cryptographic key|keys]] are self-generated randomly, generally there is no method to store a copy to allow [[data recovery]]. In this case protecting this data from accidental loss or theft is achieved through a consistent and comprehensive data backup policy. The other method is for user-defined keys, for some Enclosed hard disk drive FDE,<ref>{{cite web |title=Eclypt Core Encrypted Internal Hard Drive |url=https://www.viasat.com/products/cybersecurity/data-at-rest-encryption/ |website=Viasat.com |publisher=Viasat |accessdate=2021-02-17 |date=2020}}</ref> to be generated externally and then loaded into the FDE.
===Protection from alternative boot methods===
Recent hardware models circumvents [[booting]] from other devices and allowing access by using a dual [[Master Boot Record]] (MBR) system whereby the MBR for the operating system and data files is all encrypted along with a special MBR which is required to boot the [[operating system]].
=== Vulnerabilities ===
When a computer with a self-encrypting drive is put into [[sleep mode]], the drive is powered down, but the encryption password is retained in memory so that the drive can be quickly resumed without requesting the password. An attacker can take advantage of this to gain easier physical access to the drive, for instance, by inserting extension cables.<ref name="sed-attacks" />
The firmware of the drive may be compromised<ref>{{cite
=== Criticism ===
Hardware solutions have
In addition, implementing system wide hardware-based full disk encryption is prohibitive for many companies due to the high cost of replacing existing hardware. This makes migrating to hardware encryption technologies more difficult and would generally require a clear migration and central management solution for both hardware- and software-based [[Disk encryption#Full disk encryption|full disk encryption]] solutions.<ref>{{cite
==See also==
* [[Disk encryption software]]
* [[Crypto-shredding]]
Line 79 ⟶ 78:
==References==
{{Reflist}}
[[Category:Disk encryption]]
|