What is the first practical step in a NIS2 applicability test?
Identify the legal entity and map each service or activity to Annex I or Annex II. Only then apply the , size-independent triggers, and Article 3 essential or important classification.
Decide whether an entity, service, or planned EU operation falls within NIS2 before assigning cybersecurity and reporting work.
Use the test to map Annex I or Annex II sector coverage, size and size-independent triggers, essential or important classification, Member State jurisdiction, and the evidence needed for review.
Test one legal entity and service at a time. Confirm that the activity matches an Annex I or Annex II entity type in the Union, calculate whether the entity is medium-sized or larger, check every size-independent path, and then classify it as essential or important. Also identify the Member State with jurisdiction and whether an equivalent sector-specific EU law displaces only the overlapping NIS2 provisions. Keep the result as a cited scope record for registration, controls, reporting, and management oversight.
Start with the legal entity and the service or activity being tested. NIS2 applies to public or private entities of a type listed in Annex I or Annex II that provide services or carry out activities within the Union and meet the applicable size or special-case criteria.
Do not classify only by brand, group name, or product category. The record should identify the contracting or operating entity, the Member States where the service is provided, the sector and subsector, and the network and information systems that support the service.
Sources (2)
Primary legal source for Article 2 scope, Annex I and Annex II activities, and entity classification under Article 3.
provide their services or carry out their activities within the Union
Commission overview used for the widened sector scope and the practical distinction between essential and important entities.
wider scope, clearer rules and stronger supervision tools
The sector map is the core of the applicability test. Annex I covers sectors of high criticality such as energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management, public administration, and space. Annex II covers other critical sectors such as postal and courier services, waste management, chemicals, food, manufacturing categories, digital providers, and research organisations.
Use the defined entity types inside each annex, not only the sector heading. For example, the digital-infrastructure section distinguishes DNS service providers, TLD registries, cloud computing service providers, data centre service providers, content delivery network providers, trust service providers, and public electronic communications providers.
Sources (2)
Annex I and Annex II provide the sector, subsector, and type-of-entity lists used to decide whether the activity is potentially in scope.
SECTORS OF HIGH CRITICALITY
Commission FAQ summarises the Annex I and Annex II sector coverage and explains that NIS2 expands the prior NIS framework.
Sectors of high criticality
For most Annex I and Annex II entity types, Article 2 starts with the : the Directive applies where the entity qualifies as a medium-sized enterprise under the Annex to Commission Recommendation 2003/361/EC, or exceeds the ceilings for medium-sized enterprises, and provides the relevant services or activities in the Union.
A medium-sized enterprise does not qualify as micro or small, has fewer than 250 staff and annual turnover not above EUR 50 million and/or an annual balance-sheet total not above EUR 43 million. Calculate staff as . Add partner-enterprise data in proportion to the ownership or voting interest and add 100% of linked-enterprise data unless already consolidated. Crossing or falling below a ceiling normally changes SME status only after two consecutive accounting periods. NIS2 disapplies the Recommendation's Article 3(4) public-body ownership rule, so public ownership at or above 25% does not by itself prevent use of the SME calculation for this test.
The size calculation is not the end of the test. Article 2 applies regardless of size to listed cases, including providers of public electronic communications networks or publicly available electronic communications services, trust service providers, TLD registries and DNS service providers, sole providers of an essential service in a Member State, entities whose service disruption could have specified public-safety, systemic, or national or regional importance effects, certain public administration entities, critical entities under Directive (EU) 2022/2557, and entities providing domain name registration services.
Sources (3)
Article 2 provides the size-cap rule and the size-independent applicability cases that must be tested before excluding an entity.
Regardless of their size
Defines the staff and financial ceilings, annual work units, reference period, two-accounting-period rule, and partner and linked-enterprise aggregation used by the NIS2 size test, subject to NIS2's express disapplication of Article 3(4).
medium-sized enterprises
Commission FAQ explains that NIS2 introduced a clear size threshold while leaving Member States discretion to identify smaller entities with a high security-risk profile.
clear size threshold rule
After scope is established, Article 3 determines whether the entity is essential or important. Essential entities include large Annex I entities, qualified trust service providers, TLD registries, DNS service providers, medium-sized providers of public electronic communications networks or publicly available electronic communications services, central government public administration entities, Member State-identified essential entities under specific Article 2 triggers, critical entities under the CER Directive, and, where a Member State so provides, entities previously identified as operators of essential services.
Important entities are the in-scope Annex I or Annex II entities that do not qualify as essential. Member States may also bring local public administration and education institutions into scope. Article 2 excludes specified public-administration activity in national security, public security, defence, and law enforcement, and permits narrower exemptions for certain entities or services connected to those activities. If facts or national-law choices are missing, classify the test as blocked rather than forcing an essential or important label.
Sources (2)
Article 3 defines essential and important entities and Article 2 provides exclusions and special application rules.
shall be considered to be essential entities
Commission FAQ explains the replacement of the NIS1 OES/DSP distinction with essential and important entity categories.
divided into two categories: essential and important entities
The applicability record should identify the authority path before implementation. As a rule, an entity falls under the jurisdiction of the Member State where it is established. Article 26 instead uses the service Member State for public electronic communications providers, the establishing Member State for public administration, and the Union main establishment for the listed cross-border digital and ICT providers. A listed provider with no Union establishment must designate a representative in a Member State where it offers services.
Article 3 required Member States to establish lists of essential and important entities and domain name registration service providers by 17 April 2025 and to review them at least every two years. Article 27 separately required specified digital and ICT providers to submit registry information by 17 January 2025. Article 3 changes are due without delay and within two weeks; Article 27 changes are due without delay and within three months. National mechanisms and instructions determine the actual submission route.
Finally, apply Article 4 provision by provision. If a sector-specific Union act imposes risk-management measures or significant-incident notification requirements that are at least equivalent in effect, the corresponding NIS2 provisions and their supervision and enforcement provisions do not apply to the covered entity. NIS2 continues to apply to entities or duties the sector-specific act does not cover.
Identify the legal entity and map each service or activity to Annex I or Annex II. Only then apply the , size-independent triggers, and Article 3 essential or important classification.
Yes. Article 2 applies regardless of size to several categories, including certain public electronic communications providers, trust service providers, TLD registries, DNS service providers, critical entities under Directive (EU) 2022/2557, entities providing domain name registration services, and other listed special cases.
Keep the legal entity, service, Member States, exact Annex row, , turnover and balance-sheet data, partner and linked-enterprise calculation, size-independent trigger analysis, essential or important classification, Article 26 jurisdiction path, any Article 4 sector-specific-law analysis, registration facts, source URLs, reviewer, approver, and reassessment triggers.
Sources (3)
Article 3 supports the evidence fields for Member State lists, entity information, sector and subsector data, service Member States, and update duties.
establish a list of essential and important entities
Commission FAQ explains jurisdiction rules and exceptions for public communications, public administration, and certain cross-border digital and ICT entities.
under the jurisdiction of the Member State
Implementation source for technical and methodological cybersecurity risk-management requirements relevant after covered digital-sector entities pass the applicability test.
technical and methodological requirements
Sorena can help convert the NIS2 applicability facts on this page into cited intake questions, owner assignments, authority-registration evidence, and reassessment workflow.
Ask questions tied to cited sources about NIS2 scope, Annex I and II sectors, size-cap rules, essential or important classification, jurisdiction, and evidence.
Review a NIS2 applicability test, registration evidence gap, or next-step workflow with Sorena.
"high common level of cybersecurity across the Union"
"provide their services or carry out their activities within the Union"
"SECTORS OF HIGH CRITICALITY"
"Regardless of their size"
"shall be considered to be essential entities"
"establish a list of essential and important entities"
"medium and large-sized companies in selected sectors"
"Sectors of high criticality"
"clear size threshold rule"
"divided into two categories: essential and important entities"
"under the jurisdiction of the Member State"
"medium-sized enterprises"
"18 critical sectors across the EU"
"wider scope, clearer rules and stronger supervision tools"
"technical and methodological requirements"
"Technical Implementation Guidance"
NIS2 compliance calendar for EU transposition, Article 3 and 27 registration updates, Article 23 incident reports, technical measures, and the 2027 review.
Map NIS2 Annex I and Annex II sectors, entity types, size-cap rules, and essential versus important entity classification with official EU sources.
Build a NIS2 Article 21 control baseline from the Directive's minimum cybersecurity risk-management measures, proportionality test, supplier duties, and evidence expectations.
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.
Assess NIS2 Article 21 cybersecurity risk-management gaps by mapping current controls to Article 21(2), ownership, evidence, supplier risk, and management review.
Map NIS2 Article 23 reporting duties for significant incidents: 24-hour early warning, 72-hour notification, intermediate reports, final report, recipients, and evidence.
This NIS2 compliance checklist helps confirm scope, entity classification, management-body duties, Article 21 controls, Article 23 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.
Build an operational NIS2 country matrix for applicable national law, competent authorities, registration, incident portals, local implementation deltas, evidence, and review dates.
Classify whether an EU service is out of scope, an important entity, an essential entity, or needs national-authority review under the NIS2 Directive.
Compare NIS2 essential and important entities by scope, Article 21 and 23 duties, Article 32 and 33 supervision, evidence, jurisdiction, and penalties.
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 FAQ on entity scope, essential and important classification, Article 21 measures, Article 23 reporting, national implementation, and evidence.
Triage a possible NIS2 significant incident by recording awareness time, severity, impact, authority route, recipient communications, and Article 23 reporting clocks.
Build a NIS2 Article 23 incident reporting workflow with significance triage, CSIRT or authority notification steps, recipient communication, cross-border checks, and evidence records.
A guide to NIS2 Article 20 management body accountability: approval of Article 21 measures, oversight, national liability rules, training, reporting lines, and evidence.
Track NIS2 national transposition with Commission country pages, Article 41 dates, reasoned-opinion flags, source wording, authority contacts, and legal review triggers.
NIS2 Article 34 fine levels, calculation factors, enforcement measures, GDPR overlap, and national-law checks for essential and important entities.
Map NIS2 Article 3 entity lists, Article 27 registry submissions, competent authorities, national filing routes, required data, and change-notification deadlines.
Map NIS2 requirements for essential and important entities: scope classification, management-body duties, Article 21 cybersecurity measures, Article 23 incident reporting, and evidence records.
Apply the NIS2 medium-size test, group-data rules, regardless-of-size cases, exclusions, and essential-versus-important classification.
Apply NIS2 Article 21 to direct suppliers and service providers, and distinguish its general duty from Regulation 2024/2690's digital-entity controls.
Compare NIS2 and the CER Directive using cited rows for scope, triggers, evidence, incident handling, supervision, and shared critical-entity work.
Compare NIS2 and DORA for EU cyber compliance: covered entities, when DORA replaces NIS2 duties for financial entities, incident reporting, evidence, and supervisory handoffs.
Compare NIS2 significant-incident reporting with GDPR personal-data-breach reporting, including scope, 24-hour and 72-hour clocks, evidence, and overlap.
Compare NIS2 legal obligations with ISO/IEC 27001 ISMS requirements: scope, Article 21 controls, incident clocks, SoA evidence, audits, and certification reuse.
Compare NIS2 legal obligations with ISO/IEC 27017 cloud-service controls: entity scope, Article 21 measures, incident clocks, shared responsibility, evidence, and assurance limits.
Compare NIS2 with the repealed NIS1 Directive: expanded sectors, essential and important entities, management-body duties, Article 21 controls, Article 23 reporting, and supervision.
NIS2 scope answer for managed service providers and managed security service providers, including service definition, size-cap checks, entity status, and jurisdiction evidence.
Under NIS2 Article 23, covered essential and important entities submit an early warning within 24 hours of becoming aware of a significant incident.
NIS2 incident-notification deadline, required initial assessment, evidence, follow-up, and the 24-hour trust-service-provider exception.
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.
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.
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.