Skip to main content

Guide

NIS2 registration with BSI: Deadline, access and required information

Prepare NIS2 registration in Germany: ELSTER organisation certificate, Mein Unternehmenskonto, BSI portal and information required under section 33 BSIG.

Benjamin Schatter
|Updated|Read time: 6 minutes

NIS2 registration requires more than portal access: a reasoned classification of your entity, the required organisation details and people who will maintain access and information afterwards. The registration itself takes place in the BSI portal.

This guide explains the German authority process and the deadline under section 33 BSIG. Updated: 12 November 2026. Registration does not confirm fulfilment of all NIS2 obligations; security measures and reporting readiness must be organised in parallel.

Who needs to register?

Under section 33(1) BSIG, the duty covers essential and important entities and domain name registration service providers. The applicable category depends on activities, entity type, size and special legal rules, among other factors.

Document your classification before submission. The NIS2 applicability calculator provides initial orientation. Unclear company relationships, multiple activities and special cases need professional assessment. Waiting for an individual notice from an authority does not replace this assessment.

Critical installations and certain digital services have additional or special registration rules. Check the relevant provisions, including the transitional rules in section 66 BSIG. The steps below explain general NIS2 access; they do not replace an installation-specific assessment.

What is the registration deadline?

Generally, information must be submitted within three months of first or renewed applicability. Consequently, 6 March 2026 was relevant for entities already in scope when Germany's implementing law took effect on 6 December 2025. It is not an annually recurring deadline or a universal date for organisations that become affected later.

Record the date and basis of your applicability. If a deadline has been missed, complete registration without further delay and establish the cause. An unfinished ISMS does not extend the registration deadline. Equally, necessary security measures must not wait until registration is complete.

Step 1: Prepare an ELSTER organisation certificate

Check whether a suitable ELSTER organisation certificate is already available. Establish who manages it, which organisation it identifies and whether the appointed person may use it. Personal access and organisational access are not interchangeable.

If an organisation certificate is needed, follow the Mein Unternehmenskonto procedure. Allow for activation before submission. Do not distribute the certificate file and password through uncontrolled email; arrange authorised access and secure cover for absence.

BSI also explains the sequence of organisation certificate, login and NIS2 registration in its registration information.

Step 2: Check access through Mein Unternehmenskonto

Mein Unternehmenskonto, abbreviated MUK, authenticates organisations for digital public services. Test login with the organisation certificate and confirm the correct company assignment. Determine who may submit the registration and who maintains access during absence.

A working MUK login does not mean the entity is registered with BSI. The relevant information and its submission follow in the BSI portal.

Step 3: Register the entity in the BSI portal

Open the BSI portal and use the designated access method. Enter the entity and the information needed for the NIS2 procedure. Before submitting, check the legal entity, classification, contact details and service scope in particular.

BSI explicitly states that NIS2 registration takes place in the BSI portal, not the former reporting and information portal MIP. It describes transitional arrangements for entities already using its services. See the current BSI NIS2 information.

After submission, retain the submitted details, timestamp and confirmation or reference received. An internally saved draft is not a submitted registration.

Checklist: Information to prepare

Section 33(1) BSIG specifies in particular:

InformationInternal preparation
Name, legal form and commercial register number where applicableReconcile the legal entity with register information
Address and current contact detailsAssign owners and monitored email addresses
Public IP address ranges and telephone numbersVerify with IT and network owners
Relevant sector or industryKeep the reasoned classification available
EU member states where relevant services are providedConfirm activity scope with business teams
Competent federal and state supervisory authoritiesEstablish the authorities relevant to the registered activity

Section 34 BSIG specifies additional or particular information for certain entity types, such as the main establishment or representative. Check whether it also applies.

Do not copy public IP ranges from an old inventory without checking. Establish which addresses are actually assigned to you and which merely belong to shared services. Follow the information requirements and guidance of the relevant procedure.

What happens after registration?

Appoint an owner and deputy for maintaining the information. Changes in legal form, address, contacts or services must not fall between HR, IT and management. Under section 33, changes to required information must be communicated without undue delay and no later than two weeks after becoming known; special information under section 34 follows its separate rules. Observe the applicable version and transitional provisions of the law.

Then test access for an emergency. Who assesses whether an incident is significant? Who prepares, approves and submits the notification? The NIS2 incident reporting guide explains the process.

A blanket duty to maintain a continuously reachable contact point for every NIS2 entity cannot be inferred from the general registration obligation. Special duties for critical installations need separate assessment. Regardless, your incident response organisation must be capable of meeting the applicable reporting deadlines.

Errors you can prevent before submission

  • Only setting up access: Check that the substantive registration was actually submitted.
  • Registering the wrong organisation: Reconcile legal entity, certificate assignment and classification.
  • Using an unmonitored contact address: Establish an owner and cover for absence.
  • Waiting for complete implementation: Work on registration, reporting capability and security in parallel.
  • Losing the confirmation: Keep submitted information and receipt together.

Missing, incorrect, incomplete or late registration information can be subject to fines of up to EUR 500,000 under section 65 BSIG. This is the statutory framework, not an automatic penalty. See the NIS2 fines guide for context.

Registration complete: what comes next?

Keep the registration evidence with your NIS2 records. Systematically assess which requirements are already met, where results are missing and who will address outstanding work.

Kopexa helps track requirements, tasks and evidence. Submission to BSI takes place through the designated authority channel. The NIS2 product page explains how to use an existing ISMS or build the foundation with templates and support.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

How long does NIS2 registration with BSI take?

It depends on whether the organisation certificate, access, classification and information are ready. Allow for certificate activation before portal submission. A generic form completion time does not represent the entire process.

Do I need an ELSTER organisation certificate?

Standard organisational access to the BSI portal uses ELSTER-based Mein Unternehmenskonto. Check the appropriate organisation certificate and the acting person’s permissions. Consult current MUK and BSI guidance for special cases.

Can registration be completed after the deadline?

Complete a missed registration without further delay. This does not automatically undo an earlier breach. Establish the cause and organise future data maintenance.

Who is liable for a missed registration?

Registration is the affected entity’s duty. Missing or incorrect information can lead to a fine. Personal management liability is a separate question depending on applicable rules and the specific conduct.

What is MUK and why do I need it?

Mein Unternehmenskonto provides identification and authentication for digital public services. A MUK account alone does not register your entity with BSI for NIS2.

What information must I provide to BSI?

Section 33(1) includes name, legal form, commercial register number where relevant, address, contacts, public IP ranges, sector, relevant EU states of operation and competent supervisory authorities. Special entity types require further checks.

What effort should we budget for registration?

Allow internal time for classification, certificate and access, data checks, submission and ongoing maintenance. External support fees depend on the agreed scope. Separate this effort from the rest of NIS2 implementation.