Managed IT

NIS2 for SMEs in Germany: scope, duties and deadlines

Under Germany’s NIS2 implementation act, the Federal Office for Information Security (BSI) supervises far more companies than before, including medium-sized ones. Based on the statute, this article shows who is in scope, which duties apply and which technical steps make sense now, including for suppliers affected indirectly. Status: October 2026.

As of
Reading time
12 minutes
Updates reach your fleet in stages.
  1. 01Inventory & plan
  2. 02Pilot & rollout
  3. 03Monitor
Concept: take inventory, plan updates, test a pilot group and expand in stages with monitoring.

Legal position in October 2026: EU directive and new BSI Act

The basis is Directive (EU) 2022/2555 of 14 December 2022, the NIS 2 Directive, which member states had to transpose by 17 October 2024. Germany did so with the “Act implementing the NIS 2 Directive and regulating essential principles of information security management in the federal administration”, often called NIS2UmsuCG. It was signed on 2 December 2025, promulgated on 5 December 2025 (Federal Law Gazette 2025 I No. 301) and took effect on 6 December 2025. Its core is a rewritten BSI Act (BSIG), amended several times since, most recently on 23 July 2026; sections cited refer to that version.

The BSI expects around 29,500 particularly important and important entities. By 30 September 2026, 20,141 had registered (13,252 important, 6,837 particularly important). At EU level an amendment is under way: in January 2026 the Commission proposed simplifying the directive and aligning it with the revised Cybersecurity Act (procedure 2026/0012(COD)). As of October 2026 it is still with the European Parliament’s lead committee and nothing has been adopted, so the current BSI Act applies.

Who is in scope: sector and size

The BSI Act has two categories: particularly important and important entities (Section 28 BSIG). As a rule, your company must belong to an entity type in Annex 1 or 2 and offer goods or services there for payment, and it must reach the size threshold. Activities that are negligible within the business as a whole can be disregarded (Section 28(3)).

  • Annex 1: energy, transport, banking and financial market infrastructure, health, water, digital infrastructure (including cloud services, data centres, managed service and managed security service providers) and space.
  • Annex 2: postal and courier services, waste management, chemicals, food (wholesale and industrial production and processing), manufacturing (medical devices, computers and electronics, electrical equipment, machinery, motor vehicles, other transport equipment), online marketplaces, search engines, social networks and research organisations.

Size thresholds under Section 28 BSIG

CategorySectorsThreshold
Particularly important entityAnnex 1at least 250 employees, or both turnover above EUR 50 million and balance sheet total above EUR 43 million
Important entityAnnex 1 or 2at least 50 employees, or turnover and balance sheet total each above EUR 10 million
Not covered (except special cases)Annex 1 or 2fewer than 50 employees and turnover or balance sheet total of EUR 10 million or less

Status: October 2026, Section 28(1) and (2) BSIG. Annex 1 entities that only reach the lower threshold are important entities. Telecoms, trust services, DNS and critical facilities: see next section.

Figures follow the European Commission’s SME Recommendation (2003/361/EC), referenced in Section 28(4) BSIG. Employees are counted in annual work units: part-time and seasonal work count pro rata, working owners count, apprentices do not. The latest annual accounts apply, with turnover net of VAT. According to the BSI, a threshold must be exceeded in two consecutive financial years, not just once (Article 4(2) of the recommendation; new companies excepted). Partner enterprises are added proportionally and linked enterprises in full, unless your company is legally, economically and in fact independent of them in the design and operation of its IT systems (Section 28(4), second sentence). Rule of thumb: medium-sized companies in the listed sectors are in scope, small and micro enterprises usually are not.

Special cases: in scope regardless of size

  • Operators of critical facilities, qualified trust service providers, top-level domain name registries and DNS service providers are always particularly important (Section 28(1)).
  • Other trust service providers are always important (Section 28(2)).
  • Public telecoms networks and publicly available telecoms services: particularly important from 50 employees or more than EUR 10 million in both turnover and balance sheet total, otherwise important.
  • Domain name registration service providers must register with the BSI regardless of size (Section 33(1)).

