6.9.7 Information systems audit considerations
Information systems audit controls apply as the base guidance requires, so audit activity on operational systems is planned and agreed to minimise disruption, read as covering systems that process personal data.
3
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
- Evidence audit tooling access to personal data was itself controlled · Data governance / DLP tooling
governing documentDocuments that govern the control
- Agreed audit procedures for operational systems · Policy repository / GRC workspace
- Records of audit access granted and its scope · 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
- Audit tooling granted standing broad access to production data
- Audit activity performed without agreement, disrupting processing
- Auditor access never revoked after the engagement
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 sheet6.9.6 Technical vulnerability management · 6.10.1 Network security management