# BSI C5 DEV-10 — Separation of environments

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_bsic5_dev10_b8f1a41579-bsi-c5-dev-10-separation-of-environments
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [BSI C5 (German Cloud)](https://support.icompaas.com/support/solutions/c_gen_bsi_c5) › [Development & Change Management](https://support.icompaas.com/support/solutions/folders/f_gen_cgenbsic5_developmentchangemanagement)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

BSI C5 · Control DEV-10 · Priority: critical · Component: Development & Change Management

### What this control covers

Physically or logically separates production from test/development environments, preventing unauthorized access or malware spread. Avoids using production data in testing, ensuring cloud customer data confidentiality and system integrity.

### Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

### How to implement

#### AWS

Codify the policy intent as **SCPs, AWS Config conformance packs, and Security Hub standards** so the cloud enforces what the document says.

#### Azure

Codify in **Azure Policy initiatives** (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

#### GCP

**Org Policy Service** for guardrails and **Config Validator** in CI to pre-check Terraform plans against policy as code (Rego).

#### Google Workspace

**Endpoint Management** (basic/advanced) for BYOD/COPE; require screen lock, disk encryption and OS minimum; block sign-in on jailbroken devices.

#### GitHub

Apply **branch protection** on default and release branches: require PR review, status checks, signed commits, linear history, and dismiss stale reviews on new commits. Use **CODEOWNERS** for required reviewers, **Dependabot** + **CodeQL** for SAST, and the **Dependency graph / SBOM** export for vendor disclosures.

#### On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

### Evidence to collect

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

EDR telemetry (CrowdStrike, Defender for Endpoint) confirms threat detection. Focus: Separation of environments.

### Quick checklist

-   Risk — Protection / Cloud Customer Data
-   Review — Protection / Cloud Customer Data
-   Confidentiality — Protection / Cloud Customer Data
-   Protection — Protection / Cloud Customer Data
-   Data — Protection / Cloud Customer Data
-   Test — Protection / Cloud Customer Data

### Related articles on this site

-   [Ensure development, test and production environments are segregated](https://support.icompaas.com/support/solutions/articles/62000229689-ensure-development-test-and-production-environments-are-segregated)
-   [Ensure Restrict and Control Access to Production Environments](https://support.icompaas.com/support/solutions/articles/62000234920-ensure-restrict-and-control-access-to-production-environments)
-   [GDPR Article 98: Review of Other Union Legal Acts on Data Protection](https://support.icompaas.com/support/solutions/articles/62000236445-gdpr-article-98-review-of-other-union-legal-acts-on-data-protection)
-   [Ensure API Gateway has client certificate enabled to access your backend endpoint](https://support.icompaas.com/support/solutions/articles/62000127111-ensure-api-gateway-has-client-certificate-enabled-to-access-your-backend-endpoint)

## 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.