Express + expert help

View pricing →
Skip to main content
referenceCRA7 min read

CRA Annex I — cybersecurity requirements and evidence overview

CRA Annex I in plain terms: the product requirements in Part I, the vulnerability-handling requirements in Part II and the Annex VII evidence that shows each one is met.

By CenitiaUpdated

Fact-checked against the law as of Reviewed by Vladimír Vician on How we check

Annex I to the Cyber Resilience Act (Regulation (EU) 2024/2847) contains the essential cybersecurity requirements. Part I sets requirements for the product itself. Part II sets requirements for how the manufacturer handles vulnerabilities. Article 13(1) of the Cyber Resilience Act requires a product to be designed, developed and produced in accordance with Part I when it is placed on the market, and Article 13(8) requires vulnerabilities to be handled in accordance with Part II for the whole support period. Both apply to products placed on the market from 11 December 2027 (Article 71(2)).

Annex I Part I: requirements for the product

Part I point 1 is the general rule: the product must be designed, developed and produced so that it ensures an appropriate level of cybersecurity based on the risks.

Part I point 2 lists thirteen specific requirements, lettered (a) to (m). They apply on the basis of the manufacturer's cybersecurity risk assessment and where applicable. The product must:

  • (a) be made available on the market without known exploitable vulnerabilities;
  • (b) be made available with a secure-by-default configuration, including the possibility to reset the product to its original state (a different configuration can be agreed with a business user for a tailor-made product);
  • (c) allow vulnerabilities to be addressed through security updates, including, where applicable, automatic security updates enabled as a default setting, with a clear and easy-to-use opt-out, notification of available updates and the option to postpone them temporarily;
  • (d) protect against unauthorised access through appropriate control mechanisms, such as authentication, identity or access management, and report on possible unauthorised access;
  • (e) protect the confidentiality of stored, transmitted or otherwise processed data, for example by encrypting relevant data at rest or in transit with state-of-the-art mechanisms;
  • (f) protect the integrity of data, commands, programs and configuration against manipulation or modification not authorised by the user, and report on corruptions;
  • (g) process only data that are adequate, relevant and limited to what is necessary for the intended purpose (data minimisation);
  • (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, or of connected devices, on the availability of services provided by other devices or networks;
  • (j) be designed, developed and produced to limit attack surfaces, including external interfaces;
  • (k) be designed, developed and produced to 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 access to or modification of data, services or functions, with an opt-out mechanism for the user;
  • (m) let users securely and easily remove all data and settings permanently and, where data can be transferred to other products or systems, ensure that the transfer is done securely.

Deciding which Part I requirements apply

Article 13(2) of the Cyber Resilience Act requires the manufacturer to assess the cybersecurity risks of the product and to take the result into account from planning through to maintenance. Under Article 13(3), the documented risk assessment must state whether and how each requirement in Part I point 2 applies to the product and how it is implemented, and how the manufacturer applies Part I point 1 and Part II. Where a requirement is not applicable, Article 13(4) requires a clear justification in the technical documentation. A requirement cannot simply be left out: the reasoning has to be on file.

For models designed before 11 December 2027, the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013) says that the Regulation does not in itself require new security features or a redesign where the risk assessment shows that existing measures already address the relevant risks (paragraphs 33 and 34). The guidance is not legally binding.

Annex I Part II: vulnerability handling

Part II sets eight requirements for the manufacturer. Under Article 13(8) of the Cyber Resilience Act they apply when the product is placed on the market and for the support period. The manufacturer must:

  1. identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials (SBOM) in a commonly used, machine-readable format covering at least the top-level dependencies;
  2. address and remediate vulnerabilities without delay, in relation to the risks, including by providing security updates; where technically feasible, security updates are provided separately from functionality updates;
  3. apply effective and regular tests and reviews of the security of the product;
  4. once a security update is available, share and publicly disclose information about fixed vulnerabilities, including a description, how to identify the affected product, the impact, the severity and information that helps users remediate; publication can be delayed in duly justified cases until users have had the possibility to apply the patch;
  5. put in place and enforce a policy on coordinated vulnerability disclosure;
  6. facilitate the sharing of information about potential vulnerabilities in the product and in its third-party components, including by providing a contact address for reporting them;
  7. provide mechanisms to distribute updates securely, so that vulnerabilities are fixed or mitigated in a timely manner and, where applicable for security updates, automatically;
  8. disseminate available security updates without delay and free of charge (unless otherwise agreed with a business user for a tailor-made product), with advisory messages that give users the relevant information, including action to take.

Part II is about handling vulnerabilities. The duty to report actively exploited vulnerabilities and severe incidents to the authorities is separate: it sits in Article 14 of the Cyber Resilience Act and has applied since 11 September 2026. See CRA reporting: early warnings, notifications and final reports.

