An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesHow NIS2 Entity Registration Works
Registration Jurisdiction / 2026-10-09

How NIS2 Entity Registration Works

A NIS2 registration workflow starts with verifying the regulated entity and its essential or important classification, identifying the Member State with jurisdiction, then submitting the data required by the relevant national mechanism. Certain digital and ICT providers must also supply Article 27 information that is passed to ENISA through national channels.

Confirm the registrant and its legal status

Identify the legal entity that provides the service, not merely the group's trading brand. Match its activity to an Annex I or Annex II entity type, assess the size-cap rule and any exceptions, and determine essential or important classification under Article 3. These conclusions support the registration data and help prevent duplicate or incomplete submissions.

A multi-entity group should maintain a separate entry for each legal entity with its own service and jurisdiction assessment.

Determine which Member State is responsible

Article 26 usually points to the Member State of establishment but contains important exceptions. Providers of public electronic communications services are generally subject to the jurisdiction of the Member States where they offer services. Certain DNS, cloud, managed-service and digital-platform providers follow the main-establishment rule in Article 26(2), or the representative framework where applicable.

Document why a particular authority and registration process were selected. Central IT management may not by itself identify the competent jurisdiction.

Prepare the information package

For Article 3 entity lists, the minimum information includes entity name, address, contact details, sector or subsector where applicable, and the Member States where covered services are provided. Where Article 27 applies, the provider must address its separate technical and organisational information requirements. Review the text and any national registration templates before gathering data.

Verify IP ranges, named contacts and service territories with technical and operational teams so the filing accurately describes what is being operated.

Submit through the recognised national channel

Use the mechanism established or designated by the responsible Member State. This may be an online register or a competent-authority process; the Directive does not prescribe one identical public portal for all national regimes. Article 27 information moves to ENISA through Member State single points of contact under the prescribed framework.

Keep confirmation numbers, filing dates and the submitted version. Avoid assuming a draft or saved portal form is equivalent to a completed submission.

Maintain and update the record

Article 3 requires entities to notify changes to listed details without delay and within two weeks at the latest. Article 27 contains separate timing requirements that should be checked for providers to which it applies. Record the owner responsible for monitoring changes to legal details, operational contacts, service categories and jurisdictions.

Reassess the registration entry after acquisitions, service expansion or a change in main establishment. Keep the register aligned with incident-response contact lists and management reporting.

Questions on the text

Can a company register before determining its classification?

It should first establish the relevant entity and legal status so its submission accurately reflects its NIS2 position.

Is ENISA the first point of contact for every registration?

No. Article 27 information is handled through relevant Member State mechanisms and forwarded to ENISA.

Should registration records be retained?

Yes. Keep dated submissions, acknowledgements and update logs as part of compliance evidence.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.