Control statement
- a.Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and
- b.Exempt [Organization-defined: types of media exempted from marking] from marking if the media remain within [Organization-defined: controlled areas].
Discussion
Security marking refers to the application or use of human-readable security attributes. Digital media includes diskettes, magnetic tapes, external or removable hard disk drives (e.g., solid state, magnetic), flash drives, compact discs, and digital versatile discs. Non-digital media includes paper and microfilm. Controlled unclassified information is defined by the National Archives and Records Administration along with the appropriate safeguarding and dissemination requirements for such information and is codified in [32 CFR 2002](#91f992fb-f668-4c91-a50f-0f05b95ccee3) . Security markings are generally not required for media that contains information determined by organizations to be in the public domain or to be publicly releasable. Some organizations may require markings for public information indicating that the information is publicly releasable. System media marking reflects applicable laws, executive orders, directives, policies, regulations, standards, and guidelines.
Organization-defined parameters
These values must be resolved through the organization’s tailoring and governance process. Bracketed parameter references in the control text identify where a decision is required.
From control text to operational evidence
Use Media Marking as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to media accountability, handling, sanitization, transport, and disposal across physical and digital forms.
Implementation workflow
- Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
- Resolve each organization-defined parameter before declaring the control implemented.
- Document how the implementation satisfies every clause of the official control statement.
- Collect evidence as a normal byproduct of operation rather than only before an assessment.
- Review exceptions, changes, and monitoring results on a risk-based cadence.
Evidence examples
- media inventories and chain-of-custody records
- sanitization certificates
- transport and storage procedures
- removable-media control logs
Common failure patterns
- cloud snapshots and virtual media excluded from policy
- sanitization method not matched to media type
- untracked removable media
- disposal vendors accepted without verification
Questions practitioners should ask
- What risk decision is this control intended to support in this system?
- Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
- Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
- What event or threshold requires the implementation to be reviewed or changed?
Assessment objectives and methods
Show the assessment objective
- MP-03a.system media is marked to indicate distribution limitations, handling caveats, and applicable security markings (if any) of the information;
- MP-03b.[Organization-defined: types of media exempted from marking] remain within [Organization-defined: controlled areas].
Examine
- System media protection policy
- procedures addressing media marking
- physical and environmental protection policy and procedures
- list of system media marking security attributes
- designated controlled areas
- system security plan
- other relevant documents or records
Interview
- Organizational personnel with system media protection and marking responsibilities
- organizational personnel with information security responsibilities
Test
- Organizational processes for marking information media
- mechanisms supporting and/or implementing media marking
Related controls
These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.
Authoritative sources
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. Official control requirements and interpretations remain with NIST and the responsible authorizing organization.