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.
HomeArticlesUpdating NIS2 Registration Information
Registration Jurisdiction / 2026-10-10

Updating NIS2 Registration Information

NIS2 entity information must remain current after the initial filing. Article 3(4) requires entities to notify changes to the specified information without delay and in any event within two weeks. Certain digital and ICT service providers must also follow the separate Article 27 information framework and any applicable national reporting mechanism.

What information must remain current

Article 3(4) requires listed entities to provide their legal name, address, up-to-date contacts including email addresses, IP address ranges and telephone numbers, relevant sector or subsector where applicable, and Member States where their services are provided. The organisation should compare its submitted details against its actual legal and operational records. A changed registered address, reporting mailbox or service footprint can make a previously correct submission unreliable. The responsible team should know which information fields were provided under the applicable national mechanism.

How the two-week rule works

Under Article 3(4), relevant changes must be notified without delay and in any event within two weeks of the date of the change. This means two weeks is a latest deadline, not a suggestion to postpone a readily available update. Different obligations can apply under Article 27 and Member State implementing law, so the legal basis for each update needs to be identified separately. A workflow should capture when the change occurred, when it was identified and when notification was actually submitted.

When Article 27 requires extra attention

Specified providers such as cloud computing services, managed services, DNS and certain digital platforms are addressed by Article 27's ENISA registry framework. That provision specifies information to be communicated through relevant Member State channels and includes its own change-notification arrangements. A provider covered by both provisions should maintain a mapped list of fields rather than assume one filing automatically updates every registry. Technical owners can help ensure network and service details remain accurate when infrastructure changes.

Build a change-management process

Assign an accountable registration owner and named deputies. Connect the review to corporate secretarial updates, acquisitions, changes in operational contacts, IP allocation changes and expansion into new Member States. A central register should show the legal entity, the original filing, the competent authority, field-level changes, the applicable deadline and supporting evidence. Before submitting, confirm the relevant authority's current channel and any authentication or supporting-document requirement.

Keep a reliable audit trail

Save copies of the previous and revised data, authority acknowledgements and a dated explanation of the change. Reconcile registration contacts with incident-response and business-continuity records so regulators can reach the right people during a significant event. Schedule periodic checks even when no business change is reported. The update record should make it possible to show exactly what changed, when it changed, who approved the correction and which authority received it.

Questions on the text

When must Article 3 registration details be updated?

Article 3(4) requires relevant changes to be notified without delay and within two weeks at the latest.

Does every provider use the same update process?

No. National mechanisms differ, and Article 27 creates additional information duties for specified providers.

Should organisations save their previous registration details?

Yes. A dated record of changes and authority acknowledgements helps demonstrate what was reported and when.

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.