EU Regulation · (EU) 2024/2847
CRA: Cyber Resilience Act
The Cyber Resilience ActAn EU regulation establishing cybersecurity requirements for covered software and hardware products. It sets duties concerning product design, vulnerability handling and demonstrating conformity, subject to its exclusions and staged application provisions. sets cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. requirements for hardware and software products with digital elements placed on the EU market, from design through a support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. of usually at least five years.
- 24 hours early warning of an actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform.
- 5 years the usual minimum support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years.
- EUR 15 million or 2.5% maximum fine, whichever is higher
What Is CRA?
The CRACyber Resilience Act aims to ensure that products with digital elements are placed on the market with fewer vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., that manufacturers handle security throughout the product’s life, and that users can choose and use products securely.
The Cyber Resilience ActAn EU regulation establishing cybersecurity requirements for covered software and hardware products. It sets duties concerning product design, vulnerability handling and demonstrating conformity, subject to its exclusions and staged application provisions. (CRA) is the first EU law to set cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. requirements for products with digital elements in general: connected devices, components and software sold on the EU market. Products that meet the essential requirements carry the CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws..
It places most duties on manufacturers, with lighter duties for importers and distributors. Products already covered by sector requirements, such as medical devicesAny instrument, apparatus, software, implant, reagent, material or other article intended by its manufacturer for medical purposes such as diagnosis, prevention, monitoring, treatment or alleviation of disease, injury or disability, and that does not achieve its main action by pharmacological, immunological or metabolic means. Software can itself be a medical device., motor vehicles and civil aviation products, are excluded.
- Full title
- Cyber Resilience Act (CRA)
- Official reference
- Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024
- Type
- Regulation
- Issued by
- European Parliament and Council of the European Union
- Adopted
- 23 October 2024
- In force
- 10 December 2024
- Applies from
- 11 December 2027
- Status
- In force
- Countries
- All 27 EU member states
Official text
Verified by
Ahmet Ucar
Principal Consultant (CISSPCertified Information Systems Security Professional, CISMCertified Information Security Manager, CISACertified Information Systems Auditor, CIPP/ECertified Information Privacy Professional/Europe)
Last updated 3 November 2026
Does It Apply to You?
Answer once on your sectors, size and countries. You get the result per country, with the articles behind it.
What CRA Requires
Article 13
Security by design
Design, develop and produce the product in line with the essential requirements of Annex I, Part I, based on a documented cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..
Article 13(8)
Support period
Set a support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. reflecting the expected use time, as a rule at least five years, and handle vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. throughout it.
Annex I, Part II
Vulnerability handling
Identify and document components with a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies., fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. without delay, provide security updates, and run a coordinated vulnerability disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy.
Article 14
Reporting
Report actively exploited vulnerabilitiesA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. and severe incidents within 24 hours, 72 hours and the final deadlines, and inform users.
Show All 7 Requirements
Article 31, Annex VII
Technical documentation
Keep the technical documentation, including the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change., for ten years or the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years..
Article 32
Conformity assessment
Use the procedure for the product's class: self-assessment for default products, harmonised standards or third-party assessment for important products, certification where required for critical products.
Articles 28-30
CE marking
Draw up the EU declaration of conformity and affix the CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws. before placing the product on the market.
More Requirements in Related Documents
- CRA Product CategoriesImplementing Regulation · 4 requirements
- Kamerstuk 36875Rule · 5 requirements
- S.L. 591.06Rule · 4 requirements
| Covered entities | Kind | Article | Where defined |
|---|---|---|---|
| ManufacturerManufacturers of products with digital elements | Role | Article 3(13); Article 13 | Develops or manufactures products with digital elements, or has them designed or made, and markets them under its own name or trademark. |
| Authorised representative | Role | Article 3(15); Article 18 | Holds a written mandate from a manufacturer to perform specified tasks on its behalf. |
| Importer | Role | Article 3(16); Article 19 | Places on the Union market a product bearing the name or trademark of a person established outside the Union; checks conformity and the CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws.. |
| Distributor | Role | Article 3(17); Article 20 | Makes a product available on the Union market, other than the manufacturer or importer. |
| Open-source software stewardA legal person, other than a manufacturer, that systematically provides sustained support for the development of free and open-source software intended for commercial activities and ensures its viability, such as a foundation. The CRA gives stewards a lighter regime instead of full manufacturer obligations. | Role | Article 3(14); Article 24 | Supports on a sustained basis free and open-source software intended for commercial activities, with light-touch duties. |
Where it applies: Products made available on the EU market, wherever the manufacturer is established; manufacturers outside the EU may appoint an authorised representative.
Local representative: Not required.
It applies to products with digital elements made available on the EU market whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network. Default products are self-assessed; important products (Classes I and II, Annex III) and critical products (Annex IV) face stricter conformity assessmentThe process of verifying whether a product, service or system meets the requirements set by the applicable EU act, for example the essential cybersecurity requirements of the CRA or the high-risk requirements of the AI Act. Depending on the risk class, the manufacturer does it alone or with a notified body..
Actively exploited vulnerability Article 14(1)-(2)
When: Early warning within 24 hours of becoming aware, notification within 72 hours, final report within 14 days of a corrective measure being available.
The product, the vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., its exploitation and the corrective or mitigating measures; submitted through the single reporting platform to the CSIRTComputer Security Incident Response Team designated as coordinator and ENISAEuropean Union Agency for Cybersecurity.
24 hours
Severe incident affecting the security of the product Article 14(3)-(4)
When: First notice: Within 24 hours of becoming aware; Incident notification: Within 72 hours of becoming aware; Final report: Within one month of the incident notification
The nature and severity of the incident, its impact and the measures taken; users are also informed.
EU declaration of conformity Articles 28 and 31
When: Before the product is placed on the market, from 11 December 2027.
The declaration that the essential requirements are met, with the technical documentation kept for ten years or the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years., whichever is longer.
| Applies to | Maximum fine |
|---|---|
| Article 64(2) essential requirements and Articles 13 and 14 | EUR 15 million or 2.5% of worldwide (group) annual turnover, whichever is higher |
| Article 64(3) other listed obligations | EUR 10 million or 2% of worldwide (group) annual turnover, whichever is higher |
| Article 64(4) incorrect, incomplete or misleading information | EUR 5 million or 1% of worldwide (group) annual turnover, whichever is higher |
Criminal sanctions: Not provided for.
Fines of up to EUR 15 million or 2.5% of total worldwide annual turnover, whichever is higher, for breaches of the essential requirements and of the manufacturer obligations in Articles 13 and 14; up to EUR 10 million or 2% for other obligations; up to EUR 5 million or 1% for incorrect, incomplete or misleading information. Market surveillance authorities can also require corrective action, withdrawal or recall.
Latest CRA Updates
All CRA Updates-
20 November 2026AdoptedGermany
Bundesrat Clears Germany’s CRA Implementing Act for Promulgation
On 20 November 2026 the Bundesrat let Germany's act implementing the Cyber Resilience Act pass, so it can now be promulgated. Its notification and reporting provisions take effect the day after promulgation and the rest on 11 December 2027.
-
18 November 2026Version releaseEuropean Union
First CRA Standards Published: EN 40000-1-1 and EN 40000-1-2
The first two European standards for the Cyber Resilience Act were published on 18 November 2026: EN 40000-1-1 on terminology and EN 40000-1-2 on principles, product risk management and lifecycle activities. More than 30 more are in development.
-
17 November 2026GuidanceEuropean Union
Commission Publishes Its Cyber Resilience Act Guidance in the Official Journal
The Commission's guidance on applying the Cyber Resilience Act (C/2026/6013) appeared in the Official Journal on 17 November 2026. It is not binding, but sets out the Commission's reading of scope, support periods and the reporting duty in force since 11 September 2026.
CRA Milestones Since 2024
- Reporting obligations applyAlso covers products placed on the market before 11 December 2027, under Article 69(3).
- Rules on conformity assessment bodies applyNotification of conformity assessment bodies, Articles 35 to 51.
- Delegated Regulation (EU) 2026/881 in forceSets when CSIRTs may delay passing on notifications; date counted as the twentieth day after publication on 20 April 2026.
- Implementing Regulation (EU) 2025/2392 enters into forceArticle 3: twentieth day after publication in the OJ on 1 December 2025.
- Enters into force
- Adopted
How We Help With CRA
Start with an assessment, or have us run the work.
Questions
CRA FAQ: Common Questions Answered
What is the Cyber Resilience Act?
Regulation (EU) 2024/2847, the EU law that sets cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. requirements for products with digital elements, such as connected devices and software, placed on the EU market.
When does the Cyber Resilience Act apply?
It entered into force on 10 December 2024. Manufacturers must report actively exploited vulnerabilitiesA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. and severe incidents from 11 September 2026; the product requirements, conformity assessmentThe process of verifying whether a product, service or system meets the requirements set by the applicable EU act, for example the essential cybersecurity requirements of the CRA or the high-risk requirements of the AI Act. Depending on the risk class, the manufacturer does it alone or with a notified body. and CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws. apply from 11 December 2027.
Which products are excluded from the CRA?
Products covered by their own sector requirements, such as medical and in vitro diagnostic devices, motor vehicles and their components under type approvalVehicle Type Approval, civil aviation products and marine equipment, products developed only for national security or defence, and open-source software outside a commercial activity.
What must manufacturers report under the CRA?
Actively exploited vulnerabilitiesA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. and severe incidents affecting the security of their products: an early warning within 24 hours, a notification within 72 hours and a final report, through the single reporting platform to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity.
What are the penalties under the CRA?
Up to EUR 15 million or 2.5% of worldwide annual turnover for breaches of the essential requirements and core manufacturer duties, with lower maximums for other breaches, plus corrective action, withdrawal or recall of products.
Preparing for CRA?
Thirty minutes with a GRC+ consultant: we look at your scope, the requirements that apply and where to start.