DCH-13: Use of External Technology Assets, Applications and/or Services (TAAS)
Mechanisms exist to govern how external parties, including Technology Assets, Applications and/or Services (TAAS), are used to securely store, process and transmit data.
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 (32)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC6.7 |
| GovRAMP Low | AC-20 |
| GovRAMP Low+ | AC-20 |
| GovRAMP Moderate | AC-20 |
| GovRAMP High | AC-20 |
| MITRE ATT&CK 10 | T1020.001, T1021, T1021.001, T1021.004, T1041, T1048, T1048.002, T1048.003, T1052, T1052.001, T1072, T1078.002, T1078.004, T1098.001, T1098.002, T1098.003, T1110, T1110.001, T1110.002, T1110.003, T1110.004, T1114, T1114.001, T1114.002, T1114.003, T1119, T1133, T1134.005, T1136, T1136.001, T1136.002, T1136.003, T1200, T1530, T1537, T1539, T1550.001, T1552, T1552.004, T1552.005, T1556, T1556.001, T1556.003, T1556.004, T1557, T1557.002, T1565, T1565.001, T1565.002, T1567, T1567.001, T1567.002, T1602, T1602.001, T1602.002 |
| NIST 800-53 R4 | AC-20 |
| NIST 800-53 R4 (low) | AC-20 |
| NIST 800-53 R4 (moderate) | AC-20 |
| NIST 800-53 R4 (high) | AC-20 |
| NIST 800-53 R5 (source) | 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 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-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-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 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 |
| SCF CORE Fundamentals | DCH-13 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | DCH-13 |
| SCF CORE ESP Level 1 Foundational | DCH-13 |
| SCF CORE ESP Level 2 Critical Infrastructure | DCH-13 |
| SCF CORE ESP Level 3 Advanced Threats | DCH-13 |
US (24)
| Framework | Mapping Values |
|---|---|
| US CERT RMM 1.2 | EXD:SG3.SP1 |
| US CJIS Security Policy 5.9.3 (source) | AC-20 |
| US CMMC 2.0 Level 1 (source) | AC.L1-B.1.III |
| US CMMC 2.0 Level 1 AOs (source) | 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] |
| US CMMC 2.0 Level 2 (source) | AC.L2-3.1.20 |
| US CMMC 2.0 Level 3 (source) | AC.L2-3.1.20 |
| US CMS MARS-E 2.0 | AC-20 |
| US FAR 52.204-21 | 52.204-21(b)(1)(iii) |
| US FedRAMP R4 | AC-20 |
| US FedRAMP R4 (low) | AC-20 |
| US FedRAMP R4 (moderate) | AC-20 |
| US FedRAMP R4 (high) | AC-20 |
| US FedRAMP R4 (LI-SaaS) | AC-20 |
| US FedRAMP R5 (source) | AC-20 |
| US FedRAMP R5 (low) (source) | AC-20 |
| US FedRAMP R5 (moderate) (source) | AC-20 |
| US FedRAMP R5 (high) (source) | AC-20 |
| US FedRAMP R5 (LI-SaaS) (source) | AC-20 |
| US IRS 1075 | AC-20 |
| US NISPOM 2020 | 8-700 |
| US NSTC NSPM-33 | 6.4 |
| US - TX DIR Control Standards 2.0 | AC-20 |
| US - TX TX-RAMP Level 1 | AC-20 |
| US - TX TX-RAMP Level 2 | AC-20 |
EMEA (2)
| Framework | Mapping Values |
|---|---|
| EMEA Israel CDMO 1.0 | 11.6 |
| EMEA Saudi Arabia ECC-1 2018 | 4-2-3-1 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 | 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
There is no evidence of a capability to govern how external parties, including Technology Assets, Applications and/or Services (TAAS), are used to securely store, process and transmit data.
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to govern how external parties, including Technology Assets, Applications and/or Services (TAAS), are used to securely store, process and transmit data.
Level 2 — Planned & Tracked
Data Classification & Handling (DCH) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Document where sensitive/regulated data is stored, transmitted and processed to identify data repositories and data flows. o Create and maintain Data Flow Diagrams (DFDs) and network diagrams. o Are expected to take the initiative to work with Data Protection Officers (DPOs) to ensure applicable statutory, regulatory and contractual obligations are properly addressed, including the storage, transmission and processing of sensitive/regulated data o Geolocation requirements for sensitive/regulated data types, including the transfer of data to third-countries or international organizations. o Requirements for minimizing data collection to what is necessary for business purposes. o Requirements for limiting the use of sensitive/regulated data in testing, training and research.
- Data management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- IT/cybersecurity personnel identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for data management.
- Data protection controls are primarily administrative and preventative in nature (e.g., policies & standards) to classify, protect and dispose of systems and data, including storage media.
- A data classification process exists to identify categories of data and specific protection requirements.
- A data retention process exists and is a manual process to govern.
- Data/process owners:
- A manual data retention process exists.
- Content filtering blocks users from performing ad hoc file transfers through unapproved file transfer services (e.g., Box, Dropbox, Google Drive, etc.).
- Mobile Device Management (MDM) software is used to restrict and protect the data that resides on mobile devices.
- Physical controls, administrative processes and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
- Administrative means (e.g., policies and standards) dictate:
Level 3 — Well Defined
Data Classification & Handling (DCH) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Are expected to take the initiative to work with Data Protection Officers (DPOs) to ensure applicable statutory, regulatory and contractual obligations are properly addressed, including the storage, transmission and processing of sensitive/regulated data. o Maintain decentralized inventory logs of all sensitive/regulated media and update sensitive/regulated media inventories at least annually. o Create and maintain Data Flow Diagrams (DFDs) and network diagrams. o Document where sensitive/regulated data is stored, transmitted and processed in order to document data repositories and data flows. o Identify data classification types to ensure adequate cybersecurity and data protection controls are in place to protect organizational information and individual data privacy. o Identify and document the location of information on which the information resides. o Restrict and govern the transfer of data to third-countries or international organizations. o Limit the disclosure of data to authorized parties. o Mark media in accordance with data protection requirements so that personnel are alerted to distribution limitations, handling caveats and applicable security requirements. o Prohibit “rogue instances” where unapproved third parties are engaged to store, process or transmit data, including budget reviews and firewall connection authorizations. o Protect and control digital and non-digital media during transport outside of controlled areas using appropriate security measures. o Govern the use of personal devices (e.g., Bring Your Own Device (BYOD)) as part of acceptable and unacceptable behaviors. o Dictate requirements for minimizing data collection to what is necessary for business purposes. o Dictate requirements for limiting the use of sensitive/regulated data in testing, training and research.
- A Governance, Risk & Compliance (GRC) function, or similar function, assists users in making information sharing decisions to ensure data is appropriately protected, regardless of where or how it is stored, processed and/ or transmitted.
- A data classification process exists to identify categories of data and specific protection requirements.
- A data retention process exists to protect archived data in accordance with applicable statutory, regulatory and contractual obligations.
- Data/process owners:
- A Data Protection Impact Assessment (DPIA) is used to help ensure the protection of sensitive/regulated data processed, stored or transmitted on internal or external systems, in order to implement cybersecurity and data protection controls in accordance with applicable statutory, regulatory and contractual obligations.
- Human Resources (HR), documents formal “rules of behavior” as an employment requirement that stipulates acceptable and unacceptable practices pertaining to sensitive/regulated data handling.
- Data Loss Prevention (DLP), or similar content filtering capabilities, blocks users from performing ad hoc file transfers through unapproved file transfer services (e.g., Box, Dropbox, Google Drive, etc.).
- Mobile Device Management (MDM) software is used to restrict and protect the data that resides on mobile devices.
- Administrative processes and technologies:
Level 4 — Quantitatively Controlled
Data Classification & Handling (DCH) efforts are metrics driven and provide sufficient management insight (based on a quantitative understanding of process capabilities) to predict optimal performance, ensure continued operations and identify areas for improvement. In addition to CMM Level 3 criteria, CMM Level 4 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- 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.
- Both business and technical stakeholders are involved in reviewing and approving proposed changes.
Level 5 — Continuously Improving
Data Classification & Handling (DCH) efforts are “world-class” capabilities that leverage predictive analysis (e.g., machine learning, AI, etc.). In addition to CMM Level 4 criteria, CMM Level 5 control maturity would reasonably expect all, or at least most, the following criteria to exist:
- Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions.
- Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.
Assessment Objectives
- DCH-13_A01 connections to external systems are identified.
- DCH-13_A02 the use of external systems is identified.
- DCH-13_A03 connections to external systems are verified.
- DCH-13_A04 the use of external systems is verified.
- DCH-13_A05 connections to external systems are controlled/limited.
- DCH-13_A06 the use of external systems is controlled/limited.
- DCH-13_A07 terms and conditions consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems are defined.
- DCH-13_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.
- DCH-13_A09 types of external systems prohibited from use are defined.
- DCH-13_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).
- DCH-13_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).
- DCH-13_A12 the use of organization-defined prohibited types of external systems is prohibited (if applicable).
- DCH-13_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.
- DCH-13_A14 the use of external systems is prohibited unless the systems are specifically authorized.
- DCH-13_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>.
- DCH-13_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.
- DCH-13_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.
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