NIST 800-88 Rev. 2: What Changed in the 2025 Update

In September 2025, NIST published Revision 2 of Special Publication 800-88 — the most widely referenced data erasure guideline in the world. The update was overdue. Rev. 1 dated to December 2014, a time when NVMe drives were niche products, self-encrypting drives were uncommon, and most organizations still erased spinning hard drives with multi-pass overwrites. Rev. 2 brings the standard into the modern storage era, and any organization with a media sanitization policy needs to understand what changed.

Key Takeaways:

• NIST 800-88 Rev. 2 (September 2025) supersedes Rev. 1 (December 2014), though the core Clear/Purge/Destroy framework is unchanged
• The biggest additions address NVMe SSDs, flash-based storage (eMMC, UFS), and self-encrypting drives — technologies Rev. 1 barely covered
• Rev. 2 formally aligns with IEEE 2883-2022, creating a consistent framework for modern storage sanitization
• Cryptographic erase now qualifies as Purge when specific conditions are met, including validated encryption and verifiable key destruction
• Organizations should update policies referencing Rev. 1 to Rev. 2 and audit their SSD sanitization procedures against the new guidance

Why the Update Was Needed

NIST 800-88 Rev. 1 was published on December 18, 2014. In the decade that followed, the storage landscape transformed:

• NVMe drives went mainstream. In 2014, NVMe was an emerging protocol found primarily in data centers. By 2025, NVMe SSDs are the default in laptops, desktops, and servers. Rev. 1 had minimal guidance for NVMe-specific sanitization commands.
• SSDs overtook HDDs in new deployments. Consumer and enterprise computing shifted decisively to flash storage. The overwrite-centric guidance that served HDDs well could not address the fundamental challenges of wear leveling and over-provisioning in SSDs.
• Self-encrypting drives (SEDs) became widespread. Modern SSDs and enterprise HDDs increasingly ship with hardware encryption enabled by default. Rev. 1 acknowledged cryptographic erase but left organizations unsure about when it qualified as Purge versus Clear.
• New form factors emerged. eMMC, UFS, and other embedded flash storage types appeared in everything from tablets to IoT devices. Rev. 1 did not address these explicitly.
• IEEE 2883 was published. The 2022 release of IEEE 2883 — the first sanitization standard built specifically for modern storage — created a gap. Organizations needed to know how NIST guidance related to this new standard.

The storage technology in a 2025 laptop has almost nothing in common with a 2014 hard drive, yet organizations were still sanitizing both using the same decade-old guidance. Rev. 2 closes that gap.

Timeline: NIST 800-88 Versions

Understanding how the standard evolved helps put the current revision in context.

Each revision responded to changes in storage technology. The original publication addressed a world of spinning hard drives and magnetic tapes. Rev. 1 acknowledged that SSDs existed and behaved differently. Rev. 2 treats SSDs, NVMe, and flash as first-class citizens with the detailed guidance they require.

What Changed: Rev. 1 vs. Rev. 2

The core structure of NIST 800-88 is unchanged. Clear, Purge, and Destroy remain the three sanitization levels. The risk-based approach to selecting a level is preserved. What Rev. 2 changes is the depth and specificity of the guidance, particularly for storage technologies that barely existed when Rev. 1 was written.

1. Expanded NVMe and Flash Storage Guidance

This is the most significant change in Rev. 2. Where Rev. 1 grouped SSDs into a general category with limited procedural detail, Rev. 2 provides specific guidance by interface and technology:

• NVMe SSDs: Rev. 2 maps NVMe Sanitize (Block Erase) and NVMe Sanitize (Crypto Erase) to the Purge level. It distinguishes between NVMe Sanitize and NVMe Format — the Sanitize command is a defined, thorough operation that addresses all user data areas, while NVMe Format may only qualify as Clear depending on how the drive's firmware implements it.
• SATA SSDs: Guidance for ATA SANITIZE DEVICE and ATA SECURITY ERASE UNIT is clarified. Rev. 2 specifies that the SANITIZE DEVICE command with Block Erase or Crypto Erase sub-commands meets Purge, while SECURITY ERASE UNIT alone may not reach the same assurance level on all drives.
• eMMC and UFS: Rev. 2 adds guidance for embedded flash storage commonly found in tablets, smartphones, and IoT devices. These were absent from Rev. 1.

