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

C5 (Germany) C5-DEV-06: Testing changes

Test each change during development and deployment to a depth matching its risk rating, using suitably qualified staff or state-of-the-art automated testing, involve customers where contracts require it, and rate and remediate identified defects against defined severity criteria.

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

What else in your programme already covers this

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

NIST SP 800-218 · 6 controls

  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • DS-6 Enforce security of workload throughout DevOps lifecycle

FedRAMP High · 3 controls

  • CM-3(2) Testing, Validation, and Documentation of Changes
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))

FedRAMP Moderate · 3 controls

  • CM-3(2) Testing, Validation, and Documentation of Changes
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))

PCI DSS 4.0 · 3 controls

  • 6.2.3 6.2.3 Code review before release
  • 6.2.3.1 6.2.3.1 Manual code review independence and approval
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change
  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP04 Conduct code reviews

CIS Controls v8 · 2 controls

  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.8 Separate Production and Non-Production Systems

ISO 27001:2022 · 2 controls

  • 8.29 Security testing in development and acceptance
  • 8.33 Test information
  • CFTC-SS-5 Systems Development and Quality Assurance Category

CMMC 2.0 · 1 control

ISO 27002:2022 · 1 control

  • 8.29 Security testing in development and acceptance

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

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-06 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 35 it maps to, and the evidence behind each claim, over MCP and REST.