GUIDE · NIS2 COMPLIANCE

ACN registration obligation under NIS2: who, when and with which data

Registration with the national authority is one of the first administrative steps under NIS2, and often the easiest to postpone. This guide explains who should assess it, which data to prepare before accessing the procedure, how to find the official deadlines and how to keep the data up to date after submission. The aim is to arrive at registration with the information already to hand.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. What registration is and what it is for

Registration is the notification through which an organisation declares to the competent national authority that it falls, or believes it falls, within the NIS2 scope. In Italy, the authority is the National Cybersecurity Agency (ACN). The procedure exists because the authority needs to know who is subject to the rules, how to contact them and which contact person to address alerts, requests and incident communications to. The important message is that registration does not replace the risk assessment.

Registration is an administrative step, not a security measure. Registering does not demonstrate compliance, and it does not replace either the classification or the adjustment plan. It should, however, be seen as the point at which your organisation presents itself formally, so the data you enter must be consistent with what you will use in the event of an incident or an inspection.

2. Who should register

The population to consider depends on classification. In general, entities that have concluded they fall within the scope as essential or important should assess registration. Even those who believe they are outside it should document the decision, because a registration that is not required is a different issue from one that was missed. The conclusion should be verified with your legal adviser, who can confirm the reading of the rules and any exceptions.

Pay attention to cases where several companies within the same group carry out different activities, or where the organisation provides services to regulated entities. In these cases, looking at the main sector is not enough: each entity may have a different position. Document for each entity the classification, the contact person and the date of the decision, so that the group's position is clear even at a later review. Ask your adviser to confirm the reading, because corporate structures make the calculation more complicated.

  • Entities that have classified their activities as essential or important.
  • Organisations that believe they fall within scope and want to clarify their position.
  • Companies belonging to a group, to be assessed one by one and not only at parent company level.

3. The data to prepare before you start

Before entering the procedure, prepare a sheet with all the required data, so you can complete it in a single session without transcription errors. The exact fields may change over time, so the official form remains the reference. The table below lists the most common categories of information and why they are needed. Check the consistency of the sheet against the company registry extract and your contract documents before completing the form, because an incorrect figure must be corrected in several places.

DataWhy it is neededWhere to find it internally
Company name and tax identifiersTo identify the organisation unambiguouslyChamber of commerce extract and corporate documents
Sector and activities carried outTo link the organisation to the scope of the rulesInternal classification document
Sites and contact detailsTo allow the authority to contact the organisationCompany master data
Contact person and deputyTo identify who receives and manages communicationsManagement decision with a written mandate
Services offered and their territorial scopeTo clarify where and for whom it operates, where relevantList of services and contracts in force
Public addresses and domainsTo allow an assessment of the exposed surfaceTechnical inventory of exposed systems

4. How to work out the deadlines

Registration deadlines are set by the authority and may be communicated through specific procedures and calendars. Do not fix dates in your internal planning without official confirmation, and do not rely on unverified news about deadlines. Check the authority's official website regularly, along with the communications you receive at the organisation's reference address. Where a date is not confirmed, write in the register that it is pending verification, rather than entering an estimated date.

In your internal deadline register, record the source of each date, the person responsible for verifying it and the date of the last check. If a deadline changes, record the update with a reference to the communication that caused it. This avoids later disagreement about which information was valid at the time. A reminder set at least two advance dates, assigned to a person rather than a group, reduces the risk of anything being forgotten.

5. Who manages access and credentials

Registration must be handled by a person authorised by management, who remains with the company even when consultants or IT suppliers change. Avoid tying access to a shared mailbox or to the personal account of an employee who might leave the organisation. Store the credentials in the company's password management system, with several authorised people able to access them, and record who used them and when.

6. Common registration mistakes

The most frequent errors are organisational, not technical. Recognising them before submission avoids later corrections and clarifications that absorb time. Each item on the list should be checked with the manager of the relevant area. The items on the list are ordered by frequency, and it is worth reviewing them before every submission, because a single error can trigger clarifications that take weeks. Every access must be recorded and revoked at the end of the assignment.

  • Entering data taken from an old document without checking it against the current company registry extract.
  • Naming as contact a person who has no mandate or will soon leave the role.
  • Registering only one company in a group without assessing the other entities.
  • Having no record of who completed the procedure and with which supporting documentation.
  • Forgetting to update the registration when sites, contacts or services change.

7. After registration

Registration does not close the obligation. It must be kept up to date in the cases the procedure provides for, and every change to the reference data should be recorded in the internal register. Keep the receipt or confirmation of the procedure together with the classification and the adjustment plan, because in an inspection the authority may ask to see the path followed. If you change IT supplier or adviser, check that the contact person and contact details remain correct.

8. How to get started

The first action this week is to prepare the data sheet. Complete the table in the previous section with the information you already have, mark what is missing and assign someone to retrieve it by the end of the month. If classification is not yet clear, take the sheet to your adviser before starting the procedure. Record the submission date and the protocol number or receipt, since these will be the reference for every subsequent communication.

Then appoint the contact person and deputy with a written mandate from management. Only then open the official procedure, complete the fields with the supporting documentation and keep everything in the adjustment folder. Before submitting, have a second person check the data, because a typo in a contact detail can delay every future communication. Also keep a copy of the data submitted.

Frequently Asked Questions

If I am not sure whether I fall within scope, should I register anyway?

There is no general rule that applies to everyone. The starting point is the classification: if it is uncertain, clarify the matter with your legal adviser and document the decision in writing. Bring the organisation's data to the assessment as well, because a decision not to register must be justified and cannot rest on habit or silence.

Who can enter the data on behalf of the company?

As a rule, the procedure is entrusted to the contact person designated by management, with support from those who know the systems and services. A consultant or IT supplier can prepare the data and assist with completion, but responsibility for the information remains with the organisation. Keep a document showing who completed what and from which source.

Do I need to update the registration if the data changes?

Yes, in the cases the procedure provides for. Changes to sites, contacts, services or contact details must be kept aligned with the authority through the officially indicated channels. Check the update methods in the authority's communications, and record every change in the internal register with the date and the reason.

Is registration enough to be compliant?

No. Registration is an administrative step that sits alongside the substantive obligations: risk management, incident notification, governance and supplier relationships. A complete registration with no adjustment plan does not demonstrate compliance. Treat it as the first piece of a broader path, to be completed with the other activities in this series.

What changes if I change IT supplier?

Changing supplier does not in itself alter the registration obligation, but it may change the technical contact and the operational contact details. Before the change, check which contacts and accesses are linked to the former supplier and update the data where necessary. The new contract should also provide for timely communication of any incidents.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →