shipcra

Cyber Resilience Act: what it is, key dates and what it asks of software makers

Reviewed 4 min read

The Cyber Resilience Act (CRA) is the EU law that sets cybersecurity requirements for hardware and software sold in the EU. It entered into force on 10 December 2024. Reporting of actively exploited vulnerabilities has applied since 11 September 2026, and the rest of the regulation, including the essential requirements and CE marking, applies from 11 December 2027.

Key facts

Official name
Regulation (EU) 2024/2847
In force since
10 December 2024
Vulnerability and incident reporting
From 11 September 2026
Full application
From 11 December 2027
Who it covers
Manufacturers, importers and distributors of products with digital elements sold in the EU
Highest fine
€15 million or 2.5% of worldwide annual turnover, whichever is higher

What the Cyber Resilience Act is

The Cyber Resilience Act is a European regulation, so it applies directly in every EU country without a national law to transpose it. It covers products with digital elements: hardware and software that connect to a device or a network. That includes mobile apps, desktop software and games, as well as routers, smart speakers and industrial controllers.

The idea is simple. Whoever puts a product on the EU market is responsible for its security for as long as it is supported, not only on launch day. Products that meet the rules carry the CE marking, the same mark already used for toys and electrical goods.

Key dates

Date What applies
10 December 2024 The regulation enters into force
11 June 2026 Rules on the bodies that carry out third-party conformity assessments
11 September 2026 Article 14: reporting of actively exploited vulnerabilities and severe incidents
11 December 2027 Everything else: essential requirements, conformity assessment, CE marking

The September 2026 date catches people out. Reporting already applies to products on the market today, including those placed on the market before December 2027. The Article 14 guide explains what to report and when.

Which products are covered

A product is in scope when it has digital elements and is made available on the EU market in the course of a commercial activity. Selling it, charging for in-app purchases or subscriptions, or offering it as part of a paid service all count.

Some products are left out because other EU rules already cover them, such as medical devices, vehicles, aviation and marine equipment. Software offered purely as a service is outside the CRA unless it is the backend a product needs to work. Free and open-source software that isn’t monetised is outside it too: see the Cyber Resilience Act and open source.

Whether your own product is covered, and in which category, is a separate question. Does the CRA apply to your app or game? walks through it.

What manufacturers have to do

From 11 December 2027, before placing a product on the market, the manufacturer has to:

  1. Assess the product’s cybersecurity risks and design it to meet the essential requirements in Annex I: secure defaults, security updates, protection of data, a limited attack surface. The Annex I checklist lists each one.
  2. Handle vulnerabilities for the whole support period, which is normally at least five years. That includes drawing up a software bill of materials (SBOM) and publishing a vulnerability disclosure policy.
  3. Write the technical documentation described in Annex VII and keep it for at least ten years after the product is placed on the market, or for the support period if that is longer.
  4. Carry out the conformity assessment, draw up the EU declaration of conformity and affix the CE marking. See the EU declaration of conformity guide.
  5. Give users the information listed in Annex II, including a contact point for reporting vulnerabilities and the date support ends.

Product categories and conformity routes

Category Examples How conformity is assessed
Default Most apps, games and desktop software Self-assessment (Module A, internal control)
Important, class I Browsers, password managers, VPNs, operating systems Self-assessment only with harmonised standards applied in full; otherwise a notified body
Important, class II Hypervisors, firewalls, intrusion detection systems A notified body
Critical Smartcards, smart meter gateways, hardware security boxes European certification where required, or a notified body

The lists of important and critical products are in Annexes III and IV. A product belongs to a category because of its core functionality, not because it contains a component of that kind.

Fines

Member States set the penalties, within ceilings fixed by Article 64:

  • Up to €15 million or 2.5% of worldwide annual turnover for breaching the essential requirements or the obligations in Articles 13 and 14.
  • Up to €10 million or 2% for most other obligations.
  • Up to €5 million or 1% for giving incorrect, incomplete or misleading information to authorities.

Micro and small enterprises can’t be fined for missing the 24-hour early-warning deadline in Article 14, although they still have to report. Open-source software stewards aren’t subject to administrative fines.

Where to read the text

The official text is on EUR-Lex, in every EU language, as HTML or PDF. Annex I (essential requirements), Annex II (user information), Annex III and IV (product categories), Annex V (declaration of conformity) and Annex VII (technical documentation) are the parts a small software team uses most. The European Commission publishes explanatory pages and, since March 2026, draft guidance on scope and open source.

Questions

When does the Cyber Resilience Act apply?

In stages. It entered into force on 10 December 2024. The reporting obligations in Article 14 have applied since 11 September 2026. Everything else, including the essential cybersecurity requirements, conformity assessment and CE marking, applies from 11 December 2027.

Does the Cyber Resilience Act apply to companies outside the EU?

Yes, if they place products on the EU market. The rules follow the market, so a developer in the US, the UK or anywhere else has the same obligations as an EU developer for the products they sell or distribute in the EU.

Does the Cyber Resilience Act apply in the UK?

It isn’t part of UK law in Great Britain. It still applies to UK companies for every product they make available in the EU, so a UK studio selling a game to EU players needs to prepare for it.

What’s the difference between the CRA and NIS2?

NIS2 regulates organisations that run important services, such as energy, health or digital infrastructure. The CRA regulates products: the hardware and software those organisations, and everyone else, buy and use.

Is the Cyber Resilience Act available in French or as a PDF?

Yes. EUR-Lex publishes the official text in every EU language, as HTML and PDF. The English and French versions have the same legal value.

Sources

  1. Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex
  2. Cyber Resilience Act, European Commission
  3. Cyber Resilience Act: reporting obligations, European Commission

This guide explains the regulation in general terms. It isn’t legal advice for your product.

Find out where your product stands.

The free check asks up to nine questions and tells you whether the CRA applies and in which category.

Run the free check