Penalties GuideEU

NIS2 penalties and fines

NIS2 Article 34 sets minimum maximum administrative fine levels for essential and important entities that infringe Article 21 cybersecurity risk-management duties or Article 23 reporting duties.

Use this page to separate EU-level fine ceilings from Member State penalty rules, enforcement measures, public administration treatment, GDPR overlap, and the evidence teams should preserve.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

NIS2 does not use one flat EU fine. Article 34 requires Member States to make administrative fines effective, proportionate, and dissuasive, with different minimum maximum caps for essential and important entities. The fine exposure is tied mainly to failures under Article 21 risk-management measures and Article 23 incident-reporting obligations, while national implementation determines the competent authority route and additional penalty rules.

Section 1

What are the NIS2 Article 34 fine ceilings?

For essential entities, NIS2 requires Member States to make Article 21 or Article 23 infringements subject to administrative fines with a maximum of at least EUR 10,000,000 or at least 2% of the total worldwide annual turnover of the undertaking in the preceding financial year, whichever is higher.

For important entities, the corresponding Article 34 ceiling is a maximum of at least EUR 7,000,000 or at least 1.4% of the total worldwide annual turnover of the undertaking in the preceding financial year, whichever is higher. These are EU minimum maximum levels; a local penalty assessment still depends on national law and the facts of the case.

  • Essential entity cap: at least EUR 10,000,000 or 2% of worldwide annual turnover, whichever is higher.
  • Important entity cap: at least EUR 7,000,000 or 1.4% of worldwide annual turnover, whichever is higher.
  • The fine trigger named in Article 34 is infringement of Article 21 risk-management measures or Article 23 reporting obligations.
  • Administrative fines can be imposed in addition to other enforcement measures under Articles 32 and 33.
Section 2

Which NIS2 failures can lead to fines?

Article 34 points to infringements of Article 21 and Article 23. Article 21 covers appropriate and proportionate technical, operational, and organisational cybersecurity risk-management measures. Article 23 covers significant incident notification to the CSIRT or competent authority, and in relevant cases communication to affected service recipients.

Penalty planning should therefore start with the evidence for those two obligations: control design and operation, incident handling, reporting decisions, notification timestamps, authority communications, and remediation records.

  • 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 approval and oversight of Article 21 measures and allows liability for Article 21 infringements under national rules.
  • 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.
Section 3

How do enforcement powers differ for essential and important entities?

Essential entities face proactive supervisory powers. Competent authorities can use tools such as on-site and off-site supervision, regular and targeted audits, ad hoc audits after a significant incident or suspected infringement, security scans, requests for information, and requests for evidence of implementation.

Important entities are supervised mainly ex post: the authority acts when it has evidence, indications, or information that the entity allegedly does not comply with NIS2, especially Articles 21 and 23. Both categories can face warnings, binding instructions or orders, remediation requirements, public aspects of infringement, and Article 34 fines.

  • 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; Article 34 fines can sit alongside corrective orders and other measures.
  • The practical owner split should include legal, security, incident response, supplier risk, compliance, and management-body reporting.
Section 4

Which limits and national-law issues change the penalty analysis?

NIS2 is a directive, so Member States implement penalty rules in national law. Article 36 requires Member States to lay down penalties for infringements of national measures adopted under the Directive, and Article 34 lets each Member State decide whether and to what extent administrative fines may apply to public administration entities.

NIS2 also addresses overlap with GDPR. If a GDPR supervisory authority imposes an administrative fine for the same conduct arising from an Article 21 or Article 23 infringement that entails a personal data breach, the NIS2 competent authority must not impose an Article 34 administrative fine for that same conduct, although other NIS2 enforcement measures may still be used.

  • 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 Article 34 fine analysis from broader national penalties under Article 36.
  • Where the same conduct also involves a personal data breach, track GDPR authority action so the NIS2 fine analysis does not double-count the same conduct.
Section 5

Evidence checklist for NIS2 penalty and fine readiness

Use this checklist to make the penalty file reviewable before an incident, audit, authority request, or management-body review. The goal is not to predict a fine; it is to keep the facts needed to show classification, obligation coverage, incident decisions, authority interactions, and remediation.

Keep the country-specific legal position separate from the EU Article 34 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 Article 34?

For Article 21 or Article 23 infringements, essential entities must be subject under Member State law to administrative fines with a maximum of at least EUR 10,000,000 or at least 2% of total worldwide annual turnover in the preceding financial year of the undertaking, whichever is higher.

What are the maximum NIS2 fines for important entities under Article 34?

For Article 21 or Article 23 infringements, important entities must be subject under Member State law to administrative fines with a maximum of at least EUR 7,000,000 or at least 1.4% of total worldwide annual turnover in the preceding financial year of the undertaking, whichever is higher.

Can a NIS2 fine be imposed together with other enforcement measures?

Yes. Article 34 states that administrative fines are imposed in addition to the enforcement measures referred to in Articles 32 and 33, such as warnings, binding instructions, orders to remedy deficiencies, audit recommendations, and public aspects of infringement.

Does NIS2 always impose administrative fines on public administration entities?

No. Article 34 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.

  • 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 fine ceiling, turnover basis if relevant, GDPR overlap check, public administration treatment if relevant, and national transposition source.
Recommended next step

Turn NIS2 Article 34 risk into reviewable evidence

Sorena can help connect NIS2 Article 21 controls, Article 23 incident records, management-body approvals, and Member State transposition sources into a practical enforcement-readiness file.

Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Primary source for Article 34 fine ceilings, Article 35 GDPR-overlap treatment, and Article 36 national penalties.
"effective, proportionate and dissuasive"
enisa.europa.eu
Referenced sections
  • ENISA guidance provides implementation context and evidence examples for entities subject to the NIS2 implementing regulation.
"Technical Implementation Guidance"
digital-strategy.ec.europa.eu
Referenced sections
  • Commission FAQ context for the NIS2 entity model and the move from NIS1 to a broader cybersecurity regime.
"NIS2 Directive"
Related guides

Explore more topics

Are managed service providers in scope of NIS2?
NIS2 scope answer for managed service providers and managed security service providers, including service definition, size-cap checks, entity status, and jurisdiction evidence.
EU NIS2 Directive applicability test for entity scope
Stepwise NIS2 applicability test for Annex I and Annex II sectors, medium and large entities, size-independent cases, essential or important classification, jurisdiction, and evidence.
EU NIS2 Directive deadlines and compliance calendar | Article 23 clocks
source-linked NIS2 compliance calendar covering 17 October 2024 transposition, 18 October 2024 application, Article 27 registry data, Article 3 entity lists, Article 23 incident-reporting clocks, and Member State transposition watch items.
FAQ: NIS2 essential vs important entity classification and registration obligations
Plain-English FAQ comparing NIS2 essential entities and important entities, with Article 3 classification rules, shared Article 21 and 23 duties, supervision differences, and evidence to keep.
NIS2 24-hour early warning: what to send and when
Under NIS2 Article 23, covered essential and important entities submit an early warning within 24 hours of becoming aware of a significant incident.
NIS2 72-hour incident notification FAQ
Direct answer on the NIS2 72-hour incident notification: when it is due, what it updates, what it must include, and how to preserve evidence.
NIS2 Annex I and Annex II Sector Scoping Guide
Map NIS2 Annex I and Annex II sectors, entity types, size-cap rules, and essential versus important entity classification with official EU sources.
NIS2 Article 21 control baseline and evidence checklist
Build a NIS2 Article 21 control baseline from the Directive's minimum cybersecurity risk-management measures, proportionality test, supplier duties, and evidence expectations.
NIS2 Article 21 control-by-control evidence checklist
Map NIS2 Article 21 risk-management measures to evidence records for governance, incident handling, continuity, supply chain, testing, cyber hygiene, cryptography, access, assets, and authentication.
NIS2 Article 21 Gap Assessment Workflow: controls, evidence, and owners
Assess NIS2 Article 21 cybersecurity risk-management gaps by mapping current controls to Article 21(2), ownership, evidence, supplier risk, and management review.
NIS2 Article 23 incident notification workflow
Map NIS2 Article 23 reporting duties for significant incidents: 24-hour early warning, 72-hour notification, intermediate reports, final report, recipients, and evidence.
NIS2 Compliance Checklist: scope, controls, reporting
Use this NIS2 compliance checklist to confirm scope, entity classification, management-body duties, Article 21 controls, Article 23 reporting, and evidence.
NIS2 Compliance Guide: scope, controls, reporting, and evidence
A practical NIS2 compliance guide for mapping entity scope, Article 21 risk measures, Article 23 incident reporting, management accountability, and evidence records.
NIS2 Country Transposition Tracker: EU Status Workflow
Track NIS2 Directive transposition by EU country with Commission status pages, Article 41 deadlines, reasoned-opinion flags, source URLs, and review controls.
NIS2 Entity Classifier Workflow: essential vs important entity scoping
Classify whether an EU service is out of scope, an important entity, an essential entity, or needs national-authority review under the NIS2 Directive.
NIS2 essential vs important entities: Article 3 scope and supervision guide
Classify NIS2 essential and important entities using Article 3, Annex I and II sector scope, size-cap rules, registration evidence, and the Article 32/33 supervision split.
NIS2 essential vs important entities: supervision regime and audit evidence requirements
Compare NIS2 essential and important entities by scope, Article 21 and 23 duties, Article 32 and 33 supervision, evidence, jurisdiction, and penalties.
NIS2 FAQ: scope, Article 21 controls, incident reporting, and penalties
source-linked NIS2 FAQ for teams deciding whether they are in scope, whether they are essential or important entities, which Article 21 cybersecurity measures apply, how Article 23 incident reporting works, and what penalties and evidence records to plan for.
NIS2 incident clock triage workflow
Triage a possible NIS2 significant incident by recording awareness time, severity, impact, authority route, recipient communications, and Article 23 reporting clocks.
NIS2 Incident Reporting Workflow: 24-hour, 72-hour, and final report steps
Build a NIS2 Article 23 incident reporting workflow with significance triage, CSIRT or authority notification steps, recipient communication, cross-border checks, and evidence records.
NIS2 Management Body Accountability: board duties, training, and evidence
source-linked guide to NIS2 Article 20 management body accountability: approval of Article 21 measures, oversight, liability, training, reporting lines, and evidence.
NIS2 Member State Transposition: What Teams Must Check
How to handle NIS2 Member State transposition: use Article 41 as the EU baseline, then verify national law, authority routing, registration, and incident-reporting details.
NIS2 National Transposition Tracker: EU Member State Evidence Register
Track NIS2 national transposition with Commission country pages, Article 41 dates, reasoned-opinion flags, source wording, authority contacts, and legal review triggers.
NIS2 Registration and Authority Notification Guide
Map NIS2 Article 3 entity-list duties, Article 27 registry submissions, competent-authority contacts, and national registration portal evidence without inventing country deadlines.
NIS2 Requirements: scope, Article 21 controls, reporting, and evidence
Map NIS2 requirements for essential and important entities: scope classification, management-body duties, Article 21 cybersecurity measures, Article 23 incident reporting, and evidence records.
NIS2 Size Cap Rule and Special Scope Cases
Determine whether NIS2 applies under the medium-size rule, regardless-of-size special cases, critical entity rule, and Member State registration lists.
NIS2 size-cap rule: when medium and large entities are in scope
Plain-language FAQ on the NIS2 size-cap rule: medium and large Annex I or II entities, SME thresholds, regardless-of-size exceptions, and evidence to keep.
NIS2 supply chain security program: Article 21 controls, contracts, and evidence
Build a NIS2 Article 21 supply chain security program for direct suppliers and service providers: policy, supplier criteria, contract clauses, monitoring, registry evidence, and source-linked checks.
NIS2 vs CER Directive comparison: cyber obligations and critical-entity resilience
Compare NIS2 and the CER Directive using grounded rows for scope, triggers, evidence, incident handling, supervision, and shared critical-entity work.
NIS2 vs DORA: scope, overlap, and evidence for EU cyber compliance
Compare NIS2 and DORA for EU cyber compliance: covered entities, when DORA replaces NIS2 duties for financial entities, incident reporting, evidence, and supervisory handoffs.
NIS2 vs GDPR breach reporting: EU deadlines and overlap
Compare NIS2 significant-incident reporting with GDPR personal-data-breach reporting, including scope, 24-hour and 72-hour clocks, evidence, and overlap.
NIS2 vs ISO/IEC 27001: legal duties, ISMS evidence, and reuse limits
Compare NIS2 legal obligations with ISO/IEC 27001 ISMS requirements: scope, Article 21 controls, incident clocks, SoA evidence, audits, and certification reuse.
NIS2 vs ISO/IEC 27017: legal duties, cloud controls, and reuse limits
Compare NIS2 legal obligations with ISO/IEC 27017 cloud-service controls: entity scope, Article 21 measures, incident clocks, shared responsibility, evidence, and assurance limits.
NIS2 vs NIS1: what changed in EU cybersecurity compliance
Compare NIS2 with the repealed NIS1 Directive: expanded sectors, essential and important entities, management-body duties, Article 21 controls, Article 23 reporting, and supervision.