NIS2

NIS2 Registration with the BSI Missed: What Applies Now and What You Need to Catch Up On

TL;DR
  • The statutory registration deadline for entities already in scope ended on 6 March 2026, three months after the German NIS2 Implementation Act entered into force on 6 December 2025. It was not extended, and the BSI itself states on its website that it has expired.
  • The BSI told industry associations it expected outstanding registrations by 31 July 2026. That was a grace period, not a change in the law. You can still register at any time, and the sooner the better.
  • A missed or incomplete registration is an administrative offence under section 65 BSIG with a maximum fine of EUR 500,000. The ranges of EUR 10 million (essential) and EUR 7 million (important entities) apply to other violations, such as missing risk management measures or missed incident reports.
  • Plan one to two weeks for catching up. The bottleneck is the ELSTER organisation certificate issued through Mein Unternehmenskonto, whose activation letter regularly takes at least five working days.
  • You must update changes to your registration data in the BSI portal without undue delay and within two weeks of becoming aware of them at the latest. If you are not in scope, you do not have to register, but you should document the assessment in writing.

You are in scope of NIS2 and have not registered with the BSI, or you are not sure whether you had to? You are in good company: of roughly 29,500 entities the BSI estimates to be subject to registration, only about 11,500 had registered by the statutory deadline in March. This article explains what has applied since, what you actually risk, and how to catch up on registration within a few days without panicking.

What is the situation after the registration deadline?

The NIS2 Implementation Act fundamentally rewrote the German BSI Act (BSIG) and entered into force on 6 December 2025. Since then, essential and important entities have to register with the BSI. Section 33(1) BSIG sets the deadline: at the latest three months after an entity first qualifies as essential or important. For companies already in scope when the act took effect, that deadline expired on 6 March 2026.

What about the grace period until 31 July 2026?

The BSI portal went live on 6 January 2026. Even so, a large share of the obligated entities were missing at the deadline. According to BSI figures reported by heise in June 2026, just under 18,500 entities had registered by the end of May. In a letter to industry associations, the agency asked them to remind their members of the obligation once more and said it expected all outstanding registrations by 31 July 2026 at the latest. In exceptional cases it would allow six weeks after open questions have been clarified.

Legally, this is not an extension. The law did not change, and the statutory deadline remained 6 March. The BSI merely announced that it would not pursue late registrations for the time being. I could not find a BSI publication of its own on this; the source is the reporting on the letter to the associations. On its topic page for NIS-2-regulated companies, the BSI itself writes: "The statutory registration deadline has already expired."

As of October 2026, the grace period is history as well. Both dates have passed, the obligation remains, and you can fulfil it at any time.

Date Event
6 December 2025 NIS2 Implementation Act enters into force
6 January 2026 BSI portal opens for registration
6 March 2026 Statutory three-month deadline for entities already in scope expires
End of May 2026 Just under 18,500 entities registered (BSI figure as reported by heise)
31 July 2026 Date the BSI named to associations for outstanding registrations
Today Obligation applies, catching up is possible at any time

And if you only came into scope later?

The three-month period starts for each entity individually, from the moment it qualifies "for the first time or again" as essential or important. If your company grows beyond 50 employees during the year, acquires another company or enters a new line of business in one of the NIS2 sectors, a new deadline starts. Registration is therefore not a one-off project from spring 2026 but an obligation you re-check whenever your size or activities change.

Who has to register and who does not?

The obligation applies to essential and important entities and to domain name registry service providers. Section 28 BSIG determines which category fits you, and the answer depends on two questions: does your activity belong to an entity type in Annex 1 or 2 of the act, and how large are you?

Category Thresholds Sectors
Essential entity at least 250 employees, or more than EUR 50 million annual turnover and at the same time more than EUR 43 million balance sheet total Annex 1 (for example energy, transport, health, digital infrastructure)
Important entity at least 50 employees, or annual turnover and balance sheet total each above EUR 10 million Annex 1 and 2 (additionally, for example, manufacturing, chemicals, food, waste)
Operators of critical facilities, qualified trust service providers, TLD registries, DNS service providers regardless of size (essential) see section 28 BSIG

