Guide
Blog
Insights
17 November 2026

Who must register with the BSI for NIS2 and by when

Who must register with the BSI for NIS2 and by when

Reviewed by Sven Moritz · As of November 2026

The management of a group with four legal entities has checked applicability. Result: two of them are important entities under NIS2. The next question comes from accounting, where a letter with an ELSTER activation code has arrived that nobody can place. The letter belongs to the NIS2 registration, and it is the first sign that registering involves more people than the IT team.

This guide walks through registration under Section 33 of the German BSI Act (BSIG) as in force since 6 December 2025: who has to register, by when, with which details and through which route. Whether an entity is in scope at all is covered by our guide on checking applicability per legal entity. What comes after registration is ordered by the NIS2 checklist.

Key takeaways

  • Every entity in scope registers separately, particularly important and important entities as well as domain name registry service providers (Section 33(1) BSIG).
  • The deadline is three months after an entity first, or again, falls into scope. The act has applied since 6 December 2025. For everyone in scope on that day, the deadline ended on 6 March 2026.
  • The route runs through the BSI portal with the German company account, Mein Unternehmenskonto. That requires an ELSTER organisation certificate and a German tax number.
  • Five mandatory details are listed in Section 33(1) BSIG: name and legal form, contact details including public IP address ranges, sector, member states where services are provided, and the competent supervisory authorities.
  • Report changes no later than two weeks after you learn of them (Section 33(5) BSIG).
  • Failing to register, or registering late or incorrectly, carries a fine of up to 500,000 euros (Section 65(2) no. 6 and (5) sentence 1 no. 5 BSIG). The BSI can also register an entity itself (Section 33(3) BSIG).

Who has to register

Section 33(1) BSIG covers three groups: particularly important entities, important entities and domain name registry service providers. Whether an entity belongs to one of them follows from Section 28 BSIG, in other words from sector and size. The unit is the individual entity, not the group. A holding company with no activity listed in Annex 1 or 2 does not register, even if two of its subsidiaries do.

Two special cases run differently. Operators of critical facilities register under Section 8 of the KRITIS umbrella act, which Section 33(2) BSIG refers to. And certain digital providers fall under Section 34 in conjunction with Section 60(1) BSIG as well: DNS service providers, top-level domain name registries, domain name registry service providers, cloud computing and data centre service providers, content delivery network operators, managed service providers, managed security service providers, and providers of online marketplaces, online search engines and social networking platforms. They supply further details, such as their main establishment in the EU. They report changes no later than three months after the change occurred. The BSI forwards these details to ENISA, the EU cybersecurity agency, except for the IP address ranges (Section 34(3) BSIG).

Entities in Austria do not register with the BSI. As a rule, an entity falls under the jurisdiction of the member state in which it is established (Article 26(1) NIS2 Directive). In Austria, the NISG 2026 applies. A German group with an Austrian subsidiary therefore runs two procedures.

By when

Registration is due no later than three months after an entity first, or again, qualifies as particularly important or important (Section 33(1) BSIG). The BSIG entered into force on 6 December 2025. For everyone in scope on that day, the deadline ran out on 6 March 2026.

According to the BSI, 20,141 entities had registered under NIS2 by 30 September 2026. If you are not registered yet, register now. The act has no grace period. Once the deadline has passed, the BSI can request records and information (Section 33(4) BSIG), register the entity itself (Section 33(3) BSIG) and impose a fine (Section 65 BSIG). A late registration is still better than none.

The deadline keeps restarting. An acquisition, a new service or annual accounts above the threshold turn an entity that was out of scope into one that is in scope, and from that day three months run. That is why the applicability check belongs in a fixed process rather than a one-off project.

Which details the BSI asks for

Section 33(1) BSIG names five mandatory details. The portal adds details the BSI needs for classification. The table shows what is asked, where it comes from inside the company and who typically provides it.

