Skip to content
Simoneiasimoneia.it
Guide · ART-003

Data breach: what to do in the first 72 hours

What to do when you discover a personal data breach: contain it, assess the risk, decide whether to notify the Italian DPA within 72 hours, inform affected people and document everything.

11/15/2026 · 6 min read

You have found that someone had access to data they should not have seen: an exposed database, a compromised account, a customer file in the wrong hands. The GDPR calls this a personal data breach and sets precise rules, with a deadline that matters: 72 hours.

This article is informational and does not replace advice from a lawyer or your DPO: for decisions about your specific case, involve them right away.

When the 72 hours start

The clock starts when you become aware of the breach, not when it happened. If you cannot notify within 72 hours, you must still notify as soon as possible and explain the delay. In short: every hour the problem is ignored or not escalated internally is lost time.

The first hours: what to do, in order

1. Contain it. Stop the exposure: revoke compromised access, change the credentials involved, make private what was public, isolate the system if needed. Before shutting down or deleting anything, preserve the evidence (logs, copies): you will need it to understand what happened.

2. Alert internally. Whoever decides in the company, the IT lead or technical supplier, and the DPO if you have one. Write down the date and time you became aware of the breach.

3. Work out what happened. Which data? How many people? For how long was it accessible? Did anyone actually download it? Partial answers are useful too: write down what you know and what you do not know yet.

4. Assess the risk to people. Contact details are different from ID documents, payment data, health data or passwords. The risk depends on what the data is, how easily it can be used to harm people and how many individuals are involved.

Notify the authority or not?

The general rule is that the breach must be notified to the data protection authority (in Italy, the Garante per la protezione dei dati personali), unless it is unlikely to result in a risk to people's rights and freedoms. Notification is done through the online service the authority provides.

If the risk is high, besides the authority you must also inform the affected people, in clear language: what happened, which data, possible consequences, what they can do to protect themselves (for example change passwords) and who to contact.

If you are unsure which category your case falls into, that is exactly the moment to talk to a professional: the assessment must be made, and justified in writing, even when you conclude that notification is not needed.

Always document

The GDPR requires keeping a register of breaches, including those not notified: what happened, effects, measures taken. You will need it for inspections and, above all, to avoid repeating the same mistake.

After the emergency

  • Find the real cause (not just the symptom) and close it.
  • Verify the problem is truly solved with an independent check.
  • Update procedures and training.
  • Consider having a security test done before the next incident.

Prevention is better

Many SMB data breaches stem from visible, fixable problems: public storage, unprotected panels, weak credentials. A free check is a first step to see what is already exposed; going deeper takes a test under a mandate.

If you have just discovered an incident and want quick technical input, write to us: we will tell you honestly what we can do and what should be handled with a lawyer. For an example of an assessment on a real product, see the CMO OS case.

→ Related case: CMO OS platform security assessment