DCH-29: Logical Data Location
Mechanisms exist to identify and document the logical location of data and the specific Technology Assets, Applications and/or Services (TAAS) on which the data resides.
Renumbered: Formerly DCH-24 in SCF 2025.4.
Control Question: Does the organization identify and document the logical location of data and the specific Technology Assets, Applications and/or Services (TAAS) on which the data resides?
General (15)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC2.1-POF9 |
| MITRE ATT&CK 16 | T1005 T1025 |
| NIST 800-53 R5.2 | CM-12 |
| NIST 800-53B R5 (moderate) (source) | CM-12 |
| NIST 800-53B R5 (high) (source) | CM-12 |
| NIST 800-82 R3 | CM-12 |
| NIST 800-82 R3 MODERATE OT Overlay | CM-12 |
| NIST 800-82 R3 HIGH OT Overlay | CM-12 |
| NIST 800-161 R1 | CM-12 |
| NIST 800-161 R1 Level 2 | CM-12 |
| NIST 800-161 R1 Level 3 | CM-12 |
| NIST 800-171 R3 (source) | 03.04.11.a 03.04.11.b |
| NIST 800-171A R3 (source) | A.03.04.11.a[01] |
| NIST 800-207 | NIST Tenet 1 |
| SCF DPMP 2026 | 5.6 |
US (5)
| Framework | Mapping Values |
|---|---|
| USA Federal CJIS Security Policy 6.0 | CM-12 |
| USA Federal FedRAMP R5 (moderate) | CM-12 |
| USA Federal FedRAMP R5 (high) | CM-12 |
| USA Federal IRS 1075 2021 | CM-12 CM-12(CE-1) |
| USA Texas TX-RAMP Level 2 | CM-12 |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA LUX CCSF 22/806 2022 | 142.g |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 03.04.11.A 03.04.11.B |
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. ▪ 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 identify and document the location of information and the specific system components on which the information resides.
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-29_A01 data for which the logical location is to be identified and documented is defined.
- DCH-29_A02 the logical location of sensitive / regulated data is identified and documented.
- DCH-29_A03 the specific Technology Assets, Applications and/or Services (TAAS) on which organization-defined data is processed are identified and documented.
- DCH-29_A04 the specific Technology Assets, Applications and/or Services (TAAS) on which organization-defined data is stored are identified and documented.
- DCH-29_A05 changes to the logical location (e.g., Technology Assets, Applications and/or Services (TAAS)) where organization-defined data is processed are documented.
- DCH-29_A06 changes to the logical location (e.g., Technology Assets, Applications and/or Services (TAAS)) where organization-defined data is stored are documented.
- DCH-29_A07 the users who have access to the Technology Assets, Applications and/or Services (TAAS) where organization-defined data is processed are identified and documented.
- DCH-29_A08 the users who have access to the Technology Assets, Applications and/or Services (TAAS) where organization-defined data is stored are identified and documented.
- DCH-29_A09 the location of CUI is identified and documented.
Evidence Requirements
- E-AST-23 Geolocation Inventory
-
Documented evidence of designated internal and third-party facilities where organizational data is stored, transmitted and/or processed.
Asset Management
Technology Recommendations
Micro/Small
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
Small
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
Medium
- IT Asset Management (ITAM) program
- Data classification program
- Sensitive data inventories
- Data Flow Diagram (DFD)
- System Security & Privacy Plan (SSPP)
- Product / project management
Large
- 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
- 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