# NIST SP 800-53 Rev. 5 MP-3 — Media Marking - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-3-media-marking - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › MP — Media Protection - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `MP-3`·high·Component: **Media Protection** ## What this control requires > Mark system media with distribution limitations, handling caveats, and security markings. Exempt certain media from marking if in controlled areas, ensuring proper identification and protection. This control supports the Media Marking capability within the Media Protection family. > > — NIST SP 800-53 Rev. 5, Control MP-3 ### In plain English Mark system media with distribution limitations, handling caveats, and security markings. In practice, this means you can prove you policy management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Media Protection**, the assessor will trace your implementation back to the catalogue reference (Control MP-3) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Scope:** management, system, protection, capability, media, mark, identification, policy. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Media Marking. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.8.4** — Media Marking](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-8-4-media-marking) - [**HIPAA (45 CFR Part 164) 164.310(d)(1)** — Device and Media Controls](https://support.icompaas.com/compliance/hipaa/164-310-d-1-device-and-media-controls) - [**BSI C5:2020 SP-01** — Documentation, communication and provision of policies and instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-01-documentation-communication-and-provision-of-policies-and-instructions) - [**ISO/IEC 27001:2022 A.7.14** — Secure disposal or re-use of equipment](https://support.icompaas.com/compliance/iso-27001-2022/a-7-14-secure-disposal-or-re-use-of-equipment) - [**SOC 2 (2017 TSC) C1.1** — Confidential Information Identification and Maintenance](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/c1-1-confidential-information-identification-and-maintenance) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control MP-8** — Media Downgrading](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-8-media-downgrading) - [**Control PL-6** — Security-Related Activity Planning](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pl-6-security-related-activity-planning) - [**Control MP-8(3)** — Controlled Unclassified Information](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-8-3-controlled-unclassified-information) - [**Control MP-8(4)** — Classified Information](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-8-4-classified-information) - [**Control MP-6(5)** — Classified Information](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-6-5-classified-information) - [**Control MP-6(6)** — Media Destruction](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/mp-6-6-media-destruction) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control MP-3` Topics: governance riskpolicy management ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.