Two details take real work. Public IP address ranges are often known only to IT operations or the provider, and for companies spread across several data centres or clouds the list is longer than expected. And the contact point needs people who respond at night and at weekends. The act sets no hours for it. But the early warning of a significant incident is due no later than 24 hours after you become aware of it (Section 32(1) no. 1 BSIG), and it goes through the same portal. A shared mailbox read on Monday mornings is not enough.

Step by step

1. Document applicability

Before anyone opens the portal, a written check exists for each entity: the activity with its type of entity from Annex 1 or 2, size figures with or without group data, result, date, approval. In the portal you select the classification as important or particularly important yourself. The check shows why that classification is right. An entity active in several sectors states every applicable type of entity.

2. The ELSTER organisation certificate

Access to the BSI portal runs through Mein Unternehmenskonto, the German cross-agency account for companies. It works with an ELSTER organisation certificate that is bound to the entity's tax number. A seat in Germany is not required, but a German tax number is. Many companies already have such a certificate, usually in accounting or with their tax advisor. If not, apply for it through Mein Unternehmenskonto. The activation data arrives by email, and the activation code also arrives by letter at the address stored for the tax number. That is usually not the IT department. The BSI states that delivery takes at least five working days. Agree in advance who receives the letter.

Each entity in scope needs its own certificates and its own registration. A group with two subsidiaries in scope goes through the route twice. The BSI recommends one certificate per person who uses the portal. Whoever registers the entity in the portal first becomes its administrator and invites further users.

3. Set up access in the BSI portal

In the BSI portal you sign in with Mein Unternehmenskonto, upload the certificate and confirm the transfer of master data. Name, legal form and address come from the certificate. If they are outdated there, correct them with ELSTER first, not in the BSI portal. Portal access on its own is not yet a NIS2 registration. It also gives you the BSI information services and the reporting channel for security incidents.

4. Submit the registration

In the NIS-2 area you select the registration and enter the details from the table above: whether the entity is a federal body, KRITIS status, NIS-2 classification, sector and type of entity, member states, supervisory authorities, contact point, contact person, IP address ranges. File the confirmation with the entity's records. Name one person who keeps the details current and a deputy. At least two people should know the access, because in an emergency the early warning within 24 hours goes through this portal.

Typical mistakes

  • Registering the group instead of each entity. The law only knows the individual entity. A collective registration through the holding company leaves the subsidiaries unregistered.
  • The certificate sits in accounting, the access in IT. If the activation letter lands in the wrong inbox or the certificate leaves the building with the tax advisor, registration stalls. Decide who holds the certificate, the password and the portal access.
  • Forgetting group data. Under Section 28(4) BSIG, data of linked enterprises generally counts. A 40-person subsidiary in a large group can therefore count as large. The exception applies only if the subsidiary is independent of the group in its IT systems and processes.
  • Stating only one type of entity. A machinery manufacturer that also runs IT systems for customers is active in two types of entity.
  • Outdated contact details. The contact point changes and nobody reports it. Section 33(5) BSIG requires the change report within two weeks, and in an emergency the BSI reaches no one.
  • Treating registration as the finish line. It is the start. From here the BSI can check whether the measures under Section 30 BSIG are in place (Sections 61 and 62 BSIG).

After registration: reporting duties and measures

Once registered, you are known to the BSI, and the duties apply in full. Significant incidents are reported in stages (Section 32(1) BSIG). The early warning is due no later than 24 hours after you become aware of the incident. The notification with an initial assessment follows no later than 72 hours after. If the BSI asks, an intermediate report is added. The final report is due no later than one month after the 72-hour notification. If the incident is still ongoing then, you first submit a progress report (Section 32(2) BSIG).

The ten areas of measures under Section 30(2) BSIG have to be implemented and documented. Management has to oversee implementation (Section 38(1) BSIG) and attend training regularly (Section 38(3) BSIG). The NIS2 checklist shows how to work through the measures. Our article on the German NIS2 implementation act explains what else the act regulates.