The act’s risk management, reporting and management duties do not apply to financial entities under the DORA Regulation or parts of the healthcare telematics infrastructure, which have their own rules (Section 28(6)). Section 28(5) largely does the same for public telecoms networks and services and certain energy companies under the Energy Industry Act, unless they have other covered activities.

Tip: Tool: the BSI’s NIS 2 scope check

The BSI offers an anonymous online scope check (“NIS-2-Betroffenheitsprüfung”) whose questionnaire gives an automated first assessment; a decision tree is available as a PDF. According to the BSI, the result is not legally binding and does not replace your own assessment; the BSI gives no binding statement on scope. It recommends documenting the assessment even if the result is “not in scope”, for example with headcount, annual accounts and industry code.

The core duties: registration, risk management, reporting

Registering with the BSI

Entities in scope must register with the BSI within three months of first or once again falling under the act (Section 33 BSIG). For companies in scope since 6 December 2025, this deadline has passed; the BSI urges them to register without delay. Registration has two steps: apply for an ELSTER organisation certificate via “Mein Unternehmenskonto” (a German tax number is required), then sign in to the BSI portal with it and submit your name and legal form, contact details including public IP address ranges, sector and entity type, the EU countries you operate in and the competent supervisory authorities. Changes must be reported without delay, within two weeks at the latest.

Risk management: ten minimum measures

Entities in scope must take appropriate, proportionate and effective technical and organisational measures and document compliance (Section 30(1) BSIG). Proportionality considers factors such as risk exposure, the entity’s size and implementation costs. The measures should reflect the state of the art and must cover at least the following (Section 30(2)):

  • Policies on risk analysis and information security
  • Incident handling
  • Business continuity, such as backup management, disaster recovery and crisis management
  • Supply chain security, including relationships with direct suppliers and service providers
  • Security in the acquisition, development and maintenance of IT systems, including vulnerability handling and disclosure
  • Policies and procedures to assess the effectiveness of the measures
  • Basic IT security training and awareness
  • Policies and processes for the use of cryptography
  • Human resources security, access control and management of IT systems, products and processes
  • Multi-factor or continuous authentication, secured voice, video and text communication and, where appropriate, secured emergency communication

For certain digital providers, including cloud, data centre and managed service providers, Commission Implementing Regulation (EU) 2024/2690 specifies the requirements and takes precedence (Section 30(3)).

Reporting duties with fixed deadlines

Significant security incidents must be reported to the BSI (Section 32 BSIG). An incident is significant if it has caused or can cause severe operational disruption or financial loss for the entity, or can cause considerable material or non-material damage to others (Section 2 No. 11). Reporting is staged:

Reporting stages under Section 32 BSIG

ReportDeadlineContent (summary)
Early warningwithout undue delay, within 24 hours of becoming awaresuspected unlawful or malicious acts, possible cross-border impact
Incident notificationwithout undue delay, within 72 hours of becoming awareconfirmation or update, initial assessment of severity and impact, indicators of compromise where available
Intermediate reportat the BSI’s requestrelevant status updates
Final reportat the latest one month after the notificationdetailed description, root cause, mitigation measures, cross-border impact where relevant; if the incident is ongoing, a progress report first

Status: October 2026, Section 32(1) and (2) BSIG. Per the BSI, registered entities report via the BSI portal, unregistered ones via an online form.

The BSI says the clock starts once an employee learns of the significant incident during working hours. The BSI stresses speed over completeness; details can follow in later reports. A service provider may report for you, but responsibility for the incident and the report stays with you.

Management duties, training and fines

Management must implement the risk management measures and oversee them (Section 38(1) BSIG); the BSI says this responsibility cannot be delegated. Managers who breach this duty are liable to their entity for culpably caused damage under company law (Section 38(2)). Management must also attend regular training to identify and assess risks and risk management practices and judge their impact on the entity’s services (Section 38(3)). The act sets no interval or duration. The BSI recommends thorough initial training with regular follow-ups and complete records of dates, duration and content.

Section 65 BSIG sets the fines; the highest ranges cover, among others, breaches of the risk management, documentation and reporting duties:

