NIS2 Article 34 sets the minimum levels that national administrative-fine maximums must reach for Article 21 or 23 infringements by essential and important entities.
Separate the EU baseline from Member State penalty rules, enforcement measures, public administration treatment, GDPR overlap, and case-specific factors.
NIS2 does not impose one flat EU fine or say that every infringement receives the headline amount. requires each Member State's law to make Article 21 and 23 infringements subject to a maximum of at least the stated fixed amount or turnover percentage, whichever is higher. The authority must then consider the circumstances of the case. Check the applicable national law for the available penalties, procedure, authority, turnover calculation, and treatment of public administration entities.
1
Section 1
What are the NIS2 Article 34 fine ceilings?
For an essential entity that infringes Article 21 or 23, Member States must provide for an administrative-fine maximum of at least EUR 10,000,000 or at least 2% of the total worldwide annual turnover in the preceding financial year of the undertaking to which the entity belongs, whichever is higher.
For an important entity, the corresponding maximum must be at least EUR 7,000,000 or at least 1.4% of that undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. These figures set a floor for the maximum available under national law. They are not an automatic fine, a harmonised penalty for every case, or a statement that national law cannot set a higher maximum.
Essential entity: national law must allow a maximum of at least EUR 10,000,000 or 2% of the undertaking's worldwide annual turnover, whichever is higher.
Important entity: national law must allow a maximum of at least EUR 7,000,000 or 1.4% of the undertaking's worldwide annual turnover, whichever is higher.
The fine trigger named in is infringement of Article 21 risk-management measures or Article 23 reporting obligations.
Administrative fines are imposed in addition to the enforcement measures listed in Articles 32 and 33, subject to the applicable national process.
points specifically to infringements of Article 21 and Article 23. Article 21 requires appropriate and proportionate technical, operational, and organisational cybersecurity risk-management measures. Article 23 covers significant-incident notification to the CSIRT or competent authority and, where applicable, communication to affected service recipients.
Useful evidence shows both the decision and the facts behind it: how the entity assessed proportionality, operated and tested its controls, determined whether an incident was significant, recorded when awareness began, met each reporting stage, communicated with the authority, and corrected deficiencies without undue delay.
Article 21 evidence should cover risk analysis, incident handling, business continuity, supply-chain security, secure acquisition and development, control testing, cyber hygiene, cryptography, access control, asset management, and authentication where appropriate.
Article 23 evidence should show how the team identified a significant incident, started the reporting clock, notified the correct CSIRT or competent authority, and assessed cross-border impact.
Management-body evidence matters because Article 20 requires the management body to approve and oversee Article 21 measures; national law governs liability rules, including the treatment of public institutions and officials.
For digital infrastructure and digital provider sectors covered by Implementing Regulation (EU) 2024/2690, keep the implementing-regulation control evidence with the Article 21 evidence.
How do enforcement powers differ for essential and important entities?
Essential entities are subject to proactive and reactive supervision. Competent authorities can use on-site inspections, off-site supervision and random checks, regular and targeted audits, ad hoc audits after a significant incident or suspected infringement, security scans, information requests, and requests for implementation evidence.
Important entities are subject to ex post supervision when the authority receives evidence, indications, or information of alleged non-compliance. Both categories can face warnings, binding instructions or orders, remediation requirements, orders to publicise aspects of an infringement, and fines. For an essential entity, ineffective corrective measures can also lead, subject to national process and safeguards, to temporary suspension of a certification or authorisation or a temporary prohibition on certain managers until the deficiency is remedied; those measures do not apply to public administration entities.
Essential entities should be ready for proactive inspection, audit, scan, information-request, and evidence-request activity.
Important entities should be ready to respond quickly when a competent authority opens ex post supervision after evidence or indications of non-compliance.
Fines do not replace other enforcement actions; requires them to be imposed in addition to the listed corrective and supervisory measures.
The practical owner split should include legal, security, incident response, supplier risk, compliance, and management-body reporting.
How is the fine amount decided, and what can national law change?
The headline maximum does not decide the fine. Under Articles 34(3) and 32(7), the authority must consider at least the seriousness and duration of the infringement, previous infringements, material and non-material damage, intent or negligence, mitigation, adherence to approved codes or certification mechanisms, and cooperation. Repeated violations, failure to notify or remedy significant incidents, failure to follow binding instructions, obstruction of audits, and false or grossly inaccurate information are identified as serious infringements.
NIS2 is a directive, so Member States implement the penalty rules. Article 36 requires national penalties for infringements of measures adopted under the Directive, while addresses administrative fines for Article 21 and 23 infringements. A Member State may also allow periodic penalty payments to compel an entity to stop an infringement, and it decides whether and to what extent Article 34 fines apply to public administration entities.
The GDPR overlap rule is narrower than a general ban on parallel enforcement. If a GDPR supervisory authority imposes an administrative fine for a personal data breach arising from the same conduct as the relevant Article 21 or 23 infringement, the NIS2 authority must not impose an fine for that same conduct. It may still use the other NIS2 enforcement measures.
Check the relevant Member State transposition law before quoting a local authority, procedure, deadline, or national penalty range.
Do not assume public administration entities face the same administrative-fine treatment in every Member State.
Separate a NIS2 fine analysis from broader national penalties under Article 36.
Record the Article 32(7) factors and the evidence for each one; the statutory maximum alone does not predict the amount.
Where the same conduct also involves a personal data breach, track whether a GDPR supervisory authority has imposed a fine; the same-conduct restriction applies at that point, not merely because a breach may fall under both regimes.
Evidence checklist for NIS2 penalty and fine readiness
Use this checklist before an incident, audit, authority request, or management-body review. It cannot predict a fine, but it keeps the facts needed to show classification, obligation coverage, incident decisions, authority interactions, remediation, and the Article 32(7) factors.
Keep the country-specific legal position separate from the EU baseline so later reviewers can see which claims come from the Directive and which come from national implementation.
What are the maximum NIS2 fines for essential entities under ?
For an Article 21 or Article 23 infringement, Member State law must allow an administrative-fine maximum of at least EUR 10,000,000 or at least 2% of the total worldwide annual turnover in the preceding financial year of the undertaking to which the essential entity belongs, whichever is higher. This is a minimum level for the available maximum, not an automatic fine.
What are the maximum NIS2 fines for important entities under ?
For an Article 21 or Article 23 infringement, Member State law must allow an administrative-fine maximum of at least EUR 7,000,000 or at least 1.4% of the total worldwide annual turnover in the preceding financial year of the undertaking to which the important entity belongs, whichever is higher. This is a minimum level for the available maximum, not an automatic fine.
Can a NIS2 fine be imposed together with other enforcement measures?
Yes. requires administrative fines to be imposed in addition to the listed enforcement measures in Articles 32 and 33. Depending on the entity category and national process, those measures include warnings, binding instructions, orders to remedy deficiencies, implementation of audit recommendations, and orders to make aspects of an infringement public.
Does NIS2 always impose administrative fines on public administration entities?
No. leaves each Member State to lay down whether and to what extent administrative fines may be imposed on public administration entities, without prejudice to competent-authority powers under Articles 32 and 33.
What factors affect the amount of a NIS2 administrative fine?
The authority must consider at least the infringement's seriousness and duration, previous infringements, material and non-material damage, intent or negligence, mitigation, adherence to approved codes or certification mechanisms, and cooperation. NIS2 identifies repeated violations, failure to notify or remedy significant incidents, failure to follow binding instructions, obstruction of audits, and false or grossly inaccurate information as serious infringements. National law governs the procedure and may add relevant rules.
Can NIS2 and GDPR authorities both act on the same incident?
Yes, but Article 35 restricts duplicate administrative fines for the same conduct. If a GDPR supervisory authority imposes an administrative fine for a personal data breach arising from the same conduct as the Article 21 or 23 infringement, the NIS2 authority must not impose an fine for that same conduct. The NIS2 authority may still use the other enforcement measures listed in Articles 32 and 33.
Entity classification: essential or important status, Annex I or Annex II sector, size-cap or special-case basis, and the Member State authority context.
Article 21 file: approved cybersecurity risk-management measures, management-body oversight, control tests, supplier-risk evidence, remediation records, and training evidence.
Article 23 file: significant-incident assessment, notification clock, CSIRT or competent-authority route, recipient communication decision, cross-border impact assessment, and final report record.
Enforcement response file: authority requests, stated purpose of requests, data or document production, audit results, corrective measures, deadlines, and proof of completion.
Fine analysis file: essential or important status, undertaking and turnover basis if relevant, Article 32(7) factors, GDPR fine and same-conduct check, public administration treatment if relevant, available periodic penalty payments, and national transposition source.
Sorena can help connect NIS2 Article 21 controls, Article 23 incident records, management-body approvals, and Member State transposition sources in an enforcement-readiness file.