facebook-pixel

Australian Data Breach Notification Scheme: Complete 2026 Guide

L
Lunyb Security Team
··9 min read

Since February 2018, Australian organisations have operated under one of the strictest breach disclosure regimes in the Asia-Pacific region. The Australian Data Breach Notification Scheme — formally known as the Notifiable Data Breaches (NDB) scheme — sits inside the Privacy Act 1988 and requires eligible entities to report serious data breaches to both affected individuals and the Office of the Australian Information Commissioner (OAIC).

This guide explains how the scheme works in 2026, who it applies to, how to assess whether a breach is notifiable, the exact steps to follow after an incident, and how recent reforms have sharpened enforcement and penalties.

What Is the Australian Data Breach Notification Scheme?

The Australian Data Breach Notification Scheme is a legal framework under Part IIIC of the Privacy Act 1988 (Cth) that requires regulated organisations to notify individuals and the OAIC when a data breach is likely to result in serious harm. It came into force on 22 February 2018 and is administered by the Australian Information Commissioner.

The scheme is built around a simple principle: people have the right to know when their personal information has been compromised so they can take protective action — such as changing passwords, freezing credit, or monitoring accounts for fraud.

Key Legal Foundations

  • Privacy Act 1988 (Cth) — the primary legislation.
  • Australian Privacy Principles (APPs) — 13 principles governing handling of personal information.
  • Part IIIC — the specific provisions creating the NDB obligations.
  • Privacy Legislation Amendment (Enforcement and Other Measures) Act 2022 — dramatically increased penalties.

Who Must Comply With the NDB Scheme?

The scheme applies to "APP entities" — the same organisations already bound by the Australian Privacy Principles. This includes:

  • Australian Government agencies.
  • Businesses and not-for-profits with an annual turnover above AUD $3 million.
  • All private sector health service providers (regardless of turnover).
  • Credit reporting bodies and credit providers.
  • Tax File Number (TFN) recipients.
  • Entities that trade in personal information or provide services to the Commonwealth.

Small businesses under the $3 million threshold are generally exempt, but exemptions are narrowing. The Australian Government's 2023 Privacy Act Review Report recommended removing the small business exemption entirely, and staged reforms through 2024-2026 are gradually bringing more SMEs into scope.

Overseas Organisations

The scheme has extraterritorial reach. Foreign companies that collect or hold personal information of Australians and have an "Australian link" must also comply — a point reinforced after the Clearview AI determination.

What Is an "Eligible Data Breach"?

Not every incident triggers notification. The Privacy Act defines an eligible data breach as one that meets three criteria:

  1. Unauthorised access, disclosure, or loss of personal information held by an entity has occurred.
  2. The breach is likely to result in serious harm to one or more individuals.
  3. The entity has not been able to prevent the likely risk of serious harm through remedial action.

If all three conditions are met, notification is mandatory.

Examples of Eligible Data Breaches

  • A laptop containing unencrypted customer records is stolen.
  • Credentials are phished and an attacker exfiltrates a client database.
  • A misconfigured cloud bucket exposes identity documents publicly.
  • Ransomware encrypts personal data and the attacker exfiltrates it.
  • An employee emails a spreadsheet of customer details to the wrong recipient and it cannot be recalled.

How to Assess "Serious Harm"

"Serious harm" is the pivotal concept of the scheme. The OAIC considers it to include physical, psychological, emotional, financial, or reputational harm. When assessing risk, entities should weigh:

  • The kind and sensitivity of the information (health data and government ID numbers rank highest).
  • Whether the information was encrypted or de-identified.
  • The nature of the harm likely to result.
  • Who is likely to have obtained the information (criminal actor vs. internal error).
  • The number of individuals affected.

If a reasonable person would conclude serious harm is likely (more probable than not), the breach is notifiable.

The 30-Day Assessment Rule

Once an entity has reasonable grounds to suspect an eligible data breach, it has 30 calendar days to complete an assessment. This is a maximum — the OAIC expects assessments to be completed "as soon as practicable."

The Three-Phase Assessment Process

  1. Initiate: Appoint a response lead, convene the incident response team, and document the trigger.
  2. Investigate: Gather logs, interview staff, confirm scope, identify affected individuals and data categories.
  3. Evaluate: Apply the "likely to result in serious harm" test and document the reasoning.

If an assessment cannot reasonably be completed within 30 days, document why — the OAIC will scrutinise this closely in any subsequent investigation.

Notification Requirements: Step-by-Step

Once a breach is confirmed as notifiable, the entity must take two parallel actions "as soon as practicable."

1. Notify the OAIC

Submit the Notifiable Data Breach form via the OAIC website. The statement must include:

  • Identity and contact details of the entity.
  • A description of the breach.
  • The kinds of information concerned.
  • Recommended steps individuals should take.

2. Notify Affected Individuals

Entities can choose one of three notification options:

OptionMethodWhen to Use
Option 1Notify all individuals whose data was involvedSimplest and often safest approach
Option 2Notify only individuals at likely risk of serious harmWhen the "at risk" group can be clearly identified
Option 3Publish statement on website + take reasonable steps to publiciseOnly where options 1 and 2 are not practicable

Notifications should use the entity's normal communication channel (email, SMS, letter) and be written in plain English.

Exceptions to Notification

The Privacy Act provides limited exceptions where notification is not required:

  • Remedial action exception: The entity took action before serious harm was likely to occur (e.g. remote-wiped a stolen laptop before access).
  • Multiple entity exception: Another entity has already notified on behalf of all involved parties.
  • Enforcement body exception: Notification would prejudice enforcement activities.
  • Secrecy provisions: Where other legislation prohibits disclosure.
  • Commissioner declaration: The Commissioner has granted a specific exemption.