An example: a mechanical engineering company with 110 employees and EUR 28 million in turnover falls into the manufacturing sector in Annex 2. It exceeds the 50-employee threshold and is therefore an important entity. It has to register even if it never received a letter from the BSI. The BSI does not contact anyone on its own; the obligation arises from the law alone. How NIS2 affects mid-sized companies in general is covered elsewhere, and manufacturers get their own look at the obligations of mechanical engineering and manufacturing companies.

What to watch for when classifying your company

Three points most often lead to misjudgements in practice:

The entity type counts, not just the sector. A logistics company belongs to the transport sector, but not every one of its activities is an entity type named in Annex 1. Whether you are covered depends on the specific activity. Business activities that are negligible compared with the overall business can be disregarded under section 28(3) BSIG.

Corporate groups. You determine headcount, turnover and balance sheet total under the EU Commission's SME recommendation (2003/361/EC). You do not add the data of partner or linked enterprises if your company is demonstrably independent of them with regard to the nature and operation of its IT systems, components and processes. The burden of proof is yours. Each entity in scope registers individually.

No exemption on request. According to the BSI FAQ, entities have no way to apply for an exemption decision. You either fall under the definition or you do not.

The BSI tool for the applicability assessment

The BSI provides an anonymous applicability check that gives an initial assessment through a questionnaire. The agency explicitly stresses that the result is not legally binding and has no indicative effect in proceedings. Treat it as orientation, not as proof. This is not legal advice; clarify doubtful cases with your legal department or a law firm.

What do you risk if you are not registered?

The honest answer has two parts: the statutory range is high, but the figures often quoted belong to different violations than a missing registration. And as of October 2026, I could not find any documented reports of actual BSI fining practice on registration.

Which fines apply to a missing registration?

Section 65(2) no. 6 BSIG lists as an administrative offence that someone, contrary to section 33(1) or (2), submits a piece of information "not, incorrectly, incompletely or not in time". The maximum fine for this is EUR 500,000 under section 65(5). This also covers change notifications you send too late. For negligent conduct, the maximum is usually halved under general administrative offences law (section 17(2) OWiG).

The large figures sit elsewhere:

Violation Range under section 65 BSIG
Registration or change notification missing, incomplete or late (section 33) up to EUR 500,000
Risk management measures under section 30 not taken, reports under section 32 omitted, BSI orders disregarded up to EUR 10 million (essential) or EUR 7 million (important entities)
Total turnover above EUR 500 million up to 2 percent (essential) or 1.4 percent (important entities) of total turnover

The percentages therefore only apply to companies with more than EUR 500 million in total turnover. For a company with 100 employees, the euro cap is what matters. The BSI FAQ names a blanket range of EUR 7 to 10 million or 1.4 to 2 percent for the registration obligation. In the statutory text, I only find the allocation as described above, so check it yourself if it matters. We have broken down the NIS2 fines overall and their structure in a separate article.

The classification matters: these are maximum amounts. The amount of an actual fine depends on severity, duration and fault. How the BSI proceeds in practice is not documented as of October 2026. If you plan seriously, you plan with the range, not with the worst case and not with leniency.

What else can the BSI do besides fines?

Section 33 BSIG gives the agency two further levers. Under paragraph 3, it can carry out the registration itself, in agreement with the competent supervisory authorities, if the obligation is not fulfilled. That sounds convenient, but it means someone else decides on your data and your classification. Under paragraph 4, the BSI can demand records and information if facts justify the assumption that you are not meeting your registration obligation. You then have to be able to show how you arrived at your classification.

What does this mean for the management?

