ATA Sanitize or Secure Erase? Picking the Right Command for SATA Drives

Every SATA drive that leaves your organisation gets erased with some command, and the choice is rarely made consciously. Most technicians click a button in a tool and trust that the right thing happened underneath. When the drive held sensitive data, that trust deserves a closer look, because the two command families built into SATA storage do not offer the same assurance.

This guide is written from the bench: what each command does, which one we reach for first, and what to note down so the result stands up later.

What is the difference between ATA Sanitize and ATA Secure Erase?

Secure Erase is the older SECURITY ERASE UNIT command with a normal and an enhanced mode, while Sanitize is a newer feature set with block erase, overwrite and crypto scramble options. Sanitize gives clearer Purge outcomes; Secure Erase behaviour varies more between models.

Secure Erase arrived as part of the ATA security feature set, the same feature that lets you put a password on a drive. It has two settings. Normal mode typically writes over the user area, and enhanced mode is meant to reach reallocated sectors and other areas the host cannot see. Manufacturers were given a lot of freedom in how they implemented both, and that freedom is the root of the problem.

Sanitize came later and was designed specifically for end of life. It offers three techniques, and the drive is expected to apply them to all of its storage, including spare and cached areas, and to report progress and completion through a defined status.

Which command reaches Purge?

The Sanitize techniques are Purge options, and enhanced Secure Erase can count as Purge, but IEEE 2883 advises against relying on Secure Erase in either mode until the manufacturer confirms how that model behaves. Normal mode Secure Erase only reaches Clear.

NIST SP 800-88 Rev. 2 describes Clear as protection against simple recovery through the normal interface and Purge as making laboratory recovery infeasible while leaving the media reusable. For data that matters, Purge is the level you want. IEEE 2883-2022, which NIST now points to for technique detail, maps the SATA commands like this:

• Sanitize block erase: Purge, and the natural fit for SSDs because flash is erased in whole blocks.
• Sanitize overwrite: Purge when the drive writes to hidden areas as well as user space. This is the option that applies to hard drives.
• Sanitize crypto scramble: Purge only when the drive meets the conditions for cryptographic erase, covered in our guide to the four checks for cryptographic erase.
• Enhanced Secure Erase: Purge on paper, but only with confirmation from the manufacturer that the model does what it claims.
• Normal Secure Erase: Clear only, which is not enough for sensitive data.

Why does model variability matter so much?

Because a command name tells you what a drive should do, not what its firmware actually does. Two drives can accept the same Secure Erase command and treat spare areas very differently, and the operator cannot see the difference.

NIST makes the same point: similarly named commands can behave differently, and organisations are asked to put a degree of trust in each vendor's implementation. Sanitize narrows that gap because the expected outcome is better defined. It does not remove trust entirely, which is why recording what ran and checking the result still matter.

Which command should a technician choose for each drive?

Use Sanitize block erase for SSDs, Sanitize overwrite for hard drives, crypto scramble only on self-encrypting drives that meet the cryptographic erase conditions, and fall back to enhanced Secure Erase only with manufacturer confirmation on file.

In practice the decision tree on our bench looks like this:

1. Identify the media. Spinning disk or flash changes everything that follows.
2. Check which Sanitize options the drive reports. Most current SATA SSDs support block erase; many hard drives support overwrite.
3. If no Sanitize option is available, consider enhanced Secure Erase and keep evidence of what the manufacturer says about that model.
4. If nothing suitable is supported, or every attempt fails, route the drive to physical destruction.

What gets in the way on real hardware?

Frozen security states, USB adapters and hidden capacity are the usual obstacles. Many computers freeze the drive's security features at start-up, adapters can block commands entirely, and areas such as HPA and DCO can hide part of the disk.

A drive in a frozen state will refuse Secure Erase until it is power cycled in the right way, which is why boot order and the way a tool starts matter. USB enclosures and docks often pass normal reads and writes but quietly block sanitise commands, so connect SATA drives directly to the motherboard wherever you can. Finally, a drive can be configured to report less capacity than it holds. Before you trust any erase, compare the reported size with the label and reset hidden areas where your tool supports it.

How do RedKey USB tools handle SATA drives?

RedKey USB starts the computer from USB, outside the installed operating system, and uses the drive's own sanitise commands where the drive and computer support them, or software overwriting where they do not. It can also check and clear supported hidden disk areas.

Because it runs before Windows or Linux loads, the operating system cannot lock the disk or hide it. Advanced Mode lets experienced users see and choose the method, while the Wipe Wizard keeps the routine simple for less technical staff. Available methods always depend on the drive and the computer, so a good habit is to note which technique actually ran on each disk.

What should be recorded after a SATA erase?

Record the drive model and serial number, the method level (Clear or Purge), the technique used, the tool and version, the result, and who checked it. NIST SP 800-88 Rev. 2 lists these as the core fields of a sanitisation record.

NIST also separates verification, which checks that the technique completed without errors, from validation, which is a person's decision that the data was effectively sanitised. For Purge, IEEE suggests full verification of the addressable media where you verify at all, and a known-content check after crypto scramble, because the result is unpredictable rather than all zeros.

Frequently asked questions

Is ATA Secure Erase still safe to use?

It can be, but treat it as a fallback. Normal mode only reaches Clear, and enhanced mode should be used for sensitive data only when the manufacturer confirms how that model implements it.

Does ATA Sanitize work on hard drives?

Yes. Sanitize overwrite applies to hard drives, while block erase is for flash storage. Check which options the drive reports before choosing.

Why will my drive not accept a Secure Erase command?

It is often in a frozen security state set during start-up, or connected through an adapter that blocks the command. Connect it directly and start the computer from a bootable tool.

Ready to erase your own devices? See RedKey USB Professional. Related reading: Is Overwriting SSDs Safe? and SSD Erasure Compliance Process in 7 Steps.