What is an SSD?
A Solid-State Drive (SSD) uses NAND flash rather than moving mechanical storage. Enterprise formats include SATA SSD, NVMe M.2, U.2/U.3 and Data Center EDSFF formats such as E1.S/E3.S.
As AI Servers, Data Centers and enterprise storage adopt SSDs, these devices have become a major media-sanitization category.
Why do SSD and HDD methods differ?
Different storage principles require different treatment decisions:
- NAND flash does not store data magnetically → Degaussing is ineffective for SSDs.
- Wear Leveling → The controller distributes writes across blocks; host overwrite does not necessarily reach every physical location.
- Over-Provisioning → The source scenario describes 7–28% reserved space that ordinary host overwrite may not reach.
- Bad Block Management → Retired or remapped blocks can retain previous data.
NIST SP 800-88 outcome levels
| Level | Method | Effect on SSDs |
|---|---|---|
| Clear | Single overwrite of all addressable space | Addresses visible space, but may exclude reserved or bad blocks |
| Purge | Cryptographic Erase or firmware Sanitize | Can execute quickly where supported |
| Destroy | Physical shredding to the approved particle criterion | Highest-assurance destruction path, subject to verification |
Key pointCryptographic Erase removes encryption keys so data loses its usable decryption path. Supported SED or OPAL devices may offer an efficient path, provided encryption, key-management and verification prerequisites are satisfied.
DIN 66399 reference levels (E class)
Standards-version note: DIN lists DIN 66399:2012 as withdrawn and recommends ISO/IEC 21964. The levels and particle sizes below are retained from customer-supplied material for requirement discussions. Formal projects must confirm the adopted edition, equipment capability, contract and applicable law; this does not mean KYI is certified or a project is automatically compliant.
| Level | Particle-size criterion | Suggested context |
|---|---|---|
| E-3 | ≤ 160 mm² | Ordinary personal data |
| E-4 | ≤ 30 mm² | Confidential information |
| E-5 | ≤ 10 mm² | Highly confidential |
| E-6 | ≤ 1 mm² | Government or military |
| E-7 | ≤ 0.5 mm² | Top-secret information |
SSD physical treatment must account for the high data capacity of individual NAND chips. Smaller fragments may reduce recoverability, but the approved outcome still requires project-specific verification.
Treatment-method comparison
Method A | Firmware Secure Erase / Sanitize
Supported ATA Secure Erase or NVMe secure-erase functions instruct the firmware to perform internal treatment.
BenefitMay address reserved areas, execute quickly and preserve reuse when the command and implementation are appropriate.
LimitationsRequires command support and a responsive SSD; manufacturer implementations and results vary.
KYI project contextFunctioning SSDs intended for reuse, with verified manufacturer command support.
Method B | Cryptographic Erase
For suitable Self-Encrypting Drives or OPAL implementations, removal of the relevant keys can make encrypted data inaccessible, subject to key scope and validation.
BenefitOften completes quickly and can preserve reuse. It may support Purge where encryption, key-management and verification prerequisites are met.
LimitationsRequires a suitable encryption implementation and confirmation that all relevant keys were removed; support must not be assumed for consumer devices.
KYI project contextEnterprise encrypted SSDs, large Data Center retirement batches and time-sensitive projects.
Method C | Physical Destruction
Use suitable shredding equipment to meet the project-adopted DIN/ISO reference particle criterion.
BenefitProvides visible treatment evidence and can support Destroy through the approved particle size and downstream process.
LimitationsPrevents SSD reuse; particle criteria and suitable specialist equipment are required. Ordinary paper shredders are inappropriate.
KYI project contextHighly confidential data, failed SSDs, or government and financial projects requiring visual evidence.
Method D | Multi-Pass Overwrite
Not recommended as the primary SSD treatmentA supported single overwrite may form a Clear method for addressable space. Additional host-level passes do not establish treatment of inaccessible NAND and add write wear. The complete method must reflect device capabilities and risk.
Common pitfalls and misconceptions
- Misconception 1: SSDs can be degaussed SSDs store information in NAND flash, so a magnetic field is ineffective.
- Misconception 2: More overwrite passes are safer Extra passes do not resolve controller-managed inaccessible areas and can add unnecessary wear.
- Misconception 3: Quick formatting is sufficient Quick formatting does not establish sanitization of physical NAND cells.
- Pitfall 4: Overlooking the internal laptop SSD Embedded M.2 SSDs must be included in laptop retirement.
- Pitfall 5: Many NVMe devices in AI Servers A GPU Server may contain 8–24 NVMe devices; capture and reconcile each serial.
KYI decision path
Start with three questions:
- Is the SSD a suitable SED/OPAL encrypted device? → If yes, assess Cryptographic Erase first; otherwise assess supported Secure Erase or destruction.
- Is reuse intended? → If yes, use an applicable firmware method with verification; otherwise assess Physical Destruction.
- How sensitive is the data? → For very high sensitivity, assess an approved combination of firmware sanitization and Physical Destruction.
Verification and records
A project SSD destruction record may include:
- Brand, model, serial and capacity
- Treatment method, including key-removal confirmation where Cryptographic Erase is used
- Applicable NIST outcome
- DIN/ISO particle reference where Physical Destruction is used
- Firmware completion/status evidence for Secure Erase
Applicable industries
Cloud services, finance, AI research, listed technology manufacturers, Data Centers, government and medical imaging