DCH-28: Limit Sensitive / Regulated Data In Testing, Training & Research
Mechanisms exist to minimize the use of sensitive and/or regulated data for research, testing, or training, in accordance with authorized, legitimate business practices.
Renumbered: Formerly DCH-18.2 in SCF 2025.4.
Control Question: Does the organization minimize the use of sensitive and/or regulated data for research, testing, or training, in accordance with authorized, legitimate business practices?
General (9)
| Framework | Mapping Values |
|---|---|
| NIST 800-53 R5.2 | PM-25 SA-08(33) SA-15(12) SI-12(02) |
| NIST 800-53B R5 (privacy) (source) | PM-25 SA-08(33) SI-12(02) |
| NIST 800-82 R3 | PM-25 SA-08(33) SA-15(12) SI-12(02) |
| NIST 800-82 R3 LOW OT Overlay | PM-25 |
| NIST 800-82 R3 MODERATE OT Overlay | PM-25 |
| NIST 800-82 R3 HIGH OT Overlay | PM-25 |
| NIST 800-161 R1 | PM-25 |
| NIST 800-161 R1 Level 2 | PM-25 |
| SCF DPMP 2026 | 3.2 |
US (2)
| Framework | Mapping Values |
|---|---|
| USA Federal CJIS Security Policy 6.0 | SI-12(2) |
| USA Federal IRS 1075 2021 | SI-12(CE-2) |
EMEA (4)
| Framework | Mapping Values |
|---|---|
| EMEA EU AI Act | Article 10.2 Article 10.2(a) Article 10.2(b) Article 10.2(c) Article 10.2(d) Article 10.2(e) Article 10.3 Article 10.6 |
| EMEA EU DORA RTS 2024 | Article 16.2(d) Article 16.4 |
| EMEA EU NIS2 Annex 2024 | 6.2.2(f) |
| EMEA LUX CCSF 20/750 2020 | 3.6.2-72 |
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
Data Classification & Handling (DCH) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with DCH domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Data management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Limited media handling guidance exists for users. ▪ Requirements exist for limiting the use of sensitive/regulated data in testing, training and research. ▪ Requirements exist for minimizing data collection to what is necessary for business purposes.
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. ▪ Business stakeholders and process owners adhere to applicable compliance requirements to limit the use of sensitive/regulated data in testing, training and research.
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 minimize the use of sensitive/regulated data for research, testing, or training, in accordance with authorized, legitimate business practices.
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
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-28_A01 the developer of the system or system component is required to minimize the use of Personal Data (PD) in development and test environments.
- DCH-28_A02 techniques used to minimize the use of Personal Data (PD) for research, testing and training are defined.
- DCH-28_A03 organization-defined techniques are used to minimize the use of Personal Data (PD) for research, testing and training.
- DCH-28_A04 processes that implement the privacy principle of minimization are defined.
- DCH-28_A05 the privacy principle of minimization is implemented using organization-defined processes.
Evidence Requirements
- E-TDA-21 Test Data Management
-
Documented evidence of restrictions on the use of live / sensitive data in testing and test data integrity controls.
Technology Design & Acquisition
Technology Recommendations
Micro/Small
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Small
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Medium
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Large
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management
Enterprise
- Data classification program
- Data privacy program
- Data Protection Impact Assessment (DPIA)
- Product / project management