What this means for you: If you manage NVMe drives, Rev. 2 gives you clear answers that Rev. 1 did not. NVMe Sanitize is your path to Purge. NVMe Format is not a reliable substitute. Check your erasure tools to confirm they issue the correct commands — our SSD secure erase guide covers the specifics.

2. Alignment with IEEE 2883

Rev. 2 explicitly references IEEE 2883-2022 as a complementary standard and aligns its terminology and procedures accordingly. This alignment means:

• Organizations can follow NIST 800-88 Rev. 2 for the policy framework (determining which sanitization level is required) and IEEE 2883 for the technical implementation (which specific commands to execute on which hardware).
• The sanitization level definitions in both standards are now consistent, reducing confusion for organizations that reference both.
• Procurement requirements citing either standard will result in compatible practices.

What this means for you: You no longer need to reconcile conflicting guidance between NIST and IEEE. If your procurement contracts or compliance frameworks reference IEEE 2883, following NIST 800-88 Rev. 2 puts you in alignment. For the full picture on how these standards work together, see our data erasure standards overview.

3. Strengthened Verification Requirements

Rev. 1 required verification but provided general guidance. Rev. 2 is more specific about what constitutes acceptable verification for each sanitization method:

• For overwrite-based Clear on HDDs: Sampling sectors after the overwrite to confirm the expected pattern is present. Rev. 2 specifies minimum sampling percentages and addresses how to handle sectors that fail verification.
• For firmware-level Purge on SSDs: Checking that the drive firmware reports successful sanitization completion, then reading back a sample of sectors to confirm they contain the expected data (typically zeros or random data). Rev. 2 acknowledges that the verification method depends on the sanitize command used — Block Erase leaves cells in a known state, while Crypto Erase does not necessarily change the physical cell contents (the data is just unreadable without the destroyed key).
• For Destroy: Physical inspection or use of certified destruction equipment with documented chain of custody.

What this means for you: If your current verification procedure is "run the erase tool and trust it worked," Rev. 2 pushes you toward more documented, auditable verification. Professional tools like BitRaser automate this verification and include the results in their certificates of erasure.

4. Cryptographic Erase Formally Recognized as Purge

Rev. 1 mentioned cryptographic erase but did not clearly define when it achieved Purge-level assurance. Rev. 2 resolves this ambiguity. Cryptographic erase qualifies as Purge when all of the following conditions are met:

1. Encryption was active from provisioning. The drive must have been encrypting all data since it was first put into use — not encrypted after the fact.
2. The encryption algorithm meets current NIST standards. AES-256 or an equivalent algorithm validated under FIPS 140 or a successor standard.
3. Key destruction is verifiable. There must be a way to confirm that the media encryption key (MEK) has been destroyed, not merely flagged as deleted.

If any of these conditions are not met — for example, if the drive was used without encryption before being retroactively encrypted, or if the encryption implementation has not been validated — then cryptographic erase may only qualify as Clear.

What this means for you: If you manage self-encrypting drives, this is a major clarification. Crypto erase is fast (seconds, regardless of drive capacity) and effective, but only under the right conditions. Verify that your SEDs meet all three requirements before relying on crypto erase for Purge-level compliance. Our NIST 800-88 explainer covers the broader context of how Purge-level methods compare.

5. Updated Media Categories

Rev. 2 reorganizes the media categories to reflect the current storage landscape:

