SSD data destruction is not the same job as destroying a spinning hard drive. Solid-state drives store data in flash memory chips, spread writes across spare blocks and hide part of their capacity from the operating system. Methods that work well on magnetic drives, such as multi-pass overwriting and degaussing, can leave recoverable data on an SSD. This guide explains what changes with flash media and which methods hold up in an audit.
Short answer: what works for SSD data destruction
For drives that will be reused or resold, use the drive’s firmware-level sanitize command or a cryptographic erase, then verify the result. For drives that must be destroyed, shred or disintegrate them to a particle size small enough to break the individual memory chips. Degaussing does nothing to flash memory, and a single software overwrite cannot guarantee every cell was reached.
Why SSDs are harder to sanitize than hard drives
Wear leveling moves your data around
To prevent individual cells from wearing out, an SSD controller constantly relocates data. When software overwrites a file, the controller usually writes the new data to a fresh block and marks the old one as stale. The original data can survive in that stale block until the controller eventually erases it.
Over-provisioning hides capacity
Most SSDs reserve a portion of their flash as spare area that the operating system cannot address. Retired blocks, remapped blocks and spare capacity can all hold copies of old data that a host-based wipe tool never touches.
Magnets have no effect
Degaussing works by disrupting magnetic domains on platters and tape. Flash memory stores charge in transistors, not magnetic patterns, so a degausser leaves SSD data intact. If your current process relies on degaussing services, flash media needs a separate path.
SSD data destruction methods compared
| Method | Works on SSD? | Drive reusable? | Notes |
|---|---|---|---|
| Software overwrite (one or more passes) | Not reliably | Yes | Misses spare and remapped blocks |
| Firmware sanitize (block erase) | Yes, when supported and verified | Yes | Executed by the drive controller across all blocks |
| Cryptographic erase | Yes, on self-encrypting drives | Yes | Destroys the media encryption key |
| Degaussing | No | Not applicable | Flash is not magnetic |
| Shredding or disintegration | Yes, at a fine enough particle size | No | Particle size must break the memory chips |
Firmware sanitize and cryptographic erase
ATA, SCSI and NVMe drives support sanitize commands that instruct the controller to erase every block, including spare area. Self-encrypting drives can also perform a cryptographic erase, which replaces the internal encryption key so the stored data becomes unreadable. Both approaches fall under the Purge category described in our guide to NIST 800-88 data sanitization. The catch is verification: firmware implementations vary by manufacturer, so the result should be checked and recorded per drive.
Physical destruction for flash media
When drives cannot be verified, have failed, or carry highly sensitive data, physical destruction is the defensible option. Shredders built for hard drives often produce strips that are too large for SSDs, because a single surviving memory chip can still hold data. Ask any provider of hard drive shredding services what particle size their equipment produces for solid-state media.
Where SSDs hide in your environment
SSD data destruction planning often stops at laptops. In enterprise environments, flash media also sits in:
- Servers with SATA, SAS or NVMe boot and data drives
- All-flash and hybrid storage arrays, including cache drives
- M.2 boot drives on server motherboards and RAID controllers
- Network appliances, firewalls and controllers with internal flash
- Thin clients, kiosks and point-of-sale terminals
An accurate inventory by serial number is the first control. Drives missed in the inventory are the ones that leave the building with data on them.
Building an SSD data destruction process that holds up in an audit
- Inventory every device and record drive serial numbers before removal.
- Decide per drive: sanitize for reuse or resale, or destroy.
- Run firmware sanitize or cryptographic erase and record the tool and result.
- Send failed or unverifiable drives to physical destruction.
- Issue a certificate of destruction that lists every serial number.
DWC-IT’s hard drive destruction services include full chain-of-custody tracking and certificates issued per asset or per lot, so the SSD data destruction record matches the inventory you started with.
Frequently asked questions
Does formatting an SSD destroy the data?
No. A quick format only rebuilds the file system tables. Even a full format may not reach spare or remapped blocks on an SSD. Use a verified sanitize command or physical destruction instead.
Can you degauss an SSD?
Degaussing has no effect on SSD data because flash memory does not store data magnetically. It is only effective on magnetic media such as hard disk drives and tape.
What particle size is needed to shred an SSD?
SSDs need a much smaller particle size than hard drives because data lives on small memory chips. Confirm the exact particle size with your destruction provider and make sure it is designed for solid-state media.
Is cryptographic erase enough for SSD data destruction?
On self-encrypting drives, cryptographic erase is recognized as a Purge method when it is properly implemented and verified. If the drive cannot be verified, destroy it.
Next step
If you are retiring servers, arrays or laptops that contain SSDs, contact DWC-IT with your asset list and we will recommend sanitize or destroy per drive and document every serial number.
2 responses