Technical documentation under the Cyber Resilience Act
7 min read
The technical documentation is the evidence that product and processes meet the requirements of the Cyber Resilience Act. It is drawn up before placing on the market, keeps growing with every version and must remain available for at least ten years. This guide goes through what belongs in it, point by point.
What it has to achieve
The technical documentation contains all relevant data or details of the means used by the manufacturer to ensure that the product and its processes comply with the essential cybersecurity requirements in Annex I. Annex VII sets the minimum content (Art. 31(1)). So ticking off the points of the annex is not enough: anyone reading the documents must be able to follow how the requirements are met.
Art. 13(12) sets the order before placing on the market: first the technical documentation, then the conformity assessment, then the EU declaration of conformity and CE marking. These obligations apply from 11 December 2027 (Art. 71(2)).
Annex VIII shows who examines the documents: under internal control (Module A), the manufacturer draws them up and keeps them available. Under EU-type examination (Module B) and full quality assurance (Module H), a notified body examines them.
Source: Art. 31(1) CRA · Art. 13(12) CRA · Art. 71(2) CRA · Annex VIII Parts I, II and IV CRA
The minimum content (Annex VII)
Annex VII requires the following information, as applicable to the product concerned:
- General description: intended purpose, software versions affecting compliance with the requirements, for hardware photographs or illustrations of external features, marking and internal layout, plus the user information and instructions under Annex II.
- Design, development and production: where applicable drawings and schemes and a description of the system architecture explaining how software components build on or feed into each other; the vulnerability handling processes; the production and monitoring processes and their validation.
- An assessment of the cybersecurity risks under Art. 13, including how the requirements of Annex I Part I are applicable.
- Relevant information taken into account to determine the support period.
- A list of the harmonised standards, common specifications or European cybersecurity certification schemes applied, otherwise a description of the solutions adopted.
- Reports of the tests carried out to verify the conformity of the product and the vulnerability handling processes.
- A copy of the EU declaration of conformity.
- Where applicable, the software bill of materials further to a reasoned request from a market surveillance authority, if the authority needs it for its check.
Source: Annex VII CRA · Art. 31(1) CRA
The processes belong in it too
The Cyber Resilience Act looks not only at the product but also at how vulnerabilities are handled. Under Annex VII point 2(b), the documents therefore include:
- the software bill of materials,
- the coordinated vulnerability disclosure policy,
- evidence that a contact address for reporting vulnerabilities is provided,
- a description of the technical solutions chosen for the secure distribution of updates.
On the SBOM: Annex VII mentions it twice, in point 2(b) and in point 8 (provided further to a reasoned request from the authority). Manufacturers do not have to publish it (recital 77).
What does not apply is justified
Where individual essential requirements do not apply to the product, a clear justification goes into the technical documentation (Art. 13(4)). The risk assessment itself is part of the documents and must show whether and how the requirements of Annex I Part I are implemented (Art. 13(3)).
In its guidelines, the Commission addresses cases where a requirement cannot be fully met, for example because of mandatory interoperability. Manufacturers should document such constraints and the associated risks, implement compensating measures and periodically check whether the constraint still exists.
A product type developed before the Cyber Resilience Act need not necessarily be redesigned either. But the manufacturer must be able to demonstrate through the risk assessment and technical documentation that it achieves an appropriate level of cybersecurity and meets the requirements.
Source: Art. 13(3) and (4) CRA · Commission guidance C/2026/6013, points 32, 36, 37
With or without standards
Annex VII point 5 requires a list of the harmonised standards, common specifications and European certification schemes applied in full or in part. Where they are applied in part, the documents specify which parts.
If none of these is applied, the manufacturer describes the solutions adopted to meet Annex I Parts I and II and lists the other relevant technical specifications applied.
Source: Annex VII point 5 CRA
Keeping it up to date
The technical documentation is drawn up before placing on the market and continuously updated where appropriate, at least during the support period (Art. 31(2)). Art. 13(7) adds to this: the manufacturer systematically documents, in a manner proportionate to the risks, the relevant cybersecurity aspects, including vulnerabilities it becomes aware of and information from third parties, and updates the risk assessment where applicable.
According to the guidelines, this applies whether or not an update is a substantial modification: the risk assessment and technical documentation must stay accurate, complete and up to date with ordinary updates as well.
Source: Art. 31(2) CRA · Art. 13(7) CRA · Commission guidance C/2026/6013, point 113
Keeping and providing it
The manufacturer keeps the technical documentation and the EU declaration of conformity at the disposal of the market surveillance authorities for at least ten years after placing on the market or for the support period, whichever is longer (Art. 13(13)). The same period applies to an authorised representative who takes on this task (Art. 18(3)). Importers must ensure that they can provide the documentation on request (Art. 19(6)).
On a reasoned request, the manufacturer provides the authority with all information and documents needed to demonstrate conformity, on paper or electronically and in a language easily understood by the authority (Art. 13(22)). Art. 31 and Annex VII contain no obligation to publish the technical documentation.
Breaches can be costly: Art. 64 provides for fines of up to EUR 15 million or 2.5% of worldwide annual turnover for breaches of Art. 13 and up to EUR 10 million or 2% for breaches of Art. 31(1) to (4), in each case whichever is higher. Incorrect, incomplete or misleading information in reply to a request from authorities or notified bodies can cost up to EUR 5 million or 1%. The rules on penalties are laid down by the Member States. In Germany, the BSI is to become the market surveillance authority and impose the fines: the Bundestag passed the implementing act on 15 October 2026, but it had not been promulgated by 4 November 2026.
Source: Art. 13(13) and (22) CRA · Art. 18(3) CRA · Art. 19(6) CRA · Art. 64(1) to (4) CRA · Bundesrat, printed paper 621/26: act passed by the Bundestag (in German)
Special cases
- Product families: where variants share the same architecture, security-relevant design and intended purpose and face the same risks, the guidelines allow manufacturers to use a single risk assessment, a single set of technical documentation and one conformity assessment procedure. What matters is whether the differences are relevant to cybersecurity.
- Remote data processing and third-party services: the technical documentation states that the product has remote data processing or relies on third-party remote solutions and describes them. If the same solution serves several products, it is declared for each product; the documentation on it may be re-used.
- Notified body: the documentation and correspondence on the conformity assessment are drawn up in an official language of the Member State where the body is established or in a language acceptable to it.
- Other legal acts: Art. 31(3) provides for a single set of technical documentation for high-risk AI systems under Art. 12 and, through the EHDS Regulation from 26 March 2027, for EHR systems under Art. 32(5a). The provision contains no such rule for other products subject to further legal acts.
Source: Commission guidance C/2026/6013, points 174 to 176, 204 · Art. 31(3) and (4) CRA · Art. 12 CRA · Art. 104(2) and (3) EHDS Regulation · Art. 105 EHDS Regulation
Simplified form for small enterprises
Microenterprises and small enterprises may provide all elements of Annex VII in a simplified format. The Commission sets the form by implementing act; notified bodies must accept it (Art. 33(5)). This does not remove any element of the annex.
We had not found a finished form by 4 November 2026. The Commission told Parliament in June 2025 that it will adopt one. But its timeline (as of 27 July 2026) does not list it, and neither its feedback portal nor EUR-Lex showed a draft or an act. Check the current status before relying on it.
Source: Art. 33(5) CRA · Commission: answer to parliamentary question E-001244/2025 · Commission: implementation of the Cyber Resilience Act, as of 27 July 2026 · Commission: Cyber Resilience Act for micro, small and medium-sized enterprises
In practice
- Create one file per product or product family, structured by the points of Annex VII. That makes gaps visible quickly.
- Decide who maintains each section. Architecture, risk assessment, test reports and the vulnerability process usually sit with different people.
- Store test reports and SBOMs per version automatically from the build instead of collecting them at the end.
- Check with every release whether anything in the documents changes, and archive approved versions with their date.
- Compare marketing, instructions and documentation. The Commission names clear inconsistencies between them as a sign that the core functionality has been misrepresented (guidelines point 143).
- Choose a storage location where the documents remain readable in ten years and can still be found when people or tools change.
Related guides
- Product and evidenceEU declaration of conformity under the Cyber Resilience Act4 min read
- Product and evidenceWhat is an SBOM? Obligations under the Cyber Resilience Act3 min read
- Product and evidenceSupport period under the Cyber Resilience Act: at least five years?3 min read
- Product and evidenceSubstantial modification: when does an update make a new product?7 min read
- Related legislationEHDS and the Cyber Resilience Act: what applies to health software4 min read
- Product and evidenceAnnex I CRA: the essential cybersecurity requirements10 min read
- Product and evidenceConformity assessment under the CRA: module A, B + C or H11 min read
- Product and evidenceUser information under Annex II CRA: what must accompany a product8 min read
Terms in the Cyber Resilience Act glossary
Sources
- Regulation (EU) 2024/2847, Art. 12, 13, 18, 19, 31, 33, 64, 71, Annex VII, VIII, recital 77 (EUR-Lex, Official Journal)
- Regulation (EU) 2025/327 (EHDS), Art. 104, 105 (EUR-Lex, Official Journal)
- Commission guidance C/2026/6013, OJ C, 17 Nov 2026, not binding
Status of the Commission guidance: the Commission approved its content on 27 July 2026 (C(2026) 5252). On 17 November 2026 the guidance was published in the Official Journal as Communication C/2026/6013, in all official languages. According to our comparison, the point numbers have not changed. The guidance is not binding, but it shows how the Commission reads the Regulation (as of 11/2026).
First published 4 Nov 2026, last updated 4 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.