- Define who may access each media type or storage location, by role where possible, and keep it consistent with system-level access decisions for the same CUI.
- Where a media library or safe exists, log check-outs — the access record doubles as the accountability record.
03.08.02 — Media Access
03.08 Media Protection · NIST SP 800-171 Rev. 3
Requires restricting access to CUI on system media to authorized personnel or roles.
Rev. 3 requirement text is multi-part and parameterized with organization-defined values, so this site summarizes rather than reproduces it. The summary is independent — read the official publication for the binding wording.
NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI ↗What this requirement is after
Storage keeps media put; access decides who may take it out and read it. Access to CUI-bearing media is granted by name or role and defensible on review — not 'everyone with a key to the office'.
Brilliant at the Basics practices that support this requirement
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Implementation considerations and evidence
- The access authorization list per media store
- Check-out or access logs where operated
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
Where this came from in Rev. 2
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 3 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A Rev. 3 — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |