DEV-09 Approvals for provision in the production environment
Require authorised personnel or approval components to release each change into the production environment against defined criteria such as test results and prior sign-offs, involving cloud customers in that release where contractual requirements provide for it.
Source: BSI C5 (121-criteria catalogue), DEV-09. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open BSI C5 (121-criteria catalogue) in the compliance library.
The edition of the catalogue is not stamped here; check the edition your attestation is issued against.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Sampled release records naming the approver and evidencing each criterion · Ticketing / ITSM
- Customer sign-off records where the agreement calls for their involvement · Ticketing / ITSM
governing documentDocuments that govern the control
- Defined criteria that a change must satisfy before entering production · Policy repository / GRC workspace
- Current list of personnel or automated components entitled to release changes · Policy repository / GRC workspace
First move
Common gaps auditors find
- Approvals recorded after the change was already serving customers
- The entitled approver list is unmaintained, so departed staff keep release rights
- Automated promotion gates configured to pass even when test results are absent
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet