CPS 234 para 32 Internal Audit Review of Information Security Controls
Internal audit activities must include review of the design and operating effectiveness of information security controls, including those maintained by related parties and third parties.
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
- Audit reports on control design and operating effectiveness · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Internal audit plan covering information security · Policy repository / GRC workspace
- Scope evidence covering third party maintained controls · Vendor register / contract repository
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 covers design only and not operating effectiveness
- Third party controls out of audit scope
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 sheetCPS 234 para 31 Annual Review of Testing Program Sufficiency · CPS 234 para 33 Skill of Personnel Providing Control Assurance