DCH-32: External Transfer of Sensitive / Regulated Data
Mechanisms exist to restrict and govern the transfer of sensitive and/or regulated data: (1) Cross-border; and/or (2) Interorganizational.
Renumbered: Formerly DCH-25 in SCF 2025.4.
Control Question: Does the organization restrict and govern the transfer of sensitive and/or regulated data: (1) Cross-border; and/or (2) Interorganizational?
General (6)
| Framework | Mapping Values |
|---|---|
| AICPA Privacy Management Framework (PMF) | D6.1 S7.3 |
| CSA CCM 4.1.0 | DCS-03 |
| CSA IoT SCF 2 | LGL-08 |
| NIST 800-207 | NIST Tenet 4 |
| SCF DPMP 2026 | 5.6 |
| SWIFT CSF 2025 | 2.4 2.5A 2.9 |
EMEA (7)
| Framework | Mapping Values |
|---|---|
| EMEA EU GDPR 2016 | Article 44 Article 45.1 Article 46.1 Article 46.2 Article 46.2(a) Article 49.1 Article 49.1(a) Article 49.1(b) Article 49.1(c) Article 49.1(d) Article 49.1(e) Article 49.1(f) Article 49.1(g) Article 49.2 Article 49.3 Article 49.4 Article 49.6 |
| EMEA UK DPA 2018 | Section 109(1) Section 109(1)(a) Section 109(1)(b) Section 109(2) Section 109(2)(a) Section 109(2)(b) |
| EMEA Kenya DPA 2019 | IV.25(h) |
| EMEA LUX CCSF 22/806 2022 | 38.g |
| EMEA Nigeria DPR 2019 | 2.11 |
| EMEA Saudi Arabia CSCC-1 2019 | 2-6-1-5 |
| EMEA Saudi Arabia PDPL | Article 29.1 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Brazil LGPD 2018 | V |
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 restrict and govern the transfer of sensitive and/or regulated data to third-countries or international organizations.
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
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. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Assessment Objectives
- DCH-32_A01 the statutory, regulatory and/or contractual basis for restricting the cross-border and/or interorganizational transfer of sensitive and/or regulated data is identified.
- DCH-32_A02 mechanisms to restrict and govern the cross-border transfer of sensitive and/or regulated data are defined.
- DCH-32_A03 mechanisms to restrict and govern the cross-border transfer of sensitive and/or regulated data are implemented.
- DCH-32_A04 mechanisms to restrict and govern the interorganizational transfer of sensitive and/or regulated data are defined.
- DCH-32_A05 mechanisms to restrict and govern the interorganizational transfer of sensitive and/or regulated data are implemented.
Evidence Requirements
- E-DCH-19 Sensitive / Regulated Data Transfer Authorizations
-
Documented evidence of authorizations and records for ad-hoc and external transfers of sensitive / regulated data.
Data Protection
Technology Recommendations
Micro/Small
- Model contracts
- Binding Corporate Rules (BCR)
Small
- Model contracts
- Binding Corporate Rules (BCR)
Medium
- Model contracts
- Binding Corporate Rules (BCR)
Large
- Model contracts
- Binding Corporate Rules (BCR)
Enterprise
- Model contracts
- Binding Corporate Rules (BCR)