---
title: "CRA vs NIS-2: Differences, Overlap, Who Must Comply"
description: "CRA vs NIS-2 compared: addressees, deadlines, reporting duties, fines and evidence in one table. Plus: who must comply with both and what to merge."
url: https://panther.blue/en/comparison/cra-vs-nis-2/
lang: en
date_modified: 2026-10-26
author: David Kleinz (Blue Panther GmbH)
alternate: https://panther.blue/vergleich/cra-vs-nis-2/
---

# CRA vs NIS-2: Differences, How They Connect and Who Must Comply with Both

_As of: 26 October 2026 · Author: David Kleinz, CISSP, ISO/IEC 27001 Lead Auditor · https://panther.blue/en/comparison/cra-vs-nis-2/_

**In short:** The CRA regulates products with digital elements and binds manufacturers, importers and distributors; NIS-2 regulates organisations in critical sectors and binds operators. Manufacturers in the manufacturing sector often have to comply with both. Both require 24-hour early warnings and 72-hour notifications, so they can be merged into one reporting and vulnerability process.

The Cyber Resilience Act regulates products, NIS-2 regulates organisations. This page sets both legal acts side by side in a comparison table, shows which companies must comply with both regimes, and where vulnerability, reporting and risk processes can be merged.

## CRA vs NIS-2: product regulation meets organisational regulation

The difference between CRA and NIS-2 can be summed up in one sentence: the [Cyber Resilience Act](https://panther.blue/en/cra/) (Regulation (EU) 2024/2847) regulates **products**, the [NIS-2 Directive](https://panther.blue/en/nis-2/) (Directive (EU) 2022/2555, implemented in Germany through the NIS2UmsuCG in the BSIG) regulates **organisations**. The CRA asks: has this product with digital elements been developed securely, documented and maintained throughout its lifetime? NIS-2 asks: does this entity operate its network and information systems in a way that keeps its services available even under attack?

The CRA is a regulation and has applied directly in every Member State since 10 December 2024, without a national implementing act. It belongs to the family of European product legislation, with CE marking, declaration of conformity and market surveillance. NIS-2 is a directive that only takes effect through national law. In Germany, that is the revised BSIG, in force since 6 December 2025, with the BSI, the German Federal Office for Information Security, as the supervisory authority.

Nevertheless, the two legal acts are not separate worlds. They share the goal of detecting vulnerabilities early and reporting incidents quickly, and they meet particularly often in one group of companies: manufacturers in the manufacturing sector.

## The difference between CRA and NIS-2 at a glance

| Criterion | CRA (Cyber Resilience Act) | NIS-2 (BSIG) |
|---|---|---|
| Legal act | Regulation (EU) 2024/2847, directly applicable; national implementing act for market surveillance and sanctions in preparation (as of 26 October 2026) | Directive (EU) 2022/2555, implemented through the NIS2UmsuCG; revised BSIG in force since 6 December 2025 |
| Addressees | Manufacturers, importers and distributors of products with digital elements (Articles 13, 18 to 20); open-source software stewards under a light regime (Article 24) | Essential entities (besonders wichtige Einrichtungen) and important entities in 18 sectors (Section 28 BSIG, Annexes 1 and 2), around 29,500 organisations in Germany (estimate by the Federal Government and the BSI) |
| Trigger | Placing a product with a data connection on the market (Article 3(1)) or substantially modifying an existing product (Article 69) | Belonging to a sector and exceeding the size thresholds (from 50 employees or more than € 10 million in turnover and balance sheet total); regardless of size for certain entity types |
| Deadlines | Reporting obligations since 11 September 2026; Chapter IV since 11 June 2026; all other obligations from 11 December 2027 (Article 71) | Obligations since 6 December 2025 with no transition period; registration with the BSI within 3 months (Section 33 BSIG), grace period until 31 July 2026 communicated |
| Reporting obligations | Actively exploited vulnerabilities and severe incidents: early warning 24 h, notification 72 h, final report 14 days (vulnerability) or 1 month (incident) via the ENISA single reporting platform (Articles 14, 16) | Significant security incidents: early warning 24 h, notification 72 h, intermediate reports on request, final report within 1 month at the latest to the joint reporting office of the BSI and the BBK (Section 32 BSIG) |
| Sanctions | Up to € 15 million or 2.5 % of worldwide annual turnover (Annex I, Articles 13, 14); up to € 10 million or 2 % (other obligations); up to € 5 million or 1 % (incorrect information) (Article 64) | Essential entities up to € 10 million or 2 % of worldwide turnover; important entities up to € 7 million or 1.4 %; further offences € 100,000 to € 2 million (Section 65 BSIG) |
| Supervision | National market surveillance authorities; responsibility in Germany planned for the BNetzA and the BSI; ENISA coordinates notifications | BSI as the central supervisory authority (Sections 61 et seq. BSIG); management is liable for approving and overseeing the measures (Section 38 BSIG) |
| Evidence | Technical documentation (Annex VII), EU declaration of conformity (Annex V), CE marking (Article 30), self-assessment or notified body depending on product class (Article 32) | Documented risk management under Section 30 BSIG; operators of critical facilities provide evidence to the BSI every 3 years (Section 39 BSIG) |

> **Sanctions add up.** A manufacturer that falls under both regimes can be held liable twice for the same incident: once for an insecure product under Article 64 CRA, once for inadequate risk management measures or a missed notification under Section 65 BSIG. On top of that comes the personal responsibility of management under Section 38 BSIG.

## Who must comply with CRA and NIS-2 at the same time

The overlap is larger than many companies assume. Annex 2 of the BSIG lists the **manufacturing sector** among the "other critical sectors": manufacturers of medical devices and in-vitro diagnostics, of data processing equipment, electronics and optics, of electrical equipment, of machinery, of motor vehicles and parts, and of other transport equipment. These are exactly the industries whose products almost always have a data connection today and therefore fall under the CRA.

A machine builder with 300 employees that sells connected controllers and a remote maintenance app is therefore typically:

- **A manufacturer under Article 13 CRA** for every machine controller, every gateway and every piece of software with a data connection, including the obligation to maintain an SBOM, manage vulnerabilities, define a support period and report actively exploited vulnerabilities.

- **An important entity under Section 28(2) BSIG** for the company itself, including registration, risk management under Section 30, reporting of significant incidents under Section 32 and training of management under Section 38.

Other typical cases of dual applicability: manufacturers of energy and building technology that also supply energy utilities; IT service providers (Annex 1, ICT service management) that sell their own software. And even companies that do not fall under NIS-2 as operators feel the directive through their customers' supply chain obligations (Section 30(2) no. 4 BSIG) in the form of questionnaires and contract clauses.

You can find out in a few minutes whether your company is affected with the [CRA applicability check](https://panther.blue/en/cra/applicability-check/) and the [NIS-2 applicability check](https://panther.blue/en/nis-2/applicability-check/).

## How CRA and NIS-2 connect: three processes you should only build once

Anyone who tackles both regimes separately builds duplicate structures. Three areas can be covered with a single shared process.

### One vulnerability process

In Annex I Part II, the CRA requires a coordinated vulnerability disclosure (CVD) policy, a point of contact, an SBOM and the prompt remediation of vulnerabilities in the product. Section 30(2) no. 5 BSIG requires the management and disclosure of vulnerabilities in the organisation's own systems. Both can be merged into a Product Security Incident Response Team (PSIRT) that triages incoming vulnerability reports about products as well as vulnerabilities in the company's own IT and OT.

### One reporting process

Both legal acts work with the same rhythm: 24 hours for the early warning, 72 hours for the notification, then a final report. The recipients differ (ENISA platform with the CSIRT under Article 16 CRA, joint reporting office of the BSI and the BBK under Section 32 BSIG), as do the triggers (actively exploited vulnerability in the product vs. significant incident in the organisation). The internal workflow, however, is identical: detect, assess, escalate, report, follow up, inform users or customers. An incident in which a product vulnerability is exploited in your own production triggers both notifications. Details on both procedures are available under [CRA reporting obligations](https://panther.blue/en/cra/reporting-obligations/) and [NIS-2 reporting obligations](https://panther.blue/en/nis-2/reporting-obligations/).

### One risk analysis

Article 13(2) CRA requires a cybersecurity risk assessment per product, Section 30(2) no. 1 BSIG a risk analysis for the organisation. Methodologically, both belong in a shared framework with a uniform rating scale, uniform threat catalogues and a register that tracks product and corporate risks side by side. [IEC 62443](https://panther.blue/en/iec-62443/) provides the same methodology for both sides with Part 3-2 (zones and conduits) and Part 4-1 (threat modelling).

## Common mistakes when drawing the line

- **"We are NIS-2 compliant, so the CRA is covered."** An ISMS under ISO/IEC 27001 says nothing about the security of your products. The CRA requires evidence per product: technical documentation, declaration of conformity, support period, SBOM.

- **"We are too small for NIS-2."** The threshold for important entities is 50 employees or € 10 million in turnover and balance sheet total. For certain entity types, such as trust service providers, no size threshold applies. And your customers' supply chain obligations apply regardless of your own size.

- **"Existing products are exempt from the CRA."** Only partially. Products placed on the market before 11 December 2027 fall under the CRA if they are substantially modified (Article 69). The reporting obligations under Article 14 have applied to existing products as well since 11 September 2026 (Article 69(2)).

- **Two reporting processes, two owners.** If product security and corporate IT report separately, one of the two will miss the 24-hour deadline when it matters. A shared escalation chain with clear responsibility prevents this.

- **Management delegates everything.** Section 38 BSIG requires management to approve and oversee the measures and to undergo regular training. A waiver of claims for damages is void.

- **Waiting for harmonised standards.** As of 26 October 2026, no harmonised standard for the CRA has been cited in the Official Journal; the first publications are expected between Q4 2026 and 2027.

## Decision guide: which obligations apply to you?

Every statement you agree with extends your set of obligations.

- We place hardware or software with a data connection on the EU market under our own name: manufacturer obligations under Article 13 CRA, reporting obligations since 11 September 2026, all other obligations from 11 December 2027.

- We import or distribute such products from third parties: obligations as importer (Article 19) or distributor (Article 20) under the CRA; when selling under our own brand or substantially modifying the product, we become the manufacturer (Articles 21, 22).

- Our company belongs to a sector in Annex 1 or 2 BSIG and has at least 50 employees or more than € 10 million in turnover and balance sheet total: important entity, registration and obligations under Sections 30 to 38 BSIG.

- We belong to Annex 1 and have at least 250 employees or more than € 50 million in turnover and € 43 million in balance sheet total, or we operate a critical facility: essential entity, additionally attack detection (Section 31) and evidence every 3 years (Section 39).

- Our products, such as firewalls, routers or microcontrollers with security functions, are listed in Annex III or IV of the CRA: conformity assessment with a notified body or European certification, see [CRA product classes](https://panther.blue/en/cra/product-classes/).

- Our customers fall under NIS-2 or DORA: supply chain requirements, security evidence and contract clauses reach us even without being directly in scope.

## Next steps

If you fall under both regimes as a manufacturer, a combined gap analysis is the most efficient starting point: product obligations under the CRA and organisational obligations under the BSIG in a single pass, with one shared roadmap to 11 December 2027. Blue Panther offers [CRA consulting](https://panther.blue/en/cra/consulting/) and [NIS-2 consulting](https://panther.blue/en/nis-2/consulting/) from a single source. Run the two applicability checks first, and we will clarify scope and sequence in an initial consultation.

## Frequently asked questions

**What is the difference between CRA and NIS-2?**

The CRA (Regulation (EU) 2024/2847) governs the cybersecurity of products with digital elements and addresses manufacturers, importers and distributors. NIS-2 (Directive (EU) 2022/2555, implemented in Germany through the BSIG) governs the risk management of organisations in 18 sectors. The CRA applies directly, NIS-2 takes effect through national law.

**Can a company fall under CRA and NIS-2 at the same time?**

Yes. Manufacturers in the manufacturing sector (Annex 2 BSIG: mechanical engineering, electronics, electrical equipment, vehicle construction, medical devices) with 50 or more employees are important entities under Section 28 BSIG and, at the same time, manufacturers under Article 13 CRA as soon as their products have a data connection.

**Do CRA and NIS-2 have the same reporting deadlines?**

The rhythm is the same: early warning within 24 hours, notification within 72 hours, then a final report. The triggers and recipients differ: the CRA covers actively exploited vulnerabilities and severe incidents reported via the ENISA platform (Articles 14, 16), NIS-2 covers significant security incidents reported to the joint reporting office of the BSI and the BBK (Section 32 BSIG).

**Which regime has the higher fines?**

The CRA provides for fines of up to € 15 million or 2.5 % of worldwide annual turnover (Article 64). Under Section 65 BSIG, essential entities face up to € 10 million or 2 %, important entities up to € 7 million or 1.4 %. Where both regimes apply, both sanctions can be imposed side by side.

**Is an ISMS under ISO 27001 sufficient for the CRA?**

No. An ISMS largely covers the organisational obligations under Section 30 BSIG but says nothing about the security of individual products. The CRA requires a risk assessment per product, the essential requirements under Annex I, technical documentation and a declaration of conformity. Processes such as vulnerability management and reporting channels can, however, be shared.

## Sources

- [Regulation (EU) 2024/2847 (CRA), EUR-Lex](https://eur-lex.europa.eu/eli/reg/2024/2847/oj)
- [Directive (EU) 2022/2555 (NIS-2), EUR-Lex](https://eur-lex.europa.eu/eli/dir/2022/2555/oj)
- [BSIG (revised 2025), gesetze-im-internet.de (German)](https://www.gesetze-im-internet.de/bsig_2025/)
- [Section 28 BSIG Essential and important entities (German)](https://www.gesetze-im-internet.de/bsig_2025/__28.html)
- [Section 32 BSIG Reporting obligations (German)](https://www.gesetze-im-internet.de/bsig_2025/__32.html)
- [Section 65 BSIG Fines (German)](https://www.gesetze-im-internet.de/bsig_2025/__65.html)
- [Cyber Resilience Act, European Commission](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act)

Cite as: Blue Panther GmbH (David Kleinz): “CRA vs NIS-2: Differences, How They Connect and Who Must Comply with Both”, panther.blue, as of 26 October 2026, https://panther.blue/en/comparison/cra-vs-nis-2/
