DCH-01: Data Protection
Mechanisms exist to facilitate the implementation of data protection controls.
Control Question: Does the organization facilitate the implementation of data protection controls?
General (64)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | A1.2-POF7 C1.1 C1.1-POF2 CC2.1 CC6.5 CC6.7 CC6.7-POF2 CC8.1-POF16 CC8.1-POF17 PI1.4-POF1 PI1.4-POF2 PI1.4-POF3 PI1.4-POF4 PI1.5 PI1.5-POF1 PI1.5-POF2 PI1.5-POF3 PI1.5-POF4 |
| CIS CSC 8.1 | 3 3.1 3.3 11 11.3 |
| CIS CSC 8.1 IG1 | 3.1 3.3 11.3 |
| CIS CSC 8.1 IG2 | 3.1 3.3 11.3 |
| CIS CSC 8.1 IG3 | 3.1 3.3 11.3 |
| COBIT 2019 | APO14.01 APO14.02 APO14.03 APO14.04 APO14.05 APO14.06 APO14.07 APO14.08 APO14.09 APO14.10 |
| COSO 2017 | Principle 13 |
| CSA CCM 4 | CEK-04 DCS-01 DCS-02 DCS-03 DCS-04 DSP-01 DSP-10 DSP-17 HRS-03 |
| CSA IoT SCF 2 | DAT-02 LGL-08 |
| GovRAMP Low | MP-01 |
| GovRAMP Low+ | MP-01 |
| GovRAMP Moderate | MP-01 |
| GovRAMP High | MP-01 |
| IEC 62443-4-2 2019 | FR 4 (8.1) |
| ISO/SAE 21434 2021 | RQ-05-09 |
| ISO 27002 2022 | 5.9 5.10 5.12 5.33 7.10 8.12 |
| ISO 27017 2015 | 8.2 8.2.3 8.3 |
| ISO 27701 2025 | 7.5.3(b) |
| ISO 42001 2023 | 7.5.3 7.5.3(a) 7.5.3(b) |
| MPA Content Security Program 5.1 | OP-1.1 OP-2.0 OP-3.1 OP-3.3 TS-1.15 |
| NAIC Insurance Data Security Model Law (MDL-668) | 4.C(4)(b) 4.D(2)(b) 4.D(2)(j) |
| NIST Privacy Framework 1.0 | GV.PO-P1 |
| NIST 800-53 R4 | MP-1 |
| NIST 800-53 R4 (low) | MP-1 |
| NIST 800-53 R4 (moderate) | MP-1 |
| NIST 800-53 R4 (high) | MP-1 |
| NIST 800-53 R5 (source) | MP-1 |
| NIST 800-53B R5 (privacy) (source) | MP-1 |
| NIST 800-53B R5 (low) (source) | MP-1 |
| NIST 800-53B R5 (moderate) (source) | MP-1 |
| NIST 800-53B R5 (high) (source) | MP-1 |
| NIST 800-82 R3 LOW OT Overlay | MP-1 |
| NIST 800-82 R3 MODERATE OT Overlay | MP-1 |
| NIST 800-82 R3 HIGH OT Overlay | MP-1 |
| NIST 800-160 | 3.3.6 |
| NIST 800-161 R1 | MP-1 |
| NIST 800-161 R1 C-SCRM Baseline | MP-1 |
| NIST 800-161 R1 Level 1 | MP-1 |
| NIST 800-161 R1 Level 2 | MP-1 |
| NIST 800-171 R2 (source) | 3.8.1 3.8.3 NFO-MP-1 |
| NIST 800-171A (source) | 3.8.1[a] 3.8.1[b] 3.8.1[c] 3.8.1[d] |
| NIST 800-171 R3 (source) | 03.01.01.d.01 03.01.01.d.02 03.08.01 |
| NIST 800-207 | NIST Tenet 1 |
| NIST CSF 2.0 (source) | ID.AM-08 PR.DS PR.DS-01 PR.DS-02 PR.DS-10 |
| PCI DSS 4.0.1 (source) | 9.4 9.4.1 |
| PCI DSS 4.0.1 SAQ A (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ B (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ B-IP (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ C (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ C-VT (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 9.4.1 |
| PCI DSS 4.0.1 SAQ P2PE (source) | 9.4.1 |
| Shared Assessments SIG 2025 | P.3 |
| SPARTA | CM0001 |
| SWIFT CSF 2023 | 2.1 2.4A 2.9 2.11A |
| TISAX ISA 6 | 5.1.2 |
| UL 2900-1 2017 | 10.1 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | DCH-01 |
| SCF CORE ESP Level 1 Foundational | DCH-01 |
| SCF CORE ESP Level 2 Critical Infrastructure | DCH-01 |
| SCF CORE ESP Level 3 Advanced Threats | DCH-01 |
| SCF CORE AI Model Deployment | DCH-01 |
US (47)
| Framework | Mapping Values |
|---|---|
| US C2M2 2.1 | ARCHITECTURE-5.A.MIL1 ARCHITECTURE-5.B.MIL2 ARCHITECTURE-5.C.MIL2 |
| US CERT RMM 1.2 | KIM:SG2.SP2 |
| US CISA CPG 2022 | 2.L |
| US CJIS Security Policy 5.9.3 (source) | 4.2.3.1 5.1.1.1 5.7.2 MP-1 |
| US CMMC 2.0 Level 1 (source) | MP.L1-B.1.VII |
| US CMMC 2.0 Level 2 (source) | MP.L2-3.8.1 MP.L2-3.8.3 |
| US CMMC 2.0 Level 3 (source) | MP.L2-3.8.1 MP.L2-3.8.3 |
| US CMS MARS-E 2.0 | MP-1 |
| US DoD Zero Trust Reference Architecture 2.0 | 5.0 |
| US DHS CISA TIC 3.0 | 3.PEP.DA.PDRES |
| US DHS ZTCF | DIN-02 DPR-02 |
| US FAR 52.204-21 | 52.204-21(b)(1) 52.204-21(b)(1)(vii) |
| US FCA CRM | 609.930(a) 609.945 |
| US FDA 21 CFR Part 11 | 11.2 11.2(a) 11.10 11.10(a) 11.10(b) 11.10(c) 11.10(d) 11.10(e) 11.10(f) 11.10(g) 11.10(h) 11.10(i) 11.10(j) 11.10(k) 11.10(k)(1) 11.10(k)(2) |
| US FedRAMP R4 | MP-1 |
| US FedRAMP R4 (low) | MP-1 |
| US FedRAMP R4 (moderate) | MP-1 |
| US FedRAMP R4 (high) | MP-1 |
| US FedRAMP R4 (LI-SaaS) | MP-1 |
| US FedRAMP R5 (source) | MP-1 |
| US FedRAMP R5 (low) (source) | MP-1 |
| US FedRAMP R5 (moderate) (source) | MP-1 |
| US FedRAMP R5 (high) (source) | MP-1 |
| US FedRAMP R5 (LI-SaaS) (source) | MP-1 |
| US FERPA (source) | 1232g 1232h |
| US GLBA CFR 314 2023 (source) | 314.4(c)(1)(i) 314.4(c)(6)(ii) |
| US HHS 45 CFR 155.260 | 155.260(a)(4)(iv) 155.260(a)(4)(v) |
| US HIPAA Administrative Simplification 2013 (source) | 164.306(a)(3) 164.310(d)(1) 164.312(c)(1) 164.514(d)(3)(i) 164.530(c)(2)(i) |
| US HIPAA Security Rule / NIST SP 800-66 R2 (source) | 164.306(a)(3) 164.310(d)(1) 164.312(c)(1) |
| US HIPAA HICP Medium Practice | 4.M.B 4.M.E 7.M.C |
| US HIPAA HICP Large Practice | 4.M.B 4.M.E 7.M.C |
| US IRS 1075 | 1.3 1.9.1 1.9.2 2.A.2 2.A.3 2.B.2 2.B.3 2.C.5 2.D.1 3.3.8 MP-1 |
| US ITAR Part 120 | 120.2 120.10 120.11 120.17 120.18 120.19 120.20 120.21 120.22 120.23 120.50 120.51 |
| US NERC CIP 2024 (source) | CIP-003-8 1.1.8 CIP-011-3 1.2 |
| US NISPOM 2020 | 8-306 8-309 |
| US NNPI (unclass) | 10.1 |
| US NSTC NSPM-33 | 6.10 |
| US SSA EIESR 8.0 | 5.5 5.8 |
| US - AK PIPA | 45.48.100 |
| US - CO Colorado Privacy Act | 6-1-1305(4) 6-1-1307(2) 6-1-1307(3) 6-1-1308(5) |
| US - MA 201 CMR 17.00 | 17.03(2)(c) |
| US - NY DFS 23 NYCRR500 2023 Amd 2 | 500.18 500.3(b) |
| US - NY SHIELD Act S5575B | 4(2)(b)(ii)(B)(1) 4(2)(b)(ii)(B)(2) 4(2)(b)(ii)(B)(3) 4(2)(b)(ii)(B)(4) 4(2)(b)(ii)(C)(1) 4(2)(b)(ii)(C)(2) 4(2)(b)(ii)(C)(3) 4(2)(b)(ii)(C)(4) |
| US - TX DIR Control Standards 2.0 | MP-1 |
| US - TX TX-RAMP Level 1 | MP-1 |
| US - TX TX-RAMP Level 2 | MP-1 |
| US - VT Act 171 of 2018 | 2447(a) 2447(a)(1) 2447(a)(1)(A) 2447(a)(1)(B) 2447(a)(1)(C) 2447(a)(1)(D) 2447(a)(2) |
EMEA (30)
| Framework | Mapping Values |
|---|---|
| EMEA EU AI Act | 17.1(f) |
| EMEA Austria | Sec 14 Sec 15 |
| EMEA Belgium | 16 |
| EMEA Germany | Sec 4b Sec 9 Sec 9a Sec 16 Annex |
| EMEA Germany C5 2020 | COS-08 |
| EMEA Greece | 9 |
| EMEA Hungary | 7 8 |
| EMEA Ireland | 2 |
| EMEA Israel CDMO 1.0 | 5.1 5.2 5.3 5.5 11.6 15.1 15.6 15.7 |
| EMEA Israel | 16 17 |
| EMEA Italy | 31 33 34 35 42 |
| EMEA Netherlands | 12 13 14 |
| EMEA Norway | 13 14 29 |
| EMEA Poland | 1 36 47 |
| EMEA Russia | 7 12 19 |
| EMEA Saudi Arabia CSCC-1 2019 | 2-6 2-6-1-3 |
| EMEA Saudi Arabia ECC-1 2018 | 2-1-6 2-3-3 2-3-3-2 2-3-4 2-7-1 2-7-2 2-7-3 2-7-4 2-7-3-3 |
| EMEA Saudi Arabia OTCC-1 2022 | 2-6 2-6-1 2-6-1-1 2-6-2 |
| EMEA Saudi Arabia SACS-002 | TPC-24 TPC-39 TPC-58 |
| EMEA Serbia 87/2018 | 65 |
| EMEA South Africa | 14.1 19 21 |
| EMEA Spain BOE-A-2022-7191 | 22.1 22.3 |
| EMEA Spain 311/2022 | 22.1 22.3 |
| EMEA Spain CCN-STIC 825 | 8.5.3 [MP.SI.3] |
| EMEA Sweden | 31 33 |
| EMEA Switzerland | 6 7 |
| EMEA Turkey | 8 12 |
| EMEA UK CAF 4.0 | B3 |
| EMEA UK CAP 1850 | B3 |
| EMEA UK DEFSTAN 05-138 | 2300 2308 |
APAC (19)
| Framework | Mapping Values |
|---|---|
| APAC Australia Privacy Act | APP Part 8 APP Part 11 |
| APAC Australian Privacy Principles | APP 11 |
| APAC Australia ISM June 2024 | ISM-0337 ISM-0831 ISM-1059 ISM-1549 ISM-1599 |
| APAC Australia Prudential Standard CPS234 | 20 21(a) |
| APAC China Cybersecurity Law | 40 |
| APAC China DNSIP | 4 |
| APAC Hong Kong | Principle 4 Sec 33 |
| APAC India ITR | 7 8 |
| APAC India SEBI CSCRF | PR.AA.S14 PR.DS.S4 |
| APAC Japan APPI | 20 |
| APAC Japan ISMAP | 8.2.3 |
| APAC Malaysia | 9 |
| APAC New Zealand HISF 2022 | HHSP14 HHSP34 HHSP74 HML14 HML74 HSUP12 HSUP30 HSUP66 |
| APAC New Zealand HISF Suppliers 2023 | HSUP12 HSUP30 HSUP66 |
| APAC New Zealand NZISM 3.6 | 4.4.10.C.01 9.2.12.C.01 9.2.13.C.01 9.2.13.C.02 9.2.14.C.01 9.2.15.C.01 9.2.15.C.02 9.2.17.C.01 9.2.17.C.02 9.2.18.C.01 9.2.19.C.01 9.2.19.C.02 9.2.19.C.03 9.2.19.C.04 9.2.20.C.01 13.2.6.C.01 13.2.7.C.01 |
| APAC Philippines | 25 |
| APAC Singapore | 24 26 |
| APAC Singapore MAS TRM 2021 | 11.1.1 11.1.1(a) 11.1.1(b) 11.1.1(c) 11.1.2 11.1.3 11.1.4 11.1.5 11.1.6 11.1.7 |
| APAC Taiwan | 21 |
Americas (8)
| Framework | Mapping Values |
|---|---|
| Americas Argentina PPL | 9 12 |
| Americas Bermuda BMACCC | 6.8 6.10 6.13 |
| Americas Brazil LGPD | 46 47 |
| Americas Canada OSFI B-13 | 2.9.2 3.1.4 |
| Americas Canada ITSP-10-171 | 03.01.01.D.01 03.01.01.D.02 03.08.01 |
| Americas Canada PIPEDA | Principle 7 |
| Americas Chile | 7 |
| Americas Uruguay | 11 12 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to facilitate the implementation of data protection controls.
Level 1 — Performed Informally
Data Classification & Handling (DCH) efforts are ad hoc and inconsistent. CMM Level 1 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Data protection controls are primarily administrative in nature (e.g., policies & standards) to classify, protect and dispose of systems and data, including storage media.
- A data classification process exists to identify categories of data and specific protection requirements.
- A manual data retention process exists.
- Data/process owners are expected to take the initiative to work with Data Protection Officers (DPOs) to ensure applicable statutory, regulatory and contractual obligations are properly addressed, including the storage, transmission and processing of sensitive/regulated data.
Level 2 — Planned & Tracked
Data Classification & Handling (DCH) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Document where sensitive/regulated data is stored, transmitted and processed to identify data repositories and data flows. o Create and maintain Data Flow Diagrams (DFDs) and network diagrams. o Are expected to take the initiative to work with Data Protection Officers (DPOs) to ensure applicable statutory, regulatory and contractual obligations are properly addressed, including the storage, transmission and processing of sensitive/regulated data o Geolocation requirements for sensitive/regulated data types, including the transfer of data to third-countries or international organizations. o Requirements for minimizing data collection to what is necessary for business purposes. o Requirements for limiting the use of sensitive/regulated data in testing, training and research.
- Data management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for data management.
- Data protection controls are primarily administrative and preventative in nature (e.g., policies & standards) to classify, protect and dispose of systems and data, including storage media.
- A data classification process exists to identify categories of data and specific protection requirements.
- A data retention process exists and is a manual process to govern.
- Data/process owners:
- A manual data retention process exists.
- Content filtering blocks users from performing ad hoc file transfers through unapproved file transfer services (e.g., Box, Dropbox, Google Drive, etc.).
- Mobile Device Management (MDM) software is used to restrict and protect the data that resides on mobile devices.
- Physical controls, administrative processes and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
- Administrative means (e.g., policies and standards) dictate:
Level 3 — Well Defined
Data Classification & Handling (DCH) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Are expected to take the initiative to work with Data Protection Officers (DPOs) to ensure applicable statutory, regulatory and contractual obligations are properly addressed, including the storage, transmission and processing of sensitive/regulated data. o Maintain decentralized inventory logs of all sensitive/regulated media and update sensitive/regulated media inventories at least annually. o Create and maintain Data Flow Diagrams (DFDs) and network diagrams. o Document where sensitive/regulated data is stored, transmitted and processed in order to document data repositories and data flows. o Identify data classification types to ensure adequate cybersecurity and data protection controls are in place to protect organizational information and individual data privacy. o Identify and document the location of information on which the information resides. o Restrict and govern the transfer of data to third-countries or international organizations. o Limit the disclosure of data to authorized parties. o Mark media in accordance with data protection requirements so that personnel are alerted to distribution limitations, handling caveats and applicable security requirements. o Prohibit “rogue instances” where unapproved third parties are engaged to store, process or transmit data, including budget reviews and firewall connection authorizations. o Protect and control digital and non-digital media during transport outside of controlled areas using appropriate security measures. o Govern the use of personal devices (e.g., Bring Your Own Device (BYOD)) as part of acceptable and unacceptable behaviors. o Dictate requirements for minimizing data collection to what is necessary for business purposes. o Dictate requirements for limiting the use of sensitive/regulated data in testing, training and research.
- The Chief Information Security Officer (CISO), or similar function with technical competence to address cybersecurity concerns, analyzes the organization's business strategy to determine prioritized and authoritative guidance for data classification and handling practices.
- The CISO, or similar function, develops a security-focused Concept of Operations (CONOPS) that documents management, operational and technical measures to apply defense-in-depth techniques across the organization with regards to data classification and handling.
- A steering committee is formally established to provide executive oversight of the cybersecurity and data privacy program, including data classification and handling.
- A Governance, Risk & Compliance (GRC) function, or similar function, provides governance oversight for the implementation of applicable statutory, regulatory and contractual cybersecurity and data protection controls to protect the confidentiality, integrity, availability and safety of the organization's applications, systems, services and data regarding data classification and handling.
- A GRC function, or similar function, assists users in making information sharing decisions to ensure data is appropriately protected, regardless of where or how it is stored, processed and/ or transmitted.
- An IT Asset Management (ITAM) function, or similar function, categorizes assets according to the data the asset stores, transmits and/ or processes and applies the appropriate technology controls to protect the data according to the organization's data classification and handling requirements.
- A data classification process exists to identify categories of data and specific protection requirements.
- A data retention process exists to protect archived data in accordance with applicable statutory, regulatory and contractual obligations.
- Data/process owners:
- A Data Protection Impact Assessment (DPIA) is used to help ensure the protection of sensitive/regulated data processed, stored or transmitted on internal or external systems, in order to implement cybersecurity and data protection controls in accordance with applicable statutory, regulatory and contractual obligations.
- Human Resources (HR), documents formal “rules of behavior” as an employment requirement that stipulates acceptable and unacceptable practices pertaining to sensitive/regulated data handling.
- Data Loss Prevention (DLP), or similar content filtering capabilities, blocks users from performing ad hoc file transfers through unapproved file transfer services (e.g., Box, Dropbox, Google Drive, etc.).
- Mobile Device Management (MDM) software is used to restrict and protect the data that resides on mobile devices.
- Administrative processes and technologies:
Level 4 — Quantitatively Controlled
Data Classification & Handling (DCH) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- 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.
- Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to facilitate the implementation of data protection controls.
Assessment Objectives
- DCH-01_A01 paper media containing sensitive / regulated data is physically controlled.
- DCH-01_A02 digital media containing sensitive / regulated data is physically controlled.
- DCH-01_A03 paper media containing sensitive / regulated data is securely stored.
- DCH-01_A04 digital media containing sensitive / regulated data is securely stored.
- DCH-01_A05 data classification & handling management operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
- DCH-01_A06 adequate resources (e.g., people, processes, technologies, data and/or facilities) are provided to support data classification & handling management operations.
- DCH-01_A07 responsibility and authority for the performance of data classification & handling management-related activities are assigned to designated personnel.
- DCH-01_A08 personnel performing data classification & handling management-related activities have the skills and knowledge needed to perform their assigned duties.
Evidence Requirements
- E-CRY-01 Cryptographic Protections
-
Documented evidence of organization-approved cryptographic solutions and modules for both data at rest and in transit.
Cryptographic Protections
Technology Recommendations
Micro/Small
- Logical Access Control (LAC)
- Physical Access Control (PAC)
Small
- Logical Access Control (LAC)
- Physical Access Control (PAC)
Medium
- Logical Access Control (LAC)
- Physical Access Control (PAC)
- Data governance program
Large
- Logical Access Control (LAC)
- Physical Access Control (PAC)
- Data governance program
- Chief Data Officer (CDO)
Enterprise
- Logical Access Control (LAC)
- Physical Access Control (PAC)
- Data governance program
- Chief Data Officer (CDO)