Incident Postmortems in Australia: CPS 234, NDB and SOCI

A blameless post-incident review that also covers APRA's 72-hour CPS 234 notice, the 30-day NDB assessment and SOCI's 12- and 72-hour cyber reports.

By · · 6 min read

Illustration for the Incident Postmortem Generator guide

Australia edition. Written for Australian teams: APRA CPS 234 and CPS 230 notifications and post-incident review, the OAIC Notifiable Data Breaches scheme, and Security of Critical Infrastructure Act cyber incident reports, with an AEDT timeline. US edition

In Australia the post-incident review is where engineering practice meets four separate reporting regimes. An APRA-regulated entity must tell APRA within 72 hours of becoming aware of a material information security incident under CPS 234, and under CPS 230 within 24 hours of a disruption to a critical operation outside its tolerance. Any organisation covered by the Privacy Act 1988 that suspects an eligible data breach has 30 days to assess it under the Notifiable Data Breaches (NDB) scheme. And the responsible entity for a critical infrastructure asset has 12 or 72 hours to report a cyber security incident under the Security of Critical Infrastructure Act 2018 (SOCI Act). A blameless review that keeps an accurate timeline is the evidence for all four.

This edition walks through an incident at an APRA-regulated insurer in the Incident Postmortem Generator, with the timeline in AEDT. It summarises the rules as APRA, the OAIC and the Federal Register of Legislation publish them; which ones apply depends on your entity, so confirm with your risk and legal teams.

Four regimes and their clocks

RegimeWhoTriggerDeadline
APRA CPS 234 Information SecurityAPRA-regulated entities: banks (ADIs), general and life insurers, private health insurers, super trusteesAn information security incident that materially affected, or could have materially affected, the entity or its customers' interests, or that has been notified to another regulatorAs soon as possible, no later than 72 hours after becoming aware
APRA CPS 230 Operational Risk ManagementAPRA-regulated entitiesA disruption to a critical operation (for an insurer, at least claims processing) outside its tolerance levelAs soon as possible, not later than 24 hours after
APRA CPS 230As aboveAn operational risk incident likely to have a material financial impact or a material impact on the ability to maintain critical operationsAs soon as possible, not later than 72 hours after becoming aware
Privacy Act, NDB schemeOrganisations and agencies covered by the Privacy ActReasonable grounds to suspect an eligible data breachAll reasonable steps to assess within 30 calendar days; if eligible, promptly notify the OAIC and affected individuals
SOCI Act s 30BCResponsible entity for a critical infrastructure assetA cyber security incident having a significant impact on the availability of the assetAs soon as practicable, within 12 hours of becoming aware
SOCI Act s 30BDAs aboveA cyber security incident with a relevant impact on the asset (occurred, occurring or imminent)Within 72 hours of becoming aware

Under the SOCI Act a report can be made orally, but then a written record in the approved form must follow within 84 hours (s 30BC) or 48 hours (s 30BD). The report goes to the relevant Commonwealth body specified in the rules.

CPS 234 also shapes the review itself. It requires information security response plans to cover every stage of an incident "from detection to post-incident review", and it requires those plans to be reviewed and tested every year. An APRA reviewer reading your postmortem is checking that the plan worked as written, so the review should say where it did not.

Under the NDB scheme, a breach is eligible when it is likely to result in serious harm to one or more people and remedial action has not prevented that risk. The OAIC defines "likely" as more probable than not, judged from the position of a reasonable person in your entity's place. Its four steps (contain, assess, notify, review) end in the same review you are writing.

Worked example: a WAF change, a portal outage and a document leak

A general insurer's online claims portal starts returning errors after a web application firewall (WAF) rule change. All times are AEDT and the timeline says so at the top.

In the Incident Postmortem Generator, paste one event per line:

07:55 AEDT - Claims portal returns 502 errors after a WAF rule update
08:40 AEDT - Contact centre escalates customer complaints; no monitoring alert fired
08:52 AEDT - Incident declared, severity 2
09:35 AEDT - WAF rule rolled back; portal recovers
11:20 AEDT - Log review finds the fallback route skipped authentication on claim document downloads; 37 documents fetched by an unknown IP address
11:45 AEDT - Information security incident declared; CISO and privacy officer informed
16:30 AEDT - Fallback route removed and authentication enforced on all document paths

