Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

When a hosting incident becomes a notifiable data breach: who assesses, who notifies

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A hosting incident becomes a notifiable data breach only when three things are true: personal information held by an organisation was accessed, disclosed or lost without authorisation; that is likely to cause serious harm to at least one person; and remedial action has not removed that likelihood. When there is only a suspicion, the organisation that holds the information must assess it, and must take all reasonable steps to finish within 30 days.

If your provider also holds the data on its systems, both of you may be treated as holding it. The law then lets one of you do the assessing and notifying for both. It does not say which one. That is for you to settle in your contract before an incident, and it is the main point of this article. This is general information, not legal advice.

Why it matters

The scheme's clock runs from when your organisation becomes aware of grounds for suspicion. If the provider knows of a problem and you do not, your clock has not started, but your customers may already be at risk. If both of you assume the other will notify, neither may, and the OAIC's guide says that in that case all of the entities that hold the information may be found in breach.

Roles are also easier to agree calmly than during a crisis. The time to decide who investigates, who talks to the regulator and who writes to affected people is before the incident.

The three tests

The Office of the Australian Information Commissioner (OAIC) sets out the criteria for an eligible data breach on its Report a data breach page:

  1. There is unauthorised access to or disclosure of personal information held by an organisation or agency, or the information is lost in circumstances where unauthorised access or disclosure is likely to occur.
  2. This is likely to result in serious harm to any of the individuals to whom the information relates.
  3. The organisation has been unable to prevent that likely risk of serious harm with remedial action.

The statute is section 26WE of the Privacy Act 1988, which is expressed to be subject to the remedial-action exception in section 26WF. Two terms are worth knowing. The OAIC's guide says that likely to occur means the risk is "more probable than not (rather than possible)". It also says that serious harm is not defined in the Act, and may include serious physical, psychological, emotional, financial or reputational harm.

The third test matters in practice. If remedial action prevents serious harm, notification is not required. The OAIC guide says an organisation can, and should, take steps to reduce harm at any time, including during an assessment.

Not every security incident involves personal information. A server compromised for cryptocurrency mining that held no personal data may not meet the first test (our reading); whether it does depends on facts that an investigation has to establish.

Who the scheme covers

The OAIC guide says the scheme applies to entities with existing security obligations under the Privacy Act. That includes Australian Government agencies, and businesses and not-for-profits with an annual turnover of more than AU$3 million, as well as certain categories such as private sector health service providers, credit reporting bodies, credit providers, entities that trade in personal information and tax file number recipients. Smaller businesses outside those categories may not be covered by the scheme, though they may have other obligations. Check your own position with a legal adviser.

Assessment: the 30-day limit and what starts it

Section 26WH applies when an entity is aware of reasonable grounds to suspect an eligible data breach, but not yet aware of reasonable grounds to believe there has been one. The entity must carry out "a reasonable and expeditious assessment", and "take all reasonable steps to ensure that the assessment is completed within 30 days" after becoming aware.

The OAIC guide adds three points:

  • It expects entities to treat 30 days as a maximum, and to finish sooner where they can, because the risk of harm often grows with time.
  • Awareness is a factual question. If a person responsible for compliance, or personnel of appropriate seniority, know of information that suggests a suspected breach, an assessment should be done. An entity "should not unreasonably delay an assessment" by waiting until its CEO or board knows.
  • It suggests a three-stage assessment: initiate, investigate, evaluate. Entities may develop their own procedures, and the OAIC recommends documenting the process and outcome.

Our reading of what this means for hosted data: your awareness is what counts for your own clock, so the provider's duty to tell you quickly has to come from your contract, not from the scheme. That is why the contract wording below matters.

Notification: promptly, not at the end of 30 days

The 30 days is a limit on assessment, not a grace period for notification. Once an entity is aware of reasonable grounds to believe there has been an eligible data breach, it must prepare a statement and give a copy to the Commissioner "as soon as practicable" (section 26WK), and notify the affected individuals as soon as practicable after the statement is prepared (section 26WL(3)).

The OAIC says the notification to the OAIC and to individuals should include the organisation's name and contact details, a description of the breach, the kinds of information involved, and recommendations about the steps individuals should take. Notice to the OAIC is through its online form. The notice to individuals must include recommendations about what they should do.

Those four items are what your provider can help you with. Ask yourself what the provider would have to tell you for you to complete each one.

When your provider holds the data too

The OAIC guide explains that an entity holds personal information if it has possession or control of a record, which extends beyond physical possession. It gives the example of an entity that stores records with a cloud service provider: the provider has possession and can access the information, and the first entity has contractual rights to retain control, so "both entities hold the information". Whether a given arrangement amounts to joint holding depends on its circumstances.

Where information is jointly held:

  • An eligible breach of one entity is also an eligible breach of the other holders, and both have obligations.
  • If one entity has assessed the suspected breach, the others need not also assess it (section 26WJ).
  • Only one entity needs to notify the Commissioner and individuals at risk (section 26WM).
  • If none of them notify, all may be found in breach.

