CPS 230 para 29 Design and Embedding of Internal Controls
The entity must design, implement and embed internal controls that mitigate its operational risks in line with its risk appetite and allow it to meet its compliance obligations.
3
artefacts
0
held by a system
1
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
- Evidence controls are embedded in business process · Document repository
governing documentDocuments that govern the control
- Control library mapped to operational risks and compliance obligations · Document repository
- Control design documentation · 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
- Controls documented but not operating
- No linkage from controls to risk appetite
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 28 Risk Assessment Before Providing a Material Service to Another Party · CPS 230 para 30 Monitoring, Review and Testing of Control Effectiveness