SSD Secure Erase

Data Destruction Inc. sanitizes solid-state drives with controller-level secure erase commands, ATA Secure Erase for SATA drives and NVMe Sanitize for NVMe drives, purging every flash block including the over-provisioned cells that software overwrites miss. We verify each erase and document it to the NIST SP 800-88 r2 Purge category so drives can be safely reused.

TOP 10 WAYS TO PROTECT YOUR PRIVACY NOW!

DOWNLOAD YOUR FREE GUIDE

DOWNLOAD NOW

SSD Secure Erase Service Option

How SSD Secure Erase Works

Secure erase is a logical sanitization method: instead of destroying the medium, it instructs the drive’s own controller to reset its flash cells. This preserves a working drive, which is why it is the right choice for redeployment, lease return, and resale. The reason it succeeds where software overwrites fail is that the controller reaches storage the operating system cannot address.

Solid-state drives use wear-leveling to spread writes across cells, plus over-provisioned spare capacity the host never sees. A host-level overwrite can therefore leave between 4 and 75 percent of data recoverable, because it never reaches the remapped or reserved cells. A controller-issued secure erase purges the entire flash array, including those hidden regions.

The correct command depends on the interface:

SATA SSDs use ATA Secure Erase, and the more thorough ATA Sanitize (block erase or crypto scramble) where the drive supports it.
NVMe SSDs use NVMe Format with a user-data erase, or the more robust NVMe Sanitize, because NVMe uses a different command set than ATA.
Self-encrypting drives can be sanitized by cryptographic erase, a related but distinct path covered on our cryptographic erase service page.

Data Destruction Inc. issues the command appropriate to each drive, confirms the drive accepted and completed it, and records the result against the serial number.

Secure Erase, Sanitize, and Crypto-Erase Compared

These terms are used loosely in the market, so we keep them distinct. The table below maps each command to the NIST category it satisfies.

Command	Interface	What it does	NIST category
ATA Secure Erase	SATA	Resets user-addressable cells; some drives clear only the mapping table	Clear to Purge
ATA Sanitize (block erase)	SATA	Erases all blocks including spare area	Purge
NVMe Format (user-data erase)	NVMe	Erases user data on the namespace	Clear to Purge
NVMe Sanitize	NVMe	Erases the entire flash array, most robust NVMe option	Purge
Cryptographic erase	SED only	Destroys the media encryption key	Purge

Because some implementations of ATA Secure Erase only clear the mapping table rather than every block, we prefer the Sanitize variant where the drive supports it, and we verify the outcome rather than trusting that the command returned success.

Verification and When to Destroy Instead

A secure erase is only defensible if it is verified. Our process confirms the drive reported a successful sanitize, checks the drive security state before and after, and samples readback where the controller allows it. The verification result is recorded in the audit package.

Secure erase is not always the answer. We default to physical destruction when:

the drive is dead, frozen, or will not accept a sanitize command;
the drive cannot verify completion;
the data classification forbids any reuse of the medium; or
the drive is a self-encrypting drive whose key management cannot be confirmed.

In those cases we route the drive to SSD shredding or SSD crushing and document the change of method.

Compliance and Standards

Regulation	Requirement	How secure erase satisfies it
NIST SP 800-88 r2	Purge category for media slated for reuse	Verified controller-level sanitize of all flash blocks
HIPAA 45 CFR 164.310(d)(2)(i)	Render electronic PHI unusable before reuse	Verified Purge with serialized record
GLBA Safeguards Rule, 16 CFR Part 314	Dispose of or sanitize customer information securely	Documented, verified erase
CMMC 2.0 / NIST 800-171	Sanitize media before reuse	NIST 800-88 r2 Purge, verified per asset

We cite NIST SP 800-88 r2 (September 2025) and its deference to IEEE 2883-2022. Authoritative sources: NIST SP 800-88 r2 (PDF) and the NIST cryptographic erase definition.

Industries That Choose Secure Erase

Data centers secure erase enterprise SSDs at lease return or redeployment, preserving drive value while meeting NIST 800-88 r2 Purge.
Financial services sanitize endpoint and server SSDs for internal reuse under the GLBA Safeguards Rule.
Healthcare organizations purge SSDs from devices that will be redeployed within the organization, where PHI must be removed but the hardware retained.
Defense contractors verify Purge on controlled-unclassified-information media before reuse under CMMC 2.0 and NIST 800-171, escalating to destruction for higher classifications.

What You Receive

Serialized erasure report listing each drive, the command issued, and the verified result, mapped to the NIST 800-88 r2 Purge category.
Certificate of Destruction or sanitization for the batch, provided within 24 hours after the erase event is complete.
Chain-of-custody log documenting every transfer.
Exception list naming any drive that failed verification and was rerouted to physical destruction, with the destruction method recorded.

Frequently Asked Questions

Is secure erase enough to meet NIST 800-88 r2? A verified controller-level sanitize meets the NIST Purge category, which is acceptable for media slated for reuse. The key word is verified: we confirm the drive completed the command and record the result. For the highest-sensitivity data, physical destruction to the Destroy category is preferred.

Why not just overwrite the SSD with software? SSDs use wear-leveling and over-provisioning, so a host-level overwrite can miss remapped and reserved cells, leaving between 4 and 75 percent of data recoverable. A controller-issued secure erase or sanitize reaches the entire flash array, which a software overwrite cannot.

What is the difference between secure erase and cryptographic erase? Secure erase resets the flash cells through a controller command and works on any SSD. Cryptographic erase destroys the media encryption key on a self-encrypting drive, making encrypted data unreadable without touching the cells. Both can reach the Purge category, but they apply to different drives.

Does NVMe use the same command as SATA? No. SATA drives use ATA Secure Erase or ATA Sanitize. NVMe drives use NVMe Format or NVMe Sanitize because they run a different command set. We apply the correct command for each interface. See NVMe Destruction.

What happens if a drive fails the erase? We reroute it to physical destruction and record the change on the exception list, so every drive ends in a verified state, either Purge by erase or Destroy by shredding or crushing.