Skip to main content

DCH-02: Data Protection

DCH 10 — Critical Govern

Mechanisms exist to facilitate the implementation of data protection controls.

Renumbered: Formerly DCH-01 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, DCH-02 was Data & Asset Classification. That control is now DCH-04.

Control Question: Does the organization facilitate the implementation of data protection controls?

General (62)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) M1.0-POF4 S7.4
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.0 3.1 3.3 11.0 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.03 APO14.08 APO14.09 DSS06.02 DSS06.06
COSO 2013 13.0
CSA CCM 4.1.0 CEK-04 DSP-10 DSP-17
CSA IoT SCF 2 LGL-08
GovRAMP MP-01
GovRAMP Low MP-01
GovRAMP Low+ MP-01
GovRAMP Moderate MP-01
GovRAMP High MP-01
IEC 62443-2-1 2024 DATA 1.2
ISO 27002 2022 5.9 5.10 5.12 5.33 7.10 8.12
ISO 27017 2015 8.1.1 8.1.3 8.2.1 8.2.3
ISO 27018 2025 5.9 5.10 5.12 5.33 7.10 8.12
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.3.1 OR-1.4 OP-1.1 OP-3.0 OP-3.1
NAIC Insurance Data Security Model Law (MDL-668) 4.C(4)(b) 4.D(2)(b) 4.D(2)(j)
NIST 800-53 R4 MP-1
NIST 800-53 R5.2 MP-01
NIST 800-53B R5 (low) (source) MP-01
NIST 800-53B R5 (moderate) (source) MP-01
NIST 800-53B R5 (high) (source) MP-01
NIST 800-53B R5 (privacy) (source) MP-01
NIST SP 800-66 R2 164.310(d) 164.312(c)
NIST 800-82 R3 MP-01
NIST 800-82 R3 LOW OT Overlay MP-01
NIST 800-82 R3 MODERATE OT Overlay MP-01
NIST 800-82 R3 HIGH OT Overlay MP-01
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-171 R3 (source) 03.01.01.d.01 03.01.01.d.02 03.08.01
NIST 800-171A (source) 3.8.1[a] 3.8.1[b] 3.8.1[c] 3.8.1[d]
NIST 800-171A R3 (source) A.03.01.01.d.01 A.03.01.01.d.02 A.03.08.01[01] A.03.08.01[02]
NIST 800-172 R3 03.01.17E
NIST 800-172A R3 A.03.01.17E.ODP[02]
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
NIST Privacy Framework 1.0 ID.IM-P GV.PO-P1 CT.DM-P1 CT.DM-P2 CT.DM-P3 CT.DM-P4 PR.DS-P
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
SCF DPMP 2026 5.0
Shared Assessments SIG 2025 P.3
SPARTA 4.0 CM0001
SWIFT CSF 2025 2.5A 2.9 2.11A
TISAX ISA 6.0.3 5.1.2
US (34)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 MP-1 SI-12
USA Federal CISA CPG 2022 2.L
USA Federal DHS CISA TIC 3.0 3.PEP.DA.PDRES
USA Federal CERT RMM 1.2 KIM:SG4 KIM:SG4.SP1 KIM:SG4.SP2 KIM:SG4.SP3 KIM:SG5 KIM:SG5.SP1 KIM:SG5.SP2 KIM:SG5.SP3 KIM:SG6 KIM:SG6.SP1 KIM:SG6.SP2 KIM:GG1.GP1 KIM:GG2 KIM:GG2.GP2
USA Federal CMMC 2.0 Level 1 MP.L1-B.1.VII
USA Federal CMMC 2.0 Level 2 MPL2.-3.8.1 MPL2.-3.8.3
USA Federal NNPI (unclass) 2010 9-2
USA Federal DoD Zero Trust Reference Architecture 2.0 5.0
USA Federal FAR 52.204-21 52.204-21(b)(1) 52.204-21(b)(1)(vii)
USA Federal CJIS Security Policy 6.0 4.2.3.1 MP-1
USA Federal 21 CFR Part 11 2025 11.10 11.10(a) 11.10(b) 11.10(c) 11.10(d) 11.10(k)
USA Federal FedRAMP R5 (low) MP-01
USA Federal FedRAMP R5 (moderate) MP-01
USA Federal FedRAMP R5 (high) MP-01
USA Federal FedRAMP R5 (LI-SaaS) MP-01
USA Federal 45 CFR 155.260 155.260(a)(4)(iv) 155.260(a)(4)(v)
USA Federal IRS 1075 2021 2.B.2 2.B.4 2.B.5 2.C.5 2.C.5.1 2.C.5.1-1 2.C.5.1-2 2.C.5.1-3 MP-1
USA Federal 33 CFR Part 101 Subpart F 101.630(b)
USA Federal GLBA CFR 314 2023 314.4(c)(1)(i) 314.4(c)(6)(ii)
USA Federal HIPAA Security Rule NIST SP 800-66 R2 § 164.306(a)(3) § 164.310(d)(1) § 164.312(c)(1)
USA Federal HIPAA Administrative Simplification 2013 § 164.306(a)(3) § 164.310(d)(1) § 164.312(c)(1) § 164.514(d)(3)(i) § 164.530(c)(2)(i)
USA Federal NERC CIP 2024 CIP-003-8 1.1.8 CIP-011-3 1.2
USA Federal NISPOM 2020 §117.15(h)(8)(iii)
USA Federal NRC 10 CFR 73.54 2015 73.54(a)(2) 73.54(a)(2)(i)
USA Federal NSF RIG 2025 5.3.8
USA Federal FCA CRM 2023 609.930(a) 609.945
USA Federal FINRA 2007 248.30(a)(2)(i) 248.30(a)(2)(iii)
USA Federal TSA SDP 2021-02F IV.B
USA Nevada Privacy Law 2023 603A.200.1
USA New York DFS 23 NYCRR500 2023 Amd 2 500.3(b) 500.18
USA New York SHIELD Act 2019 899-bb.2(b)(ii)(C)
USA Texas DIR SCSC 2.2 2025 MP-01
USA Texas TX-RAMP Level 1 MP-01
USA Texas TX-RAMP Level 2 MP-01
EMEA (15)
Framework Mapping Values
EMEA CHE FINMA Circular 2023/1 IV.D-74 IV.D-75
EMEA Germany C5 2026 HR-07.01B.1 OPS-11.01B
EMEA Spain CCN-STIC 825 op.pl.2 op.exp.1 mp.si.3 mp.si.4 mp.si.5 mp.info.2
EMEA Spain Royal Decree 311 2022 Article 22(3)
EMEA EU AI Act Article 17.1(f)
EMEA EU DORA RTS 2024 Article 8.2(a)(ii) Article 11.1 Article 11.2 Article 35.1 Article 35.1(a)
EMEA UK CAF 4.0 B3
EMEA UK DEFSTAN 05-138 2024 2300 2308
EMEA UK DEFSTAN 05-138 - L1 2024 2300
EMEA UK DEFSTAN 05-138 - L2 2024 2308
EMEA UK DEFSTAN 05-138 - L3 2024 2308
EMEA LUX CCSF 20/750 2020 3.3.4-23
EMEA Saudi Arabia CSCC-1 2019 2-6-1 2-6-1-3
EMEA Saudi Arabia ECC-1 2018 2-7-1
EMEA Saudi Arabia OTCC-1 2022 2-6-1 2-6-2
APAC (11)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-0337 ISM-0831 ISM-1059 ISM-1549 ISM-1599
APAC China Cybersecurity Law 2017 Article 40
APAC India RBI Digital Payments 2021 4.a 8.h
APAC India RBI PA 2025 Annex 1.1.2
APAC India SEBI CSCRF 2024 PR.AA.S14 PR.DS.S4
APAC Japan ISMAP 5.1.1.10 5.1.1.14 8.2 8.2.3 8.2.3.1 13.2 13.2.1 13.2.1.10 13.2.1.12 13.2.1.13 13.2.1.14
APAC New Zealand HISF MLHSP 2023 HHSP14 HHSP34 HHSP74 HML14 HML74
APAC New Zealand HISF Suppliers 2023 HSUP12 HSUP30 HSUP66
APAC New Zealand NZISM 3.9 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 Singapore CCOP CII 2026 5.13.3
APAC Singapore MAS TRM 2021 11.1.1 11.1.2
Americas (4)
Framework Mapping Values
Americas Bermuda BMACCC 2020 5.3-BP3
Americas Canada ITSP-10-171 2025 03.01.01.D.01 03.01.01.D.02 03.08.01
Americas Canada OSFI B-13 2022 2.9.2 3.1.4
Americas Canada OSFI Self-Assessment Guidance 3.1.4

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

