Skip to main content

DCH-22: Use of External Technology Assets, Applications and/or Services (TAAS)

DCH 9 — Critical Protect

Mechanisms exist to govern how external parties, including Technology Assets, Applications and/or Services (TAAS), are used to securely store, process and transmit data.

Renumbered: Formerly DCH-13 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, DCH-22 was Data Quality Operations. That control is now DCH-33.

Control Question: Does the organization govern how external parties, including Technology Assets, Applications and/or Services (TAAS), are used to securely store, process and transmit data?

General (26)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC6.7
GovRAMP AC-20
GovRAMP Low AC-20
GovRAMP Low+ AC-20
GovRAMP Moderate AC-20
GovRAMP High AC-20
MITRE ATT&CK 16 T1020.001 T1021 T1021.001 T1021.004 T1021.007 T1021.008 T1041 T1048 T1048.002 T1048.003 T1052 T1052.001 T1070.008 T1072 T1078.002 T1078.004 T1098.001 T1098.002 T1098.003 T1098.004 T1098.005 T1110 T1110.001 T1110.002 T1110.003 T1110.004 T1111 T1114 T1114.001 T1114.002 T1114.003 T1119 T1133 T1134.005 T1136 T1136.001 T1136.002 T1136.003 T1200 T1505.005 T1530 T1537 T1539 T1550.001 T1552 T1552.004 T1552.005 T1555 T1556 T1556.001 T1556.003 T1556.004 T1557 T1557.002 T1565 T1565.001 T1565.002 T1567 T1567.001 T1567.002 T1578.005 T1602 T1602.001 T1602.002
NIST 800-53 R4 AC-20
NIST 800-53 R5.2 AC-20
NIST 800-53B R5 (low) (source) AC-20
NIST 800-53B R5 (moderate) (source) AC-20
NIST 800-53B R5 (high) (source) AC-20
NIST 800-82 R3 AC-20
NIST 800-82 R3 LOW OT Overlay AC-20
NIST 800-82 R3 MODERATE OT Overlay AC-20
NIST 800-82 R3 HIGH OT Overlay AC-20
NIST 800-161 R1 AC-20
NIST 800-161 R1 C-SCRM Baseline AC-20
NIST 800-161 R1 Flow Down AC-20
NIST 800-161 R1 Level 1 AC-20
NIST 800-161 R1 Level 2 AC-20
NIST 800-161 R1 Level 3 AC-20
NIST 800-171 R2 (source) 3.1.20
NIST 800-171 R3 (source) 03.01.20.a 03.01.20.b 03.01.20.c.01 03.01.20.c.02 03.01.20.d
NIST 800-171A (source) 3.1.20[a] 3.1.20[b] 3.1.20[c] 3.1.20[d] 3.1.20[e] 3.1.20[f]
NIST 800-171A R3 (source) A.03.01.20.ODP[01] A.03.01.20.a A.03.01.20.b A.03.01.20.c.01 A.03.01.20.c.02 A.03.01.20.d
US (14)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 AC-20 AC-20.a AC-20.b AC-20-IS AC-20-IS.1 AC-20-IS.2 AC-20-IS.3
USA Federal CMMC 2.0 Level 1 AC.L1-B.1.III
USA Federal CMMC 2.0 Level 1 AOs AC.L1-B.1.III[a] AC.L1-B.1.III[b] AC.L1-B.1.III[c] AC.L1-B.1.III[d] AC.L1-B.1.III[e] AC.L1-B.1.III[f]
USA Federal CMMC 2.0 Level 2 ACL2.-3.1.20
USA Federal FAR 52.204-21 52.204-21(b)(1)(iii)
USA Federal CJIS Security Policy 6.0 AC-20
USA Federal FedRAMP R5 (low) AC-20
USA Federal FedRAMP R5 (moderate) AC-20
USA Federal FedRAMP R5 (high) AC-20
USA Federal FedRAMP R5 (LI-SaaS) AC-20
USA Federal IRS 1075 2021 AC-20 AC-20(IRS-Defined)
USA Texas DIR SCSC 2.2 2025 AC-20
USA Texas TX-RAMP Level 1 AC-20
USA Texas TX-RAMP Level 2 AC-20
EMEA (3)
Framework Mapping Values
EMEA Spain Royal Decree 311 2022 Article 22(1)
EMEA LUX CCSF 22/806 2022 27
EMEA Saudi Arabia SACS-002 2022 VII.B.TPC-36
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.01.20.A 03.01.20.B 03.01.20.C.01 03.01.20.C.02 03.01.20.D

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 govern how external parties, including Technology Assets, Applications and/or Services (TAAS), are used to securely store, process and transmit data.

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

  1. DCH-22_A01 connections to external systems are identified.
  2. DCH-22_A02 the use of external systems is identified.
  3. DCH-22_A03 connections to external systems are verified.
  4. DCH-22_A04 the use of external systems is verified.
  5. DCH-22_A05 connections to external systems are controlled/limited.
  6. DCH-22_A06 the use of external systems is controlled/limited.
  7. DCH-22_A07 terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined.
  8. DCH-22_A08 controls asserted to be implemented on external systems consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined.
  9. DCH-22_A09 types of external systems prohibited from use are defined.
  10. DCH-22_A10 organization-defined criteria are consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to access the system from external systems (if applicable).
  11. DCH-22_A11 organization-defined criteria consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to process, store or transmit organization-controlled information using external systems (if applicable).
  12. DCH-22_A12 the use of organization-defined prohibited types of external systems is prohibited (if applicable).
  13. DCH-22_A13 security requirements to be satisfied on external systems prior to allowing the use of or access to those systems by authorized individuals are defined.
  14. DCH-22_A14 the use of external systems is prohibited unless the systems are specifically authorized.
  15. DCH-22_A15 the following security requirements to be satisfied on external systems prior to allowing the use of or access to those systems by authorized individuals are established: <A.03.01.20.ODP[01]: security requirements>.
  16. DCH-22_A16 authorized individuals are permitted to use external systems to access the organizational system or to process, store, or transmit CUI only after verifying that the security requirements on the external systems as specified in the organization’s system security plans have been satisfied.
  17. DCH-22_A17 authorized individuals are permitted to use external systems to access the organizational system or to process, store, or transmit CUI only after retaining approved system connection or processing agreements with the organizational entity hosting the external systems.

Evidence Requirements

E-TPM-06 Third-Party Terms & Conditions

Documented evidence of terms and conditions for external systems.

Third-Party Management

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)
  • Cybersecurity Supply Chain Risk Management (C-SCRM) program

Small

  • Secure Baseline Configurations (SBC)
  • Cybersecurity Supply Chain Risk Management (C-SCRM) program

Medium

  • Secure Baseline Configurations (SBC)
  • Cybersecurity Supply Chain Risk Management (C-SCRM) program

Large

  • Secure Baseline Configurations (SBC)
  • Cybersecurity Supply Chain Risk Management (C-SCRM) program

Enterprise

  • Secure Baseline Configurations (SBC)
  • Cybersecurity Supply Chain Risk Management (C-SCRM) program

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.