NIST SP 800-88 Rev 2 Compliance Guide
The global benchmark for media sanitization.
A technical analysis of NIST SP 800-88 Rev 2 media sanitization categories, drive controller execution commands, verification sampling protocols, and cryptographic certification.
What is NIST SP 800-88 Rev 2?
Guidelines for Media Sanitization.
NIST Special Publication 800-88 (Revision 2) is the definitive media sanitization standard published by the National Institute of Standards and Technology (NIST). It provides actionable requirements for sanitizing magnetic hard drives (HDDs), solid-state drives (SSDs), NVMe media, and optical storage.
Unlike obsolete magnetic multi-pass standards (such as DoD 5220.22-M), NIST SP 800-88 prioritizes modern controller-level commands for flash memory. Modern SSDs utilize complex flash translation layers (FTL) and wear-leveling blocks that cannot be reliably purged by OS-level sector writing.
The Three NIST Sanitization Categories
Standard redeployment within same security domain
Overwrites all user-addressable storage locations using single-pass zero filling. Protects against simple, non-invasive data recovery techniques using standard software utilities.
- Clear - Zero Overwrite (Single-pass)
Release outside organization / Circular economy resale
Executes controller-level and firmware-directed commands that bypass the OS filesystem to sanitize all addressable and unmapped storage (including wear-leveling spare blocks, HPA, and DCO). Protects against advanced laboratory and forensic recovery.
- NVMe Sanitize - Block Erase
- NVMe Sanitize - Crypto Erase
- NVMe Format (SES=1 User Data)
- NVMe Format (SES=2 Crypto Erase)
- ATA Enhanced Secure Erase
- ATA Secure Erase
Damaged, unreadable, or classified media
Physical disintegration, shredding, incinerating, or degaussing (magnetic media only) when electronic sanitization cannot be validated.
- N/A (Hardware triage & disposition record tagging)
Verification & Certification Requirements
Proving compliance to auditors.
NIST SP 800-88 Rev 2 mandates two critical operational controls often overlooked by basic wiping scripts:
1. Post-Erasure Verification Sampling
Following erasure, the software must perform read-back sampling across the storage media to confirm that no residual data or recognizable byte patterns remain. reCore reads across pseudorandom and boundary sectors, generating a cryptographic SHA-256 hash fingerprint of the verification pass.
2. Separation of Duties
Under NIST guidelines, the personnel performing the sanitization should not be the sole individual certifying its compliance. reCore enforces this in code: completed wipe records enter a verified admin queue where an authorized supervisor or auditor must review and approve the tamper-evident certificate.
Frequently Asked Questions: NIST SP 800-88 Rev 2
Direct answers for technical evaluators and compliance officers.