Skip to main content

CLD-13: Hosted Assets, Applications & Services

CLD 9 — Critical Protect

Mechanisms exist to specify applicable cybersecurity and data protection controls that must be implemented on external Technology Assets, Applications and/or Services (TAAS), consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external TAAS.

Control Question: Does the organization specify applicable cybersecurity and data protection controls that must be implemented on external Technology Assets, Applications and/or Services (TAAS), consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external TAAS?

General (2)
Framework Mapping Values
NIST 800-207 NIST Tenet 1
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) CLD-13

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to specify applicable cybersecurity and data protection controls that must be implemented on external Technology Assets, Applications and/or Services (TAAS), consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external TAAS.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to specify applicable cybersecurity and data protection controls that must be implemented on external Technology Assets, Applications and/or Services (TAAS), consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external TAAS.

Level 2 — Planned & Tracked

C|P-CMM2 is N/A, since a well-defined process is required to specify applicable cybersecurity and data protection controls that must be implemented on external Technology Assets, Applications and/or Services (TAAS), consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external TAAS.

Level 3 — Well Defined

Cloud Security (CLD) 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 Ensure the cloud security architecture supports the organization's technology strategy to securely design, configure and maintain cloud employments. o Ensure multi-tenant CSP assets (physical and virtual) are designed and governed such that provider and customer (tenant) user access is appropriately segmented from other tenant users. o Ensure CSPs use secure protocols for the import, export and management of data in cloud-based services. o Implement a dedicated subnet to host security-specific technologies on all cloud instances, where technically feasible. o Governs changes to cloud-based systems, applications and services to ensure their stability, reliability and predictability. o Reviews processes to identify and prevent use of unapproved CSPs. IT infrastructure team assigns roles and responsibilities for governing Content Delivery Network (CDN) instances, including provisioning, maintaining and deprovisioning of instances.

  • Roles and associated responsibilities for governing cloud instances, including provisioning, maintaining and deprovisioning, are formally assigned.
  • A Shared Responsibility Matrix (SRM), or similar Customer Responsibility Matrix (CRM), is documented for each Cloud Service Providers (CSPs) instance that takes into account differences between Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS) methodologies.
  • IT architects, in conjunction with cybersecurity architects:
  • A Change Advisory Board (CAB), or similar function:
  • A dedicated IT infrastructure team, or similar function, enables the implementation of cloud management controls to ensure cloud instances are both secure and compliant, leveraging industry-recognized secure practices that are CC|P-specific.
  • Cybersecurity and data privacy requirements are identified and documented for each CSP instance to address sensitive/regulated data processing, storing and/ or transmitting and provide restrictions on data processing and storage locations.
  • A Data Protection Impact Assessment (DPIA) is used to help ensure the protection of sensitive/regulated data processed, stored or transmitted on external Technology Assets, Applications and/or Services (TAAS).
Level 4 — Quantitatively Controlled

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to specify applicable cybersecurity and data protection controls that must be implemented on external Technology Assets, Applications and/or Services (TAAS), consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external TAAS.

Level 5 — Continuously Improving

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to specify applicable cybersecurity and data protection controls that must be implemented on external Technology Assets, Applications and/or Services (TAAS), consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external TAAS.

Assessment Objectives

  1. CLD-13_A01 applicable cybersecurity & data protection controls are specified that must be implemented on external systems, consistent with the contractual obligations established with the External Service Providers (ESP) owning, operating and/or maintaining external systems, applications and/or services.

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.