Contents
- 1. NIS2 is no longer just a legislative initiative
- 2. What fines does NIS2 provide for?
- 3. Have fines for NIS2 violations already been imposed in Europe?
- 4. Why should we not trust every published list of NIS2 fines?
- 5. The European Commission has also begun using penalty mechanisms against Member States
- 6. What does NIS2 mean for public institutions and municipalities?
- 7. What should organisations do now?
- 8. The key takeaway: the era of voluntary cybersecurity is ending
- Sources
1. NIS2 is no longer just a legislative initiative
The NIS2 Directive (EU 2022/2555) has become one of the most significant changes to European information security legislation in recent years.
Its main objective is not simply to require organisations to install antivirus software, use firewalls or remediate technical vulnerabilities. NIS2 changes the very approach to cybersecurity management: responsibility for the resilience of information systems becomes part of corporate governance, rather than solely a task for the IT department.
The key date is 17 October 2024. EU Member States were required to transpose the provisions of NIS2 into their national legislation by this deadline.
The Directive covers 18 sectors of the economy, including energy, transport, healthcare, digital infrastructure, public administration and the manufacture of critical products.
However, the most interesting question today is not what fines the law provides for, but whether European regulators have already begun imposing them in practice.
2. What fines does NIS2 provide for?
One of the most significant changes introduced by NIS2 is the establishment of minimum levels of administrative liability for organisations that fail to meet cybersecurity requirements.
The potential penalties depend on the category of the organisation.
It is important to understand that these penalties are not imposed automatically for every cyber incident. These are the maximum administrative fines that must be provided for in national legislation.
When determining a penalty, the regulator may take into account:
- The nature, severity and duration of the infringement.
- Whether the infringement was intentional or negligent.
- The extent of the damage caused.
- The number of affected users and organisations.
- Any previous infringements.
- The organisation's cooperation with supervisory authorities.
- The measures taken to remedy the consequences and prevent further incidents.
In addition to financial penalties, regulators may require security audits, remediation of identified shortcomings, compliance with binding instructions and evidence of compliance with the requirements.
Management accountability deserves particular attention: NIS2 provides for personal managerial liability for individuals holding management positions in organisations within the scope of the Directive.
3. Have fines for NIS2 violations already been imposed in Europe?
Yes. There is already a publicly confirmed case.
As of 19 November 2026, a shift from theoretical penalties to actual enforcement of the legislation can be observed.
The first publicly announced case in Romania is particularly illustrative.
Romania: the first publicly announced fine – September 2026
50 000 RON (approximately 9 800–10 000 euros)
On 29 September 2026, Romania's National Cyber Security Directorate (DNSC) decided to impose an administrative penalty on an organisation within the central public administration.
The official announcement was published on 30 September 2026.
What was the penalty imposed for?
The organisation had failed to fulfil its obligation to notify DNSC within the prescribed deadline under the national legislation transposing NIS2.
There is an important legal distinction here: the fine was not imposed for a cyberattack itself, or for delayed incident reporting, but for failure to meet the deadline for registration and notification of the regulator under Article 18, paragraph 2 of Romanian Emergency Ordinance OUG 155/2024.
DNSC did not disclose the name of the public institution.
This is a particularly important example because it shows that an organisation can be fined for failing to comply with NIS2 administrative requirements even without a publicly confirmed successful cyberattack.
Why is this case more important than it appears?
Before the first penalties emerged, many organisations viewed NIS2 as yet another European initiative whose actual enforcement could be postponed for years.
The Romanian case demonstrates a different reality:
- The regulator is already beginning to impose the penalties provided for by law.
- Public institutions are also held accountable.
- Failure to meet formal requirements can have financial consequences.
- The absence of a cyberattack does not mean there is no risk of a fine.
This significantly changes how organisations should prepare: they need not only to implement technical security measures, but also to provide documentary evidence that they have fulfilled their obligations.
4. Why should we not trust every published list of NIS2 fines?
Online publications already report fines in Belgium, Italy, Hungary, Lithuania and France, presenting them as penalties for NIS2 violations.
However, caution is required here.
Not every decision by a national cybersecurity regulator constitutes a penalty under NIS2. Some measures are applied under earlier legislation, national sector-specific rules, GDPR or other legislation.
For example, a fine for a GDPR infringement cannot automatically be classified as an NIS2 fine, even where the infringement involves a personal data breach and inadequate protection of information systems.
Analytical publications should therefore distinguish between:
- Confirmed penalties imposed directly under national NIS2 legislation.
- Regulatory instructions and requirements to remedy infringements.
- Fines under GDPR and other legislation.
- Penalties for infringements of earlier cybersecurity legislation.
At present, the Romanian case is the most clearly documented public example of a financial penalty under NIS2.
This does not mean that there are no other non-public inspections or penalties: there is no single public register of all NIS2 fines at European level.
5. The European Commission has also begun using penalty mechanisms against Member States
NIS2 supervision is not limited to individual organisations. The European Commission also monitors whether EU Member States themselves fulfil their obligations.
The deadline for transposing the Directive expired on 17 October 2024, but far from all Member States managed to meet the requirements on time.
On 7 May 2025, the European Commission sent reasoned opinions to 19 Member States that had not notified full transposition of NIS2 into their national legislation.
On 8 July 2026, the Commission decided to refer four Member States to the Court of Justice of the European Union:
- France.
- Ireland.
- Spain.
- The Netherlands.
The Commission asked the Court to impose financial penalties: lump-sum payments and daily penalty payments until the obligations are fulfilled.
This is a mechanism for penalising Member States, not individual companies.
Status of NIS2 transposition in Europe
As of 18 November 2026:
- 24 of the 27 EU Member States have national legislation in force.
- 3 Member States still have no law in force: France, Ireland and Spain.
This indicator demonstrates that, even at EU Member State level, introducing the requirements has proved more complex than initially expected.
It is important to bear in mind that adopting a national law does not yet mean that all organisations have met the NIS2 requirements. This requires classification of organisations, designation of the responsible authorities, registration procedures, inspections and actual implementation of security measures.
6. What does NIS2 mean for public institutions and municipalities?
Public administration is one of the most important areas covered by NIS2.
Public institutions are increasingly targeted by cyberattacks because they hold substantial volumes of information and deliver critical public services.
Potential threats include:
- Ransomware attacks against municipal information systems.
- Compromise of employee user accounts.
- Unauthorised access to databases containing information about citizens.
- Disruption of electronic administrative services.
- Attacks on water supply systems, transport and energy infrastructure.
- Compromise of external contractors and IT service providers.
NIS2 includes public administration among the regulated sectors, but national rules for identifying specific entities must be taken into account. The Directive covers certain central and regional public administration bodies, but this does not automatically mean that every municipal organisation falls within its scope.
However, this does not remove the need to ensure a high level of cybersecurity at municipal level.
Why is assessing municipal websites practically important?
A municipal website is often more than an information page. It may provide access to administrative services, contain personal data, integrate with government systems and use external services.
An assessment should therefore cover more than the website's appearance and the presence of an SSL certificate.
Particular attention should be paid to:
| Area | What should be checked |
|---|---|
| Connection security | HTTPS, TLS, certificate validity and configuration |
| HTTP headers | HSTS, CSP and other security mechanisms |
| Personal data | GDPR, privacy policy, data collection forms |
| Technical security | Vulnerabilities in CMS platforms, servers and components |
| Access management | Authentication, administrative interfaces |
| Infrastructure | DNS, email records, domain configuration |
| Risk management | Response and recovery procedures |
| Suppliers | Security of external services and subcontractors |
It is important to understand that a technical audit of a public website does not replace a comprehensive NIS2 audit. It can identify some of the risks and provide an objective picture of the technical protection of the external perimeter.
7. What should organisations do now?
Whether an organisation is public or private, preparation for NIS2 should cover several key areas.
1. Determine whether NIS2 applies
Establish whether the organisation falls into the category of essential or important entities and identify the applicable national legislation.
2. Assess the current security posture
Conduct a technical audit of infrastructure, web resources, servers, networks and external services.
3. Develop a risk management system
Identify threats, assess potential damage and prioritise the remediation of shortcomings.
4. Introduce incident response procedures
Define responsible individuals, communication channels and procedures for notifying the competent authorities.
5. Prepare documentary evidence of compliance
Develop information security policies and procedures for access management, backup and recovery.
6. Ensure management involvement
Organise training for managers and clearly define responsibilities for managing cyber risks.
7. Conduct regular assessments
Monitor the security posture, remediate newly discovered vulnerabilities and verify the effectiveness of implemented measures.
It is particularly important not to rely solely on a one-off audit. NIS2 requires ongoing risk management and regular verification of the effectiveness of security measures.
8. The key takeaway: the era of voluntary cybersecurity is ending
NIS2 is gradually evolving from a legislative requirement into a practical mechanism for supervision and accountability.
The Romanian case from September 2026 is particularly illustrative: a public institution received a fine of 50 000 lei (approximately 9 800 euros), not because of a successful cyberattack, but because it failed to meet the mandatory deadline for notifying the regulator.
This sends an important signal to organisations across Europe.
In the coming years, increased supervisory activity, more inspections and more active enforcement of administrative penalties can be expected.
However, organisations should not wait for their first inspection or incident before starting to prepare.
For public institutions, municipalities and organisations providing critical services, NIS2 compliance is becoming part of their institutional responsibility towards citizens.
This is precisely why independent assessments of technical maturity, regular checks and documented remediation of identified shortcomings should become standard practice.
Sources
- European Commission — The NIS2 Directive: frequently asked questions and penalties.
- European Commission — Referral of four Member States to the Court of Justice of the European Union, 8 July 2026.
- Cybersecurity Database — NIS2 transposition in EU Member States.
- DNSC / AGERPRES — The first publicly announced Romanian penalty related to NIS2, 30 September 2026.
- ProDefence — Legal analysis of the first Romanian NIS2 fine.
Note: This article reflects the publicly available information as of 19 November 2026. National laws may provide for additional requirements and different procedures for imposing penalties. The absence of publicly announced fines does not mean that there are no inspections or non-public supervisory measures.



