DCH-26: Transfer Authorizations
Mechanisms exist to verify that individuals or Technology Assets, Applications and/or Services (TAAS) transferring data between interconnecting TAAS have the requisite authorizations (e.g., write permissions or privileges) prior to transferring said data.
Renumbered: Formerly DCH-14.2 in SCF 2025.4.
Code reused: In SCF 2025.4 and earlier, DCH-26 was Data Localization. That control is now DCH-31.
Control Question: Does the organization verify that individuals or Technology Assets, Applications and/or Services (TAAS) transferring data between interconnecting TAAS have the requisite authorizations (e.g., write permissions or privileges) prior to transferring said data?
General (13)
| Framework | Mapping Values |
|---|---|
| CIS CSC 8.1 | 3.3 |
| CIS CSC 8.1 IG1 | 3.3 |
| CIS CSC 8.1 IG2 | 3.3 |
| CIS CSC 8.1 IG3 | 3.3 |
| CSA CCM 4.1.0 | DSP-10 |
| NIST 800-53 R5.2 | CA-03(06) |
| NIST 800-53B R5 (high) (source) | CA-03(06) |
| NIST 800-82 R3 | CA-03(06) |
| NIST 800-82 R3 HIGH OT Overlay | CA-03(06) |
| NIST 800-171 R3 (source) | 03.01.20.b 03.01.20.c.02 03.12.05.a |
| NIST 800-171A R3 (source) | A.03.01.20.b A.03.01.20.c.02 A.03.12.05.a[01] |
| NIST 800-207 | NIST Tenet 3 NIST Tenet 4 |
| SWIFT CSF 2025 | 2.1 2.4 |
US (2)
| Framework | Mapping Values |
|---|---|
| USA Federal FedRAMP R5 (high) | CA-03(06) |
| USA Federal IRS 1075 2021 | 2.E.6.2 |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Saudi Arabia CSCC-1 2019 | 2-6-1-5 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.01.20.B 03.01.20.C.02 03.12.05.A |
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 verify that individuals or Technology Assets, Applications and/or Services (TAAS) transferring data between interconnecting TAAS have the requisite authorizations (e.g., write permissions or privileges) prior to transferring said data.
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-26_A01 individuals or systems transferring data between interconnecting systems have the requisite authorizations (e.g., write permissions or privileges) prior to accepting such data.
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
- Data classification policy (public/internal/confidential)
Small
- Data classification policy
- Data handling procedures
Medium
- Data classification program
- DLP tools
- Data handling standards
Large
- Enterprise DLP solution (e.g., Microsoft Purview, Symantec DLP)
- Data classification tool
Enterprise
- Enterprise data governance platform (e.g., Collibra)
- DLP with automated classification
- Data lifecycle management