Skip to content
DT Nova

Cyber Resilience Act: what software makers must do, and by when

The Cyber Resilience Act is the EU law that sets cybersecurity requirements for products with digital elements, which means hardware and software placed on the EU market, from smart devices and routers to desktop programs and mobile apps. Its reporting duties have applied since 11 September 2026, and its full requirements apply from 11 December 2027. This guide explains who is covered, what manufacturers must do, and how to prepare a software product, with article numbers from Regulation (EU) 2024/2847 (read on 12 November 2026).

The timeline

DateWhat appliesSource
10 December 2024The Regulation entered into force, twenty days after publication on 20 November 2024Article 71(1)
11 June 2026Rules on notification of conformity assessment bodies (Chapter IV, Articles 35 to 51)Article 71(2)
11 September 2026Reporting of actively exploited vulnerabilities and severe incidents (Article 14)Article 71(2)
11 December 2027All other obligations, including the essential requirements and CE markingArticle 71(2)

The reporting duty is already live. Every manufacturer with a product in scope on the EU market, whether placed there before or after September 2026, needs a working route to report.

Which products are covered

The CRA covers products with digital elements made available on the market whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network. In everyday terms: connected hardware, the software running on it, and standalone software sold as a product, including the remote data processing the product needs to perform its functions. Products already covered by their own EU product rules, such as medical devices, in vitro diagnostics, motor vehicles, certified civil aviation products and marine equipment, are excluded (Article 2(2) to (4)).

Cloud services on their own are not CRA products. Recital 12 says that websites that do not support the functionality of a product, and cloud services designed and developed outside the responsibility of a product's manufacturer, fall outside the Regulation, and that NIS2 applies to cloud computing services such as SaaS, PaaS and IaaS. The backend of a connected device, or the server part a mobile app needs to work, is different: if the product cannot perform a function without it, it is part of the product.

Most products follow the default route, a self-assessment by the manufacturer. Annex III lists important products in two classes that face stricter conformity routes. Class I includes identity management and privileged access software, standalone and embedded browsers, password managers, antivirus software, VPN products, network management systems, SIEM systems, boot managers, PKI software, operating systems, and routers and modems. Annex IV lists critical products with the strictest route.

What manufacturers must do

The manufacturer is the company that develops or has a product developed and markets it under its own name. Its main duties come from Article 13 and Annex I:

  • Security by design. Products are designed, developed and produced to ensure an appropriate level of cybersecurity based on the risks, and are delivered without known exploitable vulnerabilities, with a secure default configuration (Annex I, Part I).
  • A risk assessment. A documented cybersecurity risk assessment that is kept up to date and included in the technical documentation.
  • A software bill of materials. Manufacturers 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 the very least the top-level dependencies (Annex I, Part II(1)).
  • Vulnerability handling. Vulnerabilities are addressed and remediated without delay, including by providing security updates, separately from functionality updates where technically feasible; security is tested regularly; fixed vulnerabilities are disclosed; and there is a policy for coordinated vulnerability disclosure (Annex I, Part II).
  • A support period. The manufacturer sets a support period during which vulnerabilities are handled. It must be at least five years, unless the product is expected to be in use for less time, in which case it matches the expected use time (Article 13(8)).
  • Documentation kept for 10 years. The technical documentation and EU declaration of conformity are kept for at least 10 years after the product is placed on the market, or for the support period if longer (Article 13(13)).
  • CE marking. From 11 December 2027, products carry the CE marking after the conformity assessment.

Importers and distributors have their own, lighter duties: they check that the manufacturer has done its part before placing the product on the market.

Reporting: 24 hours, 72 hours, 14 days

Article 14 requires manufacturers to notify any actively exploited vulnerability in their product, at the same time to the CSIRT designated as coordinator and to ENISA, through the single reporting platform of Article 16. The steps run from the moment the manufacturer becomes aware of it:

  1. Early warning within 24 hours, indicating where applicable the Member States where the product has been made available.
  2. Vulnerability notification within 72 hours, with general information on the product, the nature of the exploit and the vulnerability, the corrective or mitigating measures taken and those users can take.
  3. Final report no later than 14 days after a corrective or mitigating measure is available, describing the vulnerability, its severity and impact, any information on the malicious actor, and details of the security update.

