GUIDE · GDPR

GDPR data breach: what to do in the first 72 hours

This guide tells you what to do when a personal data breach occurs: how to contain it, how to assess the risk to individuals, when to notify the authority and the data subjects, and which evidence to keep. It also maps the topics to explore, so you can prepare before an incident happens.

Updated october 2026
10 min read
Altovar Technical Editorial Team

1. What a personal data breach is

A personal data breach, commonly called a data breach, is a security incident that results in the destruction, loss, alteration, unauthorised disclosure of or unauthorised access to personal data. It does not take a sophisticated attack. An email sent to the wrong recipient, an unencrypted laptop that is stolen, a paper archive left unattended or an account compromised through a weak password are enough.

The starting point is recognising that a security incident can also be a data breach, and that management must start immediately, even when you do not yet know everything. Many companies waste time establishing whether the problem is really serious before acting. The Regulation requires every breach to be documented, even when in the end it does not need to be reported to anyone. For this reason, the first action is always to record what happened.

2. Who needs to prepare, and why

Every company that processes personal data can suffer a breach, so every company needs a process, regardless of size. The obligations fall on the controller, meaning the company. A supplier that processes data on your behalf has in turn a duty to alert you without undue delay. For this reason the contract with suppliers must provide timelines, channels and responsibilities for reporting an incident.

If your company also falls within the scope of the NIS2 Directive, transposed in Italy by Legislative Decree 138/2024, an additional obligation applies: an initial report of significant incidents within 24 hours and a more complete notification within 72 hours. Check with an adviser whether and how this applies to you, because the two reports have different recipients and content and do not replace one another.

3. The first hours: contain and document

In the first hours the aim is to limit the damage and fix the facts. This is not the time to look for culprits or to write press releases. Whoever discovers the incident must report it immediately to a predefined internal contact, and the contact must open a register with the date and time of discovery, a description of what is known and what is not yet known. This register is the first document you will be asked for.

The second aim is containment: isolate the compromised system, revoke suspicious credentials, suspend automated emails if they are involved, without deleting traces. Deleting logs to tidy up an incident is one of the most serious mistakes, because it makes it impossible to reconstruct what happened and why. Follow the sequence below and ask the IT lead to note every action.

  1. Report the incident immediately to the designated internal contact, even if the information is partial.
  2. Open the incident register with the date, time of discovery and the name of the person who detected it.
  3. Isolate the affected systems without switching them off, if technical analysis requires their state to be preserved.
  4. Revoke suspicious credentials and replace any keys or passwords that may have been exposed.
  5. Preserve logs and evidence without altering them.
  6. Inform the IT provider and, if involved, the provider of the affected service.

4. Assessing the risk to individuals

Not every breach must be notified. The rule is to assess the risk to the rights and freedoms of individuals: could the breach cause physical, material or non-material damage? A mailing list of newsletter addresses published by mistake has a different impact from a stolen archive of medical reports. The assessment must be made case by case, with written criteria and the date on which it was completed.

The factors to consider are the nature of the data, the number of people involved, how easily those who accessed the data can identify them, the severity of the possible consequences and whether the data was protected, for example by effective encryption. Document the assessment and its reasons. If doubt remains, consult an adviser before deciding: a decision not to notify must be justified in writing.

5. Notifying the Garante: what is needed and when

Where the breach presents a risk to individuals, the controller must notify the supervisory authority, which in Italy is the Garante per la protezione dei dati personali (the Garante), without undue delay and, where feasible, within 72 hours of becoming aware of it. These hours run from the moment you have awareness of the incident, not from the end of the investigation. If the notification arrives after the deadline, the reason for the delay must be explained in writing.

The notification must describe the nature of the breach, the categories and approximate number of individuals and data records involved, the likely consequences and the measures taken or planned. It is not necessary to know everything: the communication may be made in phases, with information updated later. The template and the transmission methods must be checked on the authority's website, and drafting it is a step to carry out with an adviser.

6. Communicating with the individuals concerned

Where the breach is likely to result in a high risk to individuals, the controller must also inform the data subjects without undue delay. The communication must use clear language and explain what happened, which consequences are possible and which measures the person can take, for example changing a password or being alert to suspicious messages. It must not be written in technical terms that obscure the problem.

There are cases where direct communication is not necessary, for example where the data was effectively encrypted or where subsequent measures have significantly reduced the risk. Even in this case the decision must be documented. A poorly written communication can make the situation worse than the incident itself: have it reviewed by someone with expertise in the subject before sending it.