• Magnetic storage: HDDs (SATA, SAS), magnetic tape
• Flash-based storage: SATA SSDs, NVMe SSDs, SAS SSDs, eMMC, UFS, SD cards, USB flash drives
• Optical storage: CD, DVD, Blu-ray
• Self-encrypting devices: Treated as a cross-cutting category that applies to drives in any of the above groups

This reorganization matters because it forces organizations to classify their storage correctly before selecting a sanitization method. A policy that says "overwrite all drives" fails when half your fleet is NVMe SSDs that cannot be adequately sanitized through overwriting.

6. Clearer Decision Flowcharts

Rev. 2 includes revised decision flowcharts that guide you from data classification to sanitization method selection. The flowcharts ask:

1. What is the data confidentiality level?
2. Will the media be reused?
3. If reused, will it stay within your organization or leave your control?
4. What type of media is it?
5. Is the media functional (can it execute sanitization commands)?

Each path through the flowchart leads to a specific sanitization level and method appropriate for the media type. For failed drives that cannot execute software or firmware commands, the flowchart routes directly to Destroy.

Bottom Line: Rev. 2 does not reinvent NIST 800-88 — it modernizes it. The Clear/Purge/Destroy framework is intact. What changes is the depth of guidance for SSD, NVMe, and flash technologies, the formal alignment with IEEE 2883, and the specificity of verification requirements. If your sanitization policy was built on Rev. 1, the bones are still good — but the procedures for modern storage need updating.

What Stayed the Same

Not everything changed. Understanding what Rev. 2 preserves is just as valuable as understanding what it revised — it tells you which parts of your existing policies are still valid.

• Clear, Purge, and Destroy definitions. The intent and scope of each level are unchanged. Clear still protects against standard recovery tools. Purge still protects against laboratory-level attacks. Destroy still renders media physically unusable.
• Risk-based approach. Rev. 2 continues to tie sanitization level selection to data sensitivity, media disposition, and threat model rather than prescribing a one-size-fits-all method.
• Single-pass overwrite for HDD Clear. One pass of fixed data followed by verification remains sufficient for Clear-level HDD sanitization. Multi-pass overwriting is still unnecessary for modern drives.
• Documentation requirements. Rev. 2 maintains the requirement to document sanitization activities, including what media was sanitized, which method was used, who performed it, and whether verification succeeded.
• Destroy methods. Physical destruction techniques — shredding, disintegration, incineration, degaussing (for magnetic media) — are unchanged.

Who Needs to Care About Rev. 2

Federal Agencies and Contractors

If you are a U.S. federal agency or hold government contracts, NIST 800-88 compliance is not optional. Federal agencies will be expected to adopt Rev. 2 within their standard policy update cycles. Contractors subject to CMMC, FedRAMP, or agency-specific security requirements should proactively update their media sanitization procedures and tools. See our CMMC media sanitization guide for specific requirements.

Regulated Industries

HIPAA, PCI DSS, GDPR, SOX, and similar frameworks require appropriate data destruction but do not typically specify a NIST revision number. However, following the current revision demonstrates due diligence and best practice. If an audit or data breach investigation examines your sanitization procedures, referencing the current standard is stronger than referencing one that was superseded.

Enterprise IT Departments

Any organization managing a mixed fleet of HDDs and SSDs — which is most organizations today — should review their erasure procedures against Rev. 2. The most common gap: treating SSDs the same as HDDs by running an overwrite-only tool across all drives. Rev. 2 makes it explicit that this approach does not achieve Purge-level sanitization on SSDs.

IT Asset Disposition (ITAD) Providers

If your business provides data destruction services, your clients will increasingly expect Rev. 2 compliance. Update your certificates of erasure to reference Rev. 2, verify that your tooling supports the firmware-level commands Rev. 2 specifies for SSDs and NVMe drives, and review your verification procedures against the strengthened requirements.

Home Users

The practical impact for home users is minimal. The same advice applies as before: overwrite your HDD with a single pass, use firmware-level secure erase on your SSD, and do not rely on formatting or a Windows reset as a substitute for proper erasure. Our guide to wiping a hard drive covers everything you need.

