CPS 230 para 30 Monitoring, Review and Testing of Control Effectiveness
The entity must regularly monitor, review and test controls for design and operating effectiveness at a frequency proportionate to the materiality of the risks controlled, report results to senior management, and rectify
3
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Test results reported to senior management · Source control / CI pipeline
- Rectification tracker with closure evidence · Document repository
governing documentDocuments that govern the control
- Control testing schedule with frequency rationale by risk materiality · Document 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
- Uniform testing frequency regardless of risk materiality
- Deficiencies recorded but left open
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 230 para 29 Design and Embedding of Internal Controls · CPS 230 para 31 Remediation of Material Operational Risk Weaknesses