DCH-11: Media Marking
Mechanisms exist to mark media in accordance with data protection requirements so that personnel are alerted to distribution limitations, handling caveats and applicable security requirements.
Renumbered: Formerly DCH-04 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, DCH-11 was Data Reclassification. That control is now DCH-04.2.
Control Question: Does the organization mark media in accordance with data protection requirements so that personnel are alerted to distribution limitations, handling caveats and applicable security requirements?
General (19)
| Framework | Mapping Values |
|---|---|
| GovRAMP | MP-03 |
| GovRAMP Low+ | MP-03 |
| GovRAMP Moderate | MP-03 |
| GovRAMP High | MP-03 |
| ISO 27002 2022 | 5.10 5.13 |
| ISO 27017 2015 | 8.1.3 8.2.2 |
| ISO 27018 2025 | 5.10 5.13 |
| MPA Content Security Program 5.3.1 | OP-3.0 |
| NIST 800-53 R4 | MP-3 |
| NIST 800-53 R5.2 | MP-03 |
| NIST 800-53B R5 (moderate) (source) | MP-03 |
| NIST 800-53B R5 (high) (source) | MP-03 |
| NIST 800-82 R3 | MP-03 |
| NIST 800-82 R3 MODERATE OT Overlay | MP-03 |
| NIST 800-82 R3 HIGH OT Overlay | MP-03 |
| NIST 800-171 R2 (source) | 3.8.4 |
| NIST 800-171 R3 (source) | 03.08.04 |
| NIST 800-171A (source) | 3.8.4[a] 3.8.4[b] |
| NIST 800-171A R3 (source) | A.03.08.04[01] A.03.08.04[02] A.03.08.04[03] |
US (11)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | MP-3 MP-3.a MP-3.b |
| USA Federal DHS CISA TIC 3.0 | 3.PEP.DA.DLABE |
| USA Federal CMMC 2.0 Level 2 | MPL2.-3.8.4 |
| USA Federal NNPI (unclass) 2010 | 2-6 2-7 2-7.a(1) 2-7.a(2) 2-7.a(3) 2-7.b 2-7.b(1)(a) 2-7.b(1)(b) 2-7.b(2)(a) 2-7.b(2)(b) 2-7.c(1) 2-7.c(2) 2-7.c(2)(a) 2-7.c(2)(b) 2-7.c(2)(c) 9-2.c |
| USA Federal CJIS Security Policy 6.0 | MP-3 |
| USA Federal FedRAMP R5 (moderate) | MP-03 |
| USA Federal FedRAMP R5 (high) | MP-03 |
| USA Federal IRS 1075 2021 | 2.B.6-1 MP-3 |
| USA Federal NISPOM 2020 | §117.14(a)(1) §117.14(a)(2) §117.14(b) §117.14(c) §117.14(d) §117.14(e) §117.14(f) §117.14(f)(1) §117.14(f)(2) §117.14(g) §117.14(g)(1) §117.14(g)(2) §117.14(h) §117.14(i) §117.14(i)(1) §117.14(i)(1)(i) §117.14(i)(1)(ii) §117.14(i)(2) §117.14(i)(3) §117.14(i)(4) §117.14(j) §117.14(j)(1) §117.14(j)(1)(i) §117.14(j)(1)(ii) §117.14(j)(1)(iii) §117.14(j)(2) §117.14(j)(3) §117.14(k) §117.14(k)(1) §117.14(k)(2) §117.14(k)(3) §117.14(k)(3)(i) §117.14(k)(3)(ii) §117.14(k)(3)(iii) §117.14(l) §117.14(m) §117.14(m)(1) §117.14(m)(2) §117.14(m)(2)(i) §117.14(m)(2)(ii) §117.14(m)(2)(iii) §117.14(m)(3) §117.14(n) §117.14(n)(1) §117.14(n)(2) §117.14(n)(3) §117.14(o) §117.14(p) §117.14(q) |
| USA California CCPA 2025 | 7123(c)(4)(A) |
| USA Texas TX-RAMP Level 2 | MP-03 |
EMEA (3)
| Framework | Mapping Values |
|---|---|
| EMEA Germany C5 2026 | AM-09.01B |
| EMEA Spain CCN-STIC 825 | mp.si.1 |
| EMEA Saudi Arabia ECC-1 2018 | 2-1-5 |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-0201 ISM-0270 ISM-0272 ISM-0294 ISM-0296 ISM-0332 ISM-0356 ISM-0358 ISM-0360 |
| APAC Japan ISMAP | 8.2.2 8.2.2.1 8.2.2.2 8.2.2.3 8.2.2.4 8.2.2.5 8.2.2.6 8.2.2.7.PB 8.2.3.6 |
| APAC New Zealand NZISM 3.9 | 4.4.10.C.01 12.3.4.C.01 12.3.5.C.01 12.3.5.C.02 12.3.6.C.01 12.3.7.C.01 13.2.12.C.01 13.2.12.C.02 13.2.12.C.03 13.2.12.C.04 13.2.13.C.01 13.2.14.C.01 13.2.14.C.02 22.1.21.C.01 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.08.04 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Data Classification & Handling (DCH) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with DCH domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with DCH domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Data classification and handling-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Data classification and handling management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ A formalized data classification scheme exists to identify categories of data, based on protection requirements from applicable laws, regulations and/or contractual obligations.
Level 3 — Well Defined
Data Classification & Handling (DCH) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with DCH domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are well-documented and kept current by process owners. ▪ A Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain DCH domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of data classification and handling operations (e.g., GRC platform). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with DCH domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to mark media in accordance with data protection requirements so that personnel are alerted to distribution limitations, handling caveats and applicable security requirements.
Level 4 — Quantitatively Controlled
Data Classification & Handling (DCH) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- DCH-11_A01 types of media exempt from marking when remaining in controlled areas are defined.
- DCH-11_A02 media is marked with applicable sensitive / regulated data markings.
- DCH-11_A03 media is marked to indicate distribution limitations, handling caveats and applicable security markings (if any) of the information.
- DCH-11_A04 controlled areas where media is exempt from marking are defined.
- DCH-11_A05 types of media exempted from marking remain within controlled areas.
- DCH-11_A06 system media that contain sensitive / regulated data are marked to indicate distribution limitations.
- DCH-11_A07 system media that contain sensitive / regulated data are marked to indicate handling caveats.
- DCH-11_A08 system media that contain sensitive / regulated data are marked to indicate applicable security requirements.
- DCH-11_A09 system media that contain CUI are marked to indicate distribution limitations.
- DCH-11_A10 system media that contain CUI are marked to indicate handling caveats.
- DCH-11_A11 system media that contain CUI are marked to indicate applicable CUI markings.
Evidence Requirements
- E-DCH-02 Data Handling Practices
-
Documented evidence of an organization-specific data handling practices (e.g., guidance specific the data classification scheme).
Data Protection
Technology Recommendations
Micro/Small
- Data classification program
- Metadata tagging
- IT Asset Management (ITAM) program
Small
- Data classification program
- Metadata tagging
- IT Asset Management (ITAM) program
Medium
- Data classification program
- Metadata tagging
- IT Asset Management (ITAM) program
- Data governance program
Large
- Data classification program
- Metadata tagging
- IT Asset Management (ITAM) program
- Data governance program
Enterprise
- Data classification program
- Metadata tagging
- IT Asset Management (ITAM) program
- Data governance program