Skip to main content

Notifiable Data Breach: a step-by-step walkthrough for the first 30 days

Rules Mate Editorial3 min read

What to do hour-by-hour when you discover a suspected data breach. The 30-day assessment, the notification triggers, OAIC and affected individuals.

Hour 0: discovery

You discover (or are told about) a suspected breach. Maybe a phishing campaign succeeded. Maybe a backup was misconfigured. Maybe a forensic provider has flagged unusual activity.

Immediate actions (within the hour):

  1. Activate your incident response plan — designate an incident owner, a privacy officer point of contact, and a comms lead
  2. Preserve evidence — do not delete logs, do not reformat affected systems
  3. Open a contemporaneous incident register entry — time of awareness, who knew, initial known facts
  4. Notify your cyber insurer — check your policy's notification conditions, which are often short

Hour 0–24: containment

Contain the breach to prevent further damage:

  • Suspend affected user accounts
  • Isolate affected systems from the network
  • Rotate credentials, API keys, certificates
  • Engage forensic provider if scope is uncertain (your cyber insurer typically has a panel)

Keep contemporaneous documentation. Everything you do in the first 24 hours is potentially evidence the OAIC may ask to see.

Day 1–7: assessment kickoff

Where you suspect an eligible data breach, you must take all reasonable steps to complete the assessment within 30 calendar days after the day you become aware of the grounds for suspicion (OAIC quick reference guide). An "eligible data breach" is unauthorised access to, unauthorised disclosure of, or loss of personal information that is likely to result in serious harm to any of the individuals it relates to.

The assessment framework asks:

  1. What information was involved? Personal information, sensitive information, health information?
  2. Who is potentially affected? Customers, employees, contractors? How many?
  3. What's the risk of serious harm? Identity theft, financial loss, physical safety, emotional or psychological harm?

If the breach is clearly an eligible data breach (e.g. exfiltration of customer PII at scale), don't run the assessment clock for show — move to notification.

Day 7–30: completing the assessment

Assess as quickly as the facts allow. Things you'll do:

  • Forensic review — exactly what was accessed, exfiltrated, modified
  • Risk modelling — likelihood of serious harm to affected individuals
  • Pre-draft notification templates — OAIC NDB statement + affected-individual letter, ready to lodge
  • Engage legal counsel — particularly for cross-border issues
  • Brief executive, board (or audit & risk committee)

The 30-day clock is the maximum; assess in good faith and don't engineer delay.

Notification triggers

If your assessment concludes the breach is an eligible data breach, you must notify:

  • The OAIC — a statement, as soon as practicable
  • Individuals — as soon as practicable, using one of the options in s 26WL (below)

If the assessment concludes it is not an eligible data breach (no serious harm likely), document the reasoning and close the matter. No notification required.

Lodging with the OAIC

Use the OAIC's online NDB statement form. Mandatory content:

  • Identity of the entity (you)
  • Description of the breach (when, what, how)
  • Kinds of information involved
  • Recommended steps for affected individuals
  • Entity contact for further information

OAIC may follow up with questions, particularly for large breaches. Cooperate.

Notifying individuals

Section 26WL of the Privacy Act 1988 sets three options, in order:

  1. If practicable, notify each of the individuals to whom the relevant information relates
  2. If practicable, notify only the individuals who are at risk from the eligible data breach
  3. If neither is practicable, publish a copy of the statement on your website (if any) and take reasonable steps to publicise its contents

Website publication is a fallback, not an equal alternative. Record why direct notification was not practicable if you rely on option 3 (e.g. you don't have current contact details).

Post-incident lessons learned

Within 4–8 weeks of resolution:

  1. Root cause analysis — what control failed
  2. Remediation tracker — what you've changed (and tested) to prevent recurrence
  3. Board / audit committee briefing — non-financial risk reporting
  4. Update your breach response plan — every incident teaches you something
  5. Tabletop exercise — pressure-test the updated plan within 6 months

Done well, a breach response builds organisational resilience. Done badly, it becomes the basis for the next OAIC civil penalty proceeding.

Frequently asked

Is the deadline 72 hours?

No — that's the GDPR rule. Under the Australian Privacy Act you have up to 30 days to assess, then notify 'as soon as practicable' once eligible.

Do I have to notify the police?

Not as part of NDB. Separately, you may want to report the incident to police or to the Australian Signals Directorate through ReportCyber, and other sector reporting duties may apply.

What if I'm not sure whether it's eligible?

Continue the assessment in good faith — you have up to 30 days. Document the reasoning either way.

Can I rely on the cyber insurer's incident manager?

Helpful but not sufficient. The notification obligation is on you, the APP entity. Lawyer-led incident response is recommended for larger breaches.

Related

Related reading