Media Marking makes the sensitivity of media visible so people handle it correctly. It is part of the Media Protection (03.08) family and complements the storage, access, and sanitization requirements by putting human-readable markings on media that hold Controlled Unclassified Information (CUI). Media Marking (03.08.04) is a single statement: mark system media that contain CUI to indicate distribution limitations, handling caveats, and applicable CUI markings. Per the NIST discussion, marking refers to human-readable security attributes applied to media, in contrast to labeling for internal system data structures, and CUI, along with its marking, safeguarding, and dissemination requirements, is defined by the National Archives and Records Administration (NARA).
A common difficulty with this requirement is marking media with a generic label while missing the specific elements the requirement calls for. R3 assesses three distinct things: distribution limitations, handling caveats, and the applicable CUI markings themselves. Handling caveats in particular are easy to overlook, and they do not trace cleanly to a R2 objective, so they are effectively new attention for many organizations.
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.04 Media Marking. Only the formatting has been adjusted for readability. This is a single statement with no lettered parts:
The source control is MP-03 from NIST 800-53. There are no Organization-Defined Parameters (ODPs). Per the NIST discussion, marking uses human-readable security attributes, system media include both digital media such as drives, tapes, and discs and non-digital media such as paper and microfilm, and NARA defines CUI along with its marking, safeguarding, and dissemination requirements. You can read the requirement directly at NIST 800-171 R3, 03.08.04 (p. 46).
None (0). Requirement 03.08.04 contains no bracketed assignment, so there is no organization-defined value to select and nothing for the DoD to specify. The requirement applies as written.
Your System Security Plan (SSP) narrative for 03.08.04 therefore records how the requirement is implemented rather than a parameter you chose.
NIST 800-171A R3 breaks 03.08.04 into three (3) determination statements, and it has no Organization-Defined Parameters (ODPs). These AOs are:
The single statement expands into three separate marking elements: distribution limitations, handling caveats, and applicable CUI markings. An assessor checks all three. The full guidance on assessment methods and objects, is in NIST 800-171A R3, 03.08.04 (p. 59).
Examine: physical protection policy and procedures; media protection policy and procedures; procedures for media marking; list of system media marking security attributes; system security plan.
Interview: personnel with system media protection and marking responsibilities; personnel with information security responsibilities.
Test: processes for marking information media; mechanisms for supporting or implementing media marking.
03.08.04 maps from NIST 800-171 R2 requirement 3.8.4 (mark media with necessary CUI markings and distribution limitations):
Mapped against the three (3) AOs, two (2) are direct (minimal effort) and one (1) has no clear mapping (significant effort), with none indirect and none net new. Distribution limitations and CUI markings carry forward, but marking for handling caveats is the element that does not trace cleanly to a R2 objective. Confirm your marking scheme captures handling caveats in addition to CUI markings and distribution limitations.
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.04 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 specific marking elements, 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.04 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.04 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.04.
With two (2) AOs mapping directly and one with no clear mapping, 03.08.04 is a light lift with one element to add. A realistic sequence:
How many assessment objectives does NIST 800-171 R3 03.08.04 have? NIST 800-171A R3 breaks 03.08.04 into three (3) assessment objectives. 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.04 come from? MP-03.
How many Organization-Defined Parameters (ODPs) does NIST 800-171 R3 03.08.04 have? None (0). The requirement contains no bracketed assignment, so there is no organization-defined value and nothing for the DoD to specify.
Where does NIST 800-171 R3 03.08.04 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.04 Media Marking marks system media containing CUI to indicate distribution limitations, handling caveats, and applicable CUI markings. It maps from R2 3.8.4 with distribution limitations and CUI markings transitioning directly, while handling caveats have no clear R2 mapping. The recurring problem is a generic label that misses handling caveats. Use the NARA-defined CUI markings, mark distribution limitations, add handling caveats, and cover both digital and non-digital media.
Authoritative sources:
Authoritative sources:
This guide reproduces U.S. Government text from NIST 800-171 R3 and NIST 800-171A R3. It is educational, not legal or assessment advice. Last reviewed: 2026-09-22.