Penalties and Enforcement in 2026

The 2022 reforms transformed penalty exposure. For serious or repeated interferences with privacy, maximum penalties for bodies corporate are the greater of:

  • AUD $50 million, or
  • Three times the value of any benefit obtained from the misuse of information, or
  • 30% of adjusted turnover for the relevant period.

These penalties bring Australia into line with the GDPR and have produced a noticeable shift in boardroom attention. The OAIC has also received expanded investigation, assessment, and information-sharing powers.

Recent Enforcement Trends

The OAIC's biannual NDB reports consistently show that malicious or criminal attacks (particularly phishing and credential compromise) drive the majority of notifications, followed by human error. Health and finance remain the most-notified sectors. Civil penalty proceedings against major breached entities — including class actions running in parallel — have become a regular fixture of the Australian legal landscape.

Building a Compliant Breach Response Plan

A documented Data Breach Response Plan (DBRP) is not strictly mandatory, but the OAIC strongly expects one and will treat its absence as an aggravating factor.

Essential Plan Components

  1. Clear roles: Named response lead, legal, IT security, communications, executive sponsor.
  2. Escalation triggers: Criteria for what constitutes a suspected breach.
  3. Containment playbooks: Pre-approved technical actions (account lockdown, network isolation, token revocation).
  4. Assessment template: Structured form aligned with the "likely serious harm" test.
  5. Notification templates: Draft OAIC statement and individual communications.
  6. Post-incident review: Root cause analysis and lessons-learned register.

Reducing Breach Risk: Practical Controls

Prevention remains cheaper than notification. Recommended controls include:

  • Multi-factor authentication on every externally-facing account.
  • Encryption at rest and in transit for personal information.
  • Least-privilege access and quarterly access reviews.
  • Endpoint detection and response (EDR) across all devices.
  • Phishing-resistant authentication such as passkeys and hardware tokens.
  • Data minimisation — don't collect or retain what you don't need.
  • Vendor risk management — many notifiable breaches originate at third parties.

Simple link-handling practices matter too. If your marketing or support teams routinely share URLs that reveal customer identifiers or session tokens, consider using a privacy-first link management tool like Lunyb to shorten and sanitise outbound links without leaking data to third-party trackers. You can read more in our honest review of Lunyb.

Common Compliance Mistakes

1. Starting the Clock Too Late

The 30-day assessment window begins when the entity has reasonable grounds to suspect a breach — not when it is confirmed. Many organisations lose precious days by treating "suspect" as a higher bar than the Act requires.

2. Under-scoping Affected Individuals

Narrow definitions of "at risk" individuals often fail later legal scrutiny. When in doubt, notify more broadly.

3. Treating Notification as PR

Notification letters are a legal instrument. Overly reassuring language or missing required content can convert a bad day into a regulatory investigation.

4. Ignoring Overseas Obligations

A breach involving Australian customers may also trigger GDPR (for EU residents), the New Zealand Privacy Act, or sector-specific US rules. Map these in advance.

How the Scheme Compares Internationally

JurisdictionNotification DeadlineMax Corporate Penalty
Australia (NDB)As soon as practicable (30-day assessment)Greater of AUD $50M / 3x benefit / 30% turnover
EU (GDPR)72 hours to regulator€20M or 4% global turnover
UK (UK GDPR)72 hours to ICO£17.5M or 4% global turnover
New ZealandAs soon as practicableNZD $10,000 (criminal)
Singapore (PDPA)3 days to PDPCSGD $1M or 10% turnover

Australia's deadline is more flexible than Europe's 72-hour rule, but its penalties are now among the heaviest globally.

FAQ

Do I have to report every data breach to the OAIC?

No. Only "eligible data breaches" — those likely to result in serious harm that cannot be remedied — must be reported. Minor incidents (such as a misdirected internal email promptly recalled) typically do not trigger notification, though you should still document them.

How quickly must I notify after confirming an eligible breach?

The Privacy Act requires notification "as soon as practicable" after you are aware the breach is eligible. In practice, the OAIC expects this within days, not weeks. The 30-day window applies only to the assessment phase, not to notification itself.

Does the scheme apply to my small business?

If your annual turnover is under AUD $3 million you may be exempt — but exceptions apply if you handle health information, trade in personal information, are a credit reporting body, or contract to the Commonwealth. Reforms underway in 2026 are progressively narrowing the small business exemption.

What happens if I fail to notify?

Failure to comply with Part IIIC can constitute an interference with privacy under the Act, exposing the entity to OAIC investigation, enforceable undertakings, infringement notices, and civil penalty proceedings of up to AUD $50 million (or more under the turnover-based cap).

Do I need to notify if the stolen data was encrypted?

Strong, properly-implemented encryption can support an argument that serious harm is not "likely" — particularly if keys were not compromised. However, the analysis is fact-specific. Document your encryption standards, key management, and reasoning carefully before relying on this position.

Final Thoughts

The Australian Data Breach Notification Scheme has matured into a serious compliance regime with penalties that now match the scale of modern data risks. The entities that handle breaches best are those that prepare in peacetime: clear response plans, rehearsed playbooks, strong preventive controls, and a culture that treats personal information as a liability to be minimised rather than an asset to be hoarded.

When a breach does occur, move quickly, document everything, and treat notification as both a legal obligation and an opportunity to maintain trust with the people whose data you were privileged to hold.

Protect your links with Lunyb

Create secure, trackable short links and QR codes in seconds.

Get Started Free

Related Articles