Skip to content
Related legislation

NIS 2 and the Cyber Resilience Act: what applies to manufacturers?

As of 6 min read

The Cyber Resilience Act regulates products, NIS 2 regulates companies. Many manufacturers are affected by both: the reporting obligation under Art. 14 CRA applies to their products, the German BSI Act to their own operations. This guide shows when manufacturers in Germany fall under NIS 2 and how the two obligations interact.

Two sets of rules, two perspectives

  • The Cyber Resilience Act (Regulation (EU) 2024/2847) starts from the product: whoever places products with digital elements on the market must design them securely, handle vulnerabilities and report incidents having an impact on the security of the product.
  • NIS 2 (Directive (EU) 2022/2555) starts from the entity: companies in certain sectors above a certain size must protect their own IT systems, register with the BSI and report significant incidents.

In Germany, NIS 2 has been transposed by the new BSI Act (BSIG) (Federal Law Gazette 2025 I No. 301). According to the Federal Office for Information Security (BSI), entities have been covered since 6 December 2025.

Source: Art. 14 CRA · Directive (EU) 2022/2555 (NIS 2 Directive) · BSI: NIS 2 regulated companies (in German)

Do manufacturers fall under NIS 2?

Annex 2 of the BSIG lists, among others, these types of entity in the sector “manufacturing”:

  • manufacture of medical devices and in vitro diagnostic medical devices
  • manufacture of computer, electronic and optical products (NACE Rev. 2, division 26)
  • manufacture of electrical equipment (division 27)
  • manufacture of machinery and equipment (division 28)
  • manufacture of motor vehicles, trailers and semi-trailers (division 29) and of other transport equipment (division 30)

Companies of these types are important entities if they employ at least 50 persons or have an annual turnover and an annual balance sheet total each exceeding €10 million (Section 28(2) no. 3 BSIG). The count follows the Commission’s SME Recommendation (2003/361/EC); business activities that are negligible in relation to the overall activity may be disregarded for the classification (Section 28(3) and (4)).

Software manufacturers can also be covered, for example if they also provide cloud computing services or act as managed service providers (Annex 1). The same thresholds for important entities apply to these types of entity; from 250 employees, or more than €50 million annual turnover and more than €43 million annual balance sheet total, they are particularly important entities (besonders wichtige Einrichtungen) (Section 28(1) no. 4).

You can check whether your company is covered with the BSI’s free NIS 2 applicability check (in German).

Source: Section 28 BSIG (in German) · Annex 2 BSIG (in German) · Annex 1 BSIG (in German) · Annex II NIS 2 Directive · BSI: NIS 2 applicability check (in German)

NIS 2 registration in the BSI portal

Important and particularly important entities must register with the BSI no later than three months after they first qualify as such (Section 33(1) BSIG). They must provide:

  • the name of the entity with its legal form and, where applicable, its commercial register number,
  • the address and up-to-date contact details, including email address, public IP address ranges and telephone numbers,
  • the sector or industry under Annex 1 or 2,
  • the Member States in which the entity provides the relevant services,
  • the competent supervisory authorities of the Federation and the Länder.

If these details change, the update must be reported within two weeks at the latest (Section 33(5)). According to the BSI, registration takes two steps: apply for an ELSTER organisation certificate, then register in the BSI portal. The statutory deadline for companies covered since December 2025 has passed – anyone not yet registered should catch up without delay.

Source: Section 33 BSIG (in German) · BSI: NIS 2 regulated companies (in German)

Reporting obligation under Section 32 BSIG

Significant incidents must be reported: incidents that have caused or are capable of causing severe operational disruption of the services or financial loss for the entity, or that have affected or are capable of affecting other persons by causing considerable material or non-material damage (Section 2 no. 11 BSIG). Reports go to the joint reporting office of the BSI and the Federal Office of Civil Protection and Disaster Assistance (BBK), in practice via the BSI portal.

  1. Early first report – without undue delay, at the latest 24 hours after becoming aware: whether the incident is suspected of being caused by unlawful or malicious acts and whether it could have a cross-border impact.
  2. Report – without undue delay, at the latest 72 hours after becoming aware: confirmation or update of the first report, an initial assessment including severity and impact and, where available, indicators of compromise.
  3. Intermediate report – only at the request of the BSI.
  4. Final report – at the latest one month after the report in step 2: a detailed description, the type of threat or root cause, applied and ongoing mitigation measures and, where applicable, the cross-border impact. If the incident is still ongoing at that time, a progress report is due instead, and the final report once the incident has been handled.

According to the BSI, reports that have been submitted cannot be withdrawn, but they can be corrected by follow-up reports – speed takes precedence over completeness.

Source: Section 32 BSIG (in German) · Section 2 no. 11 BSIG (in German) · Art. 23 NIS 2 Directive · BSI: NIS 2 reporting obligation (in German)

One incident, two reports?

The two reporting obligations have different triggers, recipients and reporting channels:

  • Cyber Resilience Act, Art. 14: actively exploited vulnerabilities in the product and severe incidents having an impact on the security of the product – simultaneously to the coordinating CSIRT and ENISA, via ENISA’s Single Reporting Platform.
  • BSIG, Section 32: significant incidents of the entity itself – to the reporting office of the BSI and the BBK, via the BSI portal.

One event can trigger both obligations. An example: attackers take over a manufacturer’s update server and use it to distribute malicious code to customers. That can be a severe incident under Art. 14(5) CRA (introduction of malicious code into the product) and at the same time a significant incident under Section 2 no. 11 BSIG (damage to third parties, disruption of the company’s own operations). Assess both obligations separately – neither report automatically replaces the other.

The deadlines are similar (24 hours, 72 hours, one month), but each runs from the respective moment of awareness and in separate portals. Record the moment of awareness for both obligations.

Source: Art. 14(1), (3) and (5) CRA · Section 32 BSIG (in German) · Section 2 no. 11 BSIG (in German)

Other NIS 2 obligations at a glance

Section 30 BSIG requires appropriate, proportionate and effective technical and organisational measures and their documentation. At a minimum, these include among others:

  • risk analysis and IT security policies, incident handling, backup, business continuity and crisis management,
  • supply chain security, including the relationships with direct suppliers,
  • security in the acquisition, development and maintenance of IT systems, including vulnerability handling and disclosure,
  • training, cryptography, access control and multi-factor authentication.

Management must implement the measures, monitor their implementation and attend training regularly; it is liable under company law for damage caused culpably (Section 38 BSIG).

For manufacturers, the obligations overlap: the Cyber Resilience Act also requires supply chain measures as well as vulnerability handling and disclosure (SBOM, coordinated disclosure, Annex I, Part II). Setting up both together avoids duplicate work.

Source: Section 30 BSIG (in German) · Section 38 BSIG (in German) · Art. 21 NIS 2 Directive

What you should do now

  • Clarify whether you are covered: type of entity under Annex 1 or 2 and size under Section 28 BSIG – for example with the BSI’s applicability check.
  • If covered: apply for an ELSTER organisation certificate and register in the BSI portal.
  • Define a reporting procedure for both channels: who assesses whether an incident must be reported under the Cyber Resilience Act, under the BSIG or under both, and who reports in which portal.
  • Set up the SBOM, vulnerability handling and supplier requirements once and use them for both the Cyber Resilience Act and NIS 2.
  • Plan and document management training.

Related guides

Terms in the Cyber Resilience Act glossary

Sources

First published 19 Oct 2026, last updated 4 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.