1.1 | Purpose 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 a | 0 |
1.1-RET | Consult privacy, FOIA and records retention officials and organisational management before sanitizing, so that Federal Records Act retention duties and business history needs are m | 0 |
1.2-1.5 | Audience, assumptions, related NIST documents and document structure | 0 |
2 | Background: disposition decisions begin at system design, media leave organisational control throughout the life cycle, and sanitization is a confidentiality safeguard against data | 0 |
2.2 | Types of media: hard copy and information storage media (devices and virtual or logical storage), with non-volatile storage the main focus | 0 |
2.3 | Target of sanitization: all user data when sensitive data cannot be selectively removed, and the full physical capacity including overprovisioned and compressed areas | 0 |
2.4 | Weigh 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 |
3 | Categorise the information, assess the media and the confidentiality risk, decide the media's future, then choose and justify the sanitization method | 0 |
3.1 | Use the three methods (clear, purge, destroy) with technology-specific techniques kept current against IEEE 2883, matched carefully to the media type | 0 |
3.1.1 | Clear: logical techniques over the user interface against simple recovery; not for hard copy; avoid multi-pass overwriting on overprovisioned flash; use dedicated sanitize commands | 0 |
3.1.2 | Purge: physical or logical techniques that defeat laboratory recovery while keeping the ISM reusable; prefer purge to clear; choose techniques from IEEE 2883; cryptographic erase m | 0 |
3.1.3 | Destroy: render recovery infeasible and the media unusable by disintegrating, incinerating, melting, pulverizing or shredding; partial damage does not count; avoid shred and pulver | 0 |
3.2 | Cryptographic 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 standard | 0 |
3.2.1 | Strength 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, key | 0 |
3.2.2 | Applicability 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 backe | 0 |
3.2.3 | Sanitization 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 extern | 0 |
3.2.4 | Quality of cryptographic implementations: obtain independent validation or vendor evidence on entropy and key generation, algorithm and mode implementation, key sanitization techni | 0 |
3.2.5 | Traceability of CE: document make and model, key generation, media encryption, key wrapping, encrypted and unencrypted areas, key life cycle handling, key sanitization technique, e | 0 |
4 | Make storage sanitization part of data governance with, at minimum, disposal policies and minimum methods, scope and decision criteria, performance of sanitization, adequacy determ | 0 |
4.1 | Storage sanitization policy: align data classification with minimum methods; set disposal and reuse requirements, expected outcomes and acceptable techniques, documentation, roles | 0 |
4.2 | Scope: 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.3 | Decision 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.1 | Plan sanitization from the system security plan onward: choose ISM with sanitization in mind, obtain Statements of Volatility and the Appendix B characteristics, identify every ISM | 0 |
4.3.2 | Security 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 assign | 0 |
4.3.3-4.3.4 | Decide 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 organisati | 0 |
4.3.5 | Consider the data protection level alongside organisational control when deciding whether sanitization is necessary | 0 |
4.3.6 | Make and record the risk-based sanitization decision, then put the process, resources, verification steps and interfaces with key officials in place to carry it out | 0 |
4.4 | Perform sanitization by the selected method in line with IEEE 2883 or another policy-approved standard, using the most protective available technique, capturing results and documen | 0 |
4.5 | Assure sanitization by inspecting results and deciding adequacy; repeat with a different technique or a stronger method when unacceptable, rechecking reusability | 0 |
4.5.1 | Verify 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.2 | Validate effectiveness: analyse errors and anomalies, assess confidentiality risk, and reject the sanitization where inaccessible areas, an inappropriate method, unqualified person | 0 |
4.6 | Document each sanitized ISM on a certificate of sanitization recording manufacturer, model, serial and property numbers, media type and source, prior category, method, technique, t | 0 |
4.7 | Assign programme roles: programme managers and agency heads for governance and resources, the CIO for policy, system owners for protective maintenance contracts, information owners | 0 |
B | Obtain 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 its | 0 |
C | Sample certificate of sanitization: person performing, media information, sanitization details, destination and disposition, signature and concurrence | 0 |