| name | MP-3_media-marking |
| description | Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; |
| category | configuration |
| version | 5.2.0 |
| author | cyberstrike-official |
| tags | ["nist","sp800-53","rev5","mp-3","mp"] |
| tech_stack | ["linux","windows"] |
| cwe_ids | [] |
| chains_with | ["AC-16","CP-9","MP-5","PE-22","SI-12"] |
| prerequisites | [] |
| severity_boost | {"AC-16":"Chain with AC-16 for comprehensive security coverage","CP-9":"Chain with CP-9 for comprehensive security coverage","MP-5":"Chain with MP-5 for comprehensive security coverage"} |
MP-3 Media Marking
High-Level Description
Family: Media Protection (MP)
Framework: NIST SP 800-53 Rev 5
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 . 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.
What to Check
How to Test
Step 1: Review Documentation
Examine the System Security Plan (SSP) and related artifacts for MP-3 implementation details. Verify the organization has documented how this control is satisfied.
Step 2: Validate Implementation
# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly
# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null
Step 3: Test Operating Effectiveness
Verify the control is actively functioning, not just documented. Check logs, configurations, and operational evidence.
Tools
| Tool | Purpose | Usage |
|---|
| Manual Review | Documentation and interview-based | N/A |
Remediation Guide
Control Statement
Mark system media indicating the distribution limitations, handling caveats, and applicable security markings (if any) of the information; and
Exempt [organization-defined] from marking if the media remain within [organization-defined].
