shipcra

CRA Annex I checklist: the essential cybersecurity requirements, item by item

Reviewed 4 min read

Annex I lists the essential cybersecurity requirements that every product in scope must meet from 11 December 2027. Part I covers the product itself, such as secure defaults, security updates and data protection. Part II covers how you handle vulnerabilities, including the SBOM, a disclosure policy and free security updates.

Key facts

Where
Annex I of Regulation (EU) 2024/2847
Part I
A general requirement and 13 specific ones, (a) to (m), on the product’s properties
Part II
8 requirements on vulnerability handling
Applies from
11 December 2027
How Part I is applied
On the basis of your cybersecurity risk assessment, where applicable

How to read this checklist

Each line paraphrases one requirement of Annex I and suggests evidence a small team can realistically keep. The wording of the regulation is the reference; this is a working aid. Start with your cybersecurity risk assessment: it tells you which Part I items apply and how strictly.

Part I: properties of the product

# Requirement Evidence you can keep
1 Designed, developed and produced to ensure a level of cybersecurity appropriate to the risks The risk assessment and the design decisions it led to
2a No known exploitable vulnerabilities when placed on the market A dependency scan of the release build, with open findings resolved or justified
2b Secure by default configuration, with a way to reset to the original state A list of default settings and why each is safe
2c Vulnerabilities can be fixed through security updates, automatic by default with a clear opt-out where applicable Your update mechanism and its default setting
2d Protection from unauthorised access through authentication, identity or access management How accounts, sessions and admin functions are protected
2e Confidentiality of stored and transmitted data, for example by encryption TLS configuration and how sensitive data is stored
2f Integrity of data, commands, programs and configuration against unauthorised changes Code signing, integrity checks, server-side validation
2g Only process the data needed for the product’s intended purpose (data minimisation) A data inventory tied to features
2h Protect the availability of essential functions, including against denial-of-service Rate limits, offline behaviour, backend resilience
2i Minimise the negative impact on other devices or networks How the product limits traffic and background activity
2j Limit attack surfaces, including external interfaces A list of exposed endpoints, ports and permissions
2k Reduce the impact of an incident with exploitation mitigation Sandboxing, least privilege, memory-safe choices
2l Record and monitor relevant internal activity, with an opt-out for the user What you log, for how long, and how users switch it off
2m Let users remove all data and settings securely and permanently Account deletion and local data wipe

Part II: vulnerability handling

# Requirement Evidence you can keep
1 Identify and document components and vulnerabilities, including an SBOM covering at least top-level dependencies An SBOM for each release
2 Address and remediate vulnerabilities without delay, including by providing security updates, separately from feature updates where technically feasible Your patch policy and release history
3 Test and review the product’s security regularly Review notes, pen-test or automated scan reports
4 Once an update is available, publicly disclose information on fixed vulnerabilities Security advisories or release notes with severity and remedy
5 Put in place and enforce a coordinated vulnerability disclosure policy A published vulnerability disclosure policy
6 Make it easy to report vulnerabilities, including by providing a contact address A security contact, for example in security.txt
7 Distribute updates securely so fixes are delivered in a timely way Signed builds and the store or update channel you use
8 Provide security updates without delay and free of charge, with advisory messages for users Your update notes and how users are told

Point 4 allows you to delay publication in duly justified cases, for example when publishing would put users at greater risk before they can update.

Turning the checklist into documentation

For every line, write one of three things in your technical documentation: how you meet it, why it doesn’t apply to your product, or what you are changing and by when. Link to the evidence rather than copying it.

Two items need decisions you should make early, because they shape the product:

  • The support period. Part II applies for the whole support period, normally at least five years. Pick an end date you can honour and tell users.
  • Automatic security updates. Part I, point 2c expects automatic updates by default with an opt-out, where applicable. App stores handle much of this for mobile apps; desktop software and games may need their own updater.

What comes after the checklist

With the requirements met and documented, you can complete the conformity assessment and draw up the EU declaration of conformity. The declaration of conformity guide covers what goes in it and what to check before you sign.

Questions

Does every Annex I requirement apply to every product?

Part I is applied on the basis of your cybersecurity risk assessment and where applicable, so some items may not fit your product. You then record why. Part II, on vulnerability handling, applies to every manufacturer in scope.

Are there harmonised standards for Annex I yet?

European standardisation bodies are drafting them. Until a standard is published in the Official Journal, applying it doesn’t give a presumption of conformity, so you show how you meet each requirement yourself.

Is a completed Annex I checklist proof of compliance?

No. It is a way to organise the work and the evidence. Conformity comes from meeting the requirements, documenting how, and completing the conformity assessment.

Sources

  1. Regulation (EU) 2024/2847, Annex I, EUR-Lex
  2. Cyber Resilience Act, European Commission
  3. OCCTET: CRA best practices and checklists for SMEs and open source projects

This guide explains the regulation in general terms. It isn’t legal advice for your product.

Draft the paperwork from your answers.

The pack turns your Annex I answers into a gap report, technical documentation and a draft declaration that you review and sign.

Join early access