Breach notices
Data breach notification laws compared
Short answer
- US public companies
- Form 8-K Item 1.05, four business days after the materiality decision 4
- US health data (HIPAA)
- Individuals told no later than 60 days after discovery 5
- Australia
- Individuals and the OAIC told when serious harm is likely 8
- Canada (PIPEDA)
- Report when there is a real risk of significant harm, keep records 24 months 9
- India (CERT-In)
- Report listed cyber incidents within 6 hours of noticing them 10
Two separate duties: tell the regulator, tell the people affected
Most breach laws split the duty in two. One notice goes to a regulator. A second goes to the people whose data was exposed. The tests and deadlines for each are often different.
Under the UK GDPR, Article 33 covers notice to the regulator. The controller must act without undue delay and, where feasible, within 72 hours of becoming aware of the breach 2. No notice is needed where the breach is unlikely to result in a risk to the rights and freedoms of natural persons 2. A late notice must give reasons for the delay 2.
Article 34 covers notice to individuals. It applies when the breach is likely to result in a high risk to the rights and freedoms of natural persons 3. The European Commission gives encryption as an example of protection that can make the risk unlikely to materialise 1.
Comparison table
| Jurisdiction | Rule | Notice to regulator | Notice to individuals |
|---|---|---|---|
| European Union | GDPR Articles 33 and 34 1 | Within 72 hours of becoming aware 1 | When the risk is high 1 |
| United Kingdom | UK GDPR Articles 33 and 34 2 | Without undue delay and where feasible within 72 hours 2 | When the breach is likely to result in a high risk 3 |
| United States, listed companies | Form 8-K Item 1.05 4 | SEC filing four business days after the materiality decision 4 | Not part of this rule 4 |
| United States, health data | HIPAA Breach Notification Rule 5 | HHS Secretary within 60 days for 500 or more people, yearly for fewer 5 | Within 60 days of discovery 5 |
| California | Civil Code 1798.82 6 | Sample notice to the Attorney General when more than 500 residents are told 6 | Residents whose unencrypted personal information was acquired 6 |
| Australia | Notifiable Data Breaches scheme 8 | OAIC, through its online form 8 | When serious harm is likely 8 |
| Canada | PIPEDA 9 | OPC, real risk of significant harm test 9 | As soon as feasible 9 |
| India | CERT-In directions of 28 April 2022 10 | CERT-In within 6 hours 10 | Not set by these directions 10 |
United States: federal and state layers
The United States has no single breach law. The FTC says all states, the District of Columbia, Puerto Rico and the Virgin Islands have laws that require notice of breaches involving personal information 7. Firms covered by the FTC Health Breach Notification Rule must notify the FTC and, in some cases, the media 7.
California law requires a business or state agency to notify any California resident whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorised person 6. A business that notifies more than 500 California residents about one breach must send a single sample copy of the notice to the Attorney General 6.
For health data, HIPAA covered entities must tell individuals without unreasonable delay and no later than 60 days after discovery 5. A breach affecting more than 500 residents of a state needs notice to the media as well 5. Business associates must tell the covered entity no later than 60 days from discovery 5.
Listed companies have a separate securities duty. The SEC adopted Item 1.05 of Form 8-K on 26 July 2023 4. It covers any cybersecurity incident the company decides is material, and the filing must describe the nature, scope and timing of the incident and its material impact 4. The filing may be delayed if the US Attorney General decides disclosure would pose a substantial risk to national security or public safety 4.
Australia, Canada and India
In Australia, any organisation or agency covered by the Privacy Act 1988 must notify affected individuals and the OAIC when a breach is likely to result in serious harm 8. The notice to individuals must include recommendations about the steps they should take 8.
In Canada, PIPEDA requires organisations to report breaches of security safeguards that create a real risk of significant harm to the Privacy Commissioner 9. The number of people affected does not change the duty 9. Organisations must keep a record of every breach for 24 months, reportable or not 9. The OPC does not prosecute or fine. It can refer possible offences to the Attorney General of Canada 9.
In India, CERT-In directions issued on 28 April 2022 require listed cyber incidents to be reported within 6 hours of noticing them 10. The same directions require logs to be kept for a rolling period of 180 days within Indian jurisdiction 10.
Processors and service providers
A processor that handles data for someone else usually has to tell that party first. Under Article 33(2) of the UK GDPR, the processor must notify the controller without undue delay after becoming aware of a breach 2. The FTC tells businesses that store data for other businesses to notify them of a breach 7. The controller must document every breach, with its facts, effects and the remedial action taken 2.
Common questions
What is the GDPR breach notification deadline?
The controller must notify the supervisory authority at the latest within 72 hours of becoming aware of the breach 1.
Does every breach have to be reported to individuals?
No. Under Article 34 of the UK GDPR, notice to individuals is needed when a breach is likely to result in a high risk to their rights and freedoms 3.
When is an SEC Form 8-K Item 1.05 due?
Four business days, as a general rule, after the company determines that a cybersecurity incident is material 4.
How long do HIPAA covered entities have to notify?
No later than 60 days after discovery of the breach for notice to individuals 5.
Where do Australian organisations report a breach?
To the OAIC, using its online Notifiable Data Breach form 8.
Rules and charges change. Check the official source linked on this page before you pay or travel. Spotted an error? Email hello@noticeofrecord.com.
Sources
- European Commission: data breach question and answer page, rules for business and organisations
- legislation.gov.uk: United Kingdom General Data Protection Regulation, Article 33
- legislation.gov.uk: United Kingdom General Data Protection Regulation, Article 34
- SEC: SEC Adopts Rules on Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure by Public Companies (26 July 2023)
- HHS: Breach Notification Rule
- State of California Department of Justice: Data Security Breach Reporting
- FTC: Data Breach Response: A Guide for Business
- OAIC: About the Notifiable Data Breaches scheme
- Office of the Privacy Commissioner of Canada: What you need to know about mandatory reporting of breaches of security safeguards (29 October 2018)
- CERT-In: Directions under sub-section (6) of section 70B of the Information Technology Act, 2000 (28 April 2022)
Related
- How to check whether a notice was given
Where to look up official notices: state breach lists, the HHS breach portal, SEC EDGAR, FDA warning letters, FCA notices, WARN reports and recall lists.
- What a formal notice is
What makes a notice formal: who gives it, who receives it, the deadline and the form. Breach, recall, regulatory, layoff and court notices compared.
- Product recall notices compared
How recall notices work at the US CPSC, FDA and NHTSA, UK OPSS, EU Safety Gate, Australia's ACCC and Health Canada, and where each list is published.