DEV-07 Logging of changes
Place source code management and software deployment tooling under the role and rights concept with enforced authorisation, and configure it so every change to production system components is logged and traceable to the person or component that executed it.
Source: BSI C5 (121-criteria catalogue), DEV-07. 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
- Audit log extract showing changes attributed to identified actors · SIEM / log platform
- Setting that prevents history rewriting or removal of tool logs · SIEM / log platform
periodic reviewEvidence produced at each review
- Review of who currently holds pipeline administration rights · Ticketing / ITSM
governing documentDocuments that govern the control
- Permission model applied to the code repository and the deployment tooling · Policy repository / GRC workspace
First move
Common gaps auditors find
- Deployments executed under a shared pipeline identity that masks the requesting engineer
- Repository administrators can rewrite history and erase the trail behind them
- Tool logs retained for a shorter span than the audit window they are meant to support
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