This section explains the overwrite and firmware methods available in DriveErase. Method selection must consider the device’s media, interface, controller path, condition, intended disposition, and required assurance.
A method label identifies the requested technique. The final report determines whether the operation completed, whether required verification passed, which fallback path was used, and whether a standards-related compliance result was established.
-
How Overwrite-Based Sanitization Works
-
NIST SP 800-88 Rev. 2 Clear Overwrite
-
IEEE 2883-2022 Clear Overwrite
-
DoD and HMG Legacy Overwrite Profiles
-
RCMP, NAVSO, and NCSC Legacy Overwrite Profiles
-
Schneier, Gutmann, and Random Overwrite Profiles
-
Overwrite Verification, Coverage, and Incomplete Results
-
How Firmware-Based Sanitization Works
-
Firmware-Based Clear under NIST SP 800-88 Rev. 2 and IEEE 2883-2022
-
Firmware-Based Purge under NIST SP 800-88 Rev. 2 and IEEE 2883-2022
-
SATA/ATA SSD Secure Erase
-
NVMe Format NVM Secure Erase
-
SCSI Sanitize Block Erase
-
Firmware-Based Sanitization with Overwrite Fallback