Data Classification & Handling (DCH) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with DCH domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Data management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ A basic data classification process exists to identify categories of sensitive/regulated data for compliance-related protection requirements. ▪ Data protection controls are primarily administrative in nature (e.g., policies & standards) to classify, protect and dispose of systems and data, including storage media.

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. ▪ TAASD are categorized according to data classification and business criticality. ▪ Data classification and handling criteria govern requirements protect sensitive/regulated regardless of where it is stored, processed and/or transmitted. ▪ The data retention process is manual and IT and/or cybersecurity personnel work with business stakeholders and process owners to manage the process.

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 facilitate the implementation of data protection controls.

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

  1. DCH-02_A01 paper media containing sensitive / regulated data is physically controlled.
  2. DCH-02_A02 digital media containing sensitive / regulated data is physically controlled.
  3. DCH-02_A03 paper media containing sensitive / regulated data is securely stored.
  4. DCH-02_A04 digital media containing sensitive / regulated data is securely stored.
  5. DCH-02_A05 data classification & handling management operations are conducted according to documented policies, standards, procedures and/or other organizational directives.
  6. DCH-02_A06 resources (personnel, processes, technologies, data and/or facilities) are allocated to support data classification & handling management operations.
  7. DCH-02_A07 responsibility and authority for the performance of data classification & handling management-related activities are assigned to designated personnel.
  8. DCH-02_A08 personnel performing data classification & handling management-related activities have the skills and knowledge needed to perform their assigned duties.

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

  • 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)

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.