Secure erase
Secure erase is a context-dependent label for a storage erasure procedure whose command, scope and assurance must be specified.
Do not treat a utility's label as a protocol guarantee. Distinguish an ATA SECURITY ERASE operation, NVMe Format NVM and NVMe Sanitize, and check the selected device's documentation. NIST separates sanitization methods from particular techniques; a method's suitability depends on the medium and confidentiality requirement.
For NVMe Format NVM, the SES field selects the erase request; User Data Erase need not mean physical flash-block erasure. Check scope independently of the utility's device-path label.
For legacy ATA devices, distinguish the address range visible to a host overwrite from the scope of a device erase. HPA and DCO can restrict visibility; the openSeaChest maintainer explicitly distinguishes their treatment in normal and enhanced ATA Security Erase and Sanitize. Do not extrapolate that historical HPA/DCO distinction to newer AMAC behavior. [6] [7]
Relations
- related
- Data sanitization, NVMe sanitize, Self-encrypting drive (SED), Cryptographic erase, TRIM, NVMe Format NVM, Host Protected Area (HPA), Device Configuration Overlay (DCO), Accessible Max Address Configuration (AMAC)
Limitations
- File deletion, ordinary discard and a user-addressable overwrite are not interchangeable with an approved purge technique. [1, 3]
Citations
- NIST SP 800-88 Rev. 2 (2025), Guidelines for Media Sanitization, sections 3 and 4.5
- util-linux: blkdiscard documentation
- Seagate openSeaChest maintainer clarification (7 January 2021), discussion 52: HPA/DCO versus AMAC erase scope
- Seagate openSeaChest ATA Security Feature guide (last edited 11 February 2026), Security Erase