What goes in a CRA technical file, and how to keep it current
Annex VII lists eight things the technical documentation must contain. The harder part is keeping it true for every release over a support period of five years or more.
The CRA’s technical documentation is set out in Annex VII. It has to exist before the product is placed on the market and be kept up to date for the support period (Art. 31). You keep it for ten years or the support period, whichever is longer (Art. 13(13)). This post is the first in a series on the technical file. Later parts take the risk assessment, the development process, vulnerability handling and the SBOM in turn.
The eight parts
- A general description of the product: its intended purpose, the software versions that affect compliance, photographs or illustrations for hardware, and the user information of
Annex II. - Design, development, production and vulnerability handling: the system architecture and how the software components fit together, and the production and monitoring processes. For vulnerability handling: the SBOM, the coordinated vulnerability disclosure policy, the contact address for reports and how updates are distributed securely.
- The cybersecurity risk assessment, including how each essential requirement in
Annex I Part Iapplies to the product. - The information used to set the support period.
- The standards applied: harmonised standards, common specifications or certification schemes, and where none were applied, how each essential requirement is met instead.
- Test reports that verify conformity with
Annex I Parts I and II. - A copy of the EU declaration of conformity.
- The SBOM, where a market surveillance authority asks for it with a reasoned request.
Why a file goes stale
Parts 1, 3 and 6 change every time the product does. The SBOM changes with every dependency bump. The risk assessment has to be updated when new information arrives (Art. 13(3)). A file written once as a set of PDFs is accurate on the day it is signed, and drifts from then on.
A living file, with its processes in it
The file is more than a description of the product. Much of it is process: how the product is developed, how its vulnerabilities are handled, how a report under Art. 14 gets made. The file has to show that those processes exist and that this product follows them.
Not every process needs writing for each product. Incident handling and reporting, supplier checks and secure development usually run across the whole company. The file can point to the company-wide procedure and name the version that applies. Beside it sits the product’s own evidence: the triage log, the reports sent, the reviews done. When the procedure changes, every product’s file picks up the change from one place.
One file for every obligation on the product
The CRA is rarely the only thing a connected product has to meet. The same product may be sold in the UK under PSTI, or made by a company whose ISO/IEC 27001 ISMS already sets out how it develops software securely. Much of the evidence is shared. A vulnerability disclosure policy serves the CRA and PSTI alike. The secure development process the ISMS defines can be the one the CRA file relies on.
So put all of it in one file, and map each obligation, whichever regime it comes from, to the same evidence. A change to a process then updates its evidence once, and an auditor for any regime finds what they need in the same place. Separate document sets for each regime drift apart.
A structure that holds up
We build files in three layers:
- Fundamentals. What changes rarely: the product definition, the regulatory scope and class, the development and vulnerability handling processes (or references to the company-wide ones), the support period.
- A release record per version. The risk assessment as it stands, the traceability from each obligation to its evidence, the SBOM, the test reports and the declaration of conformity for that release.
- Release history. Each release’s record, signed and kept, so you can show what was true for any version an authority asks about.
Keep the requirements, threats and traceability as structured files in the same repository as the code. Then a release that changes a component also changes its evidence in the same pull request, and a check in CI can refuse a release whose record is incomplete.
If you’re starting a file, or inheriting one, our CRA assessment checks each essential requirement against what the product already does. It ends with a plan for writing the rest.
Talk to us
Book a 30-minute call
Tell us what the product does and where you sell it. We'll talk through what the CRA is likely to ask of it, and whether an assessment is worth doing.
Book a call or email [email protected]
Useful to have to hand
- What the product is and how it connects
- Where you sell it, and who places it on the EU market
- How often you release software or firmware
- Any date you're working towards