DCH-31: Data Localization
Mechanisms exist to constrain the impact of "digital sovereignty laws," that require localized data within the host country, where data and processes may be subjected to arbitrary enforcement actions that potentially violate other applicable statutory, regulatory and/or contractual obligations.
Renumbered: Formerly DCH-26 in SCF 2025.4.
Control Question: Does the organization constrain the impact of "digital sovereignty laws," that require localized data within the host country, where data and processes may be subjected to arbitrary enforcement actions that potentially violate other applicable statutory, regulatory and/or contractual obligations?
EMEA (3)
| Framework | Mapping Values |
|---|---|
| EMEA LUX CCSF 22/806 2022 | 68.d |
| EMEA Saudi Arabia CSCC-1 2019 | 4-2-1-1 |
| EMEA Saudi Arabia ECC-1 2018 | 4-1-3-2 4-2-3-3 |
APAC (5)
| Framework | Mapping Values |
|---|---|
| APAC China Cybersecurity Law 2017 | Article 37 |
| APAC China Privacy Law 2021 | Article 40 |
| APAC India RBI Data Localization 2018 | 2.i |
| APAC India RBI PA 2025 | III.9.c Annex 1.1.16 Annex 1.2.3 |
| APAC India SEBI CSCRF 2024 | PR.DS.S2 |
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
SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).
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 constrain the impact of "digital sovereignty laws," that require localized data within the host country, where data and processes may be subjected to arbitrary enforcement actions that potentially violate other applicable statutory, regulatory and/or contractual obligations.
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-31_A01 executive leadership, along with legal counsel, formally identifies primary risks associated with compliance (e.g., loss of confidentiality and/or integrity considerations with data governance).
- DCH-31_A02 executive leadership, along with legal counsel, formally identifies secondary risks associated with compliance (e.g., non-compliance with other laws, regulations and contractual agreements).
- DCH-31_A03 executive leadership, along with legal counsel, formally identifies tertiary risks associated with compliance (for example, human rights abuses, theft of intellectual property and espionage).
- DCH-31_A04 data localization is designed with defense-in-depth architecture to prevent host nations (where data is localized) from accessing other organizational assets not in the same geographic location as the host nation.
Evidence Requirements
- E-DCH-15 Geolocation Restrictions
-
Documented evidence of geolocation restrictions placed on specific types of sensitive and/or regulated data for where that data can be stored and/or processed.
Data Protection
Technology Recommendations
Micro/Small
- Governance, Risk & Compliance (GRC) program
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
Small
- Governance, Risk & Compliance (GRC) program
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
Medium
- Governance, Risk & Compliance (GRC) program
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
Large
- Governance, Risk & Compliance (GRC) program
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
- Data governance program
Enterprise
- Governance, Risk & Compliance (GRC) program
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
- Data governance program