Cyber Resilience Act readiness for makers of digital products

The Cyber Resilience Act dates Four dates in order: the Act entered into force on 10 December 2024, the rules on notified bodies apply from 11 June 2026, the reporting obligations apply from 11 September 2026, and the main obligations apply from 11 December 2027. 10 December 2024 The Act entered into force. 11 June 2026 Notified body rules apply. 11 September 2026 Reporting obligations apply. 11 December 2027 Main obligations apply.
As of November 2026; the Commission page governs.

The reporting duty is already in force and it reaches products sold years ago. The rest of the Act, which reaches design, documentation and support, applies from December 2027.

The short version

Cyber Resilience Act readiness is preparing a manufacturer of hardware or software for the Regulation’s product requirements, its vulnerability handling and its reporting duties, with the documentation that shows each was met.

Whether your product falls in scope, which category it is in and which conformity route applies are questions for your counsel and the market surveillance authority; we prepare the facts, the processes and the documentation they work from. As of November 2026 the points below are from the Regulation and the Commission’s Cyber Resilience Act pages, which also link its guidance of July 2026.

What it covers and when

The Act applies to products with digital elements made available on the EU market, meaning hardware and software and their remote data processing solutions, including components placed on the market separately, and its main obligations fall on manufacturers.

The Act entered into force on 10 December 2024, its reporting obligations apply from 11 September 2026, and its main obligations apply from 11 December 2027.

The reporting obligations apply to all products with digital elements made available on the EU market, including those placed on the market before 11 December 2027; the other obligations apply to such earlier products only if they are substantially modified after that date.

Reporting, already in force

A manufacturer must notify actively exploited vulnerabilities and severe incidents that affect the security of its product: an early warning within 24 hours of becoming aware, a full notification within 72 hours, and a final report, no later than 14 days after a corrective measure is available for an actively exploited vulnerability, or within a month of the 72-hour notification for a severe incident.

Manufacturers report once, through the Single Reporting Platform run by ENISA, and the notification goes to the CSIRT of the Member State of the manufacturer’s main establishment and, in general, to ENISA at the same time. ENISA publishes its Single Reporting Platform guidance, and the Commission explains the duty on its reporting page. The Commission’s summary adds that manufacturers that are micro or small enterprises may not be fined for missing the 24-hour deadline.

The reporting stages, in order Three steps in order: an early warning within 24 hours, a full notification within 72 hours, then a final report that depends on whether it was an exploited vulnerability or a severe incident. 1 Early warning Within 24 hours of becoming aware. 2 Full notification Within 72 hours. 3 Final report 14 days after a fix, or a month.
The platform is ENISA’s; the first recipient is a national CSIRT.

Vulnerability handling and the support period

A manufacturer must identify and document the vulnerabilities and components in its product, including a software bill of materials that covers at least the top-level dependencies, remediate vulnerabilities without delay with security updates, test the product’s security regularly, publish information about fixed vulnerabilities, and have a coordinated vulnerability disclosure policy and a contact address for reports.

The manufacturer determines a support period during which it handles vulnerabilities, which must be at least five years unless the product is expected to be in use for a shorter time, and the end date must be stated clearly at the time of purchase.

We build the intake, triage and disclosure process, the bill of materials pipeline and the update path with the engineering team, from secure development and vulnerability management, and keep the evidence in the form the technical documentation needs. The licence side of the component inventory is a question for your counsel.

Conformity and documentation

Before placing a product on the market, the manufacturer carries out a conformity assessment, which is a self-assessment for most products and a notified body for some important and critical ones, then draws up the EU declaration of conformity and affixes the CE marking.

The manufacturer’s cybersecurity risk assessment and the means chosen to meet the essential requirements go in the technical documentation, which must be kept at the disposal of market surveillance authorities. The Commission’s summary of the text lays out the chapters and annexes. We prepare the risk assessment and the evidence index; the declaration of conformity is signed by the manufacturer.

What you get

  • A product inventory sorted by what the Act would treat as a product with digital elements, for your counsel to confirm.
  • A reporting runbook: who decides that a vulnerability is actively exploited, who files, and how the 24 and 72 hours are met.
  • A vulnerability handling process and a bill of materials pipeline.
  • A support-period statement and the evidence index for the technical documentation.

The same incident can start the GDPR’s 72 hours as well; see the GDPR programme. For Canadian suppliers, an article on the EU AI Act covers the other side of selling into the EU.

How the work is bounded

The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.

SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.

Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.

Questions we are asked

What does Cyber Resilience Act readiness cover?

Cyber Resilience Act readiness is preparing a manufacturer of hardware or software for the Regulation’s product requirements, its vulnerability handling and its reporting duties, with the documentation that shows each was met.

What does the Cyber Resilience Act apply to?

The Act applies to products with digital elements made available on the EU market, meaning hardware and software and their remote data processing solutions, including components placed on the market separately, and its main obligations fall on manufacturers.

When do the Act’s obligations apply?

The Act entered into force on 10 December 2024, its reporting obligations apply from 11 September 2026, and its main obligations apply from 11 December 2027.

What must a manufacturer report, and when?

A manufacturer must notify actively exploited vulnerabilities and severe incidents that affect the security of its product: an early warning within 24 hours of becoming aware, a full notification within 72 hours, and a final report, no later than 14 days after a corrective measure is available for an actively exploited vulnerability, or within a month of the 72-hour notification for a severe incident.

Where are reports submitted?

Manufacturers report once, through the Single Reporting Platform run by ENISA, and the notification goes to the CSIRT of the Member State of the manufacturer’s main establishment and, in general, to ENISA at the same time.

Does it apply to products already on the market?

The reporting obligations apply to all products with digital elements made available on the EU market, including those placed on the market before 11 December 2027; the other obligations apply to such earlier products only if they are substantially modified after that date.

What does vulnerability handling require?

A manufacturer must identify and document the vulnerabilities and components in its product, including a software bill of materials that covers at least the top-level dependencies, remediate vulnerabilities without delay with security updates, test the product’s security regularly, publish information about fixed vulnerabilities, and have a coordinated vulnerability disclosure policy and a contact address for reports.

Do you decide whether our product is in scope?

Whether your product falls in scope, which category it is in and which conformity route applies are questions for your counsel and the market surveillance authority; we prepare the facts, the processes and the documentation they work from.

Tell us what you ship

Say what the product is, how it connects and where it is sold. The reply says what a scope would cover. Related: the European Union page; the article what manufacturers do before December 2027.

Discuss a scope