NIST SP 800-171 Rev. 3 3.8.5 — Media Transport

What this control requires

This control requires protecting and controlling system media containing Controlled Unclassified Information (CUI) during transport outside of controlled areas. It mandates maintaining accountability and documenting all activities associated with the transport of such media to ensure its security and prevent loss, destruction, or tampering. This control supports the Transport Management capability within the Media Protection (3.8) family.

In plain English

This control requires protecting and controlling system media containing Controlled Unclassified Information (CUI) during transport outside of controlled areas. In practice, this means you can prove you access 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.5) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• 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.
• Scope: management, cui, security, transport, encryption, protection.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.
• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Media Transport.

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-5 — Media Transport
• ISO/IEC 27001:2022 A.5.16 — Identity management
• SOC 2 (2017 TSC) CC6.6 — Boundary Protection
• CIS Controls v8 6.1 — Establish an Access Granting Process
• BSI C5:2020 IDM-02 — Granting and change of user accounts and access rights

Related controls in NIST SP 800-171 Rev. 3

• Requirement 3.8.2 — Media Access
• Requirement 3.15.2 — System Security Plan
• Requirement 3.13.4 — Information in Shared System Resources
• Requirement 3.9.1 — Personnel Screening
• Requirement 3.1.22 — Publicly Accessible Content
• Requirement 3.2.2 — Role-Based Training

References

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

Topics: governance riskidentity accessidentity managementaccess reviewprivileged accessencryption in transit