Notifiable data breaches: retailer reporting

Assess a notifiable data breach using the Australian scheme. Separate containment, harm assessment, remedial action and required customer reporting.

A notifiable data breach is a breach that a covered entity must report because serious harm is likely and remedial action has not prevented that risk. Under Australia’s Notifiable Data Breaches (NDB) scheme, the decision turns on the information exposed and the likely consequences for people.

Start containment immediately. Assess a suspected eligible breach promptly, and notify the regulator and affected individuals when the legal threshold is met, unless an exception applies. An assessment period is not permission to leave a known eligible breach unreported.

When the notification scheme applies

Check that your retail entity and the affected information fall within the scheme before making the notification decision. Most businesses with annual turnover above $3 million are covered by the Privacy Act. Some smaller businesses are covered too, including certain health service providers and businesses trading in personal information. Use the OAIC’s small-business coverage questions to identify the applicable category.

Coverage can be limited to particular information. For example, a business covered only as a tax file number recipient has NDB duties for that information. That status alone does not put every customer record in scope. The OAIC’s scheme guidance explains these boundaries. The broader Privacy Act Australia guide covers the general framework.

An eligible breach involves unauthorised access or disclosure, or lost information where unauthorised access or disclosure is likely. Serious harm must be likely for at least one affected individual. Successful remedial action can remove the notification requirement. The OAIC’s reporting criteria set out this test.

A blocked login attempt is a security event to investigate. A conversation file exposed to an unauthorised recipient requires a different assessment. Neither the number of leaked records nor the label “cyber incident” settles whether notification is required.

Contain the incident and establish the facts

Stop continuing exposure while preserving the records needed to understand what happened. The OAIC’s response procedure covers containment alongside assessment, notification and review. These activities can overlap.

Use the existing response team and assign a decision-maker with authority to obtain evidence and authorise communications. Bring in technical incident responders and privacy or legal advisers for their respective decisions. Keep a restricted incident record with the following steps.

  1. Identify the exposed location and stop further access. Revoke an exposed export link or disable a compromised account through the authorised incident process.
  2. Preserve relevant access logs, sharing settings and file versions before routine cleanup overwrites them. Record who collected each item, its source and its time zone.
  3. Identify the information involved. Read a controlled sample for customer identifiers, conversation text, order references and attachments instead of trusting the export’s filename.
  4. Establish the sequence. Record when the file became accessible, when the retailer learned of it, each containment action and any evidence of downloads or forwarding.
  5. Name the people or groups affected. Include staff or other people named in conversations where relevant, and separate confirmed exposure from the possible wider scope.

Ask the AI, hosting or support provider for the evidence it controls. Specify the affected account, period and records, using a secure incident channel. A provider can revoke access or investigate its service. The retailer still needs evidence for its own legal decision.

Where entities jointly hold the information, they can coordinate one assessment and notification. Record which entity will act and obtain confirmation that it does so. A contract assigning notification to the provider does not itself demonstrate compliance. The OAIC generally favours notification by the entity with the most direct relationship with affected people.

Assess harm and document the decision

Assess whether a properly informed reasonable person in the entity’s position would conclude that serious harm is likely. The OAIC interprets “likely” as more probable than not. Serious harm can be financial, physical, psychological, emotional or reputational. Its quick reference guide explains the threshold and remedial action.

Examine information type and sensitivity, security protections and whether they can be defeated. Consider who obtained the information, their ability to misuse it and the nature of the harm. Look at combinations of records and known vulnerabilities among affected people. These considerations follow section 26WG of the Privacy Act.

For a suspected eligible breach, carry out a reasonable and expeditious assessment. Take all reasonable steps to complete it within 30 calendar days after becoming aware of the grounds for suspicion. Record that trigger separately from the technical start of the incident. If completion takes longer, document the steps taken, reasons for delay and why the assessment remains reasonable and expeditious.

Once reasonable grounds to believe an eligible breach has occurred exist, act on notification promptly. Do not wait for the remaining assessment period. Sections 26WH, 26WK and 26WL distinguish assessment from notification.

A fictional conversation-export assessment

Suppose a retailer’s support team discovers a shared export containing customer emails, order references and free-text conversations. An attachment includes health information volunteered during a product enquiry. The link was accessible outside the authorised team for several hours. This is a fictional example, with no conclusion about a real retailer or provider.

The team revokes the link and preserves its access history. Revocation stops new access through that link. It does not establish whether someone retained a downloaded copy.

The assessor investigates the recipients and the attachment’s contents. An unfamiliar download would require examination of what was retrieved and how it could harm those people. A known unintended recipient’s prompt deletion, supported by credible evidence of no copying or forwarding, presents a different remedial case.

For unauthorised access or disclosure, the remedial exception depends on action before serious harm occurs and its effect on the likelihood of serious harm. For lost information, preventing unauthorised access or disclosure can satisfy the exception. If protection succeeds for only some people, identify the remaining group at risk.

Record the facts supporting each conclusion. Label missing download evidence as unknown, assign an owner to obtain it and set a decision checkpoint. “No customer has complained” is not evidence that a downloaded file cannot cause serious harm.

Notify through the right channels

Prepare the required statement and notify the OAIC and individuals as soon as practicable once the notification duty arises. The statement must identify the entity and its contact details, describe the breach, identify the kinds of information involved and recommend protective steps.

Use the OAIC’s Notifiable Data Breach form for the regulator notification. Its read-only training form helps the response team prepare the requested details. Attach the notification template for affected individuals as the OAIC instructs. Submitting this form does not deliver the customer messages.

Choose the permitted individual-notification option that is practicable. Notify everyone whose information is involved, or identify and notify only those at risk of serious harm. Where neither direct option is practicable, publish the statement on your website and take reasonable steps to publicise its contents. Simply placing a notice on an obscure page is insufficient.

Before sending, complete a communications check.

  1. Reconcile the recipient group against the assessment. Confirm that shared accounts or outdated contact details will not expose the incident to another person.
  2. Describe the confirmed facts in plain English. Explain uncertainty that changes the person’s protective actions, without promising that all copies have been recovered.
  3. Match advice to the exposed information. Account-security advice needs a secure recovery route. An exposed address or sensitive conversation can require a different response.
  4. Test the contact route and give support staff the approved information. Send separate messages or use a delivery method that conceals the recipient list.
  5. Keep the submitted statement, delivery evidence and publication record. Correct material errors through the regulator’s contact process and the affected individuals’ communication channel.

Coordinate any other applicable reporting duties separately. A police report, provider ticket or cybercrime report does not replace NDB notification.

Review the incident and improve the controls

Close the incident with a decision record that explains what happened, the notification outcome and the evidence supporting it. Keep this record even where the assessment concludes that NDB notification is not required.

Assign an owner and completion evidence to each corrective action. For the fictional export, that could mean restricting export permissions and proving that an unauthorised account cannot retrieve a new sample file. A policy revision alone would not demonstrate that access changed.

Review provider escalation arrangements, shared-file expiry and log availability. Retain incident evidence securely for the applicable legal and operational needs, then apply the appropriate disposal process. Avoid retaining duplicate customer exports merely because the investigation created them.

Update the data breach response plan with the responsibilities and escalation failures the incident exposed. That preparation document supports the next response. The completed assessment records why this incident required notification, or why it did not, and who accepted the decision.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup