Essential vs Important Entities Under NIS2: Who Gets Audited First

A client calls on Monday. Their regulator has not sent a letter, there has been no incident, and still the finance director wants to know: "Do we have to be ready for an inspection, or only if something goes wrong?"
The honest answer depends on one label: essential or important. The requirements of Article 21 are the same for both. The way you are supervised is not.
Essential vs important entities: the supervision gap
NIS2 splits in-scope organisations into two categories. Large entities in the Annex I sectors (energy, transport, banking, health, water, digital infrastructure and others) are generally essential. Medium-sized entities in Annex I, and entities in the Annex II sectors, are generally important. Member states can also designate specific entities as essential regardless of size.
The label decides the supervisory regime. Recital 122 of the Directive describes it plainly: essential entities get "a comprehensive ex ante and ex post supervisory regime", while important entities get "a light, ex post only" one.
In practice:
- Essential entities (Article 32) can be inspected without any trigger. Authorities can run random checks, regular audits and security scans.
- Important entities (Article 33) are supervised when there is "evidence or indication" of non-compliance, particularly with Articles 21 and 23.
Light does not mean optional. The duties are the same. An important entity that cannot show its policies after an incident or a complaint is in the same position as an essential one.
What Article 32 lets a regulator do to an essential entity
Article 32(2) lists the supervisory powers. For an essential entity, a competent authority must at minimum be able to use:
- on-site inspections and off-site supervision, including random checks;
- regular and targeted security audits, by an independent body or the authority;
- ad hoc audits after a significant incident or an infringement;
- security scans based on objective, fair and transparent risk criteria;
- requests for information, documents and evidence of implemented policies, such as results of qualified auditors.
The audited entity normally pays for audits carried out by an independent body, unless the authority decides otherwise in a substantiated case. Budget for that.
When an authority asks for information, Article 32(3) requires it to state the purpose and specify what it wants. That is useful for you: a scoped request can be answered with a scoped evidence pack.
For the evidence side, see our guide to what regulators actually ask for in supervisory audits.
What Article 33 changes for important entities
Article 33 mirrors Article 32 with two differences that matter.
First, the trigger. Authorities act "where necessary" after evidence or indication of non-compliance. A data breach notified under Article 23, a complaint, a failed supplier assessment or a news report can all qualify.
Second, the toolbox. Article 33(2) covers inspections, targeted security audits, security scans and information requests. It does not list the regular audits and ad hoc audits that Article 32(2) gives authorities against essential entities.
Do not read that as a safe harbour. Once the trigger fires, an important entity faces the same enforcement toolbox in substance: warnings, binding instructions, orders to comply with Article 21, orders to inform affected persons, and fines.
Enforcement: from warning to management bans
Article 32(4) sets out what an authority can do after finding an infringement. It includes issuing warnings, adopting binding instructions, ordering compliance with Article 21 or Article 23, ordering implementation of audit recommendations, designating a monitoring officer and ordering public disclosure of the infringement.
For essential entities there is a last step. If those measures fail and a deadline passes, Article 32(5) allows authorities to suspend a certification or authorisation temporarily, and to request a temporary ban on managerial functions for the CEO or legal representative. These measures last only until the entity complies, and do not apply to public administration entities.
Fines are set in Article 34: up to at least EUR 10 million or 2% of worldwide annual turnover for essential entities, and EUR 7 million or 1.4% for important entities, whichever is higher. Member states set the actual national amounts, so check the national law. We cover the numbers in more detail in NIS2 fines in 2026.
NIS2 Penalty Escalation — Beyond the Fine
Trigger event
Non-Compliance Detected or Incident Occurs
A supervisory authority identifies a compliance gap or an organisation fails to meet NIS2 requirements
Compliance orders with binding deadlines
Mandatory security audits at your expense
Public disclosure of violations
Binding instructions on specific security measures
Suspension of certifications or operating licences
Temporary ban on management functions for individuals
Public naming of responsible natural persons
How regulators choose: seriousness, duration, cooperation
Article 32(7) tells authorities what to weigh before enforcing. Seriousness, duration, previous infringements, damage caused, intent or negligence, mitigation measures, adherence to codes of conduct or certification, and the level of cooperation.
Serious infringements explicitly include repeated violations, failing to notify or remedy significant incidents, ignoring binding instructions, obstructing audits and providing false information.
Two of these are fully in your client's control: how fast they respond, and how well their evidence is organised. A client who answers an information request within days with a clean pack is treated differently from one who stalls.
Why the label is not always obvious
The essential/important split is not purely a size test. Article 3 and the national laws add exceptions. Some entities are essential regardless of size, and member states keep the power to designate additional entities.
It also moves with supervision. Your client may be an essential entity under one national law and an important entity under another, especially for cross-border groups. The question of which regulator applies is covered in Article 26 jurisdiction.
Where each country stands today also differs. National laws are in force in some member states, while others are still before parliament or before the Court of Justice. Check the status per client country before you promise a timeline.
NIS2 transposition by country
- AustriaIn force
- In force since October 1, 2026
- Act: NISG 2026 (BGBl. I Nr. 94/2025)
- Registration due December 31, 2026
Authority: Federal Office for Cybersecurity · Source
- NetherlandsIn force
- In force since August 15, 2026
- Act: Cyberbeveiligingswet (Stb. 2026, 187)
- Registration required, no transition period
Authority: NCSC (MijnNCSC) · Source
- LuxembourgIn force
- In force since May 10, 2026
- Act: Law of 5 May 2026
- Registration due July 10, 2026
Authority: ILR (CSSF for finance) · Source
- PolandIn force
- In force since April 3, 2026
- Act: UKSC (Dz.U. 2026 poz. 252)
- Registration due October 3, 2026
- Measures due April 3, 2027
Authority: Minister Cyfryzacji (Wykaz KSC) · Source
- PortugalIn force
- In force since April 3, 2026
- Act: Decree-Law 125/2025 (RJC)
Authority: CNCS · Source
- BulgariaIn force
- In force since February 13, 2026
- Act: Cybersecurity Act amendment (State Gazette No 17/2026)
Authority: Ministry of e-Government · Source
- MaltaIn force
- In force since January 23, 2026
- Act: S.L. 460.41
Authority: Critical Infrastructure Protection Department · Source
- SwedenIn force
- In force since January 15, 2026
- Act: SFS 2025:1506
Authority: NCSC-SE · Source
- EstoniaIn force
- In force since January 1, 2026
- Act: Cybersecurity Act (KüTS) amendment
- Registration within 3 months
Authority: RIA · Source
- GermanyIn force
- In force since December 6, 2025
- Act: NIS2UmsuCG
- Registration due March 6, 2026
- 17,729 registered by June 30, 2026
Authority: BSI · Source
- CzechiaIn force
- In force since November 1, 2025
- Act: Act No 264/2025 Coll.
- Registration within 60 days
Authority: NÚKIB · Source
- DenmarkIn force
- In force since July 1, 2025
- Act: NIS 2 Act No 434 of 6 May 2025
- Registration due October 1, 2025
Authority: Danish Agency for Societal Security · Source
- SloveniaIn force
- In force since June 19, 2025
- Act: ZInfV-1 (OG 40/25)
- Registration within 30 days
Authority: URSIV · Source
- CyprusIn force
- In force since April 25, 2025
- Act: Law 60(I)/2025
Authority: Digital Security Authority · Source
- FinlandIn force
- In force since April 8, 2025
- Act: Cybersecurity Act 124/2025
- Registration due May 8, 2025
- Measures due July 8, 2025
Authority: Traficom (NCSC-FI) · Source
- HungaryIn force
- In force since January 1, 2025
- Act: Act LXIX of 2024
Authority: SZTFH · Source
- SlovakiaIn force
- In force since January 1, 2025
- Act: Act No 366/2024 Coll.
- Registration within 60 days
Authority: NBÚ · Source
- RomaniaIn force
- In force since December 31, 2024
- Act: GEO 155/2024 (Law 124/2025)
- Registration within 30 days
Authority: DNSC · Source
- GreeceIn force
- In force since November 27, 2024
- Act: Law 5160/2024 (Gazette A' 195)
Authority: National Cybersecurity Authority · Source
- BelgiumIn force
- In force since October 18, 2024
- Registration due March 18, 2025
Authority: CCB · Source
- LithuaniaIn force
- In force since October 18, 2024
- Act: Law No XIV-2902
Authority: NCSC (MoND) · Source
- ItalyIn force
- In force since October 16, 2024
- Act: D.Lgs. 138/2024
- Baseline measures due by October 2026 (entities listed in 2025)
Authority: ACN · Source
- LatviaIn force
- In force since September 1, 2024
- Act: National Cybersecurity Law
Authority: National Cybersecurity Centre · Source
- CroatiaIn force
- In force since February 15, 2024
- Act: Cybersecurity Act (OG 14/2024)
Authority: NCSC (SOA) · Source
- FranceNot yet transposed
- Senate adopted the law on March 12, 2025
- Regulator published its framework on March 17, 2026
- Referred to the Court of Justice on July 8, 2026
- Pre-registration open
Authority: ANSSI · Source
- SpainNot yet transposed
- Draft bill approved on January 14, 2025
- Referred to the Court of Justice on July 8, 2026
- The NIS1 regime still applies
Authority: CCN / INCIBE · Source
- IrelandNot yet transposed
- Referred to the Court of Justice on July 8, 2026
- Bill not yet enacted
Authority: NCSC Ireland · Source
Status as of September 28, 2026. Other member states: see the country-by-country timeline.
What to do with this on Monday
Treat the two categories as two readiness profiles for the same standard.
- Essential clients: assume an audit can arrive unannounced. Keep a living evidence pack: approved policies, risk assessment, incident log, supplier register, training records, board approval.
- Important clients: assume the first contact is a request after something happened. Keep the same evidence, but make sure the incident reporting path under Article 23 is tested, because that is the most likely trigger.
- Both: record the category decision, the regulator and the national law in the client file, with the date you checked it.
Not sure where a client lands? Run a free NIS2 readiness scan to see their scope and the gaps that matter first.
Essential or important, the regulator expects the same thing: proof, not promises.
Still have a question?
Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.
