How scope and registration connect
Registration should follow a documented scope and classification decision. Under Article 3, Member States maintain lists of essential and important entities and entities providing domain-name registration services. Member States must require specified identifying and contact information, including relevant sector data and the Member States in which the entity provides covered services. National mechanisms may allow entities to register directly. Merely submitting details does not replace compliance with cybersecurity risk-management or incident-reporting duties.
The organisation should keep its underlying Article 2 scope analysis, Article 3 classification rationale and a record of the entity it actually registered. Corporate groups should avoid using the parent name as a substitute for every regulated subsidiary.
Which authority has jurisdiction
Article 26 establishes a general establishment-based jurisdiction rule and special arrangements for public electronic communications, particular digital and ICT providers and public administrations. Cloud, managed service, DNS and some platform providers generally use the main-establishment framework. An organisation with customers in several Member States should not automatically assume it must complete identical registrations in every country.
Record each relevant provider, its service category, the applicable jurisdictional rule and the authority designated under national legislation. This analysis is especially important when cybersecurity decisions, employees and service operations are distributed across borders.
The Article 27 registry and national entity lists
Article 27 provides an ENISA registry for specified digital infrastructure, ICT and digital service providers, based on information supplied through Member States' single points of contact. The registry is distinct from the national entity lists described in Article 3. Article 27 specifies additional information, such as the provider's main establishment or representative and service-related technical details.
A provider should check whether both Article 3 and Article 27 information duties are relevant, and what national submission procedure is available. The ENISA registry should not be presented as an unrestricted public self-service registration portal.
Information, updates and recordkeeping
Article 3(4) requires at least the entity name, address, current contact information, relevant sector or subsector where applicable and Member States where the covered services are provided. Article 27 has its own list for the provider categories covered there. Change-notification periods under these provisions need to be read precisely and applied alongside national rules.
Maintain a controlled register containing contact owners, submission dates, confirmation references and a review process after an address, service or contact change. Ensure incident-reporting contacts are operational rather than simply historic details.
Practical next steps for a covered entity
Confirm scope and essential or important status, identify the Member State with jurisdiction, read its current implementing law and competent-authority guidance, and determine which information duties apply. Assign an owner to complete or update submissions. Record any regulator acknowledgements and outstanding questions.
Once the registration decision is documented, connect the same entity inventory to board oversight, Article 21 cybersecurity measures and Article 23 significant-incident notification procedures.
Questions on the text
Is there one EU portal where every NIS2 company must register?
No. Member State mechanisms and Article 27's ENISA registry play different roles.
Does registration alone mean a company is compliant?
No. Covered entities also need to address substantive governance, risk-management and incident-reporting obligations.
Can jurisdiction differ across subsidiaries?
Yes. Assess the legal entities and Article 26 categories individually.