NIST 800-88 Explained: The Standard Behind Secure Data Sanitization

If you’ve ever seen NIST 800-88 compliant on an ITAD vendor’s site and wondered what that actually means in practice, here’s the short version.

What NIST 800-88 is

NIST Special Publication 800-88 is a guideline published by the National Institute of Standards and Technology that defines methods for sanitizing data from storage media. It’s the reference standard most data destruction processes in the U.S. are measured against, whether the vendor mentions it by name or not, and it’s referenced heavily in compliance frameworks across healthcare, finance, and government contracting.

The three sanitization categories

NIST 800-88 breaks sanitization into three tiers. Clear is a basic overwrite, appropriate for lower-risk situations like reassigning a device internally. Purge covers more advanced techniques, like cryptographic erase or degaussing, that resist even lab-level data recovery attempts, and is the right call for most enterprise drives holding business data ahead of resale. Destroy means physical destruction of the media itself, generally reserved for the highest-risk data, classified material, or media that can’t otherwise be verified as clean.

Not every device or dataset needs the same level of sanitization, and a responsible ITAD provider should be matching the method to the risk, not defaulting to the most extreme option for everything. A healthcare record on a server drive and a shared conference room laptop don’t carry the same risk profile, and treating them identically usually means overspending on one and under-protecting the other.

What happens when sanitization isn’t verified

This isn’t theoretical. A widely cited study out of the University of Hertfordshire, commissioned by Comparitech, examined 200 used hard drives purchased from online marketplaces and found that roughly six in ten still held recoverable data from previous owners, even though most sellers believed the drives had been wiped. In most cases, the drive had simply been reformatted, which looks similar to a proper wipe but isn’t remotely equivalent. That gap between intended and actual sanitization is exactly what a documented, verifiable standard is meant to close.

Verification is the part that actually protects you

The standard itself is only half the story. What matters just as much is whether the sanitization was verified and documented, meaning someone confirmed the process actually worked, not just that it was attempted. That documentation is what you’d want in hand if a regulator, auditor, or client ever asked how a specific device’s data was handled.

Why this is worth knowing

Understanding NIST 800-88 means you can ask better questions of any vendor handling your data, not just take we wipe everything at face value.