Section 38 BSIG obliges the management of essential and important entities to implement the risk management measures under section 30 and to monitor their implementation. Those who breach these duties are liable to their own entity for culpably caused damage under the applicable company law. Management members must also take part in training regularly.

Strictly speaking, section 38 concerns the risk management measures and not the registration directly. But whoever overlooks the registration usually has no picture yet of what is open in risk management, incident reporting and training. And that is where a formal omission can turn into a liability issue. Even as an IT manager below board level, you should know your personal liability risks and clarify responsibilities in writing.

How do you catch up on NIS2 registration with the BSI?

The good news: registration is not a major project. The effort is half a day to a full day of actual work, plus waiting for the certificate letter. The plan below assumes you start today.

Step 1: Clarify and record your applicability (day 1)

Check under section 28 BSIG which category you fall into, and record the result in writing before you register. The order matters: the classification has to precede the registration because you have to state sector and entity type in the portal. Use the template in the section further below.

Step 2: Apply for Mein Unternehmenskonto and the ELSTER organisation certificate (day 1)

This is the bottleneck, so start with it. To log in to the BSI portal you need an ELSTER organisation certificate, which you request through Mein Unternehmenskonto (MUK) at mein-unternehmenskonto.de. A German tax number is required. You receive the activation data by email, and an activation letter is also sent by post to the company. According to the BSI, delivery regularly takes at least five working days. This means the organisation certificate, not your personal ELSTER certificate for your tax return.

If an organisation certificate already exists because your accounting department or tax adviser uses one, clarify internally who may administer it. It should not sit on a single employee's laptop but where a deputy can reach it too.

Step 3: Name the responsible people (day 1 to 3)

While the letter is on its way, you decide who the NIS-2 contact point is, who the contact person is and who maintains the data in future. More on this in the section on responsibilities.

Step 4: Compile the data (day 2 to 5)

Collect all information required under section 33(1) BSIG, ideally in one data sheet. The table in the next section shows what you need and where to get it. The most time-consuming item is usually the public IP address ranges, because IT has to gather them from firewalls, provider contracts and cloud accounts.

Step 5: Register in the BSI portal (once the certificate arrives)

You open portal.bsi.bund.de and log in via "Mit MUK anmelden". There you upload the ELSTER organisation certificate, enter its password and confirm the data pre-filled from the certificate. Then you switch to the NIS-2 area and enter the details. The BSI has published an illustrated step-by-step guide for this, which you should keep open alongside.

Step 6: Secure the confirmation (same day)

Creating an account is not yet a registration. Only submitting the data fulfils the obligation. After sending, save the confirmation, ideally as a PDF or screenshot with the date, and file it together with the data sheet in your ISMS documentation. If the BSI asks later, it is your proof.

Step 7: Set up the change process (within one week)

Add the two-week rhythm for changes to your processes before you tick the topic off. What that looks like is described in the section on change notifications below.

Which data do you need for the registration?

The mandatory information is in section 33(1) BSIG, and the portal form asks for a few practical details on top. The table below organises both, with a note on who in the company supplies each item.

Item Content Who supplies it
Name of the entity Company name with legal form, commercial register number if applicable Management, legal department
Address and contact details Address, email address, phone numbers Administration
NIS-2 contact point Functional mailbox (not tied to a person) and phone number in international format Security officer, IT management
Contact person Person who can provide technical information and knows about their appointment Security officer, IT management
Public IP address ranges Static ranges in CIDR notation for IPv4 and IPv6 IT, network
Sector, industry, entity type Classification under Annex 1 or 2 BSIG Security officer with management
Member states EU countries in which you provide services of the relevant entity type Sales, management
Competent supervisory authorities Federal and state authorities for the activity Security officer, business unit
Website Optional Marketing

Two practical tips. First: use a functional mailbox such as nis2@yourcompany.com for the contact point, read by several people. In its guide, the BSI recommends a functional mailbox rather than a personal address, and availability is preserved when the contact person is on leave or leaves the company. Second: the contact point is the address at which the BSI reaches you. It should therefore also be staffed when a security incident occurs and the NIS2 reporting deadlines of 24 and 72 hours are running.

