CPS 234 para 36 APRA Notification of Material Control Weakness within 10 Business Days
APRA must be notified as soon as possible and no later than 10 business days after the entity becomes aware of a material information security control weakness it expects it will not be able to remediate in a timely way.
3
artefacts
0
held by a system
3
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
- Notification records with awareness dates · HR system / LMS
- Weakness register with materiality and remediation feasibility assessments · Policy repository / GRC workspace
- Evidence linking testing and audit findings to notification decisions · Policy repository / GRC workspace
governing documentDocuments that govern the control
none for this control
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
- No process connecting the weakness register to the notification duty
- Materiality threshold undocumented
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 35 APRA Notification of Material Incidents within 72 Hours