What APRA CPS 234 sets on each scheduled job
Paragraph 35 sets 72 hours for a material incident, paragraph 36 ten business days for a material control weakness, paragraph 26 an annual review and test of response plans. Tick CPS 234 on the register and every job in these classes carries its row below. A lit cell is a figure the clause states; a row that reads no clock stays that way, because the register never fills a blank the standard left open.
The clock each rule sets
| Consumer class | Clock | Clause |
|---|---|---|
| Security monitoring and log review | ||
| Security alert and monitoring report | no clock | CPS 234 para 23 Detect and respond to incidents promptlyin a timely way |
| Incident and breach reporting | ||
| Breach notification report pack | 72h | CPS 234 para 35 Notify APRA of material incidents within 72 hoursno later than 72 hours |
| Incident and service report | no clock | CPS 234 para 23 Detect and respond to incidents promptlyin a timely way |
| Incident response exercise or drill | 8,760h | CPS 234 para 26 Annual review and testing of response plansreviewed and tested every year |
| Regulator incident notification | 72h | CPS 234 para 35 Notify APRA of material incidents within 72 hoursno later than 72 hours |
| Material control weakness report | no clock | CPS 234 para 36 Notify APRA of material control weaknesses within 10 business days10 business days after becoming aware |
| no clock | CPS 234 para 29 Escalate control deficiencies that cannot be fixed promptly | |
| Board and management reporting | ||
| Board and committee pack | no clock | CPS 234 para 29 Escalate control deficiencies that cannot be fixed promptly |
| Risk register and control status report | no clock | CPS 234 para 29 Escalate control deficiencies that cannot be fixed promptly |
The clauses in full
The entity has robust means of spotting information security incidents and responding to them in good time.
What an assessor asks to see: Security monitoring architecture (SIEM, EDR, logging coverage) with scope across critical assets; Alert triage and escalation procedures with response time targets; Security operations centre or managed detection service contract and performance reports; Incident tickets showing detection-to-containment times. Where it usually falls short: Logging not enabled or not collected for critical systems or third-party services
The entity must tell APRA promptly, and at the latest within 72 hours of becoming aware, of any information security incident that either (a) had, or could have had, a material financial or non-financial effect on the entity itself or on the interests of its depositors, policyholders, beneficiaries or other customers (the impact limb), or (b) has already been notified to another regulator in Australia or overseas. A footnote covers incidents not already reported under CPS 231, SPS 231, CPS 232 or SPS 232, and counts domestic government agencies and international regulators as other regulators.
What an assessor asks to see: Notification procedure stating the 72-hour clock, who decides materiality and who submits to APRA; Materiality assessment criteria and completed assessments per incident; Copies of APRA notifications with timestamps of awareness and submission; Register of notifications to other regulators that triggers APRA notification. Where it usually falls short: Clock started at confirmation of the incident instead of awareness
Every year the entity reviews and tests its response plans so they stay effective and fit for purpose.
What an assessor asks to see: Annual exercise schedule and completed tabletop or simulation reports; Exercise participant lists including executives and, where relevant, the Board; After-action reports with improvements logged and tracked; Records of the annual plan review and resulting changes. Where it usually falls short: Plan reviewed on paper but never exercised
The entity must tell APRA promptly, and at the latest within 10 business days of becoming aware, of any material weakness in its information security controls that it does not expect to be able to remediate in good time.
What an assessor asks to see: Procedure defining material control weakness and the 10 business day notification clock; Deficiency register flagging weaknesses assessed as material and unlikely to be fixed in time; Copies of APRA notifications of control weaknesses with dates; Decision records showing who assessed materiality and expected remediation timing. Where it usually falls short: No defined trigger, so weaknesses are never assessed for notification
When testing reveals deficiencies in security controls that the entity cannot fix in good time, the entity escalates and reports them to the Board or to senior management.
What an assessor asks to see: Deficiency register with ageing and remediation due dates; Escalation criteria defining when a deficiency is overdue or cannot be fixed in time; Board or executive committee papers reporting unremediated deficiencies; Risk acceptance records signed by the right authority. Where it usually falls short: Overdue findings stay in an IT tracker and never reach senior management
Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Every regime: the index.