Fines under Section 65 BSIG (selection)

BreachParticularly important entityImportant entity
Measures not taken or not taken correctly, not documented, report missing or lateup to EUR 10 millionup to EUR 7 million
The same breaches with total turnover above EUR 500 millionup to 2% of total turnoverup to 1.4% of total turnover
Registration details not submitted, incorrect or lateup to EUR 500,000up to EUR 500,000

Status: October 2026, Section 65(2) and (5) to (8) BSIG. Total turnover: worldwide turnover of the undertaking the entity belongs to, in the financial year before the decision.

Affected indirectly: when your customers fall under NIS2

Many small companies are not covered but supply entities that are, and these must address supply chain security (Section 30(2), second sentence, No. 4). The BSI clarifies that the act does not indirectly oblige all suppliers and service providers. Entities in scope must, however, bind their suppliers to corresponding security requirements and may be unable to work with every company without breaching their own duties.

Suppliers may see this as a contract clause or audit request. The BSI recommends that entities in scope agree terms with suppliers on matters such as risk management, incident handling and patch management. Showing inventoried devices, planned updates, MFA-protected accounts and tested backups makes such requests easier to answer. For SMEs, the BSI names the CyberRisikoCheck under DIN SPEC 27076 as a low-threshold check of where you stand, but says it does not achieve NIS2 compliance.

What SMEs can do in practice now

In scope or not, these steps follow the BSI’s NIS2 recommendations:

  • Check and record your status: run the BSI scope check with your annual accounts and headcount to hand and file the dated result. If in doubt, take legal advice, as the BSI recommends.
  • Build an inventory: the BSI says all systems, applications and data must be known to be protected. A centrally maintained device inventory is the foundation.
  • Backups and recovery: the act explicitly names backup management and disaster recovery. On ransomware, the BSI stresses offline backups and asks whether restores are prepared and rehearsed.
  • Multi-factor authentication: the BSI recommends MFA with suitable knowledge and possession factors. My advice: start with email, remote access and administrator accounts.
  • Patch management: as the BSI describes for NIS2 entities, update all relevant systems regularly, critical flaws first, closing known weaknesses before they are exploited.
  • Incident and reporting plan: decide who assesses an incident, who reports within 24 hours and how warnings are passed on. The BSI recommends internal processes that alert suitable contacts to its warnings and queries outside business hours too.
  • Train management: the BSI’s management training guidance covers content and formats, from classic courses to tabletop exercises.

Note: General guidance, not legal advice

This article summarises the statute and BSI publications as of October 2026. Scope and duties depend on the individual case; if in doubt, have a lawyer review it. I offer neither legal advice nor certification; I plan and implement the technical measures with you.

Much of this is everyday IT work: inventory, patching and remote maintenance run through endpoint management (explained in RMM and managed IT for SMEs), backups and restore tests in the backup strategy for SMEs, and networks and servers belong to IT infrastructure. We set your priorities together in IT consulting.

Questions and answers

Is my SME affected by NIS2?

It depends on sector and size: companies in the sectors of Annexes 1 and 2 of the BSI Act are covered from 50 employees, or with over EUR 10 million in both annual turnover and balance sheet total. Small and micro enterprises usually are not, except special cases such as trust services, DNS, telecoms or critical facilities. The BSI’s scope check gives a first, non-binding assessment.

When do I have to register with the BSI?

No later than three months after your company first or once again falls under the BSI Act. For companies in scope since 6 December 2025, that deadline has passed; the BSI urges them to register immediately. If you fall under the act later, for example through growth, you have three months from then.

Which reporting deadlines apply to a security incident?

For a significant incident: an early warning within 24 hours of becoming aware, a notification with an initial assessment within 72 hours, and a final report within one month of that notification (Section 32 BSIG). If the incident is ongoing, a progress report comes first.

How high are the fines under the BSI Act?

For breaches of the risk management, documentation and reporting duties: up to EUR 10 million for particularly important and EUR 7 million for important entities, or up to 2% or 1.4% of worldwide total turnover where this exceeds EUR 500 million. Missing or incorrect registration details can cost up to EUR 500,000 (Section 65 BSIG).

