Annex I

Essential Cybersecurity Requirements for Products with Digital Elements

Annex I of the EU Cyber Resilience Act lists the essential cybersecurity requirements every product with digital elements must satisfy for CE marking and EU market access from 11 December 2027. It covers two sets of requirements: Part I covers product security properties (design and development), and Part II covers vulnerability handling processes (post-market obligations).

Effective: December 2027Applies to: All manufacturers of products with digital elements sold in the EU marketLast reviewed: 13 November 2026Verified against: the final text of Regulation (EU) 2024/2847
Source: Regulation (EU) 2024/2847, Annex I, official text on EUR-Lex

Structure: Part I and Part II

Annex I is divided into two parts:

Part I - Product Properties: Security requirements that must be built into the product before it is placed on the market. These are engineering and design requirements.

Part II - Vulnerability Handling: Post-market obligations for how manufacturers manage vulnerabilities discovered after the product is sold. These are operational and process requirements.

Both parts are mandatory for all in-scope products, and the conformity assessment covers both. Part II also governs ongoing obligations throughout the support period.

CRA reference:Annex I, Article 6

Part I: Product Security Properties (Design Requirements)

Part I has two points. The text below is quoted from Annex I.

reads "Products with digital elements shall be designed, developed and produced in such a way that they ensure an appropriate level of cybersecurity based on the risks."

Annex I, Part I(2) lists 13 requirements, (a) to (m), under this opening sentence. "On the basis of the cybersecurity risk assessment referred to in Article 13(2) and where applicable, products with digital elements shall:"

  • No known exploitable vulnerabilities (). "be made available on the market without known exploitable vulnerabilities;"
  • Secure by default (). "be made available on the market with a secure by default configuration, unless otherwise agreed between manufacturer and business user in relation to a tailor-made product with digital elements, including the possibility to reset the product to its original state;"
  • Security updates (). "ensure that vulnerabilities can be addressed through security updates, including, where applicable, through automatic security updates that are installed within an appropriate timeframe enabled as a default setting, with a clear and easy-to-use opt-out mechanism, through the notification of available updates to users, and the option to temporarily postpone them;"
  • Protection from unauthorised access (). "ensure protection from unauthorised access by appropriate control mechanisms, including but not limited to authentication, identity or access management systems, and report on possible unauthorised access;"
  • Confidentiality of data (). "protect the confidentiality of stored, transmitted or otherwise processed data, personal or other, such as by encrypting relevant data at rest or in transit by state of the art mechanisms, and by using other technical means;"
  • Integrity of data (). "protect the integrity of stored, transmitted or otherwise processed data, personal or other, commands, programs and configuration against any manipulation or modification not authorised by the user, and report on corruptions;"
  • Data minimisation (). "process only data, personal or other, that are adequate, relevant and limited to what is necessary in relation to the intended purpose of the product with digital elements (data minimisation);"
  • Availability of essential functions (). "protect the availability of essential and basic functions, also after an incident, including through resilience and mitigation measures against denial-of-service attacks;"
  • Minimise impact on other devices (). "minimise the negative impact by the products themselves or connected devices on the availability of services provided by other devices or networks;"
  • Limit attack surfaces (). "be designed, developed and produced to limit attack surfaces, including external interfaces;"
  • Reduce impact of incidents (). "be designed, developed and produced to reduce the impact of an incident using appropriate exploitation mitigation mechanisms and techniques;"
  • Security-relevant logging (). "provide security related information by recording and monitoring relevant internal activity, including the access to or modification of data, services or functions, with an opt-out mechanism for the user;"
  • Secure data deletion / portability (). "provide the possibility for users to securely and easily remove on a permanent basis all data and settings and, where such data can be transferred to other products or systems, ensure that this is done in a secure manner."
CRA reference: / to (2)(m)

Part II: Vulnerability Handling Requirements

Part II always applies in full. The text below is quoted from Annex I. Part II opens with "Manufacturers of products with digital elements shall:"

  • Identify & document vulnerabilities and components (SBOM) (). "identify and document vulnerabilities and components contained in products with digital elements, 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 of the products;"
  • Address & remediate without delay (). "in relation to the risks posed to products with digital elements, address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, new security updates shall be provided separately from functionality updates;"
  • Regular security testing & reviews (). "apply effective and regular tests and reviews of the security of the product with digital elements;"
  • Public disclosure of fixed vulnerabilities (). "once a security update has been made available, share and publicly disclose information about fixed vulnerabilities, including a description of the vulnerabilities, information allowing users to identify the product with digital elements affected, the impacts of the vulnerabilities, their severity and clear and accessible information helping users to remediate the vulnerabilities; in duly justified cases, where manufacturers consider the security risks of publication to outweigh the security benefits, they may delay making public information regarding a fixed vulnerability until after users have been given the possibility to apply the relevant patch;"
  • Coordinated vulnerability disclosure policy (). "put in place and enforce a policy on coordinated vulnerability disclosure;"
  • Facilitate vulnerability information sharing (). "take measures to facilitate the sharing of information about potential vulnerabilities in their product with digital elements as well as in third-party components contained in that product, including by providing a contact address for the reporting of the vulnerabilities discovered in the product with digital elements;"
  • Secure update distribution (). "provide for mechanisms to securely distribute updates for products with digital elements to ensure that vulnerabilities are fixed or mitigated in a timely manner and, where applicable for security updates, in an automatic manner;"
  • Timely, free security patches (). "ensure that, where security updates are available to address identified security issues, they are disseminated without delay and, unless otherwise agreed between a manufacturer and a business user in relation to a tailor-made product with digital elements, free of charge, accompanied by advisory messages providing users with the relevant information, including on potential action to be taken."

