Skip to main content

CLD-07: Multi-Tenant Environments

CLD 9 — Critical Protect

Mechanisms exist to ensure multi-tenant owned or managed assets (physical and virtual) are designed and governed such that provider and customer (tenant) user access is appropriately segmented from other tenant users.

Renumbered: Formerly CLD-06 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, CLD-07 was Data Handling & Portability. That control is now CLD-08.

Control Question: Does the organization ensure multi-tenant owned or managed assets (physical and virtual) are designed and governed such that provider and customer (tenant) user access is appropriately segmented from other tenant users?

General (7)
Framework Mapping Values
ISO 27002 2022 5.23
ISO 27018 2025 5.23
NIST 800-171 R2 (source) 3.1.22
NIST 800-171A (source) 3.1.22[a] 3.1.22[b] 3.1.22[c] 3.1.22[d] 3.1.22[e]
PCI DSS 4.0.1 (source) A1.1 A1.1.1 A1.1.2 A1.1.3 A1.1.4
PCI DSS 4.0.1 SAQ D Service Provider (source) A1.1.1 A1.1.2 A1.1.3 A1.1.4
Shared Assessments SIG 2025 N.2
US (4)
Framework Mapping Values
USA Federal DHS CISA TIC 3.0 3.UNI.EUSSE
USA Federal CMMC 2.0 Level 1 AC.L1-B.1.IV
USA Federal CMMC 2.0 Level 2 ACL2.-3.1.22
USA Federal FAR 52.204-21 52.204-21(b)(1)(iv)
EMEA (2)
Framework Mapping Values
EMEA Germany C5 2026 OIS-08.02B.2 OIS-08.02B.6 OPS-30.01B OPS-30.01B.1 OPS-30.01B.2 OPS-31.01B OPS-31.02B OPS-34.02B.4 IAM-07.01B IAM-07.01B.2 COS-02.01B.1 COS-05.02B COS-06.01B PSS-01.02B.14 PSS-10.01B
EMEA LUX CCSF 22/806 2022 99 136.a 138.b.ii 139 142.b
APAC (6)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-1529
APAC Japan ISMAP 9.5.1.P 9.5.1.1.P 9.5.1.2.P 9.5.1.3.P 9.5.1.4.P
APAC Malaysia RMiT 2025 10.50(d) A8-2(b) A10-B1(e)
APAC New Zealand HISF MLHSP 2023 HHSP53 HML53
APAC New Zealand HISF Suppliers 2023 HSUP45
APAC New Zealand NZISM 3.9 23.1.55.C.01 23.1.55.C.02 23.1.55.C.03 23.2.20.C.01

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

Cloud Security (CLD) 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 CLD domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with CLD 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 CLD domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Cloud management controls-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Cloud management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Cloud-based Technology Assets, Applications and/or Services (TAAS) are governed according to the same processes used for on-premises TAAS, where no formal, dedicated cloud governance process exists.

Level 3 — Well Defined

Cloud Security (CLD) 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 CLD 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 CLD domain capabilities are well-documented and kept current by process owners. ▪ A cloud governance team, or similar function, is appropriately staffed and supported to implement and maintain CLD domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of cloud governance operations (e.g., multi-cloud governance tools, policy enforcement and cost management). ▪ 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 CLD 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 ensure multi-tenant owned or managed assets (physical and virtual) are designed and governed such that provider and customer (tenant) user access is appropriately segmented from other tenant users.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

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

  1. CLD-07_A01 multi-tenant owned / managed assets (physical and virtual) are designed and governed such that provider and customer (tenant) user access is segmented from other tenant users.

Evidence Requirements

E-CLD-03 Multi-Tenant Environment Controls

Documented evidence of controls for multi-tenant cloud environments, including tenant-specific event logging, forensics and incident response capabilities.

Asset Management

Technology Recommendations

Micro/Small

  • System Security & Privacy Plan (SSPP)

Small

  • System Security & Privacy Plan (SSPP)

Medium

  • Architectural review board
  • System Security & Privacy Plan (SSPP)
  • Security architecture roadmaps

Large

  • Steering committee
  • Architectural review board
  • System Security & Privacy Plan (SSPP)
  • Security architecture roadmaps

Enterprise

  • Steering committee
  • Architectural review board
  • System Security & Privacy Plan (SSPP)
  • Security architecture roadmaps

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.