CCC-09 Change Restoration
Be able to roll a change back to the last known good state when it produces errors or a security concern, through a defined and tested process.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evidence a rollback has been performed or tested · Document repository
governing documentDocuments that govern the control
- The documented rollback process · Document repository
- Rollback plans attached to recent significant changes · Policy repository / GRC workspace
- Definition of what constitutes the known good state per asset · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Rollback plan written as a single line saying restore from backup
- Rollback never tested, so its feasibility is unknown
- No defined known good state, so there is nothing to roll back to
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 sheetCCC-08 Exception Management · CEK-01 Encryption and Key Management Policy and Procedures