# What is the EU Cyber Resilience Act (CRA)? Explained simply

URL: https://sbombox.com/blog/what-is-the-eu-cyber-resilience-act
By SBOMBox SBOM experts. Published 2026-03-18, updated 2026-11-13

> The Cyber Resilience Act (CRA) is the EU law that makes digital products secure by design. Who it covers, what it requires, key dates, fines and next steps.

Short answer: the Cyber Resilience Act (CRA), Regulation (EU) 2024/2847, is an EU law that sets mandatory cybersecurity requirements for hardware and software products sold in the EU. Manufacturers must design products to be secure, keep a software bill of materials, fix vulnerabilities with security updates for the whole support period, and report actively exploited vulnerabilities. It entered into force on 10 December 2024. Reporting duties apply from 11 September 2026 and everything else from 11 December 2027.

## What does CRA stand for?

CRA stands for Cyber Resilience Act. It is the first EU law to set horizontal cybersecurity rules for 'products with digital elements': any hardware or software product that can connect, directly or indirectly, to a device or network. It sits alongside the [NIS2 Directive](https://sbombox.com/blog/nis2-sbom-supply-chain), which regulates organisations, and the [EU AI Act](https://sbombox.com/blog/eu-ai-act-explained-simply), which regulates AI systems. The CRA regulates the products themselves.

Products that meet the CRA carry the CE mark. Products that do not cannot legally be sold in the EU after 11 December 2027, wherever the manufacturer is based.

## Who the CRA applies to

- Manufacturers: anyone who develops or has a product with digital elements made and sells it under their own name. They carry most of the duties.
- Importers and distributors: they must check that products they place on the EU market carry the CE mark and come with the required documentation.
- Open-source software stewards: foundations and similar bodies that systematically support open source intended for commercial use have lighter duties. See [the CRA and open source](https://sbombox.com/blog/cra-and-open-source).
- Non-EU companies: covered if they sell into the EU. Location does not matter; the market does.

Not covered: products already regulated by sector-specific EU law, such as medical devices, motor vehicles, civil aviation and marine equipment; products developed only for national security or defence; and non-commercial open source. Pure software-as-a-service is generally out of scope, unless it is remote data processing that a product needs to work. See [does the CRA apply to my company?](https://sbombox.com/blog/does-the-cra-apply-to-my-company) and [does SaaS need an SBOM?](https://sbombox.com/blog/sbom-for-saas-cra).

## Product categories

**CRA product categories and how they are assessed**

| Category | Examples | Conformity assessment |
| --- | --- | --- |
| Default (most products) | Apps, games, smart speakers, printers, most software | Self-assessment by the manufacturer |
| Important, Class I (Annex III) | Password managers, VPNs, browsers, routers, operating systems, smart home security devices | Self-assessment if a harmonised standard is fully applied; otherwise a notified body |
| Important, Class II (Annex III) | Firewalls, hypervisors and container runtimes, tamper-resistant microprocessors | Third-party assessment by a notified body |
| Critical (Annex IV) | Smart meter gateways, smartcards, hardware security boxes | May require European cybersecurity certification |

Around 90% of products fall in the default category. See [CRA important and critical products](https://sbombox.com/blog/cra-important-and-critical-products) for the full lists and [harmonised standards (EN 40000)](https://sbombox.com/blog/cra-harmonised-standards-en-40000) for how standards make assessment easier.

## What the CRA requires

The essential requirements are in Annex I. Part I covers the product; Part II covers how you handle vulnerabilities for as long as you support it. For all 21 requirements with the evidence for each, see the [Annex I checklist](https://sbombox.com/blog/cra-annex-i-essential-requirements).

- Secure by design and by default: no known exploitable vulnerabilities at release, a secure default configuration, access control, protection of data confidentiality and integrity, data minimisation, a limited attack surface, security logging and secure updates.
- A software bill of materials in a commonly used, machine-readable format, covering at least the top-level dependencies. See [CRA SBOM requirements](https://sbombox.com/blog/cra-sbom-requirements).
- Vulnerability handling: fix vulnerabilities without delay, test regularly, publish information about fixed vulnerabilities, have a coordinated vulnerability disclosure policy and a contact address.
- Security updates: provided free of charge for the support period, separately from feature updates where technically feasible.
- A support period that reflects how long the product is expected to be used, and at least five years unless the product's expected use is shorter. See [how long you must support a product](https://sbombox.com/blog/cra-support-period).
- Technical documentation and an EU declaration of conformity, kept for ten years or the support period, whichever is longer. See the [technical documentation checklist](https://sbombox.com/blog/cra-technical-documentation-checklist).

## Reporting: the 24-hour rule

Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting their products through ENISA's Single Reporting Platform. The sequence under Article 14 is an early warning within 24 hours of becoming aware, a fuller notification within 72 hours, and a final report: within 14 days of a fix being available for a vulnerability, or within one month for an incident. This applies to products already on the market, not just new ones. See [the CRA 24-hour reporting rule](https://sbombox.com/blog/cra-24-hour-reporting).

## Key CRA dates

**CRA timeline**

| Date | What happens |
| --- | --- |
| 10 December 2024 | The CRA entered into force |
| 11 June 2026 | Rules for notifying conformity assessment bodies apply |
| 11 September 2026 | Reporting of actively exploited vulnerabilities and severe incidents applies |
| 11 December 2027 | All remaining obligations apply, including the essential requirements, SBOM, conformity assessment and CE marking |

For a one-page view across the CRA, NIS2 and the AI Act, see the [EU compliance calendar 2026 to 2028](https://sbombox.com/blog/eu-compliance-calendar-2026-2028).

## Penalties

- Breaching the essential requirements or the reporting duties: up to 15 million euros or 2.5% of worldwide annual turnover, whichever is higher.
- Breaching other obligations: up to 10 million euros or 2%.
- Giving incorrect, incomplete or misleading information to authorities: up to 5 million euros or 1%.

Market surveillance authorities can also order products to be withdrawn or recalled. See [CRA fines](https://sbombox.com/blog/cra-fines).

## Where to start

- List the products you sell in the EU and decide which category each falls into.
- Generate an SBOM for every release, from the artifact you ship, and check it against the [minimum elements](https://sbombox.com/blog/sbom-minimum-elements).
- Set up vulnerability monitoring on those SBOMs so you can meet the 24-hour reporting clock.
- Decide and publish a support period for each product.
- Start the technical file now; it is much harder to reconstruct later.

The [free SBOM checker](https://sbombox.com/audit) scores any CycloneDX or SPDX file against a CRA readiness profile in under a minute, and the [CRA workspace](https://sbombox.com/cra) keeps SBOM, vulnerability and VEX evidence per release.

## Frequently asked questions

### What does CRA mean in cybersecurity?

CRA means the Cyber Resilience Act, Regulation (EU) 2024/2847: the EU law that sets cybersecurity requirements for hardware and software products sold in the EU. (In Canada, CRA usually means the Canada Revenue Agency, which is unrelated.)

### When does the Cyber Resilience Act apply?

It entered into force on 10 December 2024. Vulnerability and incident reporting applies from 11 September 2026. All other obligations, including the SBOM and CE marking, apply from 11 December 2027.

### Does the CRA apply to companies outside the EU?

Yes. It applies to any product placed on the EU market, wherever the manufacturer is based. Importers must check that non-EU products comply.

### Does the CRA apply to software and SaaS?

It applies to software products you sell or distribute, including apps and downloadable software. Pure SaaS is generally covered by NIS2 instead, unless it provides remote data processing that a product needs to function.

### Does the CRA require an SBOM?

Yes. Annex I, Part II requires manufacturers to draw up a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies. It goes in the technical documentation and does not have to be published.

### What is the difference between the CRA and NIS2?

NIS2 regulates organisations in critical sectors and how they manage cyber risk. The CRA regulates products and the companies that make them. A software company can be subject to both.

This is general information, not legal advice. Confirm how the rules apply to you with counsel.