Annex I does not name a format for advisories. CSAF is a common machine-readable choice, not a legal requirement. The support period comes from Article 13, not from Annex I.

CRA reference: to (8)

The 'No Known Vulnerabilities' Requirement

One of the most operationally significant Part I requirements is . Products must "be made available on the market without known exploitable vulnerabilities".

  • Known vulnerabilities in third-party components (checked against CVE databases, vendor advisories, and SBOMs) must be addressed before release.
  • Security testing must be conducted before placing products on the market.
  • requires manufacturers to identify and document 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 of the products". The SBOM is how component vulnerabilities are tracked.

This requirement places a practical obligation on manufacturers to perform pre-release vulnerability scanning and to maintain an SBOM that covers at least the top-level dependencies.

CRA reference:

Secure Update Requirements

requires that vulnerabilities can be addressed through security updates, including through the notification of available updates to users. requires mechanisms to securely distribute updates. In practice this means:

  • Updates should be signed or otherwise verifiable by the device.
  • The update mechanism itself must be resistant to attack (e.g., update-in-transit attacks, rollback attacks).
  • Users must be notified when security updates are available.
  • For products that cannot receive over-the-air updates, there must be a documented alternative update process.

This requirement has major implications for embedded systems and industrial IoT, where over-the-air updates are not standard practice.

CRA reference: /

Free Security Updates and Support Period

requires manufacturers to "ensure that, where security updates are available to address identified security issues, they are disseminated without delay and, unless otherwise agreed between a manufacturer and a business user in relation to a tailor-made product with digital elements, free of charge, accompanied by advisory messages providing users with the relevant information, including on potential action to be taken."

The support period comes from Article 13. The Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act) states that "Article 13(8) further requires that the support period be at least five years, unless the product with digital elements is expected to be in use for less than five years, in which case the support period shall correspond to the expected use time." This means:

  • You must define and publicly disclose the security support period for each product.
  • Security patches cannot be paywalled or tied to a paid support contract.
  • The support period should be commensurate with the expected use life of the product - which for many IoT and industrial products can be 10–20 years.

This requirement has significant commercial implications for manufacturers who currently monetise ongoing security support.

CRA reference:, Article 13

Conformity Assessment Against Annex I

To obtain CE marking for a product with digital elements, manufacturers must demonstrate conformity with Annex I. Article 32 sets the routes:

  1. Self-assessment (Module A) - available for products in the default category. An Important Class I product can use it only when harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least "substantial" are fully applied (Article 32(2)). No CRA harmonised standard is cited yet, so most Class I products have no Module A route today.
  2. Third-party routes - EU-type examination (Module B) plus conformity to type (Module C), or full quality assurance (Module H). Class I products use them when those standards are not fully applied. Class II products always use a third-party route, or a certification scheme specified under Article 27(9) at assurance level at least "substantial", for the requirements it covers (Article 32(3)).
  3. European cybersecurity certification - critical products (Annex IV) use a scheme under Article 8(1). Where the Article 8(1) conditions are not met, the Class II routes apply (Article 32(4)).

For all routes, the manufacturer must maintain a technical file documenting how each Annex I requirement is met.

CRA reference:Article 32, Annex I

Work through Annex I for each product in one CRA workspace.

Classify the product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

What is the minimum security support period required by Annex I?+

Annex I does not set the support period. Article 13 does. The Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act) states that "Article 13(8) further requires that the support period be at least five years, unless the product with digital elements is expected to be in use for less than five years, in which case the support period shall correspond to the expected use time." Many industrial and infrastructure products are in use for much longer than five years.

Does Annex I apply to B2B products or only consumer products?+

Annex I applies to all in-scope products with digital elements, regardless of whether they are sold to businesses or consumers. The CRA's scope covers products placed on the EU market, not just consumer goods.

Is an SBOM mandatory under Annex I?+

Yes. requires manufacturers to "identify and document vulnerabilities and components contained in products with digital elements, 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 of the products;" Going beyond the top-level dependencies is good practice for vulnerability tracking, not a legal floor.

What cryptographic standards satisfy the data protection requirement?+

The CRA does not mandate specific algorithms. requires products to protect the confidentiality of data "such as by encrypting relevant data at rest or in transit by state of the art mechanisms, and by using other technical means". In practice, this means TLS 1.2+ for transport security, AES-128 or higher for data at rest, and avoiding known-broken algorithms like MD5, SHA-1, or DES.

Need a CVD policy for Annex I?

Annex I Part II(5) asks for a coordinated vulnerability disclosure policy. Download a free template.

Browse templates →