Cybersecurity frameworks & operations

Cyber Resilience Act

Regulation (EU) 2024/2847 on horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act)

The EU regulation that requires hardware and software products with digital elements to be secure by design and supported with security updates for their lifetime.

Law / regulation Legally binding where it applies European Union

Official source: EUR-Lex ↗

Written by
MajorCyber™ Editorial
Last reviewed
Reading time
1 min

Researched and drafted with AI assistance from the official sources listed on this page. See our editorial policy.

Profile. A short orientation to Cyber Resilience Act: what it is, who it applies to and its key duties. A full MajorCyber™ guide is on the research roadmap; until then, rely on the official source for detail.

What is the Cyber Resilience Act?

The Cyber Resilience Act (CRA) is the EU’s first horizontal product-security law. It makes cybersecurity a condition for placing hardware and software products with digital elements on the EU market, much as product safety already is. Compliant products carry the CE marking.

Who does it apply to?

It applies mainly to manufacturers, including software publishers, but also importers and distributors of products with digital elements: anything with software that can connect, directly or indirectly, to a device or network. Some sectors already regulated by their own rules are excluded, such as medical devices, motor vehicles and certain aviation and marine equipment. Free and open-source software developed outside a commercial activity is generally outside scope, with lighter duties for “open-source software stewards”.

Key duties

  • Essential cybersecurity requirements: products must be designed, developed and produced to an appropriate level of security. That includes secure-by-default configuration, protection of data, minimal attack surface and the ability to receive security updates.
  • Vulnerability handling: identify and document components, including a software bill of materials; fix vulnerabilities without delay; and provide security updates for a support period that reflects expected use, normally at least five years.
  • Reporting: notify actively exploited vulnerabilities and severe incidents through the single reporting platform run by ENISA, starting with an early warning within 24 hours. This applies from 11 September 2026.
  • Conformity assessment: most products use self-assessment. “Important” and “critical” product classes need harmonised standards or third-party assessment.

How does it relate to other frameworks?

The CRA complements NIS2: NIS2 governs how organisations manage risk, and the CRA governs the security of the products they buy. Secure development practices such as NIST SSDF and OWASP SAMM help manufacturers prepare.

Sources and official references

  1. Regulation (EU) 2024/2847 (EUR-Lex) — EUR-Lex (official source)
  2. Cyber Resilience Act policy page — European Commission (official source)

Links go to the publisher's own site. Where a standard is sold or copyrighted, MajorCyber™ summarises it in original words and links to the official listing instead of reproducing its text.

This page is general educational information, not legal, audit or certification advice. Requirements depend on your organisation's circumstances and the current official text. MajorCyber™ is not affiliated with European Union.

Keep exploring