IMScollect
On a cream-coloured work surface lie an unlabelled registration checklist, a calendar, a folder and an orange check card.
Blog

Missed the NIS2 registration deadline? What to do now

Missed the NIS2 registration deadline? How SMEs check whether they are in scope, complete BSI registration late and manage the further obligations.

ISO 27001Legal requirementsRisks & opportunitiesEmergencies & business continuity
Philipp Kappe

Philipp Kappe

Founder of IMScollect

Published 3 September 20267 min read
Contents

For entities that already qualified as important or essential entities when the new German BSI Act (BSIG) entered into force on 6 December 2025, the three-month registration deadline under Section 33(1) BSIG generally ended on 6 March 2026. The Federal Office for Information Security (BSI) calls on affected entities that have not yet registered to register immediately in the BSI portal.

Entities that only fall within the statutory criteria for the first time or again at a later date, by contrast, have an individual three-month deadline from that point. The phrase “missed deadline” therefore does not apply to all companies on the same calendar day.

Waiting is not a sensible option. In practice, you should first check in a traceable way whether you are in scope and then complete the registration late using the current BSI procedure. The further statutory obligations apply in parallel with registration.

Registration deadline under Section 33 BSIG missed: what to do now

Failure to register, or incomplete or late registration, may be punished as an administrative offence. Under Section 33(3) BSIG, the BSI can also carry out a missing registration itself. This removes neither the original registration obligation nor a breach of the deadline that has already occurred.

The following practical sequence is recommended for catching up. Not every organisational step is a separate statutory obligation in its own right:

  1. Check scope and classification under Section 28 BSIG and document the assessment internally.
  2. Clarify responsibility, deputies and access to the BSI portal.
  3. Obtain an ELSTER organisation certificate or check existing access.
  4. Complete the registration with the information required by law.
  5. File the registration confirmation and the information submitted for your internal records.

The BSI provides a digital scope check. Its result is an initial assessment and is expressly not legally binding. For borderline cases, complex groups of companies or unclear sector allocation, a legal review is advisable.

Five steps to a completed late registration

1. Check scope and classification

Classification as an important or essential entity is based on Section 28 BSIG and the types of entity listed in Annexes 1 and 2. In addition to activity and size criteria, special cases, exceptions and sector-specific rules must be checked.

Classification is carried out for each individual entity. When calculating headcount, annual turnover and annual balance sheet total, Section 28(4) BSIG generally requires the rules for partner and linked enterprises from Recommendation 2003/361/EC to be taken into account as well. A statutory exception may apply if the entity is independent of its partner or linked enterprises with regard to its information technology systems, components and processes.

A blanket classification of the entire group is therefore just as inadequate as an assessment that completely ignores group relationships.

For the internal file, we recommend at least:

  • legal entity assessed
  • field of activity and sector concerned
  • size criteria used
  • result of the BSI scope check
  • internal or external legal assessment
  • date and responsible person

2. Clarify ELSTER access and responsibility

Under the procedure currently specified by the BSI, access to the BSI portal requires an ELSTER organisation certificate. This is applied for via the digital service “Mein Unternehmenskonto” (My Company Account), stating a German tax number.

The statutory registration obligation itself arises from Section 33 BSIG. The details of the procedure are specified by the BSI under Section 33(6) BSIG.

Before submitting a new application, check:

  • Does an organisation certificate already exist?
  • Who is allowed to use it for registration?
  • Is access available technically and organisationally?
  • Are deputies and secure storage arranged?

Clarify responsibility, deputies and access early. If the certificate is missing, the application should be started immediately.

3. Submit the information required by law

For a registration under Section 33(1) BSIG, the following information in particular must be submitted in full:

  • name of the entity, including legal form and, where applicable, commercial register number
  • address and current contact details, including email address, telephone numbers and public IP address ranges
  • relevant sector and, where applicable, industry under Annex 1 or 2 BSIG
  • Member States of the European Union in which the entity provides the relevant services
  • competent federal and state supervisory authorities

Further input fields may result from the current BSI portal and from special rules for certain types of entity. Before submitting, check the current mandatory fields and procedural notes from the BSI.

4. Secure the registration evidence internally

For your internal records, the registration confirmation, the information submitted and, where applicable, the internal approval should be filed in a traceable way. Section 33 BSIG does not prescribe any particular form of filing for this.

Useful items are:

  • registration confirmation
  • documented information submitted
  • date of submission
  • responsible person
  • access used
  • open queries from the BSI

The documents should not be kept exclusively in a personal mailbox. Scope and retention depend on risk and on internal and contractual requirements.

5. Report changes on time

If information subject to registration changes, the changes must, under Section 33(5) BSIG, generally be submitted to the BSI without undue delay, and at the latest within two weeks of becoming aware of them.