Who in the company is responsible for the registration?

The law addresses the obligation to the entity, not to a role. In practice you need a clear split, otherwise the registration ends up stuck between IT, the legal department and management, as in many companies.

Role Task
Management Bears responsibility, signs off the applicability assessment, decides on the contact point
Security officer or IT management Carries out the registration, maintains contact point and data sheet
IT / network Supplies the public IP address ranges and reports changes to them
Accounting / tax adviser Provides the ELSTER organisation certificate or helps with the application
Legal department or law firm Clarifies doubtful cases in classification, especially in corporate groups
Deputy Second person who can enter changes in the portal

The deputy is important. If maintaining the data lives in a single head, the two-week rhythm fails at the first holiday or departure.

What applies after registration? Changes within two weeks

Registration is not a document you file once. Section 33(5) BSIG requires you to notify the BSI of changes to the submitted information without undue delay, and within two weeks at the latest from the moment you became aware of the change. The BSI expressly points this out in its portal guide. A late notification falls under the same administrative offence as a missed registration.

Which events trigger a change notification?

  • New legal form, change of name or new commercial register number
  • New address, new phone numbers or a new functional mailbox
  • Change of contact person or contact point
  • New, changed or released public IP address ranges, for example after a provider change or a cloud migration
  • Change in sector or entity type classification, for example through a new line of business
  • New EU member states in which you provide services
  • Change of the competent supervisory authorities

So that the deadline does not fail on organisation, the following measures anchor the process: add "check BSI registration" to your change process (new provider, new domain, new site, staff change in the contact point). Also compare the data against reality once a quarter, so nothing slips through that nobody recognised as a change.

Special case: operators of critical facilities

Operators of critical facilities count as essential entities, but they register their facilities under section 33(2) BSIG via the KRITIS Umbrella Act (section 8 there). For critical components, a transitional provision in section 66 BSIG additionally applies, tied to a regulation under the KRITIS Umbrella Act that is still outstanding. If this applies to you, the obligations are described in connection with the KRITIS Umbrella Act, and the guide in the BSI portal takes precedence for you.

What comes after registration?

Registration is the lowest hurdle of NIS2. It matters because it makes you visible in the supervisory system, but it says nothing about whether you meet the substantive obligations: risk management measures under section 30 BSIG, the reporting process under section 32 with an early initial report within 24 hours, a report within 72 hours and a final report one month after the report at the latest, and training for the management. The NIS2 checklist helps you determine where you stand on these obligations. Use the momentum of registration to name the gaps right away instead of discovering them at the first BSI inquiry.

Evidence is getting closer too: operators of critical facilities must prove the implementation of the measures under section 39 BSIG every three years. How you prove the effectiveness of your measures to the BSI in general is a topic of its own, covered under NIS2 evidence and audits. On a tight budget, it pays to tackle the reporting process and management training first.

Not in scope? How to document the applicability assessment

If you conclude that you do not fall under NIS2, you do not have to register. The law provides for no negative notification to the BSI and no application for a confirmation. What you do need is a document showing that you examined the question seriously. There are two reasons for this. Under section 33(4) BSIG, the BSI can demand records if facts justify the assumption of a breach. And your result has an expiry date: it only holds as long as your size and activities do not change.

A usable assessment record contains seven items:

  1. Reference date and assessor. Date of the assessment, who carried it out, who signed it off.
  2. Figures. Employees, annual turnover and balance sheet total at the reference date, determined under the EU Commission's SME recommendation, with the source (payroll, annual accounts).
  3. Group view. Whether partner or linked enterprises are attributed, and if not, the reasoning for the independence of the IT systems and processes.
  4. Activities. Which business activities you carry out and whether they belong to an entity type in Annex 1 or 2 BSIG, each with reasoning. Also the use of the negligibility rule (section 28(3) BSIG), if you rely on it.
  5. Result. "Not in scope" or "in scope as important / essential entity" with reference to the sections.
  6. Attachment. Result of the BSI applicability check as a printout or screenshot, further advice received. The tool counts as orientation, not as evidence.
  7. Review date. Date of the next assessment, at least annually, and the triggers for an unscheduled one: growth beyond 50 employees or EUR 10 million turnover, an acquisition, a new line of business, a changed group structure.

