← CRA Glossary
CRA Regulatory

Annex VII Technical Documentation File

Annex VII of the EU Cyber Resilience Act specifies the contents of the technical documentation that manufacturers must compile and maintain to demonstrate CRA compliance. This file must be available to market surveillance authorities on request and retained for ten years after the product is placed on the market.

Annex VII of the EU Cyber Resilience Act specifies the contents of the technical documentation that manufacturers must compile and maintain to demonstrate CRA compliance. This file must be available to market surveillance authorities on request and retained for ten years after the product is placed on the market.

CRA Regulatory

Last updated 19 July 2026

What Is the Annex VII Technical File?

Annex VII of the Cyber Resilience Act specifies the technical documentation that every manufacturer of a product with digital elements must compile before placing the product on the market. This 'technical file' or 'technical documentation' is the primary evidence package that demonstrates the product was designed, developed, and tested in conformity with the CRA's essential requirements. Unlike user-facing documentation (Annex II) or the declaration of conformity (a short formal statement), the Annex VII file is a comprehensive internal record intended for regulatory scrutiny. It must be kept up to date throughout the product's market life and for ten years after the last unit is placed on the market.

CRA reference:Annex VII

Contents of the Technical Documentation File

Annex VII requires the technical file to include:

  • General description: Product name, version, intended use, and supply chain description including significant third-party components.
  • Design and development records: Architecture diagrams, data flow maps, design specifications, and records of security design decisions.
  • Risk assessment: A documented cybersecurity risk assessment identifying threats, vulnerabilities, and mitigation measures.
  • Security testing evidence: Test reports, penetration test results, code review findings, and fuzz testing outcomes.
  • Standards and specifications applied: List of harmonised standards, common technical specifications, or other technical references used.
  • Conformity declaration: A copy of the declaration of conformity.
  • SBOM: A software bill of materials identifying all software components, their versions, and origins.
  • Vulnerability handling procedures: Documentation of the CVD policy, PSIRT processes, and security advisory publication mechanism.
CRA reference:Annex VII

Retention and Availability Obligations

The Annex VII technical file must be retained for the longer of ten years after the product is placed on the market, or the entire support period of the product. Manufacturers must make the file available to national market surveillance authorities on request, typically within a defined response period (often 30 days). The file need not be submitted proactively but must be readily accessible - not stored in a way that makes rapid retrieval impractical. For products undergoing Notified Body assessment, the relevant portions of the technical file are submitted to the body as part of the assessment process. Importers and authorised representatives also have obligations to ensure the technical file is accessible to MSAs in their jurisdiction.

CRA reference:Annex VII, Article 13

Maintaining a Living Technical File

The Annex VII file must reflect the current state of the product. When a significant product update is released - for example a new hardware version, a major firmware release, or a change in a significant third-party component - the technical file must be updated to reflect the new design, updated risk assessment, and any new test evidence. Version control is essential: the file should clearly track which product versions are covered by which documentation versions. Manufacturers that maintain their technical file as a set of static documents created once at launch are common non-compliance targets when products evolve over time. Integrating technical file updates into the standard release management process is the recommended approach.

Work through the CRA for each product in one workspace.

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

Frequently asked

Does the Annex VII technical file need to be submitted to any authority proactively?+

No. The Annex VII technical file is an internal document that manufacturers must maintain but do not proactively submit to regulators. It is produced on request by market surveillance authorities during an investigation or audit. However, for products requiring Notified Body assessment, portions of the technical file are submitted to the Notified Body as part of the conformity assessment procedure. Some member states may require submission as part of national product registration schemes for certain product categories.

Is the SBOM part of the Annex VII technical file?+

Yes. Annex VII explicitly requires the technical documentation to include a software bill of materials identifying the software components integrated into the product. The SBOM does not need to be in a specific machine-readable format to satisfy the Annex VII requirement, but using CycloneDX or SPDX formats is strongly recommended as it enables automated vulnerability correlation and is consistent with emerging regulatory expectations.

What happens if a manufacturer cannot produce the Annex VII file when requested by an MSA?+

Failure to make technical documentation available to an MSA on request is itself a violation of the CRA. MSAs can treat this failure as evidence of non-compliance, enabling them to take immediate precautionary measures including product restriction. Persistent failure to cooperate with an MSA investigation can result in fines of up to €5 million or 1% of global annual turnover, in addition to any sanctions for underlying product non-compliance.

Sector checklists covering Annex VII Technical Documentation File

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.Medical DevicesMedical devices regulated under the EU Medical Device Regulation (MDR) or In Vitro Diagnostic Regulation (IVDR) are generally excluded from the CRA. However, software products used in healthcare that are not classified as medical devices under MDR may fall within CRA scope. Manufacturers should carefully verify their product's regulatory classification.Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Annex VII Technical Documentation File fits into your complete CRA compliance programme.

View checklists →