Media Use controls which types of media are allowed to be used at all, which is a different question than who can access the media. Media Access (03.08.02) restricts access to Controlled Unclassified Information (CUI) on media, while Media Use (03.08.07) restricts or prohibits the use of certain media types entirely, such as external hard drives, flash drives, or smart displays. It has two (2) parts: restrict or prohibit the use of a defined set of media types, and prohibit the use of removable media that has no identifiable owner. Per the NIST discussion, organizations can use technical and non-technical measures, such as physical port cages or disabling write capability, and requiring identifiable owners for removable media lets the organization assign responsibility and accountability.
A common difficulty with this requirement is allowing personal USB drives and other unmanaged removable media on systems that handle CUI. Removable media is a classic vector for both data exfiltration and malicious code. R3 wraps an Organization-Defined Parameter (ODP) around the media types to restrict or prohibit, and for Department of Defense (DoD) contractors that parameter is broad: any removable media not managed by or on behalf of the organization.
Where things stand for companies facing the transition from NIST 800-171 R2 to R3:
The following is reproduced verbatim from NIST 800-171 R3, requirement 03.08.07 Media Use. Only the formatting has been adjusted for readability. This requirement has two (2) lettered parts:
The source control is MP-07 from NIST 800-53. The bracketed assignment in part a is the Organization-Defined Parameter (ODP): the types of system media to restrict or prohibit. Per the NIST discussion, this requirement contrasts with 03.08.01 by restricting the use of certain media types rather than access to media, and organizations may limit portable storage devices to approved, organization-provided devices and prohibit writeable portable devices. You can read the requirement directly at NIST 800-171 R3, 03.08.07 (p. 47).
One (1) value sits inside this requirement. Depending on your contract, your organization may be permitted to define it. Organizations in the DIB subject to CMMC are not, because the DoD has defined it as policy.
The value below comes from Attachment A of the DoD Chief Information Officer (CIO) memorandum dated 10 April 2025 (signed David W. McKeown). The memo identifies each parameter by requirement sub-part, while NIST 800-171A R3 identifies the same parameter by ODP number. Both identifiers appear below so you can match your System Security Plan (SSP) language to either document.
The memo states that its values "will be updated as necessary," so confirm against the current version before writing them into policy.
NIST 800-171A R3 breaks 03.08.07 into three (3) assessment objectives: one (1) Organization-Defined Parameter (ODP) and two (2) determination statements. These AOs are:
If you are a DoD contractor, the ODP is specified. Per the DoD-specified ODP value in ComplianceForge's NIST 800-171 R3 Transition Guide, the media types to restrict or prohibit (ODP[01]) are any removable media not managed by or on behalf of the organization. The full guidance on assessment methods and objects, is in NIST 800-171A R3, 03.08.07 (p. 61).
Examine: system media protection policy and procedures; system use policy; procedures for media usage restrictions; rules of behavior; system audit records; system design documentation; system configuration settings; system security plan.
Interview: personnel with system media use responsibilities; personnel with information security responsibilities; system administrators.
Test: processes for media use; mechanisms for restricting or prohibiting the use of system media on systems or system components.
03.08.07 maps from NIST 800-171 R2 requirement 3.8.7 (control the use of removable media on system components), and it absorbs R2 requirement 3.8.8 (prohibit the use of portable storage devices when such devices have no identifiable owner):
Mapped against the three (3) AOs, two (2) are direct (minimal effort) and one (1) is net new (significant effort), with none indirect and none with no mapping. Controlling removable media and prohibiting ownerless devices carry forward, but R3 adds a defined set of media types to restrict or prohibit. Define that set deliberately, and for DoD work adopt the specified broad restriction.
Source Control in NIST 800-53 R5:
Secure Controls Framework (SCF) Crosswalk
Organizations running a single control set across multiple frameworks can satisfy 03.08.07 through the following SCF controls:
The crosswalks from NIST 800-171 R3 and NIST 800-171A R3 to the SCF are available at no cost through the SCF Set Theory Relationship Mapping (STRM): https://securecontrolsframework.com/start-here/set-theory-relationship-mapping-strm. The STRM also carries the relationship type for each mapping (Equal, Subset Of, Intersects With), which tells you whether an SCF control fully satisfies the requirement or only part of it. Mapping above taken from SCF 2026.3.
The following are issues teams may encounter rather than certainties. They are about the defined media types and enforcement, each of which needs documented evidence of due diligence and due care such as policies, standards, procedures, and configuration screenshots:
Reasonable objective evidence for an assessment is often subjective. The following examples of evidence to address NIST 800-171 R3 03.08.07 are sourced from the SCF Evidence Request List (ERL), available at https://securecontrolsframework.com/free-content/scf-download. These ERL artifacts are mapped to NIST 800-171 R3 03.08.07 through SCF controls. They establish a starting point for discussions on what an organization needs to have for evidence of due diligence and due care to withstand external scrutiny by an assessor or regulator.
Alongside these, keep the System Security Plan (SSP) narrative for 03.08.07 recording the ODP values you adopted.
With two (2) AOs mapping directly and one net new, 03.08.07 is a light lift once the media types are defined. A realistic sequence:
What value does the DoD require for the organization-defined parameter in NIST 800-171 R3 03.08.07? R3 leaves the value to the organization. For the DIB, the DoD set it in the 10 April 2025 memorandum under ODP identifier 03.08.07.a: any removable media not managed by or on behalf of the organization.
How many assessment objectives does NIST 800-171 R3 03.08.07 have? NIST 800-171A R3 breaks 03.08.07 into three (3) assessment objectives: one (1) Organization-Defined Parameters (ODPs) and two (2) determination statements. An assessor works through each one separately, so each needs its own evidence.
Which NIST 800-53 R5 control does NIST 800-171 R3 03.08.07 come from? MP-07.
Where does NIST 800-171 R3 03.08.07 sit in the NIST 800-171 R3 Kill Chain? Phase 8, Segmented Network Architecture. The Kill Chain is a phased model for sequencing R3 implementation, and it assigns this requirement to that phase.
03.08.07 Media Use restricts or prohibits the use of defined media types and prohibits removable media without an identifiable owner. It maps from R2 3.8.7 and absorbs 3.8.8, with both use restrictions transitioning directly, while the defined media-type parameter is net new. The recurring problem is allowing unmanaged removable media on CUI systems. Define the restricted media types (for DoD, any removable media not organization-managed), enforce with technical controls, and require identifiable owners.
Authoritative sources:
Authoritative sources:
This guide reproduces U.S. Government text from NIST 800-171 R3 and NIST 800-171A R3 and references the DoD ODP memorandum of 10 April 2025. It is educational, not legal or assessment advice. Last reviewed: 2026-09-22.
