DEV-08 Version Control
Maintain version control that records the dependencies between individual changes and allows affected system components to be returned to their previous state when errors or vulnerabilities are identified.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Dependency records linking a change to the components it touches · Ticketing / ITSM
governing documentDocuments that govern the control
- Branching and tagging scheme showing how releases are identified · Policy repository / GRC workspace
- Written restoration procedure plus a record of one restoration actually performed · Policy repository / GRC workspace
- Retention rules keeping prior releases available for restoration · Policy repository / GRC workspace
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
- Infrastructure and configuration definitions maintained outside version control
- Restoration has never been exercised, so its viability remains unproven
- Dependencies between changes untracked, so reverting one reintroduces an earlier defect
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 sheetDEV-07 Logging of changes · DEV-09 Approvals for provision in the production environment