Have management sign off the record and store it where your other ISMS documents live. In ISMS Lite you can, for example, create the review date as a measure with an owner and a due date so that it shows up on the deadline dashboard. And remember: even if you are not in scope yourself, customers or suppliers may place requirements on you through the supply chain that follow NIS2.

Checklist: Catching up on NIS2 registration

Clarify applicability

  • Employees, annual turnover and balance sheet total determined at the reference date
  • Activities mapped to the entity types in Annex 1 and 2 BSIG
  • Group view checked and justified
  • Result (in scope or not) recorded in writing and signed off by management
  • Date from which applicability exists recorded

Prepare access

  • German tax number of the company at hand
  • ELSTER organisation certificate requested through Mein Unternehmenskonto (the letter takes at least five working days)
  • Administrator and deputy for the certificate defined
  • Certificate password stored in the password manager

Compile the data

  • Company name, legal form and commercial register number
  • Address, email address and phone numbers
  • Functional mailbox set up for the NIS-2 contact point
  • Phone numbers in international format
  • Contact person named and informed of the appointment
  • Public IP address ranges (IPv4 and IPv6) identified from firewall, provider and cloud accounts
  • Sector and entity type determined
  • EU member states of service provision listed
  • Competent federal and state supervisory authorities identified

Register and document

  • Logged in to the BSI portal with the organisation certificate
  • Data submitted (not just the account created)
  • Confirmation with date saved as PDF or screenshot
  • Data sheet and confirmation filed in the ISMS documentation

Stay on top of it

  • Change process with the two-week deadline documented
  • Triggers for changes (provider, site, legal form, staff) anchored in change and onboarding processes
  • Quarterly comparison of registration data in the calendar
  • Deputy named for maintenance in the portal
  • Gaps in risk management, reporting process and management training recorded and given due dates

Common mistakes in NIS2 registration

Waiting to see whether the BSI gets in touch. The BSI does not write to companies. The obligation arises with the law, and the deadline runs from the moment you are in scope, without anyone confirming it.

Confusing the account with the registration. Creating Mein Unternehmenskonto and the portal account is not enough. Only the data submitted in the NIS-2 area fulfils the obligation. Secure proof of the submission.

Basing the applicability assessment on the BSI tool. The tool is anonymous, non-binding and, according to the BSI, has no indicative effect. Your own reasoned and signed-off assessment is still needed, even if the tool shows "not in scope".

Entering contact data tied to a person. If you put the contact point on the extension and mailbox of a single person, you are unreachable during holidays, illness or resignation. Use a functional mailbox and a deputy.

Forgetting changes. Provider changes, new IP ranges after a cloud migration or the departure of the contact person happen in day-to-day business, and nobody thinks of the registration. Without a firm anchor in the change process, the two-week deadline is already missed by the time someone notices.

Conclusion: Catching up is quick, staying on top of it is the real work

The deadline has passed, but registration can be caught up on at any time, and with a clean data sheet it is done in a day. Request the ELSTER organisation certificate today, because the postal route sets the schedule, and use the waiting time for the data sheet and responsibilities. If you then want to work through the substantive obligations systematically, you can select NIS2 as a framework in ISMS Lite and track measures with owners and due dates on the deadline dashboard.

Further reading

Stay on top of it after registration

You register yourself in the BSI portal. Afterwards, ISMS Lite helps you select NIS2 as a framework, assign measures with owners and due dates, and keep the deadlines in view on the dashboard.

Install now