The registration details themselves need ongoing upkeep. In GetTeddy, the details per entity are part of the programme. AI agents compile them from the applicability check, master data and network documentation. If an assessment is uncertain, it goes to a person with an approver role in your team. The Gap Audit shows open NIS2 items per entity. Existing ISO 27001 controls carry over to Section 30 BSIG: Map once. Comply everywhere. Borderline cases, such as the IT independence of a subsidiary, are worked through with you by a dedicated compliance engineer.

The registration checklist

The checklist PDF contains the check points of this article per entity: applicability, certificate, access, details, responsibilities and the change report. We send it to you by email.

Get the checklist as a PDF by email

  • Applicability check per entity in writing, with type of entity and size figures
  • ELSTER organisation certificate available per entity; custody of certificate and password agreed
  • Access set up via Mein Unternehmenskonto in the BSI portal; two people know it
  • Details under Section 33(1) BSIG complete; for providers under Section 34 BSIG also main establishment and representative
  • Contact point for security incidents staffed at night and at weekends, with a deputy
  • Registration confirmation filed; person named for change reports within two weeks
  • Applicability check repeated after acquisitions, new services and annual accounts

FAQ

Does every entity in a group have to register separately?

Yes. Section 33 BSIG refers to the entity, meaning the individual company. Every entity in scope needs its own ELSTER organisation certificate and its own registration. Entities out of scope do not register but document their check.

By when does registration have to be completed?

Within three months after an entity first, or again, falls into scope (Section 33(1) BSIG). For entities in scope since 6 December 2025, the deadline expired on 6 March 2026. If you are not registered yet, do it immediately.

Which data does the BSI ask for?

Under Section 33(1) BSIG: name and legal form, address and contact details including public IP address ranges, sector, member states where services are provided and the competent supervisory authorities. The portal adds the NIS-2 classification, KRITIS status, a contact point and a contact person.

What happens if details change?

You report the change without undue delay and no later than two weeks after learning of it (Section 33(5) BSIG). Providers under Section 34 BSIG have three months from the change. Name a person responsible for this.

Is registration the same as certification?

No. Registration is a notification to the BSI. It does not confirm that the measures are in place. For particularly important entities, the BSI can order audits, inspections or certifications by independent bodies (Section 61(1) BSIG). For important entities, it checks when facts point to shortcomings (Section 62 BSIG).

Do suppliers that are not in scope themselves have to register?

No. Section 33 BSIG applies only to particularly important and important entities and to domain name registry service providers. A supplier that is not in scope does not register. It often receives requirements from its customers, though, because they have to address the security of their supply chain (Section 30(2) no. 4 BSIG).

Does the registration cover Austrian subsidiaries?

No. As a rule, an entity based in Austria falls under Austrian jurisdiction (Article 26(1) NIS2 Directive). It registers under the NISG 2026. The German registration does not cover it.

Where to start

Set up the list of entities with the result of the applicability check. Then find out for each entity in scope where the ELSTER organisation certificate is. This step takes longest, because the activation letter comes by post. Access and registration in the portal follow after that.

Our NIS2 page shows how GetTeddy prepares and maintains the registration details per entity. How GetTeddy works explains who does which part of the work.

Sources

How GetTeddy handles this

From the first signal to an approved early warning, within 24 hours

GetTeddy links every security event to your product inventory, checks the CRA threshold and the NIS2 and GDPR duties next to it, and drafts the early warning with everything the form asks for. The decision and the submission stay with your named people.

How GetTeddy handles this

A new framework in an afternoon, not a second program

GetTeddy keeps one model of your company and one control set. When a new framework arrives, it reads every requirement against what you already have and labels it full, partial or missing. Only the real gaps become tasks.

How GetTeddy handles this

Agents do the work. You can see every step and stop any of it.

Every result in GetTeddy carries a label: done by an agent, drafted by an agent and approved by a person, or decided by you. Drafts wait for a named approver, connections are read-only unless you allow more, and every action lands in a log your auditor can read.