Choose a Sanitization Approach and Method

DriveErase provides three sanitization approaches: Overwrite Based, Firmware Based, and Firmware + Fallback. The most appropriate choice depends on the storage technology, connection interface, device capabilities, and level of sanitization required.

A method that works well on a conventional magnetic hard drive may not provide equivalent coverage on an SSD. Before selecting an approach, confirm the device’s media type and bus in the Device List.

Overwrite Based

Overwrite-based sanitization writes a defined pattern sequence across the accessible logical range of the device. It is suitable for conventional HDDs and is the normal DriveErase approach for USB-attached storage and removable flash media.

Once Overwrite Based is selected, choose the required overwrite profile. DriveErase provides NIST SP 800-88 Clear, IEEE 2883-2022 Clear, several historical multi-pass algorithms, and random overwrite methods.

A modern single-pass Clear profile is often an appropriate choice for a functioning magnetic HDD. Additional passes increase the amount of data written and the time required, but do not automatically provide better coverage of inaccessible storage areas.

Overwrite Based is available in all editions.

Firmware Based

Firmware Based allows a compatible storage device to perform a sanitization operation using commands supported by its own controller.

DriveErase supports SATA/ATA SSD Secure Erase for compatible SATA SSDs, NVMe Format NVM Secure Erase for compatible NVMe devices, and SCSI Sanitize Block Erase for supported SAS SSDs.

These methods require Pro or a higher edition and an appropriate direct connection. USB adapters, some RAID controllers, and translated storage interfaces may prevent the required firmware commands from reaching the physical device.

Firmware sanitization is especially relevant for SSDs because ordinary logical overwriting does not necessarily reach internally remapped or over-provisioned flash memory.

Firmware + Fallback

Firmware + Fallback attempts the compatible firmware operation first. If it cannot complete, DriveErase can use the configured overwrite profile as an alternative.

This can be useful when the firmware capabilities of otherwise compatible SSDs are uncertain. However, a completed overwrite fallback does not provide the same assurance as a successfully completed firmware operation.

If device-level Purge is required, an overwrite fallback may not be an acceptable substitute. Always examine the recorded operation and actual compliance result before deciding that the device has been sanitized to the required level.

Selecting an appropriate method

For a conventional SATA or SAS HDD, an overwrite-based method is generally the normal choice. For a directly connected SATA SSD, NVMe device, or compatible SAS SSD, consider the available firmware method. For a USB flash drive or external SSD, remember that DriveErase can process the logical range but cannot necessarily reach all internally managed flash storage through the USB connection.

The Potential Compliance field indicates what the selected configuration may be capable of achieving. It is not a guarantee of a successful Clear or Purge result.

After execution, check which method actually completed, whether verification succeeded where required, and whether the final compliance result supports the intended sanitization outcome.