Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Data Breach?

A data breach is a security incident in which data is accessed, disclosed, altered, lost, or destroyed without authorisation. Under UK GDPR, many must be reported to the ICO within 72 hours.

Home / Blog / Cybersecurity Terms / What Is a Data Breach?
17 November 2026

What Is a Data Breach?

What Is a Data Breach?

A data breach is a security incident in which information is accessed, disclosed, altered, lost, or destroyed without authorisation. Under UK GDPR, a personal data breach is defined broadly enough to cover a ransomware attack that makes records unavailable, an email sent to the wrong recipient, and a stolen laptop alike—not just hackers copying a database.

Three Kinds of Breach

The ICO, following European guidance, groups personal data breaches into three categories, and one incident can fall into more than one:

How Breaches Happen

Technical attacks make the headlines, but the causes are varied. Common routes include phishing that captures credentials, exploitation of unpatched internet-facing systems, reused passwords, compromised suppliers, misconfigured cloud services, malicious insiders, and plain human error. The ICO’s own data security incident trends consistently show that misdirected email and post account for a large share of reported incidents.

Two UK cases illustrate the range. In 2018, attackers altered a script on British Airways’ website and skimmed payment card details from customers making bookings; the ICO fined the airline £20 million in October 2020. In the same month, Marriott International was fined £18.4 million after a compromise of the Starwood guest reservation database that began in 2014, two years before Marriott acquired Starwood, and went undetected until 2018.

What UK GDPR Requires

ObligationWhen it appliesDeadline
Report to the ICO (Article 33)Unless the breach is unlikely to result in a risk to individuals’ rights and freedomsWithin 72 hours of becoming aware
Tell affected individuals (Article 34)When the breach is likely to result in a high risk to themWithout undue delay
Record the breach internally (Article 33(5))Every personal data breach, reportable or notOngoing

The 72-hour clock starts when you have a reasonable degree of certainty that a breach has occurred, not when the investigation ends. You can report in phases if facts are still emerging. Failing to notify can itself lead to a fine of up to £8.7 million or 2% of global annual turnover, while the higher tier for the most serious infringements reaches £17.5 million or 4%.

Other regimes may run in parallel. Operators of essential services and relevant digital service providers must report significant incidents under the NIS Regulations, financial entities in the EU follow DORA’s major ICT incident reporting timelines, telecoms and internet service providers have a 24-hour duty under PECR, and card data breaches trigger PCI DSS obligations to your acquirer and the card brands.

The First Hours of a Breach

  1. Contain without destroying evidence. Isolate affected systems, disable compromised accounts, and block known malicious infrastructure, but avoid wiping machines before forensic images are taken.
  2. Establish facts. What data, how many people, what categories (special category data raises the risk), and whether the data was actually accessed or exfiltrated.
  3. Assess risk. Consider the likely consequences for individuals: fraud, identity theft, discrimination, distress, or physical harm.
  4. Decide and notify. Involve your data protection officer and legal advisers, use the ICO’s self-assessment tool if helpful, and report within the deadline.
  5. Communicate clearly. Tell individuals what happened, what you are doing, and what they should do, such as changing passwords or watching for fraud.
  6. Learn and fix. Address the root cause, not just the symptom, and document decisions for the ICO and your board.

Reducing the Likelihood and the Impact

Strong identity controls, timely patching, encryption at rest and in transit, network segmentation, centralised logging, and data loss prevention all reduce either the chance of a breach or how much is exposed when one happens. Minimising the personal data you hold is just as effective: data you never kept cannot be leaked. Above all, rehearse the response so the first 72 hours are spent executing a plan rather than writing one. If you need help now, our incident response services team can investigate, contain, and support your reporting decisions.

FAQ – Frequently Asked Questions

Do I Have to Report Every Data Breach to the ICO?

No. You must report a personal data breach to the ICO within 72 hours unless it is unlikely to result in a risk to individuals’ rights and freedoms. A lost but fully encrypted laptop might not need reporting, while exposed health records almost certainly would. Whatever you decide, you must record every personal data breach internally, including your reasoning, so you can justify it later.

What Happens If We Miss the 72-Hour Deadline?

Report anyway, as soon as possible, and explain the reasons for the delay, which UK GDPR explicitly allows. Late reporting can count against you if the ICO considers the delay unjustified, and failure to notify is itself an infringement that can attract a fine. In practice, the ICO looks far more favourably on organisations that engage early and openly.

Is a Ransomware Attack Always a Data Breach?

If the affected systems held personal data, ransomware is almost always a personal data breach, because encryption makes the data unavailable even when nothing is stolen. Most current ransomware groups also exfiltrate data before encrypting it. You will need to assess the risk to individuals, decide on ICO notification within 72 hours, and consider whether affected people must be told.

Who Is Responsible If a Supplier Causes the Breach?

If the supplier processes personal data on your behalf, you remain the controller and are responsible for reporting the breach. The processor must tell you without undue delay after becoming aware of it, which your contract should require explicitly. You should also have assessed the supplier’s security before engaging it, as the ICO will ask what due diligence you carried out.

Related Terms

You May Be Interested In These

How the WannaCry Attack Worked

Cybersecurity Terms

17 November 2026

How the WannaCry Attack Worked

Read More
What Is Loyalty Programme Abuse?

Cybersecurity Terms

17 November 2026

What Is Loyalty Programme Abuse?

Read More
What Is a Brute Force Attack?

Cybersecurity Terms

17 November 2026

What Is a Brute Force Attack?

Read More