By Ali Hassan, Editor, UAE · Updated 11 November 2026
IEEE 2883 vs NIST 800-88 vs DoD 5220.22-M: Which to Use
If your policy still says “wipe to DoD 5220.22-M”, it’s time for an update. This IEEE 2883 vs NIST 800-88 vs DoD 5220.22-M comparison shows what each one actually is, and which belongs in a policy or tender today.
Quick answer: Specify NIST SP 800-88 Rev. 2 for your sanitization program and IEEE 2883-2022 for drive-level methods. Drop DoD 5220.22-M. It’s a legacy overwrite pattern for magnetic disks, and no multi-pass overwrite reliably sanitizes flash.
IEEE 2883 vs NIST 800-88 vs DoD 5220.22-M at a glance
| IEEE 2883-2022 | NIST SP 800-88 Rev. 2 | DoD 5220.22-M | |
|---|---|---|---|
| What it is | Standard for sanitizing storage | Guidelines for a media sanitization program | Legacy overwrite method from the NISPOM |
| Published | August 2022 | September 2025, replaced Rev. 1 | 1990s and 2000s |
| Methods | Clear, Purge, Destruct | Clear, Purge, Destroy | Overwrite only (3 or 7 passes) |
| Covers | ATA, SCSI and NVMe storage | All media, program level | Magnetic disks |
| SSD / NVMe | Yes, via device Sanitize commands | Yes | No |
| Status | Current | Current | Obsolete |
What each one is for
- NIST SP 800-88 Rev. 2 is about governance: who decides, which level suits which data, how results are verified and recorded. Revision 2 moved the focus from device-by-device tables to a sanitization program, and withdrew Revision 1.
- IEEE 2883-2022 is the technical how-to for drives. It covers ATA, SCSI and NVMe interfaces, defines Clear, Purge and Destruct, and has a clause on verification. A 2025 recommended practice, IEEE 2883.1, adds guidance on verification.
- DoD 5220.22-M is the old NISPOM overwrite approach. The NISPOM was codified as 32 CFR Part 117 in 2021, and that rule doesn’t carry the old overwrite tables forward. Many tender templates still cite it.
Why DoD 3-pass is obsolete for SSDs
- Wear-leveling: the controller decides where data lands, so an overwrite can miss the original block.
- Over-provisioning and remapped blocks: the operating system can’t see them, so no overwrite reaches them.
- Wear and time: extra full-drive writes use up flash endurance. That’s minor per drive, but it adds up in a large rollout.
- HDDs too: one verified pass is generally considered enough for modern hard drives, so extra passes mostly add time.
The right tools for SSDs are firmware Sanitize commands, cryptographic erase on self-encrypting drives, or physical destruction. If you’re also tempted to rely on a reset, read why formatting isn’t data destruction.
NVMe sanitize command standard
NVMe defines a Sanitize command with block erase, cryptographic erase and overwrite options. IEEE 2883 maps Purge for NVMe, SATA and SAS drives to the equivalent device commands. Verify by checking the command’s completion status and sampling reads. Some consumer-grade drives don’t implement Sanitize. For those, destroy the drive.
What to write into your policy
- Cite NIST SP 800-88 Rev. 2 and IEEE 2883-2022.
- Define Clear, Purge and Destroy by data classification.
- Require verification, plus a certificate with serial numbers, method and tool or command.
- Remove references to DoD 5220.22-M and Rev. 1.
- Say what happens to drives that fail or can’t be purged: destroy them.
Our data destruction process is aligned with NIST SP 800-88, and on-site hard drive shredding covers the Destroy route. For sector-specific examples, see our guides for banks and healthcare .
Updating a sanitization policy?
Send us your current wording and we’ll flag what to change. Request a sanitization method review.



