
NIST SP 800-88
If a tender asks for erasure "in accordance with NIST 800-88", it refers to a US guideline that serves worldwide as a benchmark for sanitizing data carriers. It distinguishes three levels – Clear, Purge and Destroy – and requires every sanitization to be verified and documented. This glossary entry explains the structure, the 2025 revision and what the guideline means for decommissioned IT in Germany.
In brief
NIST SP 800-88 is a guideline from the US National Institute of Standards and Technology (NIST) for the secure sanitization of data carriers ("Guidelines for Media Sanitization"). It assigns methods to the levels Clear, Purge and Destroy and requires verification and documentation of every sanitization. For IT asset disposition, it is an internationally recognized benchmark against which erasure software and service providers are measured.
What does NIST SP 800-88 regulate?
NIST is a US federal agency that publishes technical standards and guidelines. The "Special Publication 800" series (SP 800) deals with information security. Number 88 addresses how information is removed from data carriers so that it can no longer be recovered. Experts speak of Data Sanitization, that is, the sanitization of data carriers.
The guideline is mandatory for US federal agencies. For companies in Germany it is voluntary. Nevertheless, it is frequently required here because it clearly describes what level of protection a method achieves. Many erasure programs and test reports therefore refer to NIST SP 800-88.
Revision 1 and Revision 2: What has changed?
The first version was published in 2006. Revision 1 from 2014 was authoritative for a long time. It contained detailed tables showing which method is suitable for which data carrier – from hard drives to smartphones.
In September 2025, NIST published Revision 2 and withdrew Revision 1. The most important changes:
- A program instead of a recipe book: The new version describes how an organization builds a sanitization program – with responsibilities, decisions, verification and documentation.
- Technology moved out: The detailed methods for each type of data carrier are no longer in the guideline. For Clear and Purge, NIST refers to current standards such as IEEE 2883.
- Cryptographic erasure remains: The only method still addressed directly is Crypto Erase because it occurs with all kinds of encrypted data carriers.
- Trust in manufacturer functions: The guideline pays more attention to how to verify whether a drive's built-in erase commands work correctly.
If contracts mention "NIST 800-88" without a revision, it is worth asking for clarification. Older documents usually mean Revision 1.
Clear, Purge, Destroy: the three levels
The core of the guideline is three categories. They describe what type of attack a sanitization protects against.
| Level | Protection goal | Typical methods | Data carrier usable afterwards? |
|---|---|---|---|
| Clear | Protection against simple recovery with common programs | Overwriting all addressable areas, resetting to factory settings | Yes |
| Purge | Recovery not feasible even with state-of-the-art laboratory methods | Sanitize commands (Block Erase, Overwrite), Crypto Erase, degaussing for magnetic media | Yes, except after degaussing |
| Destroy | Like Purge, plus the data carrier is destroyed | Shredding, disintegrating, pulverizing, incinerating | No |
The levels are not a ranking of "good, better, best". A correctly performed Purge protects as well as Destroy but preserves the device. Economically and ecologically, that makes a big difference: an erased notebook can be resold, a shredded one cannot. Degaussing (demagnetizing) does count as Purge, but it renders modern hard drives unusable.
Rule of thumb: NIST SP 800-88 does not ask "How many times was it overwritten?", but "Which attacker does the method protect against – and is that documented?"
Who is NIST SP 800-88 relevant for?
- IT management and information security: The levels help determine, for each data class, whether a device is erased or destroyed.
- Data protection: The documented proof for each data carrier supports the accountability obligation under the GDPR.
- Purchasing: Tenders for IT asset disposition frequently name the guideline as a requirement for service providers.
- International corporations: Those with locations in the US often need uniform requirements that refer to NIST.
How to implement NIST SP 800-88
A simplified example: A company is decommissioning 300 notebooks, 20 servers and 40 smartphones and wants to work according to NIST SP 800-88.
- Define protection requirements: What data was on the devices? Personnel data and customer data mean a high need for protection.
- Choose the level: The devices leave the company and are to be resold. Purge is chosen, and Destroy for defective data carriers.
- Determine the method for each device type: HDDs, SSDs and smartphones require different methods. An erasure program selects the appropriate one for each drive.
- Verify: After each erasure, a check is made to confirm that the sanitization was successful (Erasure verification).
- Document: A record is produced for each data carrier with manufacturer, model, serial number, method, tool, result, date and responsible person. Revision 1 already contained a template for this ("Certificate of Sanitization").
- Handle exceptions: Data carriers for which erasure fails go to destruction – likewise with documentation.
How HDDs and SSDs differ in practice is explained in our guide Securely erasing hard drives and SSDs.
Distinction from similar standards
| Set of rules | Origin | Focus |
|---|---|---|
| NIST SP 800-88 | USA, NIST | Sanitization program, levels Clear/Purge/Destroy, documentation |
| IEEE 2883 | International, IEEE | Technical methods for each storage technology and interface |
| DoD 5220.22-M | USA, Department of Defense | Historical multi-pass overwriting method |
| DIN 66399 | Germany, DIN | Physical destruction, protection classes and security levels |
| BSI TL-03420 | Germany, BSI | Erasing and destroying information requiring protection, especially classified information |
the DoD 5220.22-M is often associated with "secure" multiple overwriting. As early as 2014, NIST found that for modern hard drives a single overwrite pass with a fixed pattern is generally sufficient. For public authorities in Germany, the BSI guideline TL-03420 is also important.
NIST SP 800-88 at Second IT
Second IT erases HDDs, SSDs and mobile devices using Blancco software and is a Blancco ITAD Gold Partner. The erasure methods meet international standards such as DoD 5220.22-M and NIST. Hidden areas such as HPA and DCO as well as remapped sectors are also covered. For every device there is a digitally signed erasure certificate with serial number – exactly the proof the guideline requires.
Data carriers that cannot be erased are destroyed in-house in accordance with DIN 66399, certified for security level H-5 and with a certificate of destruction. You can see the status of all devices in the customer portal. More on certified data deletion. What to look for when choosing a service provider is shown by the checklist Choosing an ITAD provider.
Frequently asked questions about NIST SP 800-88
Is NIST SP 800-88 mandatory in Germany?
No. The guideline is binding only for US federal agencies. In Germany it is a voluntary but widely used benchmark. It can become mandatory if a contract or tender explicitly requires it.
What is the difference between Clear and Purge?
Clear protects against simple recovery with common programs, for example by overwriting all addressable areas. Purge also protects against state-of-the-art laboratory methods. This requires methods that reach all storage areas, for example Sanitize commands or Crypto Erase.
Does Revision 1 still apply?
NIST withdrew Revision 1 when Revision 2 was published in September 2025. However, many contracts and erasure reports still refer to Revision 1. If in doubt, clarify which version is meant and what level of protection you expect.
Is a single overwrite enough according to NIST?
For classic hard drives, NIST considered a single pass with a fixed pattern generally sufficient as early as 2014. For SSDs, however, overwriting does not reach all memory cells. There, Sanitize commands or Crypto Erase are common. In every case, verifying the result is decisive.
What must an erasure record according to NIST contain?
Typical contents are the manufacturer, model and serial number of the data carrier, the method and tool, the verification result, the date and the responsible person. This allows every sanitization to be clearly assigned to a device.
Related terms
Erasure according to international standards – with a certificate per serial number.
Send us your device list. You will receive your offer in 48 hours on average.