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

C5 (Germany) C5-DEV-03: Policies for changes to information systems

Publish change management rules for software deployment setting criteria for risk categorisation, the testing and approvals each category demands, separation between developing, testing and releasing, customer notification duties, documentation updates, and emergency changes held to the same security level.

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

What else in your programme already covers this

This control maps to 43 controls across 20 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 · 4 controls

  • CM-1 Policy and Procedures
  • CM-3 Configuration Change Control
  • CM-3(4) Security and Privacy Representatives
  • CM-9 Configuration Management Plan

FedRAMP Moderate · 4 controls

  • CM-1 Policy and Procedures
  • CM-3 Configuration Change Control
  • CM-3(4) Security and Privacy Representatives
  • CM-9 Configuration Management Plan

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.32 Change management
  • 8.9 Configuration management

ISO 27002:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.32 Change management
  • 8.9 Configuration management

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-218 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

AWS Well-Architected Security Pillar · 2 controls

  • SEC01-BP06 Automate deployment of standard security controls
  • SEC11-BP06 Deploy software programmatically

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

  • CFTC-SS-32 Timely Advance Notice of Material Planned Changes
  • CFTC-SS-4 Systems Operations Category

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied

PCI DSS 4.0 · 2 controls

  • 1.2.2 1.2.2 Network connection and NSC changes under change control
  • 6.5.1 6.5.1 Change control procedure for production

SOC 2 · 2 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-34 Define an Update Policy for Information System Components

Azure Security Benchmark · 1 control

  • DS-6 Enforce security of workload throughout DevOps lifecycle

CIS Controls v8 · 1 control

  • CIS-16.1 Establish and Maintain a Secure Application Development Process

CMMC 2.0 · 1 control

ISO 27701:2019 · 1 control

  • 6.9.1 Operational procedures and responsibilities

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST SP 800-171 Rev 3 · 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-03 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.

If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.178.5% covered · 26 gapsIf you hold NIST SP 800-53 Rev 572.7% covered · 33 gapsIf you hold FedRAMP Moderate71.1% covered · 35 gapsIf you hold ISO 27002:202267.8% covered · 39 gapsIf you hold ISO 27001:202257% covered · 52 gapsIf you hold NIST SP 800-171 Rev 350.4% covered · 60 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll C5 (Germany) controls