🕑 Estimated reading time: 6 minutes | Last updated: May 14, 2024
Most modern data protection laws require organisations to report serious data breaches quickly. Under the EU and UK GDPR and the Nigeria Data Protection Act, the regulator must be notified within 72 hours of becoming aware of a reportable breach, and affected individuals must be told without undue delay if the risk is high. US public companies must disclose material cybersecurity incidents within four business days of determining materiality, every US state has its own breach notification law, and India’s CERT-In requires certain incidents to be reported within six hours.

When a company discovers a breach, a stopwatch starts. In many countries it has just 72 hours to tell the regulator, and sometimes far less. Knowing those deadlines before something goes wrong is half the battle.
When a company discovers that hackers have accessed its customer database, the clock starts ticking. Under many laws, the organisation has only days, sometimes hours, to tell regulators and the people affected. Missing those deadlines can turn an already damaging incident into a regulatory enforcement action.
Below, we explain what counts as a reportable breach, the main deadlines around the world, and how to prepare so your organisation can meet them.
Table of Contents
What Counts as a Data Breach?
Under the GDPR and laws modelled on it, a personal data breach is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. That definition is broader than many people expect. It includes:
- a ransomware attack that encrypts customer records, even if nothing is stolen;
- an email containing personal data sent to the wrong recipient;
- a lost laptop or USB drive holding unencrypted data;
- a misconfigured cloud storage bucket left publicly accessible;
- an employee viewing records they have no business reason to access.
Not every breach must be reported. Most laws require notification when the breach is likely to result in a risk to individuals’ rights, for example identity theft, financial loss, discrimination or reputational damage. But organisations should record every breach internally, including the reasons for deciding not to report.
EU and UK GDPR: 72 Hours
The controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the breach, unless it is unlikely to result in a risk to individuals. If the notification is late, the reasons for the delay must be explained. Information can be provided in phases if the investigation is ongoing.
Where the breach is likely to result in a high risk, affected individuals must also be informed without undue delay, in clear language, describing the likely consequences and the steps they can take to protect themselves. Processors must notify their controller without undue delay.
Nigeria: 72 Hours to the NDPC
The Nigeria Data Protection Act 2023 follows a similar model. Controllers must notify the Nigeria Data Protection Commission within 72 hours of becoming aware of a breach likely to result in a risk to the rights and freedoms of individuals, and must inform affected data subjects without undue delay if the breach is likely to result in a high risk. Separately, the Cybercrimes Act expects organisations to share information about cyber incidents with the national CERT, and sector regulators such as the Central Bank of Nigeria have their own incident reporting expectations for financial institutions.
Elsewhere in Africa
Kenya’s Data Protection Act 2019 requires notification to the Data Commissioner within 72 hours and to affected individuals within a reasonable time. South Africa’s Protection of Personal Information Act (POPIA) requires notification to the Information Regulator and to data subjects as soon as reasonably possible after discovering a compromise. Many other African data protection laws contain similar provisions, so multinational businesses should map the rules in every country where they operate.
United States: A Patchwork of Rules
The US has no single federal breach notification law for all businesses. Instead:
- State laws: All 50 states have data breach notification statutes. They differ in what data they cover, how quickly notice must be given (some set fixed deadlines such as 30, 45 or 60 days) and whether the state attorney general must also be notified.
- Public companies: Under rules adopted by the Securities and Exchange Commission in 2023, listed companies must disclose a material cybersecurity incident on Form 8-K within four business days after determining that the incident is material. The requirement took effect in December 2023 for most companies.
- Healthcare: The HIPAA Breach Notification Rule requires covered entities to notify affected individuals without unreasonable delay and no later than 60 days after discovery, and to notify the Department of Health and Human Services. Breaches affecting 500 or more residents of a state must also be reported to prominent media outlets.
- Critical infrastructure: The Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) will require covered entities to report substantial cyber incidents to CISA within 72 hours and ransom payments within 24 hours once final rules are in place. CISA published its proposed rule in April 2024.
India: Six Hours
Directions issued by India’s CERT-In in 2022 require service providers, intermediaries, data centres and government bodies to report specified types of cyber incidents within six hours of noticing them, one of the tightest deadlines anywhere.
What a Notification Usually Must Include
- the nature of the breach, including categories and approximate numbers of people and records affected;
- the name and contact details of the data protection officer or another contact point;
- the likely consequences of the breach;
- the measures taken or proposed to address the breach and mitigate its effects.
How to Prepare Before a Breach Happens
- Write an incident response plan that names who decides whether a breach is reportable and who contacts regulators.
- Map your obligations by country, sector and contract. Customers and partners may require notification even faster than the law.
- Prepare templates for regulator and customer notices so you are not drafting from scratch under pressure.
- Keep a breach log of every incident and decision.
- Run tabletop exercises so that legal, IT, communications and leadership know their roles.
- Line up external help, such as forensic investigators and specialist lawyers, in advance.
Prepare your notification process before a breach
Breach notification laws exist so that regulators can respond to threats and individuals can protect themselves quickly. The deadlines are short because the risks are real. Organisations that plan ahead, know which rules apply to them and practise their response will find it far easier to act lawfully and maintain trust when something goes wrong.
Frequently Asked Questions
When does the 72-hour clock start?
When the organisation becomes “aware” of the breach, meaning it has a reasonable degree of certainty that a security incident has compromised personal data. A short initial investigation is allowed, but it should not be used to delay notification.
Do I have to report a breach if the data was encrypted?
Often not to individuals, and sometimes not to the regulator, if the data was strongly encrypted and the key was not compromised, because the risk to individuals is low. Record your reasoning either way.
What happens if I report late?
Regulators can impose fines for failing to notify on time, separate from any penalty for the breach itself, and late notification can damage customer trust.
Should I notify customers before the regulator?
Follow the legal sequence and deadlines that apply to you. In urgent cases you may need to warn customers quickly so they can protect themselves; your incident plan should address this.