Annex VII

Technical Documentation Requirements Under the CRA

Annex VII specifies the content of the technical documentation that manufacturers must prepare and maintain to support CRA compliance. The technical file is the complete evidence base demonstrating that a product meets the essential requirements - it includes product design documentation, cybersecurity risk assessments, software bills of materials, test results, and references to the CVD policy. This documentation must be available to market surveillance authorities on request and must be kept for at least 10 years after the product is placed on the market, or for the support period if that is longer (Article 13(13)).

Effective: December 2027Applies to: All manufacturers of products with digital elements required to maintain technical documentationLast reviewed: 9 November 2026Verified against: the final text of Regulation (EU) 2024/2847
Source: Regulation (EU) 2024/2847, Annex VII, official text on EUR-Lex

Overview of Technical Documentation Structure

Annex VII requires manufacturers to compile and maintain a technical file for each product with digital elements. The technical file is not a single document - it is a collection of documents, test reports, design specifications, and records that together constitute the evidence base for CRA compliance.

The technical file must contain sufficient information to demonstrate that the product meets the essential requirements in Annex I, and to enable a competent authority or notified body to assess that compliance independently. The documentation must be coherent, consistent with the actual product, and kept up to date when product changes occur.

For software products with frequent update cycles, maintaining an up-to-date technical file requires ongoing documentation discipline - not just a one-time documentation exercise at product launch.

CRA reference:Annex VII

Product Description and Intended Use

Annex VII(1) asks for a general description of the product, including:

  • Intended purpose: what the product is for
  • Software versions: the versions of software that affect compliance with the essential requirements
  • Hardware: where the product is a hardware product, photographs or illustrations that show its external features, marking and internal layout
  • User information: the information and instructions for the user set out in Annex II

Good practice is to also describe network connectivity, the data the product handles, and its dependencies on hardware, third-party software and cloud services. That description is the foundation for the cybersecurity risk assessment that follows.

CRA reference:Annex VII(1)

Cybersecurity Risk Assessment

The Annex VII technical file must include the cybersecurity risk assessment for the product. Article 13(3) requires it to state which Annex I Part I requirements apply to the product and how they are implemented. Good practice for the analysis is to:

  • Identify threats: Enumerate the realistic threats to the product - who might attack it, how, and with what goals
  • Assess vulnerabilities: Identify weaknesses in the product design or implementation that could be exploited
  • Evaluate impact: Assess the potential harm to users, third parties, and systems if an attack succeeds
  • Document controls: Describe the security measures implemented to address each identified risk
  • Residual risk: Identify any risks that cannot be fully mitigated and the rationale for accepting them

The risk assessment must be proportionate to the product's threat profile. A consumer smart light bulb requires a less extensive risk assessment than an industrial control system, but both require a genuine risk-based analysis.

The risk assessment also provides the justification for compliance decisions: why certain security measures were implemented, why certain Annex I requirements are addressed in specific ways, and why certain approaches were deemed sufficient.

CRA reference:Annex VII(3), Article 13(3)

Software Bill of Materials and Component Documentation

Annex VII(2)(b) asks for the vulnerability handling processes, including the software bill of materials (SBOM). requires an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies of the product. A market surveillance authority can ask for the SBOM on reasoned request (Annex VII(8)).

Good practice is to list first-party, commercial and open-source components with their versions, and to keep the SBOM current when an update changes component versions. SPDX and CycloneDX are the dominant formats.

The SBOM serves a dual purpose: it documents the product's composition, and it supports the vulnerability handling that Annex I Part II requires for the whole support period, because it is the list of components against which new vulnerabilities are checked.

CRA reference:Annex VII(2)(b), Annex VII(8),

Security Test Results and CVD Policy Reference

The technical file must include evidence that the product has been tested against the essential requirements. This evidence typically includes:

Security testing reports: Results of penetration testing, vulnerability scanning, static and dynamic code analysis, and any other security testing conducted. Reports should be prepared by qualified security professionals and should document the testing scope, methodology, findings, and remediation actions taken.

Harmonised standard compliance evidence: Where harmonised standards were applied, documentation demonstrating that the product meets the standard's requirements - for example, test results from standard-specified test cases.

CVD policy reference: The manufacturer's coordinated vulnerability disclosure policy and the contact address for reporting vulnerabilities (Annex VII(2)(b), and ).

Security update mechanism description: Technical documentation explaining how security updates are delivered to users, including the update authentication mechanism, rollback prevention, and the process for testing updates before distribution.

Support period documentation: The information taken into account to determine the support period (Annex VII(4), Article 13(8)).

EU declaration of conformity: A copy of the EU declaration of conformity (Annex VII(7)).

CRA reference:Annex VII(2)(b), Annex VII(4)–(7)

Work through Annex VII for each product in one CRA workspace.

Classify the product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

How long must the technical documentation be retained?+

Article 13(13) requires the technical documentation and the EU declaration of conformity to be kept for at least 10 years after the product is placed on the market, or for the support period if that is longer. Because each unit is placed on the market separately, count from the last unit. For a product with a 10-year market life, this could mean documentation is retained for up to 20 years. Manufacturers should ensure their document management systems are capable of providing reliable long-term retention and retrieval.

Does the technical file need to be in a specific language?+

Where a notified body takes part, the technical documentation and the correspondence must be in an official language of the Member State where the body is established, or in a language that the body accepts (Article 31). A market surveillance authority can ask for information in a language it can easily understand (Article 13). Manufacturers should be prepared to provide translations on request.

Can the technical file contain references to external documents rather than copies?+

Yes - the technical file can incorporate documents by reference, provided the referenced documents are accessible when the technical file is presented to authorities. For example, a third-party penetration test report held by an external testing firm may be referenced and retrieved on request. However, documents critical to demonstrating compliance should be held by the manufacturer, not solely by third parties who might lose them or change access arrangements.

Does a software update always require a new or revised technical file?+

Not necessarily for every update, but significant updates that change the product's security-relevant functionality, introduce new components, or affect compliance with essential requirements should result in technical file updates. Minor bug-fix updates that do not change the security-relevant aspects of the product may not require a full technical file revision, but the SBOM should always be updated when component versions change.

Need a CVD policy for Annex VII?

Annex I Part II(5) asks for a coordinated vulnerability disclosure policy. Download a free template.

Browse templates →