Compliance/Frameworks
CRA Controls: Cyber Resilience Act (Regulation (EU) 2024/2847)
Horizontal cybersecurity requirements for products with digital elements | Reference: Annex I (Parts I and II) and Art. 14/16
Legend: Critical High Medium Low
Annex I, Part I: Essential Cybersecurity Requirements (secure by design)
| Code | Title | Priority | Category | Description |
|---|---|---|---|---|
| CRA-P1-01 | Risk-based cybersecurity (secure by design) | High | Essential Cybersecurity Requirements (Annex I, Part I) | The product with digital elements is designed, developed and produced so as to ensure an appropriate level of cybersecurity based on the identified risks. |
| CRA-P1-02 | Placing on the market without known exploitable vulnerabilities | High | Essential Cybersecurity Requirements (Annex I, Part I) | The product is made available on the market without known exploitable vulnerabilities as of the release date. |
| CRA-P1-03 | Secure by default configuration | High | Essential Cybersecurity Requirements (Annex I, Part I) | The product is made available with a secure by default configuration, including the possibility of resetting the product to its original secure state (except where a specific custom configuration agreement exists with the professional user). |
| CRA-P1-04 | Vulnerabilities fixable through security updates | High | Essential Cybersecurity Requirements (Annex I, Part I) | Vulnerabilities can be fixed through security updates, including, where applicable, automatic updates enabled by default with a simple opt-out option for the user. |
| CRA-P1-05 | Protection against unauthorised access | High | Essential Cybersecurity Requirements (Annex I, Part I) | The product protects itself against unauthorised access through appropriate control mechanisms, including authentication systems and identity and access management, and reports the occurrence of unauthorised access. |
| CRA-P1-06 | Protection of data confidentiality | High | Essential Cybersecurity Requirements (Annex I, Part I) | The confidentiality of stored, transmitted or otherwise processed data is protected through encryption and other technical mechanisms appropriate to the state of the art. |
| CRA-P1-07 | Protection of the integrity of data, commands and configuration | High | Essential Cybersecurity Requirements (Annex I, Part I) | The integrity of stored, transmitted or otherwise processed data, of commands, programs and of the configuration is protected against unauthorised manipulation or modification, with reporting of detected corruption. |
| CRA-P1-08 | Minimisation of processed data | Medium | Essential Cybersecurity Requirements (Annex I, Part I) | The product processes only data, personal or otherwise, that is adequate, relevant and limited to what is necessary for its intended purpose (data minimisation). |
| CRA-P1-09 | Protection of the availability of essential functions | High | Essential Cybersecurity Requirements (Annex I, Part I) | The availability of the product's essential functions is protected, including resilience and mitigation against denial-of-service (DoS) attacks. |
| CRA-P1-10 | Minimisation of negative impact on other devices and networks | Medium | Essential Cybersecurity Requirements (Annex I, Part I) | The negative impact of the product or of devices connected to it on the availability of services provided by other devices or networks is minimised. |
| CRA-P1-11 | Limitation of the attack surface | High | Essential Cybersecurity Requirements (Annex I, Part I) | The product is designed and produced so as to limit attack surfaces, including external interfaces. |
| CRA-P1-12 | Incident impact mitigation mechanisms | High | Essential Cybersecurity Requirements (Annex I, Part I) | The product is designed and produced so as to reduce the impact of an incident through appropriate exploitation mitigation mechanisms and techniques. |
| CRA-P1-13 | Logging and monitoring of security-relevant internal activity | Medium | Essential Cybersecurity Requirements (Annex I, Part I) | The product provides security-related information by recording and/or monitoring relevant internal activity, including access to or changes of data, services or functions, with the possibility for the user to opt out of this functionality. |
| CRA-P1-14 | Secure and permanent removal of user data | Medium | Essential Cybersecurity Requirements (Annex I, Part I) | The product provides a functionality that allows the secure and permanent removal of all user data and settings and, where such data can be transferred to other products or systems, ensures that the transfer is carried out securely. |
Annex I, Part II: Vulnerability Handling
| Code | Title | Priority | Category | Description |
|---|---|---|---|---|
| CRA-P2-01 | Identification and documentation of vulnerabilities and components (SBOM) | High | Vulnerability Handling (Annex I, Part II) | The manufacturer identifies and documents vulnerabilities and components of the product, including by drawing up a Software Bill of Materials (SBOM) in a commonly used, machine-readable format covering at the very least the top-level dependencies of the product. |
| CRA-P2-02 | Remediation of vulnerabilities without undue delay | High | Vulnerability Handling (Annex I, Part II) | Vulnerabilities are addressed and remediated without undue delay through security updates, including, where technically feasible, by providing security updates separately from functionality updates. |
| CRA-P2-03 | Regular security testing and reviews | High | Vulnerability Handling (Annex I, Part II) | Effective and regular security tests and reviews are applied to the software and hardware composition of the product. |
| CRA-P2-04 | Public disclosure of fixed vulnerabilities | Medium | Vulnerability Handling (Annex I, Part II) | Once a security update has been made available, the manufacturer publicly discloses information about the fixed vulnerabilities, including a description, severity and remediation guidance, and may delay disclosure for duly justified security reasons. |
| CRA-P2-05 | Coordinated vulnerability disclosure policy | High | Vulnerability Handling (Annex I, Part II) | The manufacturer puts in place and enforces a coordinated vulnerability disclosure policy. |
| CRA-P2-06 | Sharing of information about potential vulnerabilities | Medium | Vulnerability Handling (Annex I, Part II) | The manufacturer takes measures to facilitate the sharing of information about potential vulnerabilities in the product and in its components, including by providing a published contact address for reporting vulnerabilities. |
| CRA-P2-07 | Secure update distribution mechanisms | High | Vulnerability Handling (Annex I, Part II) | Mechanisms are provided for the secure distribution of security updates for the product, so as to ensure that exploitable vulnerabilities are fixed or mitigated in a timely manner. |
| CRA-P2-08 | Free and prompt dissemination of security updates | High | Vulnerability Handling (Annex I, Part II) | Where available, security updates are disseminated without undue delay and, unless otherwise agreed with the professional user, free of charge, accompanied by advisory messages providing the relevant information, including recommended remediation actions. |
Art. 14 / Art. 16: Notification of Vulnerabilities and Incidents
| Code | Title | Priority | Category | Deadline | Description |
|---|---|---|---|---|---|
| CRA-ART14-01 | Early warning of an actively exploited vulnerability within 24 hours | High | Notification of Vulnerabilities and Incidents (Art. 14) | 24h | The manufacturer notifies ENISA and the designated CSIRT, without undue delay and in any event within 24 hours of becoming aware of it, of an actively exploited vulnerability in the product with digital elements. |
| CRA-ART14-02 | Vulnerability notification within 72 hours | High | Notification of Vulnerabilities and Incidents (Art. 14) | 72h | Within 72 hours of becoming aware of the actively exploited vulnerability, the manufacturer submits a vulnerability notification with detailed information, updating the previous early warning. |
| CRA-ART14-03 | Final vulnerability report | Medium | Notification of Vulnerabilities and Incidents (Art. 14) | 14 days | The manufacturer submits a final report no later than 14 days after a corrective or mitigating measure for the actively exploited vulnerability becomes available. |
| CRA-ART14-04 | Early warning of a severe incident within 24 hours | High | Notification of Vulnerabilities and Incidents (Art. 14) | 24h | The manufacturer notifies ENISA and the designated CSIRT, without undue delay and in any event within 24 hours of becoming aware of it, of a severe incident having an impact on the security of the product with digital elements. |
| CRA-ART14-05 | Severe incident notification within 72 hours | High | Notification of Vulnerabilities and Incidents (Art. 14) | 72h | Within 72 hours of becoming aware of the severe incident, the manufacturer submits an incident notification with detailed information, updating the previous early warning. |
| CRA-ART14-06 | Final severe incident report | Medium | Notification of Vulnerabilities and Incidents (Art. 14) | 1 month | The manufacturer submits a final report no later than one month after the submission of the severe incident notification. |
| CRA-ART14-07 | Submission via the single reporting platform | Medium | Notification of Vulnerabilities and Incidents (Art. 14) | N/A | The notifications provided for in Art. 14 are submitted through the single reporting platform provided for in Art. 16, using the electronic notification end-point of the CSIRT designated as coordinator in the Member State where the manufacturer has its main establishment in the Union, and are simultaneously accessible to ENISA. |
Crosswalks and Scope
- CRA → ISO 27001: 18 mappings.
- CRA → NIS2: 22 mappings, mostly PARTIAL/RELATED (not EQUIVALENT). The CRA regulates products with digital elements placed on the EU market ("secure by design"), whereas NIS2 regulates entities (risk management measures and incident notification at the organisational level). The two frameworks are complementary, not substitutes for one another.
Full application: 11 December 2027 | Art. 14 reporting obligations: from 11 September 2026
Total: 29 controls (14 Annex I Part I + 8 Annex I Part II + 7 Art. 14/16)
Source: Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 (Cyber Resilience Act, CRA). Catalogue derived from the official text (EUR-Lex, eli/reg/2024/2847/oj); wording is summarised and requires human legal review before commercial use.