EvidenceSheet

A.8.4 Access to source code

Appropriately manage read and write access to source code, development tools and libraries.

16
artefacts
5
held by a system
5
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • Access request and approval logs · Identity provider / directory
  • IDE access logs · SIEM / log platform
  • Vulnerability scan reports for libraries · Vulnerability scanner / patch tooling
  • Change request tickets · Ticketing / ITSM
  • Merge request audit logs · SIEM / log platform

periodic reviewEvidence produced at each review

  • Periodic access review report · Identity provider / directory
  • Tool account provisioning records · Identity provider / directory
  • MFA configuration screenshots · Identity provider / directory
  • Code review sign‑off records · Ticketing / ITSM
  • Release approval board minutes · Ticketing / ITSM

governing documentDocuments that govern the control

  • Repository permission matrix · Policy repository / GRC workspace
  • User role definition document · Policy repository / GRC workspace
  • Privileged tool usage policy · Policy repository / GRC workspace
  • Approved third‑party library list · Document repository
  • Component licensing register · Policy repository / GRC workspace
  • Dependency update approval workflow document · Document repository

First move

Start with the 5 of 16 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

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

A.8.3 Information access restriction · A.8.5 Secure authentication