CPS 230 para 29 Monitor, review and test controls; report results; rectify gaps promptly
On a regular basis the entity must monitor, review and test its controls for both design and operating effectiveness, at a frequency matched to how material the controlled risk is. Test results must go to senior management, and gaps or deficiencies found in the control environment must be fixed promptly.
Source: APRA CPS 230, CPS 230 para 29. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open APRA CPS 230 in the compliance library.
Applies to APRA-regulated entities.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Issue log of control deficiencies with owners, due dates and closure evidence · SIEM / log platform
periodic reviewEvidence produced at each review
- Control testing results with design and operating effectiveness conclusions · Document repository
- Senior management reports summarising test results · Source control / CI pipeline
governing documentDocuments that govern the control
- Risk-based control testing plan showing frequency set by risk materiality · Policy repository / GRC workspace
First move
Common gaps auditors find
- All controls tested on the same cycle regardless of materiality
- Deficiencies overdue with no escalation
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 Design, implement and embed internal controls · CPS 230 para 30 Remediate material weaknesses and keep them in the risk profile until fixed