C5 Field Guideunofficial

DEV · Procurement, Development and Modification of Information Systems

DEV-06 Risk Assessment, Categorisation and Prioritisation of Changes

3 sub-criteria: 2 basic, 1 additional

Changed since C5:2020 · formerly DEV-05

Basic criterion

Extended requirement for the risk assessment of changes to consider cumulative effects and dependencies.

Added requirement regarding the handling of planned changes with a high risk.

Additional criterion

Slight linguistic adaptation.

Added specification that changes without an effect on service usage or security posture are excluded from the scope of the criterion.

Wording in C5:2020

Basic criterion

In accordance with the applicable policies (cf. DEV-03), changes are subjected to a risk assessment with regard to potential effects on the system components concerned and are categorised and prioritised accordingly.

Additional criterion

In accordance with the contractual agreements, meaningful information about the occasion, time, duration, type and scope of the change is submitted to authorised bodies of the cloud customer so that they can carry out their own risk assessment before the change is made available in the production environment. Regardless of the contractual agreements, this is done for changes that have the highest risk category based on their risk assessment.

All changes since C5:2020

Basic criterion

DEV-06.01B

In accordance with the applicable policies, changes are subject to a risk assessment evaluating its potential impact on the overall cloud service in scope. In addition, when multiple changes are implemented concurrently, their mutual interactions and cumulative effects are also subject to the risk assessment in order to identify potential conflicts or dependencies. All identified risks and dependencies are categorised and prioritised accordingly.

DEV-06.02B

If the risk associated to a planned change is high, appropriate mitigation measures are taken before deploying the change in the cloud service's production environment.

Additional criterion

DEV-06.01AC

Additional, complementing

In accordance with the contractual agreements, meaningful information about the occasion, time, duration, type and scope of the change is submitted to authorised bodies of the cloud service customer so that they can carry out their own risk assessment before the change is made available in the production environment. Regardless of the contractual agreements, this is done for changes that have the highest risk category based on their risk assessment. This does not include changes without an effect on the service usage or security posture of the service.

BSI text from C5:2026 and its changelog: © Federal Office for Information Security 2026, reproduced unchanged under CC BY-ND 4.0. Unofficial site, not affiliated with BSI. Licence and sources