In short
The Bundestag passed the German CRA implementing act on 15 October 2026: the BSI becomes market surveillance and notifying authority and, as the CSIRT, coordinates reports under Article 14. Fines follow Article 64 CRA (up to EUR 15 million or 2.5%). The Bundesrat and promulgation are pending; reporting duties have applied since 11 September 2026.
Status on 14 November 2026: Bundestag Has Voted, Bundesrat Takes It Up on 20 November
On Thursday, 15 October 2026, the Bundestag adopted the federal government’s bill implementing Regulation (EU) 2024/2847 in the version amended by the Committee on Internal Affairs (BT-Drs. 21/8622). CDU/CSU, SPD and Bündnis 90/Die Grünen voted in favour, the AfD group against; Die Linke abstained (see the Bundestag text archive and committee recommendation 21/8622). The BSI refers to the act as the CRA Implementing Act (CRA-DG); it creates the national legal basis for the BSI to act as market surveillance authority and as notifying authority under the Cyber Resilience Act (see BSI, Notification CRA).
As of 14 November 2026 the legislative procedure is not complete: DIP listed the procedure as “Verabschiedet” (passed by the Bundestag) on 27 October 2026; the Bundestag’s resolution has since been put before the Bundesrat as printed paper 621/26 of 30 October 2026 (note “Fristablauf: 20.11.26”, see BR-Drs. 621/26), and the Bundesrat has not yet completed the second passage. According to the Bundestag’s documentation system DIP, the act does not require Bundesrat consent (“Nein, laut Gesetzentwurf (260/26 (bes.eilbed.))”, see DIP procedure 334566). Under Art. 77(2) of the Basic Law the Bundesrat may demand the mediation committee within three weeks of receiving the Bundestag’s resolution; under Art. 78 an adopted act comes into being, among other cases, if the Bundesrat does not make that request (see Art. 77 GG and Art. 78 GG).
The second passage is on the agenda of the Bundesrat’s 1070th session on Friday, 20 November 2026, starting 9:30: the agenda (status 13 November 2026) lists the act as item 7 (printed paper 621/26; see agenda of the 1070th session and BundesratKOMPAKT); the agenda of the 1069th session on 16 October 2026 did not contain the act (see the agenda of the 1069th session). Once an act has come into being, the Federal President signs it and it is promulgated in the Federal Law Gazette (Art. 82(1) GG); at the time of retrieval the BMI shows the procedure as “Gesetz noch nicht verkündet” (not yet promulgated, see BMI, legislative procedure).
| Date | Step | Source |
|---|---|---|
| 1 May 2026 | Government bill sent to the Bundesrat as a particularly urgent proposal because the Regulation’s notification provisions apply from 11 June 2026 | BR-Drs. 260/26 |
| 26 May 2026 | Government bill tabled in the Bundestag | BT-Drs. 21/6134 |
| 11 June 2026 | First reading in the Bundestag, referral to the Committee on Internal Affairs (lead) | BT-Drs. 21/8622, section I |
| 12 June 2026 | Bundesrat, 1066th session: no objections in the first passage | BT-Drs. 21/6512; Art. 76(2) GG |
| 14 October 2026 | Committee on Internal Affairs concludes deliberations and recommends adoption with a change to the entry-into-force provisions | BT-Drs. 21/8622 |
| 15 October 2026 | Bundestag adopts the act and a resolution | Bundestag text archive |
| 20 November 2026 | Bundesrat, 1070th session (Friday): second passage as item 7; deadline per printed paper | BR-Drs. 621/26; agenda of the 1070th session |
| open | Signature and promulgation in the Federal Law Gazette; entry into force in parts on the following day | Art. 82(1) GG; BT-Drs. 21/8622, Art. 4 |
What the Act Regulates: BSI as Market Surveillance, Notifying and CSIRT Authority
The implementing act creates no new manufacturer obligations. The committee report records that the obligations for businesses arise from the directly applicable Regulation (EU) 2024/2847 and that the act merely designates the competent authorities and regulates their cooperation (BT-Drs. 21/8622, section E). Article 1 amends the BSI Act (BSIG) and inserts a new Part 8 on the cybersecurity of products with digital elements; Articles 2 and 3 amend the Telecommunications Act and the Energy Industry Act (see bill 21/6134).
For these tasks the bill provides 141 additional posts by 2029, one-off material costs of EUR 10 million (in particular for a regulatory sandbox) and running material costs of EUR 8.1 million a year, mainly for external service providers in market surveillance (BT-Drs. 21/8622, section D).
| Provision (BSIG draft) | Content | Entry into force under Art. 4 |
|---|---|---|
| § 65 | BSI is the competent national market surveillance authority; cooperation with sectoral market surveillance authorities; complaints office for consumers | 11 December 2027 (“in all other respects”) |
| § 66 | BSI is the notifying authority; assessment and monitoring of conformity assessment bodies by the national accreditation body, by the BSI itself where there is a public interest | Day after promulgation |
| § 67 | Support for economic operators, in particular SMEs and open-source software stewards: awareness, training, regulatory sandbox for cyber resilience | 11 December 2027 (“in all other respects”) |
| §§ 69, 70 | Administrative offences law applies mutatis mutandis to infringements under Art. 64(2) to (4) CRA; BSI is the administrative authority; no fines against public authorities and bodies | 11 December 2027 (“in all other respects”) |
| § 3(1) sentence 2 nos. 30, 31 | Tasks and powers as market surveillance authority and as notifying authority | Day after promulgation |
| § 5(3) sentence 2 no. 6 (no. 5 only editorially adjusted) | Tasks as CSIRT under Regulation (EU) 2024/2847 | Day after promulgation |
Entry Into Force: Why 11 December 2027 Matters for Market Surveillance
The entry-into-force clause has two parts. Under Art. 4(1) as amended by the committee, § 3(1) sentence 2 nos. 30 and 31, § 5(3) sentence 2 nos. 5 and 6 and § 66 BSIG as well as Articles 2 and 3 enter into force on the day after promulgation; “in all other respects” the act enters into force on 11 December 2027 under Art. 4(2) (BT-Drs. 21/8622, recommendation point a, and BT-Drs. 21/6134, Art. 4). On its wording, the provisions that enter into force only on 11 December 2027 include the market surveillance competence (§ 65), the support measures (§ 67) and the fining provisions (§§ 69, 70).
The bill had tied § 66 BSIG and the task assignments in § 3 to 11 June 2026 and the CSIRT task in § 5 to 11 September 2026 (BT-Drs. 21/6134, Art. 4). The committee explains the change by saying that this link had become moot with the passage of time and that the rules apply from their entry into force (BT-Drs. 21/8622, explanatory statement IV.1). The date of 11 December 2027 matches the general date of application of the Regulation under Art. 71(2) CRA.
Together with the act the Bundestag adopted a resolution: in BSI market surveillance the government is to prioritise the examination of routers and exhaust the legal framework; the resolution names no further product classes for market surveillance (BT-Drs. 21/8622, recommendation point b).
The Deadline Chain: What Applies Since When and What Is Still Ahead
Under Art. 71(2), Regulation (EU) 2024/2847 applies from 11 December 2027; by way of derogation Article 14 applies from 11 September 2026 and Chapter IV (Articles 35 to 51) from 11 June 2026 (see Regulation (EU) 2024/2847, EUR-Lex). This yields the chain below; the German procedural dates come from the parliamentary papers and the Bundesrat calendar.
| Date | Event | Provision or source |
|---|---|---|
| 10 December 2024 | Regulation (EU) 2024/2847 enters into force | Art. 71(1) CRA; BT-Drs. 21/6134 |
| 11 June 2026 | Chapter IV applies: notification of conformity assessment bodies (Articles 35 to 51) | Art. 71(2) CRA |
| 11 September 2026 | Article 14 applies: reporting duties for actively exploited vulnerabilities and severe incidents; Single Reporting Platform live | Art. 71(2) CRA; ENISA, SRP launch |
| 15 October 2026 | Bundestag passes the implementing act | BT-Drs. 21/8622 |
| 20 November 2026 | Bundesrat, 1070th session (Friday): second passage is item 7 on the agenda | BR-Drs. 621/26; agenda of the 1070th session |
| Day after promulgation | § 66 BSIG (notification), CSIRT and authority tasks in the task catalogue, Articles 2 and 3 enter into force | BT-Drs. 21/8622, Art. 4(1) |
| 11 December 2026 | Member States: sufficient number of notified bodies (a mandate to the states, not a manufacturer deadline) | Art. 35(2) CRA |
| 11 December 2027 (Saturday) | Remaining CRA obligations apply; market surveillance and fining provisions of the implementing act enter into force | Art. 71(2) CRA; Art. 4(2) implementing act |
Reading the Dates: 11 December 2026, Legacy Products and the Time Until Enforcement
The date of 11 December 2026 is often read as a manufacturer deadline. The German version of Art. 35(2) CRA reads “Die Mitgliedstaaten sorgen bis zum 11. Dezember 2026 dafür, dass es in der Union eine ausreichende Zahl notifizierter Stellen gibt” (Member States ensure by that date that there is a sufficient number of notified bodies). The English version is softer: Member States “shall strive to ensure, by 11 December 2026 that there is a sufficient number of notified bodies in the Union to carry out conformity assessments, in order to avoid bottlenecks and hindrances to market entry” (see Regulation (EU) 2024/2847, EUR-Lex). In both versions it is a mandate to the states. It matters to manufacturers whose product requires third-party assessment; according to the BSI overview, most products need only a self-assessment and only a few require a notified third party (see BSI, Cyber Resilience Act).
Legacy products need separate treatment: the remaining requirements cover products placed on the market before 11 December 2027 only after a substantial modification (Art. 69(2)). The obligations under Article 14, by contrast, apply to all products within scope that were placed on the market before 11 December 2027 (Art. 69(3)). Anyone with software in the market therefore needs the reporting process for the entire delivered installed base.
Duty and supervision should be kept apart in time. The reporting duty in Art. 14 has applied since 11 September 2026. The market surveillance provisions (Articles 52 to 60) and the penalty provision (Article 64) are not among the provisions that Art. 71(2) brings into application earlier, and the German competence and fining provisions (§§ 65, 69, 70 BSIG) enter into force only on 11 December 2027 under Art. 4(2) of the implementing act. The sources reviewed contain no official statement on how infringements of Art. 14 are treated before that date. The duty exists; on the wording, the enforcement framework applies later. How that affects your risk assessment is a question for your legal department.
Two dates are routinely confused: 11 December 2026 (Art. 35(2) CRA) is a mandate to the Member States, while 11 December 2027 (Art. 71(2) CRA) is when the remaining manufacturer obligations start to apply.
The BSI in Four Roles: What Manufacturers Can Expect From Each
The BSI combines four functions in Germany: market surveillance, notification, CSIRT coordination of CRA reports and a complaints office for consumers (see the BSI press release of 16 October 2026, in German).
Market surveillance (§ 65 BSIG, Articles 52 to 54 CRA)
By its own account the BSI can check IT products for cybersecurity on a sample or targeted basis, demand improvements, impose sanctions and fines for infringements and take products off the market (BSI press release of 16 October 2026). The Regulation sets the frame: on a reasoned request the market surveillance authority gets access to the data needed to assess design, development, production and vulnerability handling, including internal documents (Art. 53). If it has sufficient reason to believe that a product poses a significant cybersecurity risk, it evaluates the product, requires corrective action within an appropriate period or withdrawal or recall, and can take provisional measures if the operator does not act (Art. 54(1) and (5)). It also monitors how manufacturers applied the Article 13(8) criteria when setting the support period (Art. 52(16)).
Notifying authority (§ 66 BSIG, Article 35 et seq. CRA)
The assessment and monitoring of conformity assessment bodies is in principle a matter for the national accreditation body; the BSI may carry it out itself where there is a public interest and notifies the bodies to the Commission and the other Member States under Art. 35(1) CRA (§ 66(2) to (4) of the BSIG draft, BT-Drs. 21/6134). This matters to manufacturers only if third-party assessment is foreseen for their product. For conformity assessment bodies the BSI describes a procedure involving accreditation by DAkkS and a mandatory kick-off meeting before the application (see BSI, Notification CRA).
CSIRT coordinator and reporting route (§ 5(3) BSIG, Articles 14 and 16 CRA)
Since 11 September 2026 the BSI has coordinated CRA reports for Germany, according to its own statement (BSI press release of 16 October 2026). ENISA lists Germany with the BSI’s CERT-Bund in its list of CSIRTs designated as coordinators (see ENISA, List of CSIRTs Designated as Coordinators). The reporting route does not run through the BSI portal but exclusively through the Single Reporting Platform operated by ENISA; the report is made available to the coordinating CSIRT and ENISA simultaneously, must be written in English and goes by e-mail to CERT-Bund only as an exception when the platform is temporarily unavailable (see BSI, CRA Single Reporting Platform). The competent CSIRT is that of the Member State in which the manufacturer has its main establishment in the Union (Art. 14(7)). The statutory task assignment as CSIRT (§ 5(3) sentence 2 no. 6 of the BSIG draft) enters into force on the day after promulgation (Art. 4(1)).
Complaints office and support (§§ 65(3), 67 BSIG)
The BSI sets up a complaints office for consumers (§ 65(3)) and supports in particular SMEs and open-source software stewards, among other things through a regulatory sandbox for cyber resilience (§ 67; Art. 33(2) CRA). The dual role as CSIRT and market surveillance authority has a practical consequence: under Art. 16(3) CRA the coordinating CSIRTs make the reported information that the market surveillance authorities of their Member State need for their tasks available to them, and under Art. 52(4) both cooperate in supervising the reporting duties. A 24-hour or 72-hour report should therefore be written as if the supervisory authority will read it.
Penalty Framework: Fines Under Art. 64 CRA and the German Procedural Layer
The level of the fines is set not by the German act but by Art. 64 CRA (see Regulation (EU) 2024/2847). The implementing act adds the procedure: the Administrative Offences Act (OWiG) applies mutatis mutandis to infringements under Art. 64(2) to (4), with § 17 OWiG and § 30(1) and (2) OWiG excluded; the BSI is the administrative authority in fining proceedings, and no fines are imposed on authorities and other public bodies (§§ 69, 70 of the BSIG draft, see bill 21/6134). In committee the Greens criticised that fines are possible only against the private sector (BT-Drs. 21/8622, report IV.2).
| Offence (Art. 64 CRA) | Maximum | Applicable |
|---|---|---|
| Para. 2: non-compliance with the essential cybersecurity requirements (Annex I) or breach of the obligations in Articles 13 and 14 | up to EUR 15 million or, for undertakings, up to 2.5% of total worldwide annual turnover of the preceding financial year | whichever is higher |
| Para. 3: breaches of, among others, Articles 18 to 23, 28, 39, 41, 47, 49 and 53 | up to EUR 10 million or up to 2% of worldwide annual turnover | whichever is higher |
| Para. 4: incorrect, incomplete or misleading information in reply to a request from notified bodies and market surveillance authorities | up to EUR 5 million or up to 1% of worldwide annual turnover | whichever is higher |
Reading the Penalty Framework: Reporting Duty, Exemptions and Calculation
Two points matter in practice. First, the reporting duty carries fines: breaches of Articles 13 and 14 fall under Art. 64(2), and fines can be imposed in addition to corrective and restrictive measures (Art. 64(9)). Second, Art. 64(10) contains exemptions: for micro and small enterprises the fines do not apply to a failure to meet the 24-hour deadline under Art. 14(2)(a) and (4)(a); open-source software stewards are exempt for any infringement. The duty itself remains. Since the corrigendum of 2 July 2025, Art. 64(10) reads “by way of derogation from paragraphs 2 to 9”, so the exemption expressly covers the tier for Articles 13 and 14 as well (see corrigendum, OJ L 2025/90555).
In setting a fine, among other things the nature, gravity and duration of the infringement and the size and market share of the operator, in particular for micro and small enterprises and SMEs, are to be taken into account (Art. 64(5)).
Preparation 1: Make the Article 14 Reporting Process Operational
The duty has applied since 11 September 2026, and ENISA put the platform into operation on that day in a first stage (see ENISA, The CRA Single Reporting Platform is launched). The deadlines run from the manufacturer’s awareness: early warning without undue delay and in any event within 24 hours; notification within 72 hours; final report no later than 14 days after a corrective or mitigating measure is available and, for severe incidents, within one month of the 72-hour notification (Art. 14(2) and (4); see Regulation (EU) 2024/2847 and European Commission, Reporting obligations). Seven process decisions follow from the provision and should be made before the first real case:
How far your organisation has come is shown by the free [CRA reporting readiness check](/check/cra) in about 3 minutes; reporting templates, CVD policy and incident runbook can be created with the [Governance Document Builder](/templates/governance-doc).
- Define the awareness point: the 24-hour deadline is tied to the manufacturer’s awareness (Art. 14(2)(a)). The ticket schema needs a mandatory field for the time of reliable awareness, the evidence for it and the person who establishes it.
- Triage reportability cleanly: an actively exploited vulnerability requires reliable evidence of proven exploitation (Art. 3(42)); according to the BSI, published exploits, proof-of-concept code or port scans are not sufficient. A ransomware incident at the manufacturer is not automatically a severe incident under the CRA; it is one only if it affects product security or can lead to manipulation of software, updates or signing keys (see [BSI, CRA Single Reporting Platform](https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Informationen-und-Empfehlungen/Cyber_Resilience_Act/Single_Reporting_Platform-CRA/single_reporting_platform-cra.html)).
- Name representatives: reports are submitted by a person designated for the manufacturer (Assigned Representative); the BSI recommends reliable cover by at least two people and does not require registration before the first need to report. Recommendation: register and assign roles before an incident so that no account has to be created within the 24-hour window.
- Prepare report content: the early warning names the Member States in which the product was made available to the manufacturer’s knowledge (Art. 14(2)(a)); for incidents it states whether unlawful or malicious acts are suspected (Art. 14(4)(a)). A market and version list per product in the master data saves time; according to the BSI the report itself is to be written in English, so English text modules belong in the template.
- Determine the competent CSIRT: what counts is the Member State of the main establishment, i.e. where decisions on the cybersecurity of the products are predominantly taken; failing that, the state with the highest headcount (Art. 14(7)). Manufacturers without an establishment in the Union, for example a Swiss manufacturer without an EU subsidiary, follow an order of precedence via authorised representative, importer, distributor and the state with the most users.
- Treat the release date as a deadline trigger: the final report is linked to the availability of the corrective or mitigating measure (Art. 14(2)(c)); release management reports the release date to compliance. The coordinating CSIRT can request intermediate reports (Art. 14(6)).
- Regulate user information and double reporting: alongside the report, Art. 14(8) requires informing affected users, where appropriate in a structured, machine-readable format (for example as a CSAF advisory); the SRP report does not replace this. An incident can additionally be reportable under NIS2 via the BSI portal, and both reports can carry a reference note (BSI, CRA Single Reporting Platform).
Preparation 2: Vulnerability Management, SBOM and BSI TR-03183
Annex I Part II of the Regulation sets out eight requirements for vulnerability handling (see Regulation (EU) 2024/2847). Translated into pipeline and operations they are mainly these points:
- No. 1: identify and document vulnerabilities and components, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at least the top-level dependencies — SBOM generation in the build, stored versioned with the release artefact.
- Nos. 2 and 8: address and remediate vulnerabilities without delay; disseminate security updates without delay and, unless agreed otherwise for tailor-made products, free of charge, separated from functionality updates where technically feasible — patch SLAs by severity.
- Nos. 3 and 4: test and review security regularly and effectively; once a security update is available, share and publicly disclose information about fixed vulnerabilities — test evidence as a release gate, advisory process.
- Nos. 5 and 6: a coordinated vulnerability disclosure policy and a contact address for vulnerability reports — CVD policy and functional mailbox; the single point of contact belongs in the user information under Annex II no. 2.
- No. 7: mechanisms for the secure distribution of updates — signed artefacts and controlled update channels.
Supply Chain and TR-03183: What the Component Duty Means for the SBOM
A supply-chain duty applies to components: where the manufacturer identifies a vulnerability in an integrated component, including an open-source one, it reports it to the person or entity manufacturing or maintaining the component and addresses and remediates it under Annex I Part II (Art. 13(6)). SBOM quality therefore determines how quickly a manufacturer can tell whether a new component vulnerability affects its own product and whether a reporting duty follows.
BSI TR-03183 is the BSI’s entry guide to the requirements; it is expressly non-binding and does not create a presumption of conformity. Currently Part 1 (General Requirements) is available in version 1.0.0, Part 2 (SBOM) in version 2.1.0, Part 3 (Vulnerability Reports and Notifications) in version 1.0.0 and Part H (conformity based on full quality assurance, Module H) in version 1.1.0 (see BSI, Technical Guideline TR-03183). For SBOM fields and formats see BSI TR-03183 Part 2: SBOM requirements, for the series as a whole TR-03183 as an entry guide to the CRA.
On the organisational side, the BSI recommends in its technical implementation document (Part 3) a CSIRT functional mailbox alongside a PSIRT functional mailbox; in smaller organisations the same people can take on both tasks (BSI, CRA Single Reporting Platform, FAQ).
Preparation 3: Responsibilities, Documentation and Conformity Assessment
Market surveillance is document-based. On a reasoned request it gets access to data and internal documents (Art. 53); the technical documentation and the EU declaration of conformity must be kept for at least ten years or for the duration of the support period, whichever is longer (Art. 13(13)). The software bill of materials is part of the description of vulnerability handling (Annex VII no. 2(b)) and must be provided on the authority’s reasoned request (Annex VII no. 8). The following mapping helps to assign evidence and owners; the role suggestions are an Alev-B recommendation, not a requirement of the Regulation.
| Area | Provision | Evidence the authority can request | Suggested role |
|---|---|---|---|
| Support period | Art. 13(8) and (19); Art. 52(16) | Determination with reasons (expected use time, user expectations, third-party components); at least five years unless the expected use time is shorter; end date stated with month and year at the time of purchase | Product owner with legal |
| Risk assessment | Art. 13(3); Annex VII no. 3 | Documented and updated cybersecurity risk assessment during the support period | Product security |
| Vulnerability handling | Annex I Part II; Annex VII no. 2(b) | SBOM, CVD policy, evidence of the contact address, description of secure update distribution | PSIRT lead |
| Tests and reviews | Annex VII no. 6 | Reports on tests and reviews verifying conformity with Annex I Parts I and II | QA and security engineering |
| EU declaration of conformity | Art. 13(13); Annex VII no. 7 | Copy of the declaration, kept at least ten years or for the duration of the support period | Legal and compliance |
| Reporting process | Art. 14 | Reports and timestamps in the SRP, internal decision records | Primary and secondary Assigned Representative |
Support Decisions as Compliance Decisions
Market surveillance authorities monitor how manufacturers set the support period under Art. 13(8); ADCO can recommend that they prioritise product categories with inadequate periods (Art. 52(16)). End of support, LTS cycles and update cadence are therefore product decisions with a supervisory dimension and belong in product planning, not only in compliance review.
In supplier and integration chains, commitments on SBOM delivery, reporting chains and response times belong in contracts, because Art. 13(6) requires component vulnerabilities to be passed on to the component manufacturer. The Vendor / Third-Party Assessment structures supplier evaluation; the Delivery Audit assesses the maturity of release, quality and security processes.
Delineation: CRA Reporting, NIS2 Reporting and Product Liability
Three regimes interlock for software manufacturers, with different addressees. CRA reports go through the ENISA SRP to the coordinating CSIRT, NIS2 reports through the BSI portal. A severe incident can be reportable under both regimes; both reports can carry a reference note. According to the BSI, the Digital Omnibus proposed by the Commission would remove the double reporting, but it is only a proposal; until then both routes have to be served separately (see BSI, CRA Single Reporting Platform). The article Regulatory Collision 2026: NIS2, DORA, CRA and AI Act compares the deadline and reporting logic of the regimes; the Article 14 process details are covered in Cyber Resilience Act: The 24-Hour Reporting Duty.
No-fault product liability for software under Directive (EU) 2024/2853 is a separate, parallel regime with a cybersecurity link; cut-off date, update liability and burden of proof are covered in Product Liability for Software: What Directive (EU) 2024/2853 Changes for IT Delivery.
Primary Sources and Retrieval Status
This account is current as of 27 October 2026; all sources were retrieved on that day (Regulation (EU) 2024/2847, parliamentary papers, Bundesrat and BSI pages). The statements on the second Bundesrat passage were updated on 14 November 2026 against printed paper 621/26 and the agenda of the 1070th session. The article places legal texts in context and does not replace legal advice; the linked legal texts are authoritative.
- Committee recommendation and report, BT-Drs. 21/8622: https://dserver.bundestag.de/btd/21/086/2108622.pdf
- Government bill, BT-Drs. 21/6134: https://dserver.bundestag.de/btd/21/061/2106134.pdf
- Bundestag text archive on the vote of 15 October 2026: https://www.bundestag.de/dokumente/textarchiv/2026/kw42-de-cyberresilienz-1224508
- Bundesrat: submission as a particularly urgent bill, BR-Drs. 260/26: https://dserver.bundestag.de/brd/2026/0260-26.pdf
- Bundesrat plenary dates and BundesratKOMPAKT: https://www.bundesrat.de/DE/plenum/to-plenum/to-plenum-node.html
- BSI press release of 16 October 2026 (German): https://www.bsi.bund.de/DE/Service-Navi/Presse/Pressemitteilungen/Presse2026/261020_CRA-Durchf%C3%BChrungsgesetz.html
- BSI, CRA Single Reporting Platform: https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Informationen-und-Empfehlungen/Cyber_Resilience_Act/Single_Reporting_Platform-CRA/single_reporting_platform-cra.html
- ENISA, Single Reporting Platform: https://www.enisa.europa.eu/topics/product-security/vulnerability-services/eu-incident-response-and-cyber-crisis-management/single-reporting-platform-srp
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex: https://eur-lex.europa.eu/eli/reg/2024/2847/oj
Key Takeaways
- The Bundestag passed the CRA implementing act on 15 October 2026; it creates no new manufacturer obligations but designates the BSI as market surveillance and notifying authority (BT-Drs. 21/8622).
- As of 14 November 2026 the second Bundesrat passage (1070th session on 20 November 2026, item 7) and promulgation are outstanding; according to DIP the act does not require Bundesrat consent.
- The reporting duties under Art. 14 CRA have applied since 11 September 2026; the route is the ENISA SRP, and the coordinating CSIRT in Germany is CERT-Bund at the BSI.
- The penalty framework follows directly from Art. 64 CRA: up to EUR 15 million or 2.5% of worldwide annual turnover; the BSI becomes the administrative authority in fining proceedings.
- Market surveillance (§ 65 BSIG) and the fining provisions (§§ 69, 70 BSIG) enter into force on 11 December 2027 under Art. 4(2), § 66 BSIG on the day after promulgation; 11 December 2026 is a mandate to the Member States (Art. 35(2) CRA).
- Operationally what counts now: a robust 24-/72-hour reporting process with two named representatives, SBOM and CVD under Annex I Part II, documentation under Annex VII and a reasoned support period under Art. 13(8).
Frequently Asked Questions
No. The Bundestag passed it on 15 October 2026; the second Bundesrat passage (1070th session on 20 November 2026, item 7) and promulgation are outstanding (as of 14 November 2026). Individual parts enter into force on the day after promulgation, the rest on 11 December 2027. The duties under Art. 14 CRA have applied since 11 September 2026 regardless, because the Regulation is directly applicable.
According to the Bundestag’s documentation system DIP it does not (“Nein, laut Gesetzentwurf”). Under Art. 77(2) of the Basic Law the Bundesrat can demand the mediation committee within three weeks of receiving the Bundestag’s resolution; in the first passage on 12 June 2026 it raised no objections. The second passage is on the agenda of the plenary session on 20 November 2026 (item 7).
Indirectly: the report goes through the ENISA SRP and is made available to the coordinating CSIRT and ENISA simultaneously; with a main establishment in Germany the CSIRT is CERT-Bund at the BSI. The BSI reporting portal is not intended for CRA reports, and e-mail to CERT-Bund is an exception for an unavailable platform. According to the BSI, reports must be written in English.
Art. 64 CRA provides for fines of up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher, for breaches of Annex I and Articles 13 and 14; further tiers are EUR 10 million or 2% and EUR 5 million or 1%. The BSI becomes the administrative authority in fining proceedings; the fining provisions enter into force on 11 December 2027 under Art. 4(2) of the act.
Art. 35(2) CRA addresses the Member States: by 11 December 2026 they are to ensure a sufficient number of notified bodies (the English version says “shall strive to ensure”). For manufacturers it matters only if their product requires third-party assessment; according to the BSI overview, a self-assessment suffices for most products.
Yes. Under Art. 69(3) the obligations in Article 14 apply to all products with digital elements within scope that were placed on the market before 11 December 2027. The remaining requirements cover such products only after a substantial modification (Art. 69(2)).
No. According to the BSI, a severe incident can be reportable under NIS2 (via the BSI portal) and under the CRA (via the SRP); both reports can carry a reference note. The Digital Omnibus proposed by the Commission would remove the double reporting, but according to the BSI it is only a proposal.