# Data breach

URL: https://tnb-tech.com/en/glossary/data-breach/

## What is a data breach?

A data breach is any incident in which personal data becomes available to an outsider, is altered, destroyed or lost. The law calls it a personal data breach, and it need not be an attack: an email sent to the wrong recipient, an open folder on a server or a lost phone all count. Where the incident is likely to put people at risk, the data protection authority has to be told within 72 hours.

**Example**

A shop finds that an old plugin was used to download a file with 9,000 customer records: name, email, phone, delivery address and order history. No readable passwords, no card data, because none is stored. The clock starts when the company becomes aware, not when the break-in happened. In order:

- Stop the leak: remove the plugin, replace keys and passwords, and keep the server logs, because without them nobody can say what was taken.

- Establish what left, whose data it was and from when.

- If people are likely to be at risk, notify the data protection authority within 72 hours; where facts are still missing, file and complete the notification afterwards.

- Where the risk is high, tell the customers too, in plain language: what leaked, what could happen, what to do now.

- Record the incident in your internal breach register, even when no notification is required.

If an outside firm maintains the site, it processes the data on your behalf and has to tell you without delay, because your 72 hours start with their phone call.

**Why it matters for a business**

A breach rarely looks dramatic. Usually it is one file, quietly downloaded, followed by three days of nobody being sure who does what, which are precisely the days the deadline is running. The cost sits in the response: a prepared list of names, phone numbers and access to the logs turns a crisis into a procedure. Businesses in scope of NIS2 work to separate, shorter deadlines, with an early warning in the first 24 hours. Data you never collect, and data you do not keep longer than you need, cannot leak.

**What to ask**

- Who hears about an incident first, and which number do they call on a Saturday evening?

- Are there server logs, how far back do they go, and are they enough to say what was taken?

- What does the contract with your website supplier say about how fast they must tell you?

- Which personal data is collected at all, where does it sit, and for how long?

- When was a restore from backup last tested?

Before an incident, the useful thing is an outside look: website security testing shows which door opens while that is still your own business rather than everyone’s news.

- Services: [Cybersecurity](https://tnb-tech.com/en/services/cybersecurity/)
- Glossary: https://tnb-tech.com/en/glossary/
