Compliance  ·  4 min read

Why two of your certificates might cite different NIST 800-88 revisions

Pull up the verification pages for a WipeCert certificate issued in the summer and one issued this month, and the wording differs. The older one says "Erasure performed in compliance with NIST Special Publication 800-88 Revision 1." The newer one says "This certificate cites NIST Special Publication 800-88 Revision 2." The Standards line on each PDF names its revision, and a few field labels differ too.

That is not a mistake. It is what should happen when the standard changes partway through your erasure program, and it is worth understanding before an auditor asks about it.

What changed in Rev. 2

NIST published Revision 2 of Special Publication 800-88, Guidelines for Media Sanitization, in September 2025. It supersedes Revision 1 from December 2014. The three sanitization methods are still Clear, Purge and Destroy (Sec. 3.1). The main differences a records owner will notice:

• No more technique tables. Rev. 1's Appendix A listed sanitization techniques per media type, including Table A-8 for flash-based storage. Rev. 2 removed those appendices and points to IEEE 2883 for technique selection (Sec. 3.1, 4.4 and Appendix D).
• Method and technique are separate words. Rev. 2 uses "method" for Clear, Purge and Destroy and "technique" for the operation that carries it out, such as overwrite, block erase or cryptographic erase (Sec. 3.1).
• Verification and validation. Rev. 2 introduces sanitization assurance: verification checks that the technique completed (Sec. 4.5.1), and validation is the decision to accept the result or repeat it (Sec. 4.5.2). Full or sampled read-back of a drive is not needed unless your own policy requires it.
• Multi-pass overwrite is not needed for Clear. The change log says the Clear method was clarified to counter the old DoD 5220.22-M pass counts (Appendix D).

For a full walk-through of Clear, Purge and Destroy, see our plain-English NIST 800-88 guide. This piece is about something narrower: what happens to certificates issued on either side of the change.

What changed on the certificate

A certificate issued under Rev. 2 follows Rev. 2's vocabulary. The field that carries Clear or Purge is labeled "Method (NIST 800-88)", and the operation is labeled "Technique". The notice box that explains the method no longer cites Table A-8, because Rev. 2 has no Table A-8; it cites the Rev. 2 sections instead.

For remote wipes through Microsoft Intune, the notice is also more explicit about key copies. Both revisions warn about this: Rev. 1 (Sec. 2.6.3) and Rev. 2 (Sec. 3.2.2) each say cryptographic erase should not be trusted where keys have been backed up or escrowed, unless the organization has a high level of confidence about how and where those copies are stored and managed. A Rev. 2 WipeCert certificate states the condition directly: the Purge method is met only when no copy of the key exists outside the device. If that applies to your fleet, our post on the BitLocker key Intune leaves behind explains the setting that removes the escrowed copy.

Why old certificates do not rewrite themselves

A WipeCert certificate cites the revision that was current when it was first signed. That citation is carried inside the signed record. A later download of the PDF, a view of the verification page, or a reissue of the certificate keeps the revision it started with, and a certificate first issued under Rev. 1 keeps its Rev. 1 wording word for word.

That is deliberate. A certificate is a record of what happened to a drive on the day it happened, measured against the standard that applied that day. If a software update quietly changed the words on an old certificate, it would stop being a historical record and become a statement of whatever the current standard says, which is a much weaker thing to hand an auditor.

In practice, your records split cleanly. Certificates first signed before WipeCert moved to Rev. 2 read Revision 1, and certificates first signed after read Revision 2. Nothing flips after the fact.

When an auditor asks

If an auditor points out that two of your certificates word the standard differently, the answer is not to apologize or reissue the older one. The older certificate is an accurate record of the standard that applied when that drive was erased, and the newer one is an accurate record of the standard that applies now. A certificate that only says "NIST 800-88 compliant", with no revision, cannot make that distinction.

You do not have to take our word for which revision a certificate cites. It is printed on the PDF in the Standards line, and it appears on the public verification page, which anyone can open by scanning the certificate's QR code, signed in or not.

Start a free trial, with two wipes included and no card required, and look at a certificate that names its own standard.