C5 (Germany)
C5: Procurement, Development and Modification of Information Systems

C5 (Germany) C5-DEV-10: Separation of environments

Keep production environments physically or logically apart from development and test environments to prevent unauthorised access to customer data, malware spread and unintended component changes, and do not use production data inside those non-production environments.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 34 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 3 controls

  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
  • SA-3 System Development Life Cycle
  • SC-2 Separation of System and User Functionality

FedRAMP Moderate · 3 controls

  • CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))
  • SA-3 System Development Life Cycle
  • SC-2 Separation of System and User Functionality

PCI DSS 4.0 · 3 controls

  • 6.5.5 6.5.5 No live PANs in pre-production
  • 6.5.3 6.5.3 Separate pre-production from production
  • 6.5.4 6.5.4 Separate roles between production and pre-production

ISO 27001:2022 · 2 controls

  • 8.31 Separation of development, test and production environments
  • 8.33 Test information

ISO 27002:2022 · 2 controls

  • 8.31 Separation of development, test and production environments
  • 8.33 Test information

ISO 27701:2019 · 2 controls

  • 6.11.3 Test data
  • 6.9.1 Operational procedures and responsibilities
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • AUCDR-IS-3 Securely manage information assets over their lifecycle

CIS Controls v8 · 1 control

  • CIS-16.8 Separate Production and Non-Production Systems

GDPR · 1 control

  • 161R1-PM-25 Minimization of Personally Identifiable Information Used in Testing, Training, and Research

NIST SP 800-172 · 1 control

  • 3.13.4e Physical and Logical Isolation Techniques

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in C5: Procurement, Development and Modification of Information Systems

You are reading one control. How much of C5 (Germany) have you already done?

C5 (Germany) C5-DEV-10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of C5 (Germany) your existing evidence covers. Hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 and 95 of 121 C5 (Germany) controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 pair alone.

Query this from an agent

The graph holds this control, the 34 it maps to, and the evidence behind each claim, over MCP and REST.