Migrating from Rev. 1 to Rev. 2

If your media sanitization policy references Rev. 1, here is a practical migration path:

Step 1: Update the Reference

Change any mention of "NIST SP 800-88 Rev. 1" to "NIST SP 800-88 Rev. 2" in your policy documents, procurement specifications, and compliance documentation.

Step 2: Audit Your Storage Inventory

Identify which drives in your environment are HDDs, SATA SSDs, NVMe SSDs, or self-encrypting drives. Many organizations do not track this distinction, which makes it impossible to apply the correct sanitization method.

Step 3: Review SSD Sanitization Procedures

This is where most organizations will find gaps. If your current procedure runs an overwrite tool on all drives regardless of type, you are not meeting Purge-level requirements for SSDs under either Rev. 1 or Rev. 2. Rev. 2 makes this unambiguous.

• For SATA SSDs: Confirm your tooling issues ATA SANITIZE DEVICE or ATA SECURITY ERASE UNIT commands
• For NVMe SSDs: Confirm your tooling issues NVMe Sanitize commands (Block Erase or Crypto Erase)
• For self-encrypting drives: Determine whether crypto erase meets the three conditions for Purge qualification

Step 4: Strengthen Verification

Compare your current verification steps against Rev. 2 requirements. At minimum, you need post-erasure sector sampling for overwrite-based methods and firmware status confirmation for command-based methods. If your erasure tool does not automate verification and document the results, consider upgrading to one that does. BitRaser generates certificates that include verification results and reference both NIST 800-88 and IEEE 2883.

Step 5: Update Training and Documentation

Staff performing sanitization need to understand the distinction between HDD and SSD procedures, know which firmware commands apply to which drive types, and follow the updated verification steps. Update your standard operating procedures and any training materials.

Step 6: Reference IEEE 2883

Consider adding IEEE 2883-2022 as a complementary reference in your policy. Since Rev. 2 aligns with IEEE 2883, citing both standards demonstrates thorough, current guidance.

Recommended Tools for Rev. 2 Compliance

The right tool depends on your drive types and compliance needs:

• BitRaser Drive Eraser: Supports NIST 800-88 Rev. 2 Clear and Purge across HDDs, SATA SSDs, and NVMe SSDs. Issues firmware-level commands, automates verification, and generates tamper-proof certificates referencing NIST 800-88 and IEEE 2883. The strongest option for organizations that need audit-ready documentation.
• Manufacturer utilities: Samsung Magician, Western Digital SSD Dashboard, and similar vendor tools can issue secure erase commands for their own drives. Free, but limited to a single manufacturer's hardware and without compliance reporting.
• Linux command-line tools: hdparm (for SATA) and nvme-cli (for NVMe) can send the raw firmware commands Rev. 2 specifies. No certificate generation or automated verification — suitable for technically proficient users who can document the process manually.

For a full comparison of erasure tools across features, standards support, and pricing, see our best data erasure software roundup.

Frequently Asked Questions

When was NIST 800-88 Rev. 2 published?

NIST published Special Publication 800-88 Revision 2 in September 2025. It supersedes Revision 1, which was published in December 2014 and had served as the primary reference for media sanitization for over a decade.

What are the biggest changes in NIST 800-88 Rev. 2?

The most significant changes include expanded guidance for NVMe SSDs and flash-based storage, alignment with IEEE 2883-2022, strengthened verification requirements, formal recognition of cryptographic erase as a Purge-level method for qualifying self-encrypting drives, updated media categories, and clearer decision flowcharts for selecting sanitization methods.

Does NIST 800-88 Rev. 2 still use Clear, Purge, and Destroy?

Yes. The three-tier sanitization model — Clear, Purge, and Destroy — remains the foundation of Rev. 2. The definitions and intent of each level are unchanged. What Rev. 2 updates is the specific guidance for how to achieve each level on modern storage technologies like NVMe SSDs, eMMC, and self-encrypting drives.