7. The evidence to keep

In the event of an inspection, the Garante or a customer will ask to see how you handled the incident. The Regulation requires every breach to be documented, with the facts, the effects and the measures adopted. This register of breaches is different from the notifications sent: it also contains incidents you did not notify, with the reasons for the decision taken at the time. Each entry must be dated and signed by whoever writes it.

Keep the register, the technical evidence, the risk assessment, copies of notifications and communications, and the minutes of decisions. Store them in a protected place separate from the systems involved, because they may not be accessible precisely during the incident. A complete, dated file is the most useful proof that you acted methodically. Anyone who accesses it must be known and limited to the minimum necessary.

8. The preventive plan: roles, contacts and suppliers

Managing an incident has to be prepared in advance. The plan must say who does what: who coordinates, who decides on notification, who speaks to customers and staff, who calls the IT provider and who is reachable out of hours. A plan that exists only in a folder, without up-to-date names and contacts, is of no use when it is really needed. Each role must also have a deputy, because incidents do not happen during office hours.

Check that the supplier contracts require the supplier to report an incident to you without delay, through a known channel that is always reachable. A plan whose suppliers do not know they must respond is an incomplete plan, and the discovery of this gap almost always happens during the incident. Also ask who, on the supplier's side, responds outside working hours and through which channel.

RoleMain taskWhat to prepare in advance
Internal contactOpens the register and coordinates the first hoursName, reachable contact details and a deputy
IT leadContains the incident and collects evidenceList of systems, available logs, emergency access
Privacy adviserAssesses the risk and drafts the notificationSupport contract and templates already prepared
Communications leadManages the message to customers and the publicApproved drafts, to avoid improvisation
SuppliersSupport recovery and report incidents affecting themReporting clauses in the contracts

9. How to start

This week, write a page with three things: the name of the internal contact and their deputy, the channel through which the IT supplier can be contacted out of hours, and the place where the breach register is kept, even if it is only a shared and protected spreadsheet. These are the basics without which the first hours are lost looking for who should act.

Then schedule a simulation with the team: a fake incident, for example an email sent to the wrong recipient. Observe how long the report takes to reach the contact and which steps are missing. The simulation reveals the gaps in the plan far better than any document, and gives you the starting point to work from with the adviser. Repeat the exercise each time key people or suppliers change, because the plan ages quickly.

Frequently Asked Questions

Do I have to notify every breach to the Garante?

No, not every breach must be notified. Notification is required when the incident presents a risk to the rights and freedoms of individuals. All breaches, however, must be recorded together with the reasons for the decision taken. If you have doubts about the risk, it is wiser to consult an adviser in the first hours, because a decision not to notify must be justified in writing.

What happens if I lose a laptop containing customer data?

It is an incident that must be handled regardless. Record it immediately and assess the risk. If the device was effectively encrypted and the credentials were not compromised, the risk may be low. If it was not encrypted, the risk increases. Check with the IT lead which protections were active and document the assessment in the breach register.

My IT supplier was attacked: is it up to me to notify?

The controller is the company that processes the data, so responsibility towards the authority and the individuals remains yours, even if the incident happened at the supplier. The supplier must, however, alert you without delay, and the contract must set out how it will do so. Ask for complete information immediately and check with the adviser the timing and content of the notification.

Must I inform customers even if I have not notified the Garante?

It depends on the risk to individuals. Communication to data subjects is required when the risk is high, but may not be necessary in some cases, for example if the data was effectively protected. Every decision must be documented. It is not enough to believe the case is minor: a written assessment explaining the reasoning is needed.

How long do I have to decide whether to notify?

The Regulation requires notification without undue delay and, where possible, within 72 hours of becoming aware of the breach. The time available for the assessment is therefore very short. For this reason preparation matters: a contact, a register and an adviser already engaged let you decide in time, without improvising under pressure.

If I do not yet know everything, must I wait?

No. Notification can be made with the information available, followed by a later update. Waiting to have the full picture is one of the most common mistakes and can trigger the delay. Better an initial notification that is complete for what you know, followed by updates as the investigation clarifies the rest.

Does the Garante check the breach register?

The breach register is a document you keep available and which may be requested in an inspection. It is not sent periodically. It must, however, be kept up to date and complete, including incidents that were not notified. An empty register in a company that processes personal data can raise questions about how security events are handled.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →