Regulation

CRA technical documentation: the Annex VII checklist

By SBOMBox SBOM experts · · Updated · 5 min read

Short answer: for every product, the CRA requires a technical file that shows how you meet the essential requirements. Annex VII lists its contents: a product description, design and vulnerability handling information including the SBOM, a cybersecurity risk assessment, how you set the support period, the standards you applied, test reports and the EU declaration of conformity. Keep it for at least 10 years after the product is placed on the market, or the support period if longer. You do not publish it; market surveillance authorities can ask for it.

The Annex VII checklist

CRA technical documentation contents (Annex VII)
Annex VII itemWhat to includeTypical evidence
1. General descriptionIntended purpose, the software versions affecting compliance, photos or illustrations for hardware, and the user information required by Annex IIProduct sheet, release list, user and security instructions
2(a). Design and developmentHow the product is designed and built, including a system architecture that explains how software components build on or feed into each otherArchitecture diagrams, data-flow diagrams, design records
2(b). Vulnerability handlingThe software bill of materials, the coordinated vulnerability disclosure policy, evidence of a contact address for reporting vulnerabilities, and how updates are distributed securelySBOM per version, CVD policy, security.txt or contact page, update signing design
2(c). Production and monitoringProduction and monitoring processes and how they are validatedCI/CD description, build provenance, monitoring runbooks
3. Risk assessmentThe cybersecurity risk assessment under Article 13, including how each Part I essential requirement appliesThreat model, risk register, Annex I applicability matrix
4. Support periodThe information used to set the support period under Article 13(8)Expected-use analysis and the published end date
5. Standards appliedHarmonised standards, common specifications or certification schemes applied in full or in part, or the alternative solutions usedStandards list and gap notes; see EN 40000 harmonised standards
6. Test reportsReports of tests verifying conformity of the product and the vulnerability handling processPenetration tests, SAST/DAST results, process audits
7. Declaration of conformityA copy of the EU declaration of conformitySigned declaration
8. SBOM on requestWhere applicable, the SBOM provided to a market surveillance authority on a reasoned requestExport of the SBOM for the version in question

Item 3 is the backbone. The Annex I checklist lists all 21 essential requirements with the evidence for each, so you can map your risk assessment to it line by line.

How long you must keep it

Manufacturers shall keep the technical documentation and the EU declaration of conformity at the disposal of the market surveillance authorities for at least 10 years after the product with digital elements has been placed on the market or for the support period, whichever is longer.

Regulation (EU) 2024/2847, Article 13(13)

Ten years is longer than most CI systems keep artifacts, and longer than many teams keep a vendor. Store the file, and the SBOM for each version, somewhere that will outlive your build tooling.

Do you have to publish the SBOM?

No. The SBOM is part of the technical documentation under Annex VII, point 2(b), and point 8 says it is supplied to a market surveillance authority 'further to a reasoned request' where the authority needs it to check compliance. You may choose to share SBOMs with customers, and many buyers ask, but the CRA does not require publication. See CRA SBOM requirements for what the SBOM itself must contain.

One file per product, kept current per version

The CRA workspace keeps the SBOM, vulnerability findings and VEX decisions for each release together, which covers much of item 2(b), and the free SBOM checker shows how complete your current SBOMs are.

Frequently asked questions

What is CRA technical documentation?

The file each manufacturer must draw up before placing a product on the market, showing how it meets the Cyber Resilience Act's essential requirements. Its contents are set out in Annex VII.

How long must CRA technical documentation be kept?

At least 10 years after the product is placed on the market, or for the support period if that is longer, together with the EU declaration of conformity.

Does the technical documentation have to be published?

No. It is kept at the disposal of market surveillance authorities, who can request it. Only the EU declaration of conformity, or a simplified version with a link to it, goes to users.

Is the SBOM part of the technical documentation?

Yes. Annex VII, point 2(b) lists the software bill of materials as part of the vulnerability handling information, and point 8 covers providing it to authorities on a reasoned request.

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