A permanently responsible internal person and a deputy therefore make organisational sense. However, the internal allocation of tasks shifts neither the statutory obligations away from the entity nor the obligations under Section 38 BSIG away from its management body.

Registration done: these obligations apply regardless

Registration is only one of the statutory obligations. The specific internal design of the following tasks generally remains an organisational decision:

Legal basisStatutory obligationPossible practical implementation
Section 30(1) and (2) BSIGtake appropriate, proportionate and effective risk management measures and document compliance with themassess risks, plan measures, assign responsibilities and evidence
Section 32 BSIGreport significant security incidents within the statutory stages and deadlinesorganise detection, internal escalation and reporting templates
Section 38(1) BSIGmanagement body implements risk management measures and monitors their implementationorganise reports, decisions and monitoring in a traceable way
Section 38(3) BSIGmanagement body regularly attends suitable trainingplan training needs, attendance and updates internally
Section 30(2) no. 6 BSIGprovide policies and procedures to assess effectivenessuse controls, metrics, audits and action tracking

A registration confirmation proves registration. It does not prove that risk management measures are effective or that incident processes work. Nor do the substantive obligations begin only once registration is complete; they begin as soon as their respective statutory conditions are met.

Is ISO 27001:2022 enough for NIS2?

No. According to the BSI, certification to ISO 27001:2022 means neither automatic NIS2 compliance nor full compliance with the BSIG. In particular, it is not in itself sufficient evidence of the obligations under Section 30 BSIG.

The following limits are particularly relevant:

  • The certified scope of the ISMS may be narrower than the entity's operations relevant under the BSIG.
  • Risk treatment and risk acceptance under ISO 27001:2022 are not equivalent to the statutory requirements for appropriate, proportionate and effective measures.
  • Registration under Section 33, incident reports under Section 32 and the management body's obligations under Section 38 BSIG do not arise from the standard.
  • A certificate answers the specific audit and evidence questions of statutory supervision only incompletely.

ISO 27001:2022 can nevertheless provide a suitable basis for implementation. Certification is neither required by law nor a prerequisite for this; the BSI does not prescribe any particular standard. Existing ISMS structures must be checked by a gap analysis against the BSIG obligations that actually apply and supplemented where necessary.

The knowledge overview on ISO 27001:2022 helps you classify the management system. How to check the accreditation and current status of a certificate is explained in the article “IAF is no longer operational: what old Combined Marks on certificates mean”.

Managing NIS2 in an integrated management system

NIS2 is not an additional ISO standard. Its obligations should therefore not be artificially assigned to a clause of a standard. An integrated system can, however, provide shared management processes:

  1. record the legal obligation,
  2. assign the legal entity and services concerned,
  3. define responsible persons and deputies,
  4. link risks and measures,
  5. control evidence and versions,
  6. monitor deadlines and follow-ups,
  7. review effectiveness and handle deviations.

ISO 9001:2026 may be affected where outages affect customer processes, service delivery or contractual requirements. The subject-matter focus of information security remains with ISO 27001:2022. The statutory NIS2 assessment remains visible as a separate reference.

How shared processes work across several areas of standards without blurring subject-matter differences is shown in the white paper on the integrated management system for ISO 9001:2026, ISO 14001:2026 and ISO 27001:2022.

Conclusion

In practice, we recommend first checking scope in a traceable way and then completing an overdue registration using the current BSI procedure. However, the further statutory obligations do not begin only after registration: risk management measures under Section 30, reporting obligations under Section 32 and management body duties under Section 38 BSIG apply in parallel as soon as the respective conditions are met.

ISO 27001:2022 can provide structures for this, but replaces neither registration nor the specific obligations of the BSIG. IMScollect can link the recorded obligations, responsibilities, measures, documents and audit evidence in a traceable way.

Frequently asked questions

What deadline applies to NIS2 registration under Section 33 BSIG?▾

Important and essential entities must generally register no later than three months after they first or again fall within the statutory criteria. For entities already in scope when the act entered into force on 6 December 2025, this deadline generally ended on 6 March 2026.

What must a company do if it has missed the NIS2 registration?▾

The BSI calls on affected entities that have not yet registered to register immediately. Late or incomplete registration may be punished as an administrative offence; further statutory obligations apply regardless of registration status.

How can you check whether a company is in scope of NIS2?▾

The BSI provides a digital scope check. It gives an initial assessment but is not legally binding; for borderline cases, special rules or complex groups of companies, a legal review is advisable.

What is needed to register in the BSI portal?▾

Under the current BSI procedure, access requires an ELSTER organisation certificate via “Mein Unternehmenskonto” (My Company Account). The statutory obligation arises from Section 33 BSIG; the BSI specifies how the procedure works in detail.

Is ISO 27001 certification enough for NIS2?▾

No. ISO 27001:2022 can provide structures for risk management and measures, but does not automatically prove NIS2 compliance. Registration, incident reports and management body duties arise independently from the BSIG.

Sources