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 wher
4
artefacts
1
held by a system
2
at each review
moderate
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Current list of personnel or automated components entitled to release changes · Ticketing / ITSM
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
First move
Start with the 1 of 4 artefacts that already live in a system (Ticketing / ITSM); keep the periodic reviews but log each one as a dated record with a named reviewer.
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