Skip to content
All CMMC practices
CMMC · Rev 2.13L2MP · Media Protection

MP.L2-3.8.4

Media Markings

Requirement

Mark media with necessary CUI markings and distribution limitations.

Assessment objectives

An assessor checks each lettered objective separately. The letters in brackets elsewhere on this page, such as [a] or [b,c], refer to these.

Determine if:

  1. amedia containing CUI is marked with applicable CUI markings; and
  2. bmedia containing CUI is marked with distribution limitations.

From the CMMC Level 2 Assessment Guide v2.13 · publisher approved 2026-10-31.

How to implement

Mark every piece of media that contains CUI, paper and digital, so anyone who picks it up knows it is CUI and who may receive it. Follow the marking instructions in your contract and the DoD CUI marking guidance: a CUI banner, a designation indicator, and any limited dissemination control or DoD distribution statement that applies. For USB drives, disks and discs, that means a physical CUI label; for files and emails, banners applied in the document or by sensitivity labels.

The minimum for a small organization · Expert CMMC's reading, not official text

Mark media that holds CUI with the CUI markings [a] and with its distribution limits [b]. Documents carry the CUI banner and designation indicator; drives and discs carry a CUI label; and both show the distribution statement or dissemination control.

Required outcome: what the requirement or its objectives call for. Recommended way: one common way to get there. Going further: worth doing, more than this practice asks.

  1. 1
    Required outcomeTechnicalIdentify the media that hold CUI and mark each one, documents, files, drives and discs alike, with the CUI markings that apply to it (the CUI banner and designation indicator on documents and files, a CUI label on drives and discs), and with the distribution statement or limited dissemination control that applies.[a][b]

    You can tell it worked when sampled CUI documents and media carry the CUI markings that apply (the banner and designation indicator on documents, a CUI label on drives and discs) and show the distribution statement or limited dissemination control.

  2. 2
    Recommended wayPolicyWrite a CUI marking procedure based on DoDI 5200.48 and the DoD CUI marking guidance: what the banner looks like ('CUI' at top and bottom), the designation indicator block (controlled by, category, dissemination control, point of contact), and how to carry forward the government's markings and distribution statements when you create derivative documents. Follow contract-specific instructions when they differ.[a][b]
  3. 3
    Recommended wayProcessIdentify all CUI media and train staff to recognize it: incoming government documents and drawings already carry markings; when you create CUI (derived drawings, reports, spreadsheets), apply the same banner and the source's distribution statement or dissemination control.[a][b]
  4. 4
    Recommended wayTechnicalLabel physical media: apply CUI labels (NARA SF 902 or SF 903, or an equivalent printed label) to USB drives, external disks, optical discs and tapes, and add the owner's name or asset number so the item also has an identifiable owner, which MP.L2-3.8.8 relies on (the label alone does not meet that practice: you still need the rule that devices with no identifiable owner are not used).[a]
  5. 5
    Recommended wayTechnicalShow distribution limits on the media itself: the DoD distribution statement (for example Distribution D: DoD and U.S. DoD contractors only) or limited dissemination control (such as NOFORN, FEDCON or DL ONLY) on documents, labels and file headers, as the source document specifies.[b]
  6. 6
    Recommended wayTechnicalAutomate digital markings where you can: sensitivity labels that insert CUI headers, footers and watermarks in Office files and emails, and document templates with the banner and designation block built in.[a][b]
  7. 7
    Recommended wayProcessSpot-check quarterly: sample CUI files, printouts and media for correct marking and fix any gaps; record the check.[a][b]

Evidence to collect

Artifacts that show the practice is implemented and operating. Tags show which assessment objectives each one supports.

A process you started recently is shown honestly by its dated procedure, the first record it produced and the date it began. No evidence row needs more history than the process has existed, and the review periods shown are suggestions unless a guide page or regulation is named beside them.

CUI marking procedure[a][b]

Examples of marked documents and media[a][b]

Also supports 1 other practice: keep it once

Sensitivity label configuration[a][b]

Marking training records[a][b]

Quarterly marking spot-check[a][b]

The detail for 5 evidence items: how to produce each, how fresh it must be, what it must include and what it does not show.

Free with an account. Create a free account or sign in.

How assessors check

What an assessor examines, asks and tests: 3 notes.

Free with an account. Create a free account or sign in.

Tools and products

Named options a contractor can adopt, with an honest cost tier. The industry standard is listed even when it is expensive, alongside what is free and acceptable for a very small shop.

Microsoft Purview Information Protection (sensitivity labels)Automated document markingPaid
Fortra Titus ClassificationEnterprise data classificationEnterprise pricing
NARA SF 901 cover sheet and SF 902 / SF 903 labelsStandard formsFree
DoD CUI Program marking guidanceStandardFree
Label printer (Brother P-touch, DYMO) and document templatesPhysical labelsPaid

11 dated vendor facts and notes on 5 products for this practice: what each assumes, what it does not cover and what stays yours.

Free with an account. Create a free account or sign in.

Editorial mentions, not endorsements. Pricing and tiers change; confirm with the vendor and check FedRAMP or GCC High availability where CUI is involved.

Common pitfalls

  • Unlabeled USB drives full of CUI drawings.
  • Dropping the government's distribution statement when copying content into your own drawings or reports.
  • Using legacy FOUO markings or inventing your own scheme instead of the DoD CUI format.
  • Marking everything as CUI 'to be safe', which makes it impossible to tell what actually needs protection and can conflict with contract instructions.

Platform notes

  • Microsoft 365 (GCC / GCC High)
  • Google Workspace
  • On-premises or MSP-managed

Notes for 3 platforms.

Free with an account. Create a free account or sign in.

Related practices: MP.L2-3.8.8, MP.L2-3.8.1, AT.L2-3.2.1, AC.L2-3.1.3

Editorial implementation guidance published November 14, 2026. It is not part of the official requirement and does not replace the assessment guide.

The NIST requirements this practice is built on, what NIST made of each in the newer edition, and the SP 800-53 controls behind them, each from an official NIST or DoD table. Open any one to read it and see every CMMC practice it supports.

NIST SP 800-171 Rev 2

3.8.4

SP 800-171 Rev 3

03.08.04

SP 800-53 Rev 4

MP-3

SP 800-53 Rev 5

MP-3DS
How these were reached
  • MP-3 · Media Marking
    • D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison · via 800-53 Rev 4 MP-3 → 800-53 Rev 5 MP-3
    • S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-171 Rev 3 03.08.04 → 800-53 Rev 5 MP-3

Rev 5 paths: D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison; S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL); C SP 800-172 (Feb 2021) Appendix C. NIST also names this Rev 3 requirement as the successor of other withdrawn requirements: open “How these were reached” under the Rev 5 controls for which, in NIST's words.

Where each link comes from (5 links from 5 official documents)

32 CFR Part 170 Office of the Federal Register / GPO

  • MP.L2-3.8.4 → 3.8.4“Level 2 security requirement”32 CFR 170.14(c)(1) numbering (REQ is the NIST SP 800-171 R2 requirement number) and 170.14(c)(3)

NIST SP 800-171 Rev 2 → Rev 3 change analysis NIST

  • 3.8.4 → 03.08.04“No Significant Change”sheet "Change Analysis 800-171 R2-R3" row 74

NIST SP 800-171 Rev 2 NIST

  • 3.8.4 → MP-3“Appendix D mapping”p.87 Table D-8

NIST SP 800-53 Rev 4 → Rev 5 comparison NIST

  • MP-3 → MP-3“Changes control text Changes discussion”sheet "Rev4 Rev5 Compared" row 536

NIST SP 800-171 Rev 3 (OSCAL) NIST

  • 03.08.04 → MP-3“Source control”control 03.08.04 link rel=reference (MP-03)

Further discussion

All media, hardcopy and digital, must be properly marked to alert individuals to the presence of CUI stored on the media. The National Archives and Records Administration (NARA) has published guidelines for labeling media of different sizes. MP.L2-3.8.8 requires that media have an identifiable owner, so organizations may find it desirable to include ownership information on the device label as well. Example You were recently contacted by the project team for a new DoD program. The team said they wanted the CUI in use for the program to be properly protected. When speaking with them, you realize that most of the protections will be provided as part of existing enterprise cybersecurity capabilities. They also mentioned that the project team will use several USB drives to share specific data. You explain that the team must ensure the USB drives are externally marked to indicate the presence of CUI [a]. The project team labels the outside of each USB drive with an appropriate CUI label following NARA guidance [a]. Further, the labels indicate that distribution is limited to those employees supporting the DoD program [a]. Potential Assessment Considerations • Are all media containing CUI identified [a,b]?

Practice guide notes

Implementation guidance

Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.

In plain language

Mark media with the applicable controlled-information markings and distribution limitations.

Implementation example

Example from the source assessment guide (not a mandatory implementation): You were recently contacted by the project team for a new DoD program. The team said they wanted the CUI in use for the program to be properly protected. When speaking with them, you realize that most of the protections will be provided as part of existing enterprise cybersecurity capabilities. They also mentioned that the project team will use several USB drives to share specific data. You explain that the team must ensure the USB drives are externally marked to indicate the presence of CUI [a]. The project team labels the outside of each USB drive with an appropriate CUI label following NARA guidance [a] . Further, the labels indicate that distribution is limited to those employees supporting the DoD program [a].

Evidence examples

Examples suggested by the source guide (not an exhaustive or mandatory checklist): System media protection policy; procedures addressing media marking; physical and environmental protection policy and procedures; system security plan; list of system media marking security attributes; designated controlled areas; other relevant documents or records

Common mistakes

Using a generic sensitive label that omits applicable markings or limitations.

Track this in a workspace

The compliance workspace tracks each objective, its evidence and the tasks to close gaps. It is open to invited contractors while in pilot: request access below.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Source: DoD CIO · https://dodcio.defense.gov/CMMC/