# BSI C5 OPS-24 — Separation of Datasets in the Cloud Infrastructure

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_bsic5_ops24_1ce4ada227-bsi-c5-ops-24-separation-of-datasets-in-the-cloud-infrastructure
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [BSI C5 (German Cloud)](https://support.icompaas.com/support/solutions/c_gen_bsi_c5) › [Operations Security](https://support.icompaas.com/support/solutions/folders/f_gen_cgenbsic5_operationssecurity)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

BSI C5 · Control OPS-24 · Priority: critical · Component: Operations Security

### What this control covers

Securely separates cloud customer data on shared resources per OIS-07 risk analysis, using documented approaches to ensure confidentiality and integrity. Prevents unauthorized access or data leakage in multi-tenant environments.

### Why it matters

A well-architected cloud landing zone bakes most of these controls in at the platform layer — done well, individual workloads inherit security for free.

### How to implement

#### AWS

Segment workloads into separate **VPCs/accounts per environment**. Use **security groups** as stateful allow-lists (least-port, source by SG ID not 0.0.0.0/0) and **VPC Flow Logs** to CloudWatch/S3. Front public services with **AWS WAF + Shield Advanced** and use **PrivateLink/VPC Endpoints** to keep service traffic off the internet.

#### Azure

Use **Network Security Groups** and **Application Security Groups** for east-west, and an **Azure Firewall** or NVA in a hub VNet for north-south. Enforce **Private Endpoints** for PaaS and turn on **Defender for Cloud — Network** for adaptive hardening recommendations.

#### GCP

Use **VPC Service Controls** to draw a perimeter around sensitive APIs and a hierarchical **Firewall policy** at the org/folder level so projects inherit a deny-by-default posture. Front HTTP workloads with the global **Cloud Load Balancer + Cloud Armor**.

### Evidence to collect

-   `infra_scan` — See the iCompaas Evidence library for the canonical source for this evidence type.

Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Focus: Separation of Datasets in the Cloud Infrastructure.

### Quick checklist

-   Risk — - Configuration / Cloud Customer Data
-   Security — - Configuration / Cloud Customer Data
-   Confidentiality — - Configuration / Cloud Customer Data
-   Data — - Configuration / Cloud Customer Data
-   Separation — - Configuration / Cloud Customer Data
-   Access — - Configuration / Cloud Customer Data

### Related articles on this site

-   [Microsoft Cloud Security Posture Management (CSPM)](https://support.icompaas.com/support/solutions/articles/62000234105-microsoft-cloud-security-posture-management-cspm-)
-   [Ensure a log metric filter and alarm exist for changes to Network Access Control Lists (NACL)](https://support.icompaas.com/support/solutions/articles/62000084031-ensure-a-log-metric-filter-and-alarm-exist-for-changes-to-network-access-control-lists-nacl-)
-   [Ensure Security Groups do not allow unrestricted ingress access to any port](https://support.icompaas.com/support/solutions/articles/62000127014-ensure-security-groups-do-not-allow-unrestricted-ingress-access-to-any-port)
-   [Ensure Security Groups do not allow unrestricted ingress access to Oracle Ports 1521 or 2483](https://support.icompaas.com/support/solutions/articles/62000127015-ensure-security-groups-do-not-allow-unrestricted-ingress-access-to-oracle-ports-1521-or-2483)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.