What goes in each section of a CRA Annex VII technical file

Article 31(1) of Regulation (EU) 2024/2847 provides that the technical documentation “shall at least contain the elements set out in Annex VII”. Annex VII is eight numbered points; the first two break down into lettered sub-points, which is how the eight become thirteen items in practice. Each one below carries the regulation's own words, its citation, and one line on what a real answer looks like.

Annex VII, point 1(a) — General description of the product with digital elements, including its intended purpose.

“its intended purpose;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 1(a).

A real answer describes what the product does and what it is for in prose a non-engineer can follow, and says plainly what it does not do. No scan can write it.

Annex VII, point 1(b) — General description must state versions of software affecting compliance with essential cybersecurity requirements.

“versions of software affecting compliance with essential cybersecurity requirements;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 1(b).

ceproof derives this from the release identity in version control: a real tag, not a bare commit hash, which it deliberately refuses to treat as a version.

Annex VII, point 1(c) — For hardware products, photographs or illustrations showing external features, marking and internal layout.

“where the product with digital elements is a hardware product, photographs or illustrations showing external features, marking and internal layout;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 1(c).

Only relevant for hardware products. A software-only product says so, and says why, rather than leaving the item blank.

Annex VII, point 1(d) — User information and instructions as set out in Annex II.

“user information and instructions as set out in Annex II;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 1(d).

Points at the user documentation required by Annex II. A real answer references the shipped documentation, not a promise to write it.

Annex VII, point 2(a) — Necessary information on the design and development of the product, including drawings/schemes and a description of the system architecture.

“necessary information on the design and development of the product with digital elements, including, where applicable, drawings and schemes and a description of the system architecture explaining how software components build on or feed into each other and integrate into the overall processing;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 2(a).

Architecture and design: how the components fit together and how data moves through them. Usually an existing internal design document, referenced.

Annex VII, point 2(b) — Necessary information and specifications of the vulnerability handling processes: software bill of materials, coordinated vulnerability disclosure policy, contact address for reporting vulnerabilities, and secure update distribution.

“necessary information and specifications of the vulnerability handling processes put in place by the manufacturer, including the software bill of materials, the coordinated vulnerability disclosure policy, evidence of the provision of a contact address for the reporting of the vulnerabilities and a description of the technical solutions chosen for the secure distribution of updates;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 2(b).

ceproof can evidence parts of this — a security policy file, a disclosure contact, SBOM readiness — which is why it is the one item marked partial rather than derived.

Annex VII, point 2(c) — Necessary information and specifications of the production and monitoring processes of the product and the validation of those processes.

“necessary information and specifications of the production and monitoring processes of the product with digital elements and the validation of those processes;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 2(c).

How the product is built, released and monitored, and how those processes are validated. Your release engineering, written down.

Annex VII, point 3 — An assessment of the cybersecurity risks against which the product is designed, developed, produced, delivered and maintained pursuant to Article 13, including how the essential cybersecurity requirements in Annex I Part I are applicable.

“an assessment of the cybersecurity risks against which the product with digital elements is designed, developed, produced, delivered and maintained pursuant to Article 13, including how the essential cybersecurity requirements set out in Part I of Annex I are applicable;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 3.

The risk assessment itself. This is the single largest piece of human work in the pack, and no repository scan can stand in for it.

Annex VII, point 4 — Relevant information taken into account to determine the support period pursuant to Article 13(8).

“relevant information that was taken into account to determine the support period pursuant to Article 13(8) of the product with digital elements;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 4.

Not just the support period, but the reasoning that produced it — what you took into account when you chose that length.

Annex VII, point 5 — A list of the harmonised standards, common specifications, or European cybersecurity certification schemes applied (in full or in part), or descriptions of the solutions adopted where none were applied.

“a list of the harmonised standards applied in full or in part the references of which have been published in the”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 5.

Which harmonised standards, common specifications or certification schemes you applied, in full or in part, and what you did instead where none were applied.

Annex VII, point 6 — Reports of the tests carried out to verify conformity of the product and of the vulnerability handling processes with the essential cybersecurity requirements in Annex I Parts I and II.

“reports of the tests carried out to verify the conformity of the product with digital elements and of the vulnerability handling processes with the applicable essential cybersecurity requirements as set out in Parts I and II of Annex I;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 6.

Test reports covering both the product and the vulnerability handling processes. References to the real reports, not a summary of them.

Annex VII, point 7 — A copy of the EU declaration of conformity.

“a copy of the EU declaration of conformity;”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 7.

The Annex V declaration itself, included in the pack. ceproof composes this item from the Annex V draft it generates, so the two never disagree.

Annex VII, point 8 — Where applicable, the software bill of materials, further to a reasoned request from a market surveillance authority.

“where applicable, the software bill of materials, further to a reasoned request from a market surveillance authority provided that it is necessary in order for that authority to be able to check compliance with the essential cybersecurity requirements set out in Annex I.”

Regulation (EU) 2024/2847 (Cyber Resilience Act), consolidated text 02024R2847-20241120 (base act + Corrigenda 1-3, none of which touch Annex V, Annex VII, or Articles 13/31/33), Annex VII, point 8.

The SBOM, produced on a reasoned request from a market surveillance authority. ceproof emits CycloneDX 1.6 and SPDX 2.3 for free; see where the SBOM obligation sits.

The shape of the work

Two of the thirteen can be derived from a repository scan, one partially. The remaining ten need a person who understands the product. That is not a limitation of any particular tool — most of Annex VII asks for judgement, not for facts that exist in source code.

See all thirteen filled in, in a real generated pack → · The same items alongside Annex V →

Draft yours from your own repository

ceproof lays out all 21 items in the regulation's order, cites each one, derives what your repository can evidence, and lists what is still open. Free to scan and to see the gap checklist. $99, one-time to export the Annex VII pack and the Annex V DoC draft.

Needs a repository with an npm or Python manifest. C or C++ firmware is not supported today.