Annex I CRA: the essential cybersecurity requirements
10 min read
Annex I is the technical core of the Cyber Resilience Act. It sets out which properties a product with digital elements must have and how the manufacturer handles vulnerabilities. This guide goes through every requirement in turn and shows how they connect with the risk assessment, the support period, the technical documentation and standards.
Two parts: product and processes
Annex I is headed “Essential cybersecurity requirements” and consists of two parts. Part I concerns the properties of the product itself. Part II concerns vulnerability handling, in other words the manufacturer's processes.
Art. 6 links both parts to market access: products with digital elements are made available on the market only where they meet the requirements of Annex I Part I and the processes put in place by the manufacturer comply with Annex I Part II. For Part I this applies provided that the product is properly installed, maintained, used for its intended purpose or under conditions which can reasonably be foreseen and, where applicable, the necessary security updates have been installed.
According to recital 54, the requirements are meant to ensure that products are secure both when placed on the market and during the time they are expected to be in use.
Source: Art. 6 CRA · Annex I CRA · Recital 54 CRA
Which requirements apply: the risk assessment decides
The manufacturer ensures that the product has been designed, developed and produced in accordance with Annex I Part I (Art. 13(1)). To that end, it assesses the cybersecurity risks of the product and takes the outcome into account from planning through to maintenance (Art. 13(2)).
- Part I point (1) always applies: the product is designed, developed and produced in such a way that it ensures an appropriate level of cybersecurity based on the risks.
- Part I point (2)(a) to (m) apply “on the basis of the cybersecurity risk assessment” and “where applicable”. The assessment indicates whether and how each of these requirements is applicable and how it is implemented (Art. 13(3)).
- Part II: the assessment indicates how the manufacturer is to apply the vulnerability handling requirements (Art. 13(3)). According to recital 54, manufacturers should comply with all vulnerability handling requirements throughout the support period.
Where an essential requirement is not applicable, the manufacturer includes a clear justification in the technical documentation (Art. 13(4)). Recital 55 gives the example of widely recognised interoperability standards whose security features are no longer considered state of the art. Where the manufacturer has nonetheless identified risks in relation to a non-applicable requirement, it should address them by other means, for instance by limiting the intended purpose to trusted environments or by informing users.
How the assessment is structured and when you update it is covered in our guide on the risk assessment.
Source: Art. 13(1) to (4) CRA · Annex I Part I points (1) and (2) CRA · Recital 54 CRA · Recital 55 CRA
Part I: delivery and updates (a–c)
- (a) No known exploitable vulnerabilities: the product is made available on the market without known exploitable vulnerabilities.
- (b) Secure by default: the product is made available with a secure by default configuration, including the possibility to reset it to its original state. For a tailor-made product, manufacturer and business user may agree otherwise.
- (c) Security updates: vulnerabilities must be addressable through security updates. Where applicable, this includes automatic security updates installed within an appropriate timeframe, enabled as a default setting, with a clear and easy-to-use opt-out mechanism. Users are notified of available updates and have the option to postpone them temporarily.
Part I: access and data (d–g, m)
- (d) Protection from unauthorised access by appropriate control mechanisms, including but not limited to authentication, identity or access management systems. Possible unauthorised access is reported.
- (e) Confidentiality: protect stored, transmitted or otherwise processed data, personal or other. The text gives the example of encrypting relevant data at rest or in transit by state of the art mechanisms.
- (f) Integrity: protect data, commands, programs and configuration against any manipulation or modification not authorised by the user, and report on corruptions.
- (g) Data minimisation: process only data that are adequate, relevant and limited to what is necessary in relation to the intended purpose.
- (m) Removal and transfer: users can securely and easily remove all data and settings on a permanent basis. Where data can be transferred to other products or systems, this is done in a secure manner.
Part I: availability, attack surface, logging (h–l)
- (h) Protect the availability of essential and basic functions, also after an incident, including through resilience and mitigation measures against denial-of-service attacks.
- (i) Minimise the negative impact of the product itself or connected devices on the availability of services provided by other devices or networks.
- (j) Limit attack surfaces, including external interfaces.
- (k) Reduce the impact of an incident using appropriate exploitation mitigation mechanisms and techniques.
- (l) Provide security related information by recording and monitoring relevant internal activity, including the access to or modification of data, services or functions. Users get an opt-out mechanism.
How an applicable requirement is implemented is indicated by the manufacturer in the risk assessment (Art. 13(3)).
Source: Annex I Part I point (2)(h) to (l) CRA · Art. 13(3) CRA
Part II: vulnerability handling (points 1–8)
Part II is addressed to manufacturers. They must:
- Identify and document vulnerabilities and components, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies.
- In relation to the risks, address and remediate vulnerabilities without delay, including by providing security updates. Where technically feasible, new security updates are provided separately from functionality updates.
- Apply effective and regular tests and reviews of the security of the product.
- Once a security update has been made available, share and publicly disclose information about fixed vulnerabilities: a description, the affected product, impacts and severity, and clear and accessible information to help users remediate. In duly justified cases, the manufacturer may delay publication until users have been given the possibility to apply the patch.
- Put in place and enforce a policy on coordinated vulnerability disclosure.
- Facilitate the sharing of information about potential vulnerabilities in the product and in third-party components it contains, including by providing a contact address for reporting vulnerabilities.
- Provide for mechanisms to securely distribute updates, so that vulnerabilities are fixed or mitigated in a timely manner and, where applicable for security updates, automatically.
- Disseminate available security updates without delay and free of charge, accompanied by advisory messages with relevant information, including on potential action to be taken. For tailor-made products, manufacturer and business user may agree otherwise.
In addition, Art. 13(6) requires: where the manufacturer identifies a vulnerability in an integrated component, including an open-source component, it reports the vulnerability to the person or entity manufacturing or maintaining the component. Where it has developed a fix itself, it shares the relevant code or documentation.
Source: Annex I Part II points (1) to (8) CRA · Art. 13(6) CRA
For how long: the support period
When placing a product on the market, and for the support period, manufacturers ensure that vulnerabilities of the product, including its components, are handled effectively and in accordance with Annex I Part II (Art. 13(8)).
- The support period reflects the length of time the product is expected to be in use and is at least five years. Where the product is expected to be in use for less than five years, it corresponds to the expected use time.
- The information taken into account to determine it belongs in the technical documentation.
- Each security update under Part II point (8) remains available after it has been issued for a minimum of ten years or for the remainder of the support period, whichever is longer (Art. 13(9)).
- For software with subsequent substantially modified versions, the manufacturer may ensure compliance with Part II point (2) only for the version last placed on the market, provided that users of earlier versions have access to it free of charge and incur no additional costs to adjust their hardware and software environment (Art. 13(10)).
Source: Art. 13(8) to (10) CRA
What belongs in the technical documentation
Annex VII sets the minimum content of the technical documentation. For Annex I, these points matter most:
- Point 2(b): information on the vulnerability handling processes, including the software bill of materials, the coordinated vulnerability disclosure policy, evidence of the contact address and a description of the technical solutions chosen for the secure distribution of updates.
- Point 3: the cybersecurity risk assessment, including how the requirements of Annex I Part I are applicable.
- Point 4: the information taken into account to determine the support period.
- Point 5: the harmonised standards, common specifications or certification schemes applied; where none are applied, descriptions of the solutions adopted to meet the requirements of Annex I Parts I and II.
- Point 6: reports of the tests carried out to verify the conformity of the product and the processes with Annex I Parts I and II.
The manufacturer draws up the technical documentation before placing the product on the market (Art. 13(12)).
Source: Annex VII points 2 to 6 CRA · Art. 13(4) and (12) CRA
Presumption of conformity through standards (Art. 27)
Art. 27(1): products and manufacturer processes in conformity with harmonised standards or parts thereof, the references of which have been published in the Official Journal of the European Union, are presumed to be in conformity with the essential cybersecurity requirements of Annex I covered by those standards.
- The Commission requests European standardisation organisations to draft harmonised standards for the requirements of Annex I (Art. 27(1)).
- The Commission may adopt common specifications by implementing act, but only under certain conditions: among others, where no reference to suitable harmonised standards has been published in the Official Journal and none is expected within a reasonable period. Products and processes in conformity with common specifications are also presumed to conform, in so far as these cover the requirements (Art. 27(2) and (5)).
- An EU statement of conformity or certificate issued under a European cybersecurity certification scheme pursuant to Regulation (EU) 2019/881 also gives rise to the presumption, in so far as it covers the requirements (Art. 27(8)).
The presumption only ever extends as far as the standard, specification or certification covers the requirement in question. For the rest, you describe your own solutions (Annex VII point 5).
Source: Art. 27(1), (2), (5) and (8) CRA · Annex VII point 5 CRA
What applies from when
- From 11 September 2026, Art. 14 applies: manufacturers notify actively exploited vulnerabilities and severe incidents having an impact on the security of the product (Art. 71(2), Art. 14(1) and (3)). This also covers products placed on the market before 11 December 2027 (Art. 69(3)).
- From 11 December 2027, the Regulation applies (Art. 71(2)), and with it Art. 6, Art. 13 and Annex I Parts I and II.
- Products placed on the market before 11 December 2027 are subject to the requirements only if, from that date, they are subject to a substantial modification (Art. 69(2)).
Source: Art. 71(2) CRA · Art. 14(1) and (3) CRA · Art. 69(2) and (3) CRA
In practice
The following points are our own recommendations, not requirements of the Regulation and not legal advice.
- Set up a table with all 22 points (Part I point 1, point 2(a)–(m), Part II points 1–8). For each row: applicable yes or no, justification, implementation, evidence, responsible person.
- Translate each applicable requirement into concrete work items in the backlog, such as reviewing factory settings, a reset function, an update channel with signature verification, roles and permissions, encryption, logging with opt-out, a deletion function.
- Before each release, check for known exploitable vulnerabilities (point (a)), for example by matching the software bill of materials against vulnerability databases.
- Separate security and functionality updates in the release process where technically possible, and record where it is not.
- Set up the contact address and disclosure policy early; the reporting obligation under Art. 14 already applies.
- Watch which harmonised standards appear in the Official Journal, and map your table to the sections of the standards once they are available.
Checklist
- Risk assessment drawn up, covering Part I point 1, each of (a)–(m) and Part II
- Justification for each non-applicable requirement in the technical documentation
- Secure by default configuration and reset to original state
- Update mechanism with notification, where applicable automatic with opt-out and postponement
- Access protection, confidentiality, integrity, data minimisation, deletion function
- Availability, limited attack surface, exploitation mitigation, logging with opt-out
- Software bill of materials covering at least the top-level dependencies
- Regular security tests and test reports
- Coordinated vulnerability disclosure policy, contact address, publication of fixed vulnerabilities
- Support period determined and justified; security updates free of charge and available for long enough
Related guides
- Product and evidenceCybersecurity risk assessment under the Cyber Resilience Act6 min read
- Product and evidenceTechnical documentation under the Cyber Resilience Act7 min read
- Product and evidenceSupport period under the Cyber Resilience Act: at least five years?3 min read
- Product and evidenceWhat is an SBOM? Obligations under the Cyber Resilience Act3 min read
- Reporting obligationsCoordinated vulnerability disclosure under the Cyber Resilience Act5 min read
- Reporting obligationsCyber Resilience Act: reporting under Art. 14, step by step7 min read
- Product and evidenceConformity assessment under the CRA: module A, B + C or H11 min read
- Product and evidenceUser information under Annex II CRA: what must accompany a product8 min read
Terms in the Cyber Resilience Act glossary
Sources
First published 9 Nov 2026, last updated 9 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.