Do I have to implement NIS2 as a supplier even though I am not in scope?

Not by law. The BSI says the act does not indirectly oblige all suppliers. Your customers in scope must, however, secure their supply chain and bind suppliers to corresponding security requirements. Your obligations then follow from the contract.

Does Gläser IT assess my NIS2 status legally?

No. I offer neither legal advice nor certification. I help with the technical side: current-state review, inventory, backups, MFA, patch management and an incident plan, including their documentation. The legal assessment stays with you and your legal adviser.

Sources

The information reflects the date above. Sources are named so you can look them up; the website does not link to external sites.

  1. Federal Law Gazette (Bundesgesetzblatt): Gesetz zur Umsetzung der NIS-2-Richtlinie und zur Regelung wesentlicher Grundzüge des Informationssicherheitsmanagements in der Bundesverwaltung, BGBl. 2025 I Nr. 301, 5 December 2025
  2. Federal Ministry of Justice / Federal Office of Justice: BSI-Gesetz (BSIG), Sections 2, 28, 30, 32, 33, 38, 65, 66 and Annexes 1 and 2, as amended on 23 July 2026, retrieved 18 Oct 2026
  3. Official Journal of the European Union: Directive (EU) 2022/2555 (NIS 2 Directive), OJ L 333, 27.12.2022, Articles 2, 3, 34 and 41, 14 December 2022
  4. European Commission: Recommendation 2003/361/EC concerning the definition of micro, small and medium-sized enterprises, 6 May 2003
  5. European Parliament, Legislative Observatory: Procedure File 2026/0012(COD): Amending the NIS 2 Directive as regards simplification measures and alignment with the Cybersecurity Act 2, retrieved 18 Oct 2026
  6. BSI: NIS-2-regulierte Unternehmen (notice on the expired registration deadline), retrieved 18 Oct 2026
  7. BSI: NIS-2-Pflichten, retrieved 18 Oct 2026
  8. BSI: NIS-2 in Zahlen (figures as of 30 Sep 2026), retrieved 18 Oct 2026
  9. BSI: NIS-2-Betroffenheitsprüfung (information page and questionnaire), retrieved 18 Oct 2026
  10. BSI: Allgemeine FAQ zu NIS-2 (questions 26 and 28: linked enterprises, first-time threshold breach), retrieved 18 Oct 2026
  11. BSI: BSI-Portal zur Registrierung und Meldung für die regulierte Wirtschaft; Anleitung zur Registrierung im BSI-Portal, retrieved 18 Oct 2026
  12. BSI: #nis2know: NIS-2-Meldepflicht, retrieved 18 Oct 2026
  13. BSI: Schulung für Geschäftsleitungen: Handreichung zur Schulungspflicht nach dem BSI-Gesetz, version 1.0, 17 April 2026
  14. BSI: NIS-2-Checkliste: Was Unternehmen jetzt tun sollten, 13 March 2026
  15. BSI: #nis2know: Sichere Lieferkette, retrieved 18 Oct 2026
  16. BSI: #nis2know: Dokumentationspflicht, retrieved 18 Oct 2026
  17. BSI: #nis2know: Personalsicherheit, Zugriffskontrolle, Assetmanagement, retrieved 18 Oct 2026
  18. BSI: #nis2know: BCM, retrieved 18 Oct 2026
  19. BSI: #nis2know: Multi-Faktor-Authentisierung, kontinuierliche Authentifizierung und gesicherte Kommunikation, retrieved 18 Oct 2026
  20. BSI: #nis2know: Sicherheitsmaßnahmen und Schwachstellenmanagement, retrieved 18 Oct 2026
  21. BSI (CERT-Bund): Ransomware: Bedrohungslage 2022, July 2022

AI. Software. Infrastructure. One point of contact.

Good IT starts
with a conversation.

Tell me what you are planning. Together, we will work out which AI, software and IT support will move you forward.

Free initial consultation · Personal and without obligation

  • AI development
  • Custom software
  • Thoughtful infrastructure
  • Practical automation
  • One personal point of contact
  • Support that thinks ahead