EvidenceSheet

A.8.34 Protection of information systems during audit testing

Plan and agree audit tests on operational systems with management to avoid disruption.

15
artefacts
4
held by a system
4
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

  • Test plan version history · Source control / CI pipeline
  • Change request ticket linked to test · Ticketing / ITSM
  • Notification log sent to operations · SIEM / log platform
  • Incident log if disruption occurred · SIEM / log platform

periodic reviewEvidence produced at each review

  • Management signoff sheet · Source control / CI pipeline
  • Meeting minutes with it and business units · Vendor register / contract repository
  • Risk assessment report for test · Policy repository / GRC workspace
  • Test results report · Source control / CI pipeline

governing documentDocuments that govern the control

  • Approved test plan document · Policy repository / GRC workspace
  • Email agreement on test window · Vendor register / contract repository
  • Risk acceptance form · Vendor register / contract repository
  • Impact analysis matrix · Policy repository / GRC workspace
  • Contingency plan document · Policy repository / GRC workspace
  • Scheduled downtime announcement · Document repository
  • Lessons learned summary · Document repository

First move

Start with the 4 of 15 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.33 Test information · 9.2.1 General