Skip to main content
All news

Cybersecurity ·

NIS2 incident notification: the 24h / 72h / 1-month procedure with ACN

When a significant incident hits an organisation subject to NIS2, a clock starts ticking that does not stop. Art. 25 of Legislative Decree 138/2024 (D.Lgs. 138/2024) requires a notification procedure in three stages — 24 hours, 72 hours and one month — to the Agenzia per la Cybersicurezza Nazionale (ACN – Italy's National Cybersecurity Agency). Knowing what happens at each of these steps, and preparing before it happens, is what separates professional handling from a breach that can be penalised.

By Fabio Vantaggiato, CEO & Co-Founder

Directive (EU) 2022/2555 introduced a uniform regime for notifying significant incidents across the European Union. In Italy, Legislative Decree no. 138 of 4 September 2024 transposed this obligation in Art. 25, structuring the procedure around three cumulative deadlines. Each has a technical name, a specific purpose and mandatory minimum content. Missing any one of these time windows — even through disorganisation, even through doubts about how to classify the event — exposes the organisation to heavy administrative penalties and, above all, to an ACN investigation that is unlikely to be closed within a few days.

What is a "significant incident"

Before talking about timing, we need to clarify when the notification obligation is triggered. Art. 25 applies to significant incidents, defined by the decree as events that:

  • have caused or are capable of causing severe operational disruption of the services or financial losses for the entity concerned;
  • have affected or are capable of affecting other natural or legal persons by causing considerable material or non-material damage.

The definition is deliberately broad, because it covers both successful cyber attacks (ransomware, data breaches, defacement) and accidental incidents (human error, hardware failures, prolonged unavailability of essential services) that produce similar effects. When in doubt, a practical rule applies: if an incident could have had consequences for essential services, for customers or for the company's operations, it should be treated as "significant" and taken through the notification procedure. Over-notifying is better than a failure to notify judged to be negligent.

T+24h — Early warning

Within 24 hours of the organisation becoming aware of the significant incident, an early warning must be sent to ACN. This is a short notice — not a technical report — intended to let the authority know what is happening and to assess initial coordination.

As a minimum, it must contain:

  • Identification of the NIS entity (name, ACN identifier, Annex I/II sector);
  • Date and time of detection of the incident and how it was discovered;
  • A preliminary indication of the nature of the event: is an unlawful or malicious act suspected? Is an attack under way?
  • Services and assets involved, even on a preliminary basis;
  • Any cross-border impact: could the incident affect other EU Member States?

The early warning does not require a completed forensic analysis. It does, however, require a clear channel and a designated person: who the organisation's NIS2 contact is, how they can be reached out of hours, and who is authorised to send the notification on behalf of the legal representative.

T+72h — Full notification

Within 72 hours of the organisation becoming aware of the incident, the full notification must be sent to ACN. This time the level of detail increases: an initial assessment of the event is required, including severity, impact and — where available — technical indicators of compromise.

Expected minimum content:

  • An update on the early warning (what has changed in the following 48 hours);
  • An initial assessment of severity and of the impact on services, users and data;
  • Indicators of compromise (IoCs): hashes of malicious files, IP addresses, domains, compromised accounts, attack vectors identified;
  • Mitigation measures already taken or being taken (containment, eradication, recovery);
  • Coordination with other authorities: if the incident involves unlawful processing of personal data, is a notification to the Italian Data Protection Authority (Garante Privacy) under Art. 33 GDPR under way? Has a complaint been filed with the judicial authorities?

72 hours is not long if the organisation has not prepared in advance. For this reason, the Incident Response Plan (IRP) must include pre-filled templates for the notification, with the identification and technical fields already prepared. Every minute saved on drafting is an extra minute spent on containment.

T+1 month — Final report

Within one month of the full notification, the organisation must send ACN the final report on the incident. This closes the cycle: the event has been analysed, its causes identified, corrective measures implemented and lessons learned documented.

It must contain:

  • A detailed description of the incident, its scope and its actual (no longer estimated) severity;
  • The type of threat and the causes that made the event possible (root cause analysis);
  • Mitigation measures adopted, including long-term corrective measures (architectural changes, new controls, targeted training);
  • Any cross-border impact confirmed after the fact;
  • Lessons learned and changes to the IRP for the future.

The final report carries particular weight: it is the document ACN will use to assess the maturity of the organisation's response. An incident that is well handled, well documented and followed by concrete corrective measures is a mitigating factor in any subsequent penalty proceedings. Conversely, an incomplete report or the absence of corrective measures is an aggravating factor.

What happens if the incident has not yet been resolved

If, one month on, the incident is still ongoing (e.g. systems being rebuilt, data being restored from backup, forensic investigations not yet concluded), a progress report is required instead of the final report, followed by a final report within one month of the end of incident handling. The logic is simple: ACN wants to be kept informed continuously, not left waiting in silence. An open dialogue with the authority is one of the strongest signs of a sound compliance posture.

Informing users: the other notification

Art. 25 also provides for a second level of communication: when a significant incident is likely to adversely affect the provision of services, the NIS entity must inform the recipients of its services without undue delay, pointing out the measures they can take to limit the consequences. This is a different notification from the one to ACN, aimed at transparency and user empowerment. It should be built into the IRP, with content, channels and timings standardised in advance.

Preparation: what to do BEFORE an incident

The first 24 hours are not the time to find out who the organisation's ACN contact is, or to go looking for the notification template. A notification procedure works if it has been prepared. These are the minimum steps:

  • Advance registration of the NIS entity's contacts and designated persons on the ACN platform;
  • A formal Incident Response Plan (IRP), with a chain of command, a virtual war room and clear roles and responsibilities;
  • Pre-filled templates for the early warning, the full notification and the final report, with the identification fields already completed;
  • A 24/7 on-call procedure for the NIS2 contact: who gets called at night, who takes escalation decisions;
  • Regular exercises (table-top exercises) to test the procedure before a real incident does it for you;
  • Documented coordination with the DPO, legal, communications and critical suppliers;
  • A chain of custody for evidence (logs, disk images, snapshots) that allows both forensic analysis and, if necessary, use in court.

Penalties and mitigating factors

Failure to notify, or late notification, exposes the organisation to significant administrative fines under Art. 38 of D.Lgs. 138/2024. For essential entities these can reach €10 million or 2% of total worldwide annual turnover (whichever is higher); for important entities, up to €7 million or 1.4% of turnover. On top of these penalties comes the personal liability of Management for failing to oversee security measures, which can lead to disqualification measures in the most serious cases.

There are, however, mitigating factors that significantly reduce the size of penalties and may even avoid them. They all relate to the quality of preparation and to cooperation with the authority: complete documentation of the security measures implemented, evidence of staff training (Art. 20), timely notification, active cooperation during the investigation, and concrete corrective measures after the incident. This is where documented compliance makes a practical difference: it not only reduces the risk of suffering an incident, it drastically reduces the consequences when an incident — sooner or later, unfortunately — does occur.

In short: the clock starts when you become aware

The key point of Art. 25 is the dies a quo: the 24-hour, 72-hour and one-month clock starts from the moment the organisation becomes aware of the incident, not from when it objectively occurred. This means that the detection system (SIEM, EDR, SOC) and internal reporting are integral parts of the notification procedure: an alert that is not escalated is a lost compliance opportunity.

Building a sound posture takes three things, in this order: technology to detect incidents, process to handle them, and training so that people know what to do when the alarm goes off. NIS2 does not ask you to be infallible: it asks you to be prepared and transparent.

Related resources

For the complete regulatory framework: NIS2: the complete guide to D.Lgs. 138/2024. For the technical measures required: NIS2 technical measures under Art. 21 — the CISO checklist. For penalties in the event of failure to notify: NIS2 penalties under Art. 38. For supply chain security: NIS2 and the supply chain. To build your security posture with Easy Health's support: NIS2 consulting and Art. 20 training.

In healthcare organisations, cyber notification sits alongside its clinical counterpart: the reporting of adverse events for patient safety purposes. The two processes share the same logic and organisational discipline, as explained in our article on the Gelli-Bianco Law fully in force from 16 March 2026.

Related articles

Would you like to find out more?

Get in touch to find out how our solutions can support your healthcare organisation.

Talk to an expert

Talk to us

Tell us how care is organised in your area: we'll prepare a demo on your own pathways, not on a textbook case.

NIS2 incident notification: the 24h / 72h / 1-month procedure with ACN | Easy Health