NIST SP 800-171 Rev. 3 3.8.3 — Media Sanitization

What this control requires

This control requires sanitizing system media containing Controlled Unclassified Information (CUI) before disposal, release, or reuse. It includes applying sanitization techniques such as cryptographic erasure, clearing, purging, or physical destruction to ensure that CUI cannot be retrieved or reconstructed, protecting against unauthorized disclosure. This control supports the Sanitization Management capability within the Media Protection (3.8) family.

In plain English

This control requires sanitizing system media containing Controlled Unclassified Information (CUI) before disposal, release, or reuse. In practice, this means you can prove you information management-level controls on a defined cadence.

Why it matters

DoD contractors and their subcontractors must implement all 100 SP 800-171 requirements to keep CUI handling contracts. Gaps are scored against the SPRS scoring methodology; below a 110-point starting score, each unmet requirement deducts points and a below-threshold score can disqualify a bid.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A C3PAO conducting a CMMC Level 2 assessment uses NIST SP 800-171A objectives. They expect a System Security Plan (SSP), Plan of Action & Milestones (POA&M) for any gaps, and objective evidence (configurations, ticket records, training records) for every requirement.

Within Media Protection, the assessor will trace your implementation back to the catalogue reference (Requirement 3.8.3) and look for objective evidence on the latest two assessment cycles.

How to implement

Physical Security

Inheritance. For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Information. Document the trigger, the owner and the cadence.
• Protection. Document the trigger, the owner and the cadence.
• System. Document the trigger, the owner and the cadence.
• Media. Document the trigger, the owner and the cadence.
• Physical. Document the trigger, the owner and the cadence.
• Scope: management, cui, security, sanitization, cryptographic erasure, protection, disposal.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Media Sanitization.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-53 Rev. 5 MP-6(1) — Review, Approve, Track, Document, And Verify
• ISO/IEC 27001:2022 A.7.3 — Securing offices, rooms and facilities
• SOC 2 (2017 TSC) P2.1 — Communication of Data Subject Choices and Consequences
• HIPAA (45 CFR Part 164) 164.308(a)(5)(i) — Security Awareness and Training
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions

Related controls in NIST SP 800-171 Rev. 3

• Requirement 3.8.1 — Media Storage
• Requirement 3.8.4 — Media Marking
• Requirement 3.13.11 — Cryptographic Protection
• Requirement 3.15.1 — Policy and Procedures
• Requirement 3.10.6 — Alternate Work Site
• Requirement 3.4.11 — Information Location

References

• NIST Computer Security Resource Center — NIST SP 800-171 Rev. 3
• Catalogue identifier: Requirement 3.8.3

Topics: governance riskphysical securitypolicy management