# CRA Annex I essential requirements: the full checklist

URL: https://sbombox.com/blog/cra-annex-i-essential-requirements
By SBOMBox SBOM experts. Published 2026-11-13

> Every CRA Annex I essential requirement in plain English: 13 product security properties, 8 vulnerability-handling duties and the evidence for each.

Short answer: Annex I of the Cyber Resilience Act (Regulation (EU) 2024/2847) holds the essential cybersecurity requirements every product with digital elements must meet from 11 December 2027. Part I sets 13 security properties for the product itself, applied on the basis of your risk assessment. Part II sets 8 vulnerability-handling duties that run for the whole support period. Together they are the checklist your technical documentation must answer, requirement by requirement.

## How Annex I is structured

Part I, point (1) is the overarching rule: products must be designed, developed and produced to ensure an appropriate level of cybersecurity based on the risks. Point (2) then lists thirteen properties, (a) to (m), that apply 'on the basis of the cybersecurity risk assessment' and 'where applicable'. That wording matters: you do not have to implement every property in every product, but you must record in the risk assessment why a property does or does not apply. Part II applies in full to every product.

New to the regulation? Start with [what the Cyber Resilience Act is](https://sbombox.com/blog/what-is-the-eu-cyber-resilience-act), then come back to this checklist.

## Part I: product security requirements

**Annex I, Part I, point (2): the 13 security properties**

| Point | Requirement in plain English | Typical evidence |
| --- | --- | --- |
| (a) | Ship without known exploitable vulnerabilities | Vulnerability scan of the release SBOM, with VEX for anything not fixed |
| (b) | Secure by default configuration, with a way to reset to the original state | Default configuration review; reset procedure |
| (c) | Vulnerabilities can be fixed through security updates, automatic by default where applicable, with an opt-out and a postpone option | Update mechanism design; release notes |
| (d) | Protection from unauthorised access: authentication, identity and access management, and reporting of possible unauthorised access | Access-control design; penetration test results |
| (e) | Confidentiality of stored, transmitted and processed data, for example encryption at rest and in transit | Encryption inventory (a [CBOM](https://sbombox.com/blog/cryptographic-bill-of-materials-cbom) helps) |
| (f) | Integrity of data, commands, programs and configuration, and reporting of corruption | Signed updates; integrity checks |
| (g) | Data minimisation: process only the data needed for the intended purpose | Data-flow inventory; privacy review |
| (h) | Availability of essential functions, also after an incident, including resilience against denial-of-service | Resilience testing; recovery design |
| (i) | Minimise negative impact on the availability of other devices and networks | Rate limiting and network behaviour tests |
| (j) | Limit attack surfaces, including external interfaces | Interface inventory; closed ports and debug interfaces |
| (k) | Reduce the impact of incidents with exploitation mitigation mechanisms | Hardening flags; sandboxing; memory-safety measures |
| (l) | Record and monitor relevant internal activity (security logging), with a user opt-out | Logging design |
| (m) | Let users securely and permanently remove all data and settings, and transfer them securely where possible | Data-deletion procedure; test record |

## Part II: vulnerability-handling requirements

Part II applies for the whole support period, which must be at least five years unless the product is expected to be used for less. See [how long you must support a product](https://sbombox.com/blog/cra-support-period). The first requirement is the SBOM:

> Manufacturers of products with digital elements shall: (1) 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;
>
> — Regulation (EU) 2024/2847, Annex I, Part II, point (1). [Official text on EUR-Lex](https://eur-lex.europa.eu/eli/reg/2024/2847/oj)

**Annex I, Part II: the 8 vulnerability-handling duties**

| Point | Requirement in plain English | Typical evidence |
| --- | --- | --- |
| (1) | Identify and document components and vulnerabilities, including an SBOM | An SBOM per release; see [CRA SBOM requirements](https://sbombox.com/blog/cra-sbom-requirements) |
| (2) | Address and remediate vulnerabilities without delay, with security updates separate from feature updates where technically feasible | Vulnerability tickets with dates; release history |
| (3) | Test and review the product's security effectively and regularly | Test plans and results per release |
| (4) | Once a fix is available, publicly disclose fixed vulnerabilities: description, affected products, impact, severity and remediation | Security advisories; see [CSAF and VEX](https://sbombox.com/blog/csaf-vs-vex-security-advisories) |
| (5) | Have and enforce a coordinated vulnerability disclosure policy | Published CVD policy |
| (6) | Make it easy to report vulnerabilities, including a contact address | security.txt; security contact page |
| (7) | Distribute updates securely, automatically where applicable | Signed update channel |
| (8) | Disseminate security updates without delay and free of charge, with advisory messages | Update notices; pricing terms |

## How to use this checklist

- Run the risk assessment first. For each Part I property, record whether it applies and why. 'Not applicable' needs a reason.
- Map each requirement to a harmonised standard where one exists. Applying harmonised standards gives a presumption of conformity; see [EN 40000 and the CRA harmonised standards](https://sbombox.com/blog/cra-harmonised-standards-en-40000).
- Attach evidence per release, not once. Part II duties are continuous, so your evidence must be dated.
- File everything in the technical documentation (Annex VII). See the [technical documentation checklist](https://sbombox.com/blog/cra-technical-documentation-checklist).
- Check your product category: important and critical products need stricter conformity assessment. See [important and critical products](https://sbombox.com/blog/cra-important-and-critical-products).

## Where SBOMBox fits

SBOMBox covers the evidence for Part I (a) and Part II (1), (2) and (4): an SBOM per release, continuous vulnerability matching, VEX decisions and an audit trail. Score your current SBOM against the CRA readiness ruleset on the [free SBOM checker](https://sbombox.com/audit), or see the [CRA workspace](https://sbombox.com/cra).

## Frequently asked questions

### How many essential requirements does the CRA have?

Annex I has 21 specific requirements: 13 product security properties in Part I, point (2)(a) to (m), and 8 vulnerability-handling duties in Part II, points (1) to (8). Part I, point (1) adds the general duty to ensure an appropriate level of cybersecurity based on the risks.

### Do all Annex I requirements apply to every product?

Part II applies to every product. The Part I properties apply on the basis of your cybersecurity risk assessment and where applicable, so you must document why each one does or does not apply.

### When do the CRA essential requirements apply?

From 11 December 2027. Vulnerability and incident reporting under Article 14 has applied since 11 September 2026.

### Is there a harmonised standard for Annex I?

Harmonised standards are being developed, including the EN 40000 series. Applying a published harmonised standard gives a presumption of conformity with the requirements it covers.

### Is an SBOM part of the essential requirements?

Yes. Annex I, Part II, point (1) requires an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies.

This is general information, not legal advice. Confirm how the rules apply to your products with counsel.
