United States (federal information systems; adopted internationally as practice)

NIST SP 800-88 Rev 2

35 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

35 controls 0 frameworks share controls with it United States (federal information systems; adopted internationally as practice) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1.1Purpose and scope: sanitization protects the recorded information, not the media; media assumed to hold information at the system's FIPS 199 confidentiality category; a programme a0
1.1-RETConsult privacy, FOIA and records retention officials and organisational management before sanitizing, so that Federal Records Act retention duties and business history needs are m0
1.2-1.5Audience, assumptions, related NIST documents and document structure0
2Background: disposition decisions begin at system design, media leave organisational control throughout the life cycle, and sanitization is a confidentiality safeguard against data0
2.2Types of media: hard copy and information storage media (devices and virtual or logical storage), with non-volatile storage the main focus0
2.3Target of sanitization: all user data when sensitive data cannot be selectively removed, and the full physical capacity including overprovisioned and compressed areas0
2.4Weigh the decision factors: media type, size and capacity, confidentiality requirement, controlled area, in-house or third party, on-site or off-site, volume, equipment, training, 0
3Categorise the information, assess the media and the confidentiality risk, decide the media's future, then choose and justify the sanitization method0
3.1Use the three methods (clear, purge, destroy) with technology-specific techniques kept current against IEEE 2883, matched carefully to the media type0
3.1.1Clear: logical techniques over the user interface against simple recovery; not for hard copy; avoid multi-pass overwriting on overprovisioned flash; use dedicated sanitize commands0
3.1.2Purge: physical or logical techniques that defeat laboratory recovery while keeping the ISM reusable; prefer purge to clear; choose techniques from IEEE 2883; cryptographic erase m0
3.1.3Destroy: render recovery infeasible and the media unusable by disintegrating, incinerating, melting, pulverizing or shredding; partial damage does not count; avoid shred and pulver0
3.2Cryptographic erase as a purge technique: sanitize or block access to the keys that encrypt the data; federal agencies use modules validated to the current FIPS 140 standard0
3.2.1Strength of cryptography for CE: at least 128-bit security strength, entropy at least equal to the key length, and the Table 1 requirements on key generation, media encryption, key0
3.2.2Applicability of CE: only where no sensitive plaintext was ever stored since the last sanitization, with caution for long-lived sensitivity, and never trusted where keys were backe0
3.2.3Sanitization of keys: zeroize every copy of the target cryptographic keys and all keys beneath them, eliminate unwrapped copies in volatile memory or registers, and consider extern0
3.2.4Quality of cryptographic implementations: obtain independent validation or vendor evidence on entropy and key generation, algorithm and mode implementation, key sanitization techni0
3.2.5Traceability of CE: document make and model, key generation, media encryption, key wrapping, encrypted and unencrypted areas, key life cycle handling, key sanitization technique, e0
4Make storage sanitization part of data governance with, at minimum, disposal policies and minimum methods, scope and decision criteria, performance of sanitization, adequacy determ0
4.1Storage sanitization policy: align data classification with minimum methods; set disposal and reuse requirements, expected outcomes and acceptable techniques, documentation, roles 0
4.2Scope: unclassified federal ISM never holding FOUO, Privacy Act or PII need no sanitization; otherwise target all user data, treat selective and partial sanitization as risky, and 0
4.3Decision framework: identify the confidentiality level under FIPS 199 and SP 800-60, accept clear for moderate data only as a conscious risk decision, weigh purge or clear against 0
4.3.1Plan sanitization from the system security plan onward: choose ISM with sanitization in mind, obtain Statements of Volatility and the Appendix B characteristics, identify every ISM0
4.3.2Security categorisation set early under FIPS 199, SP 800-60 or CNSSI 1253, revisited at least every three years or on significant change, and internal confidentiality labels assign0
4.3.3-4.3.4Decide on reuse (destroy is simplest when media will not be reused) and account for who controls the media: maintenance under contract or on-site supervision stays under organisati0
4.3.5Consider the data protection level alongside organisational control when deciding whether sanitization is necessary0
4.3.6Make and record the risk-based sanitization decision, then put the process, resources, verification steps and interfaces with key officials in place to carry it out0
4.4Perform sanitization by the selected method in line with IEEE 2883 or another policy-approved standard, using the most protective available technique, capturing results and documen0
4.5Assure sanitization by inspecting results and deciding adequacy; repeat with a different technique or a stronger method when unacceptable, rechecking reusability0
4.5.1Verify the outcome: inspect destruction remnants and equipment; for logical techniques check tool completion status, errors, anomalies and media health; for physical purge confirm 0
4.5.2Validate effectiveness: analyse errors and anomalies, assess confidentiality risk, and reject the sanitization where inaccessible areas, an inappropriate method, unqualified person0
4.6Document each sanitized ISM on a certificate of sanitization recording manufacturer, model, serial and property numbers, media type and source, prior category, method, technique, t0
4.7Assign programme roles: programme managers and agency heads for governance and resources, the CIO for policy, system owners for protective maintenance contracts, information owners0
BObtain from ISM vendors the media type and coercivity, each supported sanitize command with the areas it does not address, its expected duration and any validation results, and its0
CSample certificate of sanitization: person performing, media information, sanitization details, destination and disposition, signature and concurrence0

Tell me when NIST SP 800-88 Rev 2 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for NIST SP 800-88 Rev 2, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition