NIS2 scope: who is an essential entity and who is an important entity
The first step for any organisation is to understand whether it is in scope. D.Lgs. 138/2024 identifies two categories of entity, based on two combined criteria: the sector of activity (Annexes I and II) and the size of the organisation (number of employees, turnover, balance sheet total).
Annex I lists the sectors of high criticality: energy, transport, banking, financial market infrastructure, health, drinking water and waste water, digital infrastructure, ICT service management (B2B), public administration and space. Annex II lists the other critical sectors: postal services, waste management, chemicals, food, manufacturing (medical devices, computers and electronics, machinery, motor vehicles and other transport equipment), digital providers and research.
Large enterprises (more than 250 employees, more than €50 million in turnover and more than €43 million in balance sheet total) in Annex I sectors are classified as essential entities. Medium-sized enterprises in Annex I sectors and medium-sized and large organisations in Annex II sectors are classified as important entities. The distinction is not a formality: it changes the supervisory regime (ex ante for essential entities, ex post for important ones) and the size of penalties.
There are, however, exceptions that can bring smaller organisations into scope as well — for example sole providers of an essential service, or entities whose disruption would have a significant impact. A NIS2 gap analysis always starts with a close reading of the Annexes and of size, supplemented by the operational guidance published by ACN.
Art. 20: governance, training and Management liability
Art. 20 is the political heart of NIS2. It moves cybersecurity from the IT department to the management body's table. Boards of directors, managing directors and senior executives must approve the risk management measures, oversee their implementation and are personally accountable for breaches. The liability is individual, goes with the role and, for events that occurred during the term of office, does not lapse when the term ends.
The second paragraph of Art. 20 introduces an obligation of regular training, for both Management and operational staff. Training must be proportionate to the role and to risk exposure, must be documented and must be verifiable in the event of an inspection. "Having organised a course" is not enough: a structured programme is needed, with traceability of hours delivered, evidence of assessments passed and a personal certificate of attendance.
We have devoted a specific article to the operational side of Art. 20: NIS2 training: why Art. 20 changes the rules (and the liability).
Art. 21: the minimum technical and organisational measures
Art. 21 is the technical "shopping list" of NIS2: it lists the minimum measures organisations must adopt to manage the risks posed to the security of network and information systems. These measures are not optional, but they are proportionate to the risk.
The main areas covered by Art. 21 are:
- Policies on risk analysis and information system security;
- Incident handling (detection, classification, response);
- Business continuity: backup, disaster recovery, crisis management;
- Supply chain security (suppliers and the supply chain);
- Security in the acquisition, development and maintenance of systems, including vulnerability handling and disclosure policies;
- Policies and procedures to assess the effectiveness of the measures;
- Basic cyber hygiene and cybersecurity training;
- Policies on the use of cryptography and, where appropriate, encryption;
- Human resources security, access control and asset management;
- Multi-factor authentication, secured voice, video and text communications and — where necessary — secured emergency communications.
Each measure requires documentary evidence: an approved policy, a process carried out, a log or a report. "Substantive" adoption of the measures alone is not enough in the event of an inspection: ACN expects to be able to reconstruct the security posture over time. For an operational checklist aimed at CISOs, see NIS2 technical measures under Art. 21 — the CISO checklist.
Art. 25: notification of significant incidents (24h / 72h / 1 month)
Art. 25 governs the procedure for notifying ACN of incidents classified as "significant". The procedure is structured around three time windows, all calculated from the moment the organisation became aware of the incident:
- Early warning within 24 hours: an initial notice to ACN indicating at least whether the event may be malicious and whether it may have a cross-border impact;
- Full notification within 72 hours: an update with an initial assessment of the incident, its severity, impact and indicators of compromise (where available), together with the mitigation measures taken or planned;
- Final report within one month: a detailed description, root cause analysis, measures taken, any ongoing mitigation measures and cross-border impact.
The critical point is the dies a quo: the clock starts from the moment of awareness, not from the objective occurrence of the event. This means that the quality of the SIEM, the EDR and the internal escalation process is an integral part of compliance: an alert that is not escalated is a lost compliance opportunity. We cover the procedure in operational detail in a dedicated article: NIS2 incident notification: the 24h / 72h / 1-month procedure with ACN.
Art. 38: the penalty regime
Art. 38 defines the regime of administrative fines. The distinction between essential and important entities re-emerges here very clearly:
- Essential entities: fines of up to €10 million or 2% of total worldwide annual turnover in the previous financial year, whichever is higher;
- Important entities: fines of up to €7 million or 1.4% of total worldwide annual turnover, again whichever is higher.
In addition to fines, Art. 38 provides for disqualification measures and, in the most serious cases, the personal liability of Management for failing to oversee security measures, up to temporary suspension from office. For a detailed analysis of the offences, mitigating and aggravating factors, see NIS2 penalties: what management risks under Art. 38.
Compliance timelines and the role of ACN
D.Lgs. 138/2024 has been in force since 16 October 2024. The operational deadlines — registration with ACN, adoption of the Art. 21 measures, activation of the Art. 20 training plan — have been set out by ACN in several phases, over a multi-year period. The reference timeline typically comprises:
- Registration and initial census of in-scope entities;
- Progressive adoption of the basic measures in the months following registration;
- Full compliance with the Art. 21 measures within the deadlines set by ACN Determinations.
The Agenzia per la Cybersicurezza Nazionale (ACN – Italy's National Cybersecurity Agency) is the competent authority: it manages registration, receives incident notifications, publishes operational guidelines, carries out inspections and has the power to impose penalties. ACN Determinations are the ongoing operational reference for in-scope entities: they should be monitored alongside the European Commission's publications on implementing regulations.
NIS2 FAQ
My company has fewer than 50 employees: is it in NIS2 scope?
In general, no: D.Lgs. 138/2024 excludes small and micro enterprises. There are, however, exceptions — sole providers of an essential service, entities whose disruption would have a significant impact, and certain categories expressly included regardless of size (for example providers of public communications networks and trust service providers). This has to be checked case by case, starting from Annexes I/II and the ACN Determinations.
Who is actually liable for NIS2 breaches?
The management body, under Art. 20. Liability is individual and non-delegable as regards the decision on and oversight of the measures; their execution can be delegated. In the event of a breach, in addition to the fine on the organisation (Art. 38), disqualification measures may be imposed on individual directors for the most serious conduct.
What do you risk if you fail to notify a significant incident on time?
Failure to notify, or late notification, exposes the organisation to the penalties of Art. 38 (up to 2% of turnover for essential entities) and affects the overall assessment of the adequacy of its risk management measures (Art. 21), paving the way for a broader ACN investigation. Timely notification is also one of the main mitigating factors in penalty proceedings.
Is NIS2 training mandatory only for Management or for all staff?
For both. Art. 20 clearly distinguishes between Management training (governance) and staff training (operational). Training must be proportionate to the role and regularly updated. Easy Health offers four e-learning paths tailored to Management, CISOs, IT technicians and non-technical staff.
What happens in the event of an ACN inspection?
The organisation must be able to show documentary evidence of everything: approved policies, records of training delivered, system logs, vulnerability assessment and penetration test reports, incident response procedures, contracts with critical suppliers and security clauses. NIS2 compliance largely depends on the quality of documentation, not only on the adoption of measures.
Where to start
The typical NIS2 compliance journey has five steps: scoping (checking whether you are in scope), gap analysis (mapping the Art. 21 measures against the current state), remediation plan (prioritising actions), execution (implementing policies, processes and technologies) and ongoing governance (audits, training, keeping up with ACN Determinations).
At Easy Health we support organisations throughout the journey: from the initial gap analysis to continuous auditing, through to the Art. 20 e-learning paths for Management, CISOs, IT technicians and non-technical staff. For a free initial assessment of your organisation's level of exposure, contact us.