Cyber Resilience Act · Regulation (EU) 2024/2847 · Products with software in them

Build products people can trust, and prove it.

The CRA sets security rules for anything with software in it that’s sold in the EU, from apps to smart devices. Reporting has applied since 11 September 2026; the full rules arrive on 11 December 2027. Done early, it becomes a selling point: a CE mark that says your product is secure.

What is the CRA?

Security built in, not bolted on.

The CRA is the first EU law to set security requirements for products with digital elements across the whole market, for as long as they are supported.

What the CRA asks for

  • Secure by design: no known exploitable flaws at release, secure default settings, protected data, and a way to update (Annex I, Part I).
  • Vulnerability handling for the support period, normally at least five years: a software bill of materials, a disclosure policy, and free security updates (Annex I, Part II).
  • Reporting: actively exploited vulnerabilities and severe incidents go to ENISA’s platform, with a 24-hour early warning, a 72-hour notification and a final report (Article 14).
  • Paperwork that proves it: risk assessment, technical file, declaration of conformity and the CE mark.

Who it covers

  • Manufacturers of software and hardware sold in the EU, wherever they are based.
  • Importers and distributors, who must check the manufacturer has done its part.
  • Open-source stewards that support projects used commercially, under a lighter regime.
  • Not pure SaaS: that falls under NIS2. But a cloud backend your product can’t work without counts as part of the product.
  • Not products with their own rules, such as medical devices, cars and aviation.
Key dates

Part of it is already live.

1

11 September 2026: reporting

The 24-hour and 72-hour reporting duties apply now, including to products already on the market.

2

11 December 2026: assessors

The Commission’s target for enough notified bodies, the independent assessors some products will need. Expect queues.

3

11 December 2027: everything

Security requirements, vulnerability handling, technical file, conformity assessment and CE marking all apply.

Why start now

What getting ready gives you.

A calm first 24 hours

Could you file an early warning on ENISA’s platform tomorrow? A tested playbook turns a bad day into a routine one.

A place in the queue

Some products need an independent assessor, and there aren’t many yet. Knowing your product class early lets you book one in time.

Software is now a product

From 9 December 2026 the new Product Liability Directive covers software. Good CRA records are your best evidence if something goes wrong.

Assess once, cite twice

For high-risk AI in a CRA product, meeting the CRA’s security requirements counts towards the AI Act’s cybersecurity rule.

Sell into all of the EU

One CE mark, one set of rules, 27 markets. Customers will start asking for it in contracts.

Know the real exposure

Fines go up to €15M or 2.5% of worldwide turnover, whichever is higher. Micro and small companies aren’t fined for missing the 24-hour early warning alone.

How ReadyForAI helps

Live duties first, then 2027.

1

Scope and class

Which of your products are in, which class each falls into, and whether any need an independent assessor.

2

Reporting readiness

Triage rules, on-call, ENISA access and the 24h and 72h templates, because this part is live now.

3

Gap check

Each product against Annex I, with the long-lead items (support period, updates, assessor) flagged first.

4

Plan to December 2027

Software bill of materials, update policy, technical file and conformity route, with the latest safe start date for each.

Make security part of what you sell.

A 30-minute call to check which products are in scope and whether your reporting is ready. Guidance only, not legal advice.