Do I need to update my media sanitization policy for Rev. 2?

If your policy references NIST 800-88 Rev. 1 specifically, yes — you should update the reference to Rev. 2 and review your procedures against the new guidance. In particular, check that your SSD sanitization procedures use firmware-level commands rather than overwriting, and that your verification steps match the strengthened requirements in Rev. 2.

Does Rev. 2 change how I should erase HDDs?

Not significantly. A single-pass overwrite still meets Clear-level requirements for HDDs, and ATA Secure Erase still qualifies for Purge. The core HDD guidance from Rev. 1 remains valid. The major changes in Rev. 2 target SSDs, NVMe drives, and flash-based storage.

How does NIST 800-88 Rev. 2 handle NVMe drives?

Rev. 2 provides specific guidance for NVMe sanitization that Rev. 1 lacked. It maps NVMe Sanitize (Block Erase and Crypto Erase) to the Purge level, addresses the differences between NVMe Sanitize and NVMe Format, and specifies verification procedures for NVMe operations. NVMe Format alone may only qualify as Clear depending on the implementation.

Does Rev. 2 accept cryptographic erase as Purge?

Yes, under specific conditions. The self-encrypting drive must have had encryption active since provisioning, the encryption algorithm must meet current NIST standards (AES-256 or equivalent), and the key destruction must be verifiable. If any of these conditions are not met, cryptographic erase may only qualify as Clear.

What is the relationship between NIST 800-88 Rev. 2 and IEEE 2883?

Rev. 2 explicitly aligns with IEEE 2883-2022, the first sanitization standard built specifically for modern storage. The two are complementary — NIST 800-88 provides the policy framework for determining the right sanitization level, and IEEE 2883 provides technology-specific implementation procedures. Organizations following Rev. 2 will find their practices compatible with IEEE 2883.

Is my organization legally required to follow Rev. 2 instead of Rev. 1?

Federal agencies and contractors bound by NIST guidelines will be expected to transition to Rev. 2 within their standard policy update cycles. For private organizations, regulations like HIPAA, GDPR, and PCI DSS require appropriate data destruction without naming a specific NIST revision. However, following the current revision demonstrates best practice and strengthens your compliance posture.

Where can I read the full text of NIST 800-88 Rev. 2?

The full text of NIST SP 800-88 Rev. 2 is available for free download from the NIST Computer Security Resource Center at csrc.nist.gov. NIST publications are public domain and do not require purchase, unlike some standards published by organizations like IEEE or ISO.

The Bottom Line

NIST 800-88 Rev. 2 is an evolution, not a revolution. The Clear/Purge/Destroy framework stands. What changed is the guidance for modern storage — NVMe, flash, and self-encrypting drives — that Rev. 1 could not adequately address. Update your policy references, audit your SSD procedures, and confirm your tools issue the right firmware-level commands. Start with our NIST 800-88 overview for the full standard explained in plain English.

Last updated: February 2026. We regularly review and update our guides to ensure accuracy.

Sources:

• NIST Special Publication 800-88 Rev. 2, "Guidelines for Media Sanitization." https://csrc.nist.gov/publications/detail/sp/800-88/rev-2/final
• NIST Special Publication 800-88 Rev. 1, "Guidelines for Media Sanitization" (December 2014). https://csrc.nist.gov/publications/detail/sp/800-88/rev-1/final
• IEEE 2883-2022, "IEEE Standard for Sanitizing Storage." https://standards.ieee.org/ieee/2883/10277/
• NIST Computer Security Resource Center. https://csrc.nist.gov/
• NVMe Specification, "Sanitize Command." https://nvmexpress.org/specifications/
• NIST FIPS 140-3, "Security Requirements for Cryptographic Modules." https://csrc.nist.gov/publications/detail/fips/140/3/final