3.8.7·high·Component: Media ProtectionWhat this control requires
This control restricts or prohibits the use of specific types of system media, such as external hard drives and flash drives, and mandates the prohibition of removable media without an identifiable owner. The control includes using technical and non-technical measures to manage media usage, such as limiting devices to approved ones and enforcing restrictions on writable media. This control supports the Media Usage Control System capability within the Media Protection (3.8) family.
In plain English
This control restricts or prohibits the use of specific types of system media, such as external hard drives and flash drives, and mandates the prohibition of removable media without an identifiable owner. In practice, this means you can prove you protection security-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.7) and look for objective evidence on the latest two assessment cycles.
How to implement
Endpoint Protection
MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.
EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.
Operational checklist
- 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.
- Media Use. Document the trigger, the owner and the cadence.
- Security. Document the trigger, the owner and the cadence.
- Scope: security, external hard drives, flash drives, protection.
Evidence to collect
- User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).
Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Media Use.
Common pitfalls
- Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.
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.
Related controls in NIST SP 800-171 Rev. 3
- Requirement 3.13.1 — Boundary Protection
- Requirement 3.13.12 — Collaborative Computing Devices and Applications
References
- NIST Computer Security Resource Center — NIST SP 800-171 Rev. 3
- Catalogue identifier:
Requirement 3.8.7
Topics: endpoint securityendpoint protection