Severe incidents having an impact on the security of the product follow a similar early warning and notification sequence under Article 14(3) and (4). The manufacturer also informs affected users about the vulnerability or incident and the measures they can take. To meet a 24-hour clock, the work has to be prepared in advance: a monitored security contact, a named person who decides whether a vulnerability is actively exploited, and a template for each report.

Open source and the CRA

Free and open-source software that is not monetised and not supplied in the course of a commercial activity is outside the Regulation's main obligations, and the CRA introduces a lighter regime for open-source software stewards, the organisations that support open-source projects intended for commercial use. For a manufacturer the key point is different: open-source components inside your commercial product are your responsibility. They belong in your SBOM, their vulnerabilities in your handling process, and Article 13(6) requires you to report a vulnerability you find in a component, including an open-source one, to the person or entity that maintains it.

Penalties

Article 64 sets maximum fines. Breaching the essential requirements of Annex I or the obligations in Articles 13 and 14 can bring fines of up to 15 million euro or 2.5 % of total worldwide annual turnover, whichever is higher. Breaching certain other obligations can bring up to 10 million euro or 2 %, and supplying incorrect, incomplete or misleading information to notified bodies or market surveillance authorities up to 5 million euro or 1 %. Market surveillance authorities can also order a product to be withdrawn or recalled.

How to prepare a software product

  1. Decide whether each product is in scope, and in which class, and write the reasoning down.
  2. Set up reporting now. A security contact on your website, a monitored inbox, a decision owner, report templates and access to the single reporting platform.
  3. Produce an SBOM in the build. Generate it automatically in the build pipeline in a common format such as SPDX or CycloneDX, so it is always current.
  4. Scan dependencies continuously, and track each finding to a fix or a documented decision.
  5. Separate security updates from feature releases where you can, and make updates automatic by default where it fits the product.
  6. Set and publish the support period, and check that your hosting, components and team plan cover it.
  7. Write the risk assessment and technical documentation as part of development, not at the end, so the conformity assessment before 11 December 2027 is a review rather than a rewrite.

Companies that are also in scope of NIS2 should align the two processes, because one incident can trigger reports under both laws, and a personal data breach adds a GDPR notification. Our incident response plan guide shows how to build one plan for all three.

How we help

We build and maintain software products, and we build them with the CRA in mind: SBOM generation and dependency scanning in the pipeline, secure defaults, a separate security update channel, logging that supports a 24-hour early warning, and documentation written as we go. For an existing product, a security audit checks the code and the processes against Annex I and ends in a ranked fix list. For connected devices, see IoT software development; for apps, mobile app maintenance covers the long support period. The code stays yours.

Questions people ask

Does the Cyber Resilience Act apply to apps and desktop software?

Yes, when they are products with digital elements made available on the EU market in the course of a commercial activity. That covers software sold or distributed as a product, such as desktop software, mobile apps and firmware, together with the remote data processing the product needs to perform its functions. Software covered by its own EU product law, such as medical devices or vehicles, is excluded.

Does the CRA cover SaaS?

Cloud services as such are not covered. Recital 12 of the Regulation says that websites that do not support the functionality of a product, and cloud services designed and developed outside the responsibility of the product's manufacturer, are outside its scope, and that NIS2 applies to cloud computing services such as SaaS. Remote processing that a product needs to work, such as the backend of a connected device or app, is part of the product.

What has to be reported, and when?

Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting the security of their products to the coordinating CSIRT and ENISA, through the single reporting platform. For a vulnerability: an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days after a fix or mitigation is available.

Does the CRA apply to products already on the market?

The reporting duty of Article 14 applies to all products in scope from 11 September 2026, including those placed on the market before that date. The other requirements apply to products placed on the market from 11 December 2027, and to older products only when they are substantially modified after that date.

What are the fines under the Cyber Resilience Act?

For breaching the essential requirements of Annex I or the obligations of Articles 13 and 14, administrative fines of up to 15 million euro or 2.5 % of worldwide annual turnover, whichever is higher (Article 64(2)). Lower ceilings apply to other obligations and to supplying incorrect information.

Sources