DCH-07: Sensitive / Regulated Data Protection
Mechanisms exist to protect sensitive and/or regulated data wherever it is processed and/or stored.
Renumbered: Formerly DCH-01.2 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, DCH-07 was Media Transportation. That control is now DCH-16.
Control Question: Does the organization protect sensitive and/or regulated data wherever it is processed and/or stored?
General (26)
| 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-POF2 CC8.1-POF17 |
| CIS CSC 8.1 | 3.1 |
| CIS CSC 8.1 IG1 | 3.1 |
| CIS CSC 8.1 IG2 | 3.1 |
| CIS CSC 8.1 IG3 | 3.1 |
| COBIT 2019 | DSS06.02 DSS06.06 |
| IEC 62443-2-1 2024 | DATA 1.2 |
| 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-3.0 |
| NIST SP 800-66 R2 | 164.312(c) |
| NIST 800-171 R2 (source) | 3.10.6 |
| NIST 800-171 R3 (source) | 03.01.01.d.01 03.01.01.d.02 03.01.02 03.01.20.a 03.01.20.b 03.01.20.c.01 03.01.20.d 03.06.05.d 03.08.01 03.08.02 03.08.05.a 03.17.01.c |
| NIST 800-171A R3 (source) | A.03.01.01.d.01 A.03.01.01.d.02 A.03.01.02[01] A.03.01.02[02] A.03.01.20.a A.03.01.20.b A.03.01.20.c.01 A.03.01.20.d A.03.06.05.d A.03.08.01[01] A.03.08.01[02] A.03.08.02 A.03.08.05.a[02] A.03.17.01.c |
| NIST 800-172 R3 | 03.01.17E |
| NIST 800-172A R3 | A.03.01.17E.ODP[02] |
| NIST 800-207 | NIST Tenet 4 |
| NIST CSF 2.0 (source) | PR.DS |
| NIST Privacy Framework 1.0 | CT.DM-P1 CT.DM-P2 |
| PCI DSS 4.0.1 (source) | 3.5 3.5.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 3.5.1 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 3.5.1 |
| SPARTA 4.0 | CM0001 |
| SWIFT CSF 2025 | 2.5A 2.9 2.11A |
| TISAX ISA 6.0.3 | 1.3.2 8.2.6 |
US (19)
| Framework | Mapping Values |
|---|---|
| USA Federal CISA CPG 2022 | 2.L |
| USA Federal DHS CISA TIC 3.0 | 3.PEP.DA.PDRES |
| USA Federal CMMC 2.0 Level 2 | PEL2.-3.10.6 |
| USA Federal NNPI (unclass) 2010 | 9-2 9-2.a |
| USA Federal DoD Zero Trust Reference Architecture 2.0 | 5.0 |
| USA Federal DoD Zero Trust Execution Roadmap v1.1 | 5.4.4 |
| USA Federal FAR 52.204-21 | 52.204-21(b)(1) |
| USA Federal CJIS Security Policy 6.0 | 4.2.4 |
| USA Federal FFIEC ITEH 2016 | II.C.13.a |
| USA Federal IRS 1075 2021 | 2.C.5 2.C.7 2.C.7-1 2.C.7-2 2.C.8 2.C.8.1 2.C.8.2 |
| USA Federal HIPAA Security Rule NIST SP 800-66 R2 | § 164.312(c)(1) |
| USA Federal HIPAA Administrative Simplification 2013 | § 164.312(c)(1) § 164.514(d)(3)(i) § 164.530(c)(2)(i) |
| USA Federal NISPOM 2020 | §117.15(a) §117.15(a)(1) §117.15(a)(2) §117.15(a)(2)(i) §117.15(a)(2)(ii) §117.15(a)(3) §117.15(a)(3)(i) §117.15(a)(3)(ii) §117.15(a)(3)(iii) §117.15(a)(3)(iii)(A) §117.15(a)(3)(iii)(B) §117.15(a)(3)(iii)(C) §117.15(a)(3)(iii)(D) §117.15(a)(3)(iii)(E) §117.15(a)(3)(iii)(F) §117.15(a)(3)(iv) §117.15(a)(3)(iv)(A) §117.15(a)(3)(iv)(B) §117.15(b) §117.15(c) §117.15(c)(1) §117.15(c)(2) §117.15(c)(3) §117.15(e)(2) §117.15(e)(3) §117.15(e)(3)(i) §117.15(e)(3)(ii) §117.15(e)(3)(iii) §117.15(e)(3)(iv) §117.15(e)(6) §117.15(f) §117.15(f)(1) §117.15(f)(2) §117.15(f)(3) |
| USA Massachusetts 201 CMR 17.00 2008 | 17.03(2)(g) |
| USA Nevada Privacy Law 2023 | 603A.215.2(b) |
| USA New York DFS 23 NYCRR500 2023 Amd 2 | 500.18 |
| USA New York SHIELD Act 2019 | 899-bb.2(b)(ii)(C)(3) |
| USA Texas SB 2610 2025 | 542.004(a)(3)(A) 542.004(a)(3)(B) 542.004(a)(3)(C) |
| USA Vermont Act 171 2018 | 2447(b)(3) |
EMEA (11)
| Framework | Mapping Values |
|---|---|
| EMEA CHE FINMA Circular 2023/1 | IV.C.b-64 IV.D-75 IV.D-76 IV.D-79 |
| EMEA Spain Royal Decree 311 2022 | Article 22(3) |
| EMEA UK DEFSTAN 05-138 2024 | 2308 |
| EMEA UK DEFSTAN 05-138 - L2 2024 | 2308 |
| EMEA UK DEFSTAN 05-138 - L3 2024 | 2308 |
| EMEA Israel CDMO 2.0 | Appendix A, 5.2 |
| EMEA LUX CCSF 22/806 2022 | 68.e 83 |
| EMEA Saudi Arabia CSCC-1 2019 | 2-6-1-1 2-6-1-3 |
| EMEA Saudi Arabia ECC-1 2018 | 2-7-1 |
| EMEA Saudi Arabia OTCC-1 2022 | 2-1-1-3 |
| EMEA Saudi Arabia SACS-002 2022 | VII.B.TPC-39 VII.B.TPC-58 |
APAC (9)
| Framework | Mapping Values |
|---|---|
| APAC Australia CCM 2026 | GOV-10 |
| APAC Australia ISM June 2026 | ISM-1802 |
| APAC India RBI Digital Payments 2021 | 56.d |
| APAC India RBI PPI 2025 | 7.9.d |
| APAC Malaysia RMiT 2025 | A5-B5 A7-D2(d)(vi) |
| APAC New Zealand HISF MLHSP 2023 | HHSP14 HHSP74 HML14 HML74 |
| APAC New Zealand HISF Suppliers 2023 | HSUP12 HSUP66 |
| APAC New Zealand NZISM 3.9 | 16.2.7.C.01 16.2.7.C.02 18.6.8.C.01 |
| APAC Singapore MAS TRM 2021 | 11.1.1(a) 11.1.1(b) 11.1.1(c) 11.1.6 |
Americas (4)
| Framework | Mapping Values |
|---|---|
| Americas Bahamas DPA 2003 | V.46(1) V.46(2) V.46(2)(a) V.46(2)(b) |
| Americas Bermuda BMACCC 2020 | 6.13 |
| Americas Canada ITSP-10-171 2025 | 03.01.01.D.01 03.01.01.D.02 03.01.02 03.01.20.A 03.01.20.B 03.01.20.C.01 03.01.20.D 03.06.05.D 03.08.01 03.08.02 03.08.05.A 03.17.01.C |
| Americas Canada OSFI B-13 2022 | 2.9.2 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
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. ▪ 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. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to document where sensitive/regulated data is stored, transmitted and/or processed.
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 protect sensitive/regulated data wherever it is processed and/or stored.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
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-07_A01 sensitive / regulated data inventories exist.
- DCH-07_A02 protection mechanisms are defined for each type of sensitive / regulated data.
- DCH-07_A03 organization-defined mechanisms protect sensitive / regulated data wherever it is processed and/or stored.
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
Enterprise
- Logical Access Control (LAC)
- Physical Access Control (PAC)
- Data governance program