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.
Source: BSI C5 (121-criteria catalogue), DEV-08. 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
- Dependency records linking a change to the components it touches · Ticketing / ITSM
- Written restoration procedure plus a record of one restoration actually performed · Backup / DR tooling
governing documentDocuments that govern the control
- Branching and tagging scheme showing how releases are identified · Policy repository / GRC workspace
- Retention rules keeping prior releases available for restoration · Policy repository / GRC workspace
First move
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