DOMAIN 2 · Asset Security
Media sanitization and secure disposal
Choose clear, purge, or destroy using information sensitivity, storage technology, reuse plans, and evidence of successful sanitization.
Define the protection goal
Section titled “Define the protection goal”Media sanitization makes access to target information infeasible for a specified level of effort. NIST SP 800-88 Rev. 2, published in September 2025, supersedes Rev. 1 and emphasizes an organizational sanitization program.1 The goal is protecting information confidentiality when media or logical storage is reused, transferred, or retired.
Do not begin with a favorite erasure tool. Establish what information was stored, how sensitive it is, who will control the media next, and what evidence the organization needs.
Compare the three methods
Section titled “Compare the three methods”| Method | Protection concept | Important consideration |
|---|---|---|
| Clear | Logical techniques address user-accessible storage | Does not automatically reach every hidden or remapped area |
| Purge | Makes recovery infeasible using advanced laboratory techniques | Requires an appropriate technique and evidence for the medium |
| Destroy | Makes recovery infeasible and media unusable for storage | Physical damage alone is not proof of successful sanitization |
The 2026 NIST FAQ confirms these three methods and explains that Rev. 2 refers to evolving standards for media-specific techniques.2 A method is the protection category; a command, process, or device is a technique used to implement it.
Account for storage behavior
Section titled “Account for storage behavior”Solid-state storage can remap blocks and maintain spare capacity outside ordinary user writes. Overwriting the visible filesystem should not be assumed to sanitize every copy. Degaussing applies to appropriate magnetic media; it does not sanitize flash simply because a drive becomes inoperable.2
Select a supported technique for the actual device and required outcome. Record the model, asset identifier, condition, relevant configuration, and any failure. Treat an unreadable or failed device as a decision requiring an approved alternative, rather than evidence that its information is safe.
Evaluate cryptographic erase carefully
Section titled “Evaluate cryptographic erase carefully”Cryptographic erase removes the keys needed to decrypt protected information. Its effectiveness depends on sound encryption and key handling, including the absence of earlier sensitive plaintext copies and the sanitization of relevant keys.2
For an illustrative cloud dataset, deleting one local key is inadequate if a wrapping key, exported key, or recoverable key backup still provides access. Shared keys can also prevent selective erasure without affecting other tenants. Establish the encryption boundary and all recovery paths before relying on this technique.
Separate verification from validation
Section titled “Separate verification from validation”Verification checks whether the sanitization operation completed successfully without technical errors. Validation uses that evidence and information sensitivity to decide whether the result is acceptable.2 A tool’s success message is one input, not the complete approval decision.
An evidence record can connect the asset, method, technique, operator, date, results, exceptions, and authorized disposition. These are practical record examples rather than a claim that every organization needs an identical form.
Example: retiring employee laptops
Section titled “Example: retiring employee laptops”First check retention obligations and preserve records that must remain. Inventory each laptop and its storage, confirm sensitivity, and decide whether it will remain inside the organization or leave its control. Select an approved technique, perform verification, validate the result, and document handover.
Keep unsuccessful devices out of the reuse stream until a suitable alternative completes. If an external provider performs the work, define evidence and exception handling in advance; a purchase order alone does not establish successful sanitization.
Avoid common misconceptions
Section titled “Avoid common misconceptions”File deletion, formatting, and an unverified factory reset are not interchangeable assurances. Repeating an overwrite many times does not solve a technique that cannot reach the target data. Cloud storage also needs sanitization planning: service agreements, encryption boundaries, key management, and traceable evidence matter.2
Continue learning
Section titled “Continue learning”Use information classification to determine sensitivity and cryptography to understand key dependencies.
Footnotes
Section titled “Footnotes”-
NIST, SP 800-88 Rev. 2, September 2025. ↩
-
NIST, FAQ for SP 800-88r2, July 16, 2026, questions 1–9 and 13. ↩ ↩2 ↩3 ↩4 ↩5
Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.
Editorial policy & attribution