Self-encrypting drive (SED)
A self-encrypting drive encrypts stored data internally using integrated cryptographic and key-management capabilities.
Self-encryption does not by itself establish an acceptable cryptographic erase. The encryption must have covered the target sensitive data, and the applicable keys must be sanitizable. NIST also calls for scrutiny of backed-up or escrowed keys and the required lifetime of confidentiality. [1]
SP 800-88 Rev. 2 cites ISO/IEC 27040 for a minimum security strength of 128 bits for the algorithm and mode, and for random-source entropy of at least the key length. ECB mode is excluded, and federal use requires modules validated to the current FIPS 140 standard. [1]
The erased key may be the data-encryption key or a wrapping or derivation key above it. Erasing any one of these leaves the dependent ciphertext undecryptable, provided no other copy of that key survives. [1]
In the Linux Opal interface, secure erase of a locking range reads that range's active-key reference and issues GenKey on it, so a new media key replaces the old one. The interface carries keys of up to 256 bytes and up to 9 locking ranges, each with its own active key. [3] [4]
Relations
Advantages
- Replacing a media key can sanitize a range with high assurance much faster than overwriting every block. [1, 3]
Limitations
- An encryption feature label is not evidence that every relevant key copy has been sanitized. [1]
- Ciphertext stays on the media after the key is erased, so confidentiality depends on the algorithm resisting attack for as long as the data must stay secret. [1]
Citations
- NIST SP 800-88 Rev. 2 (2025), Guidelines for Media Sanitization, sections 3.2 and 4.5
- Linux v6.12 block/sed-opal.c: locking-range secure erase via active key and GenKey
- Linux v6.12 include/uapi/linux/sed-opal.h: Opal key length, locking ranges and erase ioctls
Further reading
Sources & caveats
- nist-r2 is NIST SP 800-88 Rev. 2 (2025), read in sections 3.2 and 4.5.
- linux-opal-c and linux-opal-h are block/sed-opal.c and include/uapi/linux/sed-opal.h at Linux v6.12, read in the erase and key paths.
- 128 bits, the entropy rule, the ECB exclusion and the key types come from nist-r2.
- 256 bytes, 9 locking ranges and the GenKey erase sequence come from linux-opal-h and linux-opal-c.