Batch Register

Material control weakness report

None of the published texts sets a fixed period on this consumer; every row below reads no period set by the text. Paste one job that feeds this consumer, for example control_weakness_escalation, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.

Matched on the job name or the consumer column by these words: control weakness, weakness report, control deficien, deficiency report, control weakness report. The clocks on this class run from the event, not from a schedule, so the register asks for the drill or exercise job that proves the pack can be produced in time.

The clock each rule sets

RegimeClockClause
CPS 234no clockCPS 234 para 36 Notify APRA of material control weaknesses within 10 business days10 business days after becoming aware
no clockCPS 234 para 29 Escalate control deficiencies that cannot be fixed promptly
PCI DSSno clockPCI DSS 10.7.2 Detect and alert on critical security control failurespromptly

Questions this page answers

How often does APRA CPS 234 require material control weakness report?

The text of CPS 234 para 36 (Notify APRA of material control weaknesses within 10 business days) sets no fixed period: 10 business days after becoming aware. The text of CPS 234 para 29 (Escalate control deficiencies that cannot be fixed promptly) sets no fixed period: no period set by the text. 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. 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.

How often does PCI DSS v4.0 require material control weakness report?

The text of PCI DSS 10.7.2 (Detect and alert on critical security control failures) sets no fixed period: promptly. When a critical security control system fails, the failure must be detected, alerted and addressed promptly, covering at least failures of: IDS/IPS; network security controls; anti-malware; change-detection tools; logical access controls; physical access controls; segmentation controls where used; audit logging mechanisms; mechanisms for reviewing audit logs; and any automated security testing tools in use. Applies to all entities, service providers included. Applicability: takes the place of 10.7.1 from 31 March 2025 and adds two control systems that 10.7.1 did not list (the mechanisms for reviewing audit logs and automated security testing tools). Objective under the customized approach: any failure of a critical security control system is spotted and dealt with promptly. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

What does the register ask the owner of a material control weakness report job?

Which weaknesses in the last run could not be remediated in a timely way, and were they escalated to the board?

The clauses in full

CPS 234 para 36 Notify APRA of material control weaknesses within 10 business daysthe standard's page

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

CPS 234 para 29 Escalate control deficiencies that cannot be fixed promptlythe standard's page

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

PCI DSS 10.7.2 Detect and alert on critical security control failuresthe standard's page

When a critical security control system fails, the failure must be detected, alerted and addressed promptly, covering at least failures of: IDS/IPS; network security controls; anti-malware; change-detection tools; logical access controls; physical access controls; segmentation controls where used; audit logging mechanisms; mechanisms for reviewing audit logs; and any automated security testing tools in use. Applies to all entities, service providers included. Applicability: takes the place of 10.7.1 from 31 March 2025 and adds two control systems that 10.7.1 did not list (the mechanisms for reviewing audit logs and automated security testing tools). Objective under the customized approach: any failure of a critical security control system is spotted and dealt with promptly. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

What an assessor asks to see: Process document covering failure detection for all ten listed control systems; Health check and heartbeat monitoring configuration, including for the SIEM and log review tooling; Sample alerts showing detection of a control failure (for example firewall offline, agent stopped); Coverage matrix mapping each critical control system to its failure alert. Where it usually falls short: Failure of the SIEM or log review tooling itself is not monitored

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. Run this job through the register