Registration is not the same as coverage
A company's obligations flow from the NIS2 scope provisions and national implementing law, not simply from the act of completing a form. Under Article 3(3), Member States must establish lists of essential and important entities and entities providing domain-name registration services. Article 3(4) addresses information supplied for those lists, and Member States may establish mechanisms for direct registration.
An organisation should not assume it is exempt solely because it has not received a notification or been added to a public list. Determine whether the law applies before checking the submission route.
Who supplies information for national lists
Article 3(4) sets minimum information for entities on the relevant lists: name, address and current contacts including email, IP ranges and telephone numbers, the relevant sector or subsector where applicable, and Member States where the entity provides covered services. National rules may determine the exact form and designated authority. The same article requires notice of relevant changes without delay and in any event within two weeks.
A current entity-and-services inventory makes these submissions more reliable. Designate someone to review changes to contact details, sector classification and service territories.
Additional provisions for digital and ICT providers
Article 27 creates a separate framework for an ENISA registry of specified provider categories, including DNS, cloud, managed service, managed security, data centre and certain platform services. Its information requirements are more detailed than simply entering a company name in a database. The information is generally channelled through Member States' competent authorities and single points of contact.
Providers should identify whether Article 27 applies to their defined activity and consult national submission instructions. An ordinary technology supplier should not infer coverage from its marketing description.
Finding the appropriate national process
The competent Member State depends on the entity's circumstances and Article 26 jurisdiction rules. The general establishment rule has exceptions, notably for certain digital providers and electronic communications providers. A cross-border organisation may have multiple operating entities and should identify the correct national process for each, rather than making a duplicate filing everywhere without analysis.
Consult the competent authority's current site, implementing law and registration guidance. Record the exact version and date of the guidance used.
After the initial submission
Save registration acknowledgements, submitted contact information and responsible internal owners. Add an update trigger whenever the entity changes its name, address, service categories, personnel contacts or the Member States served. Track any new national deadlines and distinguish registration records from cybersecurity control evidence.
Registration information supports supervisory contact, but it does not establish that Article 21 controls or Article 23 reporting processes have been implemented.
Questions on the text
Are all NIS2 entities required to use the same registration website?
No. National administrative mechanisms differ, while Article 27 addresses a separate ENISA registry for specified providers.
What happens if our information changes?
Article 3(4) requires relevant changes to be notified without delay and in any event within two weeks; other applicable provisions should also be checked.
Does a company need to wait to be contacted by an authority?
It should proactively check its scope and national information duties rather than assuming no obligation exists until contacted.