# BSI C5:2020 DEV-10 — Separation of environments

- Source: https://support.icompaas.com/compliance/bsi-c5-2020/dev-10-separation-of-environments
- Section: [Compliance](https://support.icompaas.com/compliance) › [BSI C5:2020 (Cloud Computing Compliance Criteria)](https://support.icompaas.com/compliance/bsi-c5-2020) › Development & Change Management (DEV)
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**BSI C5:2020**·Criterion `DEV-10`·critical·Component: **Development & Change Management**

## What this control requires

> 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.
> 
> — BSI C5:2020, Criterion DEV-10

### In plain English

Physically or logically separates production from test/development environments, preventing unauthorized access or malware spread. In practice, this means you can prove you risk protection-level controls on a defined cadence.

## Why it matters

BSI C5 is the default cloud-security baseline German public-sector buyers and many DAX-listed enterprises expect; gaps here directly block procurement in the DACH region and frequently appear as must-have items in EU public-tender documents.

This control is rated **critical** in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping.

## What an auditor looks for

A C5 attesting auditor (under ISAE 3000 / IDW PS 860) tests both the design and — for a Type 2 — the operating effectiveness over the attestation period. For each criterion they look for both the Basic and any in-scope Additional objectives.

Within **Development & Change Management**, the assessor will trace your implementation back to the catalogue reference (Criterion DEV-10) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Endpoint Protection

**MDM.** Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

**EDR.** Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

#### Code Review Testing

**Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

#### Cloud Posture

**CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.

### Operational checklist

-   **Risk.** Document the trigger, the owner and the cadence.
-   **Review.** Document the trigger, the owner and the cadence.
-   **Confidentiality.** Document the trigger, the owner and the cadence.
-   **Protection.** Document the trigger, the owner and the cadence.
-   **Data.** Document the trigger, the owner and the cadence.
-   **Scope:** protection, cloud customer data, development, environments, management.

## Evidence to collect

-   **Edr Scan.** `edr_scan` evidence
-   **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

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

## Common pitfalls

-   Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.
-   Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.

## How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

-   [**NIST SP 800-53 Rev. 5 CM-2(6)** — Development And Test Environments](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cm-2-6-development-and-test-environments)
-   [**ISO/IEC 27001:2022 A.8.31** — Separation of development, test and production environments](https://support.icompaas.com/compliance/iso-27001-2022/a-8-31-separation-of-development-test-and-production-environments)

## Related controls in BSI C5:2020

-   [**Criterion DEV-09** — Approvals for provision in the production environment](https://support.icompaas.com/compliance/bsi-c5-2020/dev-09-approvals-for-provision-in-the-production-environment)
-   [**Criterion OPS-22** — Testing and Documentation of known Vulnerabilities](https://support.icompaas.com/compliance/bsi-c5-2020/ops-22-testing-and-documentation-of-known-vulnerabilities)
-   [**Criterion DEV-03** — Policies for changes to information systems](https://support.icompaas.com/compliance/bsi-c5-2020/dev-03-policies-for-changes-to-information-systems)
-   [**Criterion DEV-04** — Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools.](https://support.icompaas.com/compliance/bsi-c5-2020/dev-04-safety-training-and-awareness-programme-regarding-continuous-software-delivery-and)
-   [**Criterion OPS-19** — Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests](https://support.icompaas.com/compliance/bsi-c5-2020/ops-19-managing-vulnerabilities-malfunctions-and-errors-penetration-tests)
-   [**Criterion AM-06** — Asset Classification and Labelling](https://support.icompaas.com/compliance/bsi-c5-2020/am-06-asset-classification-and-labelling)

## References

-   [Bundesamt für Sicherheit in der Informationstechnik (BSI) — BSI C5:2020](https://www.bsi.bund.de/EN/Topics/CloudComputing/Compliance_Criteria_Catalogue/Compliance_Criteria_Catalogue_node.html)
-   Catalogue identifier: `Criterion DEV-10`

Topics: governance riskedr xdrendpoint protectioncode review testingcloud posture

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