Evidence: what the technical documentation must show

Article 31 of the Cyber Resilience Act requires technical documentation that is drawn up before the product is placed on the market and kept up to date at least during the support period. Annex VII lists its minimum content:

  1. a general description of the product: intended purpose, software versions that affect compliance, photographs or illustrations for hardware, and the user information required by Annex II;
  2. a description of design, development, production and vulnerability handling, including the system architecture, the SBOM, the coordinated vulnerability disclosure policy, evidence of the contact address for vulnerability reports and the technical solution for secure distribution of updates;
  3. the cybersecurity risk assessment, including how the Part I requirements apply;
  4. the information used to determine the support period;
  5. a list of the harmonised standards, common specifications or European cybersecurity certification schemes applied, in full or in part, or a description of the solutions adopted where they were not applied;
  6. reports of the tests carried out to verify conformity of the product and of the vulnerability-handling processes;
  7. a copy of the EU declaration of conformity;
  8. where applicable, the SBOM, on a reasoned request from a market surveillance authority.

A planned control is not evidence that a requirement is met. Annex VII point 6 asks for reports of tests that were carried out, so link each applicable requirement to a test or assessment record for the configuration that is actually placed on the market.

Standards and presumption of conformity

Under Article 27(1) of the Cyber Resilience Act, a product that conforms to a harmonised standard is presumed to conform to the Annex I requirements that the standard covers, but only once the reference of that standard has been published in the Official Journal of the European Union. When we checked on 21 November 2026 we found no such reference published for the Cyber Resilience Act; see CRA harmonised standards for the status and how to check it. Standards cited under other acts do not give that presumption: EN 18031-1, -2 and -3:2024 are cited under the Radio Equipment Directive 2014/53/EU by Implementing Decision (EU) 2025/138.

CRA manufacturer duties, support period and retention (Regulation (EU) 2024/2847, Article 13)

Under the Cyber Resilience Act, for products placed on the market from 11 December 2027, the manufacturer documents a cybersecurity risk assessment and the technical evidence (Article 13(2) to (4), Annex VII). Article 13(8) requires a support period that reflects the time the product is expected to be in use, taking reasonable user expectations into account; it is at least five years unless the expected use is shorter. Article 13(13) requires the technical documentation and the EU declaration of conformity to be kept for at least ten years after the product is placed on the market or for the support period, whichever is longer. Annex VII lists the content of the technical documentation.

CRA penalty ceilings (Regulation (EU) 2024/2847, Article 64)

Under Article 64(2) of the Cyber Resilience Act, non-compliance with the essential cybersecurity requirements in Annex I and with the obligations in Articles 13 and 14 can be fined up to EUR 15 million or, for an undertaking, up to 2.5 % of total worldwide annual turnover, whichever is higher. Other infringements have lower ceilings. Article 64(10) spares microenterprises and small enterprises fines for missing the 24-hour early-warning deadline; it does not exempt them from reporting. These are maximum amounts for Member States’ penalty rules, not automatic fines, and they concern the Cyber Resilience Act only. The Annex I and Article 13 obligations apply from 11 December 2027; Article 14 has applied since 11 September 2026.

Primary references

FAQ

Frequently asked questions

  • How many requirements does CRA Annex I contain?

    Annex I to the Cyber Resilience Act (Regulation (EU) 2024/2847) has two parts. Part I contains one general requirement (point 1: an appropriate level of cybersecurity based on the risks) and thirteen specific product requirements (point 2, letters (a) to (m)). Part II contains eight vulnerability-handling requirements for the manufacturer, numbered 1 to 8.

  • Do all Annex I Part I requirements apply to every product?

    No. Part I point 2 applies on the basis of the manufacturer's cybersecurity risk assessment and where applicable. Under Article 13(3) of the Cyber Resilience Act the risk assessment must state whether and how each requirement applies and how it is implemented. Where a requirement is not applicable, Article 13(4) requires a clear justification in the technical documentation.

  • Is a software bill of materials (SBOM) mandatory under the CRA?

    Yes. Annex I Part II point 1 requires the manufacturer to draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies of the product. It belongs in the technical documentation (Annex VII point 2(b)). The Regulation does not require the manufacturer to publish it: Annex II point 9 applies only if the manufacturer decides to make it available to users, and a market surveillance authority can ask for it by reasoned request (Annex VII point 8).

  • From when must products meet CRA Annex I?

    Products placed on the EU market from 11 December 2027 must meet Annex I (Article 71(2) of the Cyber Resilience Act). Products placed on the market before that date are subject to the requirements only if they are substantially modified from that date (Article 69(2)). The separate Article 14 reporting duty has applied since 11 September 2026.

Continue reading

Related guides

Put this into practice

Free tools & references

New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.