The OAIC is careful about who does what. Its guide says the scheme "does not prescribe which entity should conduct an assessment" or which should notify, so entities can tailor arrangements to their contracts. It suggests that the entity with the most direct relationship with the affected individuals is generally best placed to notify them. For a business hosting its customers' data, that is usually the business, not the host (our reading of the OAIC's suggestion).

The OAIC also says entities should establish clear procedures for complying when they enter service agreements, including obligations around communication of suspected breaches, processes for assessments, and "responsibility for containment, remediation, and notification".

One of the OAIC's worked examples shows the pattern: an email marketing provider detects that mailing lists were downloaded and notifies its customer, who investigates and assesses whether it must notify. The example assumes the provider is not itself an APP entity, which shows that the provider may not be covered by the scheme at all.

What to agree with your provider

Our recommendation, drawing on the OAIC's suggestions:

  1. Notification to you. The provider tells you, by a named route and within a stated time, when it suspects unauthorised access to systems holding your data. The scheme does not state this; the contract must.
  2. Facts you will need. Systems and data affected, time window, what is known about access or copying, the provider's containment steps and log availability.
  3. Who assesses and who notifies. A written default, with the customer as the person dealing with affected individuals unless agreed otherwise.
  4. Who speaks to the regulator. Agree who contacts the OAIC and when each party copies the other.
  5. Evidence and logs. What the provider preserves, for how long, and how you may ask for it.
  6. Cost and cooperation. Who pays for forensic work and customer notification, and how quickly the provider cooperates.

Questions to put to your provider

  • When you suspect unauthorised access to data we host, how and how fast do you tell us?
  • What information will you give us in the first 24 hours, and what only later?
  • Do you treat yourself as holding our personal information, and have you assessed your own obligations?
  • Who at your end works with our incident contact, and how do we reach them out of hours?
  • Will you preserve logs for the affected period, and for how long?

A worked example (illustrative)

The following is invented. A clinic hosts a booking system on a provider's server. On a Monday the provider notices that an administrator account has been used from an unfamiliar address. It tells the clinic's contact by phone the same day. The clinic's practice manager treats this as a suspected breach, starts an assessment that day and records the start date.

Within a week the provider's logs show that a database holding patient names, phone numbers and appointment reasons was copied. The clinic concludes that serious harm is likely for some patients. It prepares a statement, notifies the OAIC through the online form and writes to the patients concerned. Its contract had said the clinic would notify and the provider would supply the facts, so neither party was unsure who should act.

Risks and limits

  • The OAIC guide is being updated for a 2024 amendment; its web page and PDF carry different dates. Check the current text.
  • We checked the quoted sections against Compilation No. 104 (4 June 2026). The Act can be amended again; check the current compilation, and note that the OAIC says Division 5 of Part IIIC (ministerial declarations) commenced on 11 December 2024.
  • Other obligations may apply, including contracts, sector rules and insurance. We did not research them.
  • Whether a particular incident is an eligible data breach is a fact-specific legal judgement; this article does not make it.
  • This is general information, not legal advice.

Next step

Agree breach-notification contacts with your provider in writing: the names and out-of-hours numbers of who tells whom, the facts the provider will supply, and who assesses and notifies. If you are reviewing a hosted service, the Managed Services page is a starting point for that conversation; ask for the scope in writing.

Sources

  • Privacy Act 1988, Federal Register of Legislation, Compilation No. 104, compilation date 4 June 2026 (authorised version C2026C00227, registered 17 June 2026); sections 26WE, 26WF, 26WH, 26WJ, 26WK, 26WL and 26WM in Part IIIC, Division 2 and Division 3, read from the compilation PDF on 16 November 2026.
  • Section pages on AustLII, Commonwealth Consolidated Acts, for convenience: 26WE, 26WH, 26WJ, 26WK, 26WL, 26WM. Archive copies of these pages (captured 2024 to 2025) were compared with the compilation; the quoted wording matches.
  • Report a data breach, Office of the Australian Information Commissioner, archive capture 15 October 2026, date unavailable on the page.
  • About the Notifiable Data Breaches scheme, Office of the Australian Information Commissioner, archive capture 5 October 2026, date unavailable on the page.
  • Data breach preparation and response, Office of the Australian Information Commissioner, archive capture 7 November 2026; page says "This guide was updated in June 2024"; PDF footer says February 2024; the guide is read from the PDF.

All first accessed 15 November 2026; statute and OAIC pages re-read 16 November 2026.

Learning notes

  • A suspected breach triggers an assessment; a likely serious harm triggers notification.
  • The 30 days is for assessing, not for delaying notification.
  • A provider that holds your data may share your obligations, but the Act lets one party act for both.
  • The Act does not say who tells whom; your contract should.