The generator splits each line into time and event. Enter 45 for time to detect, 100 for time to mitigate and 515 for time to resolve, and the report shows 45 min, 1 h 40 min and 8 h 35 min.

Now read the timeline against the four regimes:

  • Detection. Forty-five minutes with customers as the only alarm is the first finding, before any regulation. It produces a detection action item: "Synthetic claim submission every 2 minutes, alert after two consecutive failures, owner: SRE lead".
  • CPS 234. The insurer became aware of an information security incident at 11:20 AEDT. Claim documents hold health and financial details, so it plainly could materially affect policyholders' interests. Seventy-two hours from 11:20 AEDT on a Tuesday is 11:20 AEDT on Friday. The standard counts this deadline in hours; it uses business days only for a different notice (10 business days for a material control weakness that cannot be fixed in time). Record the time APRA was notified.
  • CPS 230. Claims processing is a critical operation every insurer must classify as one unless it can justify otherwise, and the insurer has set a tolerance for how long it can be disrupted. If the 1 h 40 min outage (07:55 to 09:35 AEDT) went beyond that tolerance, APRA must be told as soon as possible and not later than 24 hours after; counting cautiously from the first errors, that is 07:55 AEDT on Wednesday. Record the tolerance, whether it was breached, and the decision and time of any notice.
  • NDB scheme. With 37 claim documents taken by an unknown party, the insurer has reasonable grounds to suspect an eligible data breach and must take all reasonable steps to finish its assessment within 30 calendar days. Health information taken by an unknown party needs careful assessment against the serious harm test, and if the breach is eligible the OAIC and the 37 claimants must be notified promptly; the assessment and its reasoning go into the review.
  • SOCI Act. Only if the insurer is the responsible entity for a critical infrastructure asset. If it were, the outage's impact on availability would be weighed under s 30BC (12 hours from becoming aware) and the unauthorised access under s 30BD (72 hours). The review should record whether these sections were considered, and the conclusion.

The trigger was the WAF rule. The root cause is that a fallback route with weaker controls existed at all, and that no test exercised the portal's behaviour when the WAF blocked traffic. Action items follow from that: remove the fallback route (solution), add an automated test that fails if any document path is reachable without a session (prevention), and add the WAF change type to the change-review checklist (prevention). If every item lands in one category, the generator's grouping makes the imbalance visible.

Running the review so it stands up

  • One time zone. Logs from cloud services arrive in UTC and staff in other states may note their own local times. Convert everything to the zone named at the top of the timeline; the Time Zone Converter helps.
  • Separate learning from discipline. The review asks what let a WAF change open an unauthenticated path, not who wrote the rule. APRA and the OAIC both want an accurate account, and fear produces missing timestamps.
  • Write down what you do not know. The generator shows "Not recorded" for any blank duration. That is safer in a document a regulator may read than a guess that becomes the official figure.
  • Feed the annual test. CPS 234 requires response plans to be tested every year. Each review should end with what the plan got wrong and an owner to change it, so the next test exercises the fix.

When the causal chain is long, the Root Cause Analysis tool walks through 5 Whys and fishbone diagrams, and a failure mode analysis helps for a system that keeps failing in new ways.

Tools for this job

For the general method behind blameless reviews, see the incident postmortem guide.

Frequently asked questions

How long does an APRA-regulated entity have to report a cyber incident?

Under CPS 234, it must notify APRA as soon as possible and no later than 72 hours after becoming aware of an information security incident that materially affected, or could have materially affected, the entity or its customers, or that has been notified to another regulator.

How long do we have to assess a suspected data breach?

The OAIC says an entity that suspects an eligible data breach must take all reasonable steps to complete its assessment within 30 calendar days of becoming aware of the grounds for suspicion, and should notify promptly if the breach is eligible.

What is the difference between the 12-hour and 72-hour SOCI reports?

Section 30BC covers cyber security incidents with a significant impact on the availability of a critical infrastructure asset and requires a report within 12 hours. Section 30BD covers incidents with a relevant impact, including imminent ones, and allows 72 hours.

Does CPS 234 require a post-incident review?

It requires information security response plans to include mechanisms for managing every stage of an incident, from detection to post-incident review, and to be reviewed and tested every year.

Sources and further reading

Open the Incident Postmortem Generator

More Documentation & Review

Every tool in the Documentation & Review section, free and in your browser.