CRA technical documentation: what Annex VII requires and how to keep it current

Article 31 of the Cyber Resilience Act requires manufacturers to draw up technical documentation before placing a product on the market, containing everything needed to assess conformity with the essential requirements, and to keep it for ten years or the support period, whichever is longer. Annex VII lists what it must contain.

By the Vellaci teamPublished Updated 4 min readOperational guidance, not legal advice

Share:LinkedInXE-mail

Key facts

Legal basis
Art. 31; Annex VII; retention Art. 13(13)
When
Before placing on the market; updated during the support period
Retention
10 years after placing on the market or the support period, whichever is longer
Who may ask
Market surveillance authorities; notified bodies during assessment
Includes the SBOM
Yes, where applicable (Annex VII(2)(b) and (3))

What Annex VII requires

Annex VII itemContentPractical source
1. General descriptionIntended purpose, software versions affecting compliance, hardware and photographs where relevant, user information and instructions per Annex IIProduct registry, versions, user documentation
2. Design, development, production; vulnerability handlingArchitecture and how components interact; processes for secure development; vulnerability-handling processes including the SBOM, CVD policy, contact address and update distributionSDLC policy, architecture docs, SBOM per version, CVD policy, update mechanism description
3. Cybersecurity risk assessmentThe assessment under Art. 13(2)–(3), including how each Annex I Part I requirement applies or why it does notRisk assessment record with requirement mapping
4. Support periodThe determined support period and the information taken into accountSupport period record with rationale
5. Standards and specificationsHarmonised standards, common specifications or certification schemes applied in full or in part; solutions adopted where they were notStandards mapping, gap list
6. Test reportsReports of the tests carried out to verify conformity with Annex I Part I and Part IISecurity testing, penetration tests, code review, SCA results
7. EU declaration of conformityCopy of the declaration per Annex VDeclaration document
8. SBOMWhere applicable, the SBOM on reasoned request of an authoritySBOM per version from the pipeline

A structure that stays maintainable

Documentation that lives in a folder is out of date the day after the audit. Structure it per product as living sections with version history and links to evidence that already exists elsewhere: the SBOM stays in the SBOM system and the documentation links to the version; test reports are attached as evidence with review dates; the risk assessment references the controls in the readiness framework. Vellaci organises fourteen sections per product along Annex VII, with change history, evidence links and a ZIP export that a notified body or authority can open without an account.

Keeping it current

  1. Tie documentation review to releases: every version placed on the market updates the general description, the SBOM link and, where relevant, the risk assessment.
  2. Review the risk assessment when a severe incident or exploited vulnerability occurs; both are new information about the product's risk.
  3. Version the CVD policy and update policy; keep superseded versions.
  4. Store test reports with dates and scope; a two-year-old penetration test does not evidence the current version.
  5. Assign an owner per section and a review date; overdue reviews are readiness findings.

What good looks like per section

General description: name every version placed on the market with its release date, the intended purpose in the words used in marketing and user documentation, and the hardware it runs on. A notified body will compare this with the product it is handed.

Design and development: architecture at the level of trust boundaries — what talks to what, over which protocols, with which authentication — plus the secure development lifecycle you actually follow (threat modelling, code review, dependency policy, signing). Link the policy documents rather than restating them.

Vulnerability handling: the SBOM per version, the CVD policy and contact, the triage process with its SLAs, how advisories are published and how updates reach users. This is the section most often thin, and the one authorities read first after an incident.

Risk assessment: a table of Annex I Part I requirements against the product's risks, controls and residual risk, with 'not applicable' entries justified. Update it when incidents change the picture.

Tests: reports with date, scope, tool or tester, findings and their disposition. A finding fixed in a later version should point at that version.

Retention in practice

Ten years from placing on the market is longer than most tooling and most employment relationships. Store the documentation in a system with retention policies, legal hold and export, keep evidence files checksummed, and make sure the archive of a discontinued product survives the team that built it. Vellaci's evidence vault applies retention categories and legal hold per record and produces a complete export with an integrity manifest.

Documentation for simplified cases

Microenterprises and small enterprises may provide certain documentation in a simplified form the Commission will specify. The obligation to have the documentation remains; the form may be lighter. Until the simplified format is available, follow Annex VII proportionately.

Frequently asked questions

Is the documentation public?
No. It is made available to market surveillance authorities on reasoned request and to notified bodies during conformity assessment. Only the declaration of conformity and the user information are user-facing.
In which language?
In a language easily understood by the relevant authority — in practice English is commonly accepted, but authorities may request the documentation in their official language.
Where does evidence of Article 14 reporting belong?
Reporting cases are part of the vulnerability-handling record and support the process description in Annex VII(2). Keep the case files, submissions and user communications retrievable for the same ten years.

From requirement to evidence

What the obligations in this guide mean for an engineering, security or compliance team, the Vellaci workflow that supports each one, and the records it leaves. The full map for every CRA obligation is on the CRA compliance software page.

How to read this. Official requirement summarises the text of Regulation (EU) 2024/2847 with its reference. What your team does is Vellaci’s operational interpretation, not legal advice. Vellaci workflow and Evidence describe what the product does today. Methodology · reviewed 2026-10-05.

  1. Software bill of materials

    Annex I, Part II(1)Applies from 11 Dec 2027
    Official requirement
    Identify and document vulnerabilities and components contained in the product, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies.
    What your team does (interpretation)
    Generate an SBOM in the build for every released version, keep it with that version rather than overwriting it, and make sure components carry identifiers (purls) that vulnerability data can be matched against.
    Vellaci workflow
    SBOM ingestion per product version (UI, API, CLI, GitHub/GitLab), original file preserved, components normalised and deduplicated. How it works
    Evidence produced
    • Original SBOM file with SHA-256 checksum, bound to the version
    • Parse record and warnings
    • Component inventory per version and diff against the previous version
  2. Systematically document vulnerabilities

    Article 13(7)Applies from 11 Dec 2027
    Official requirement
    Systematically document, proportionately to the nature and the cybersecurity risks, relevant cybersecurity aspects of the product, including vulnerabilities the manufacturer becomes aware of and relevant information provided by third parties, and update the risk assessment where applicable.
    What your team does (interpretation)
    Keep the reasoning, not just the status. A 'not affected' without a justification is not documentation; neither is a status that was silently overwritten.
    Vellaci workflow
    Append-only decision history and hash-chained audit log; VEX states with CycloneDX justification codes per product version. How it works
    Evidence produced
    • Per-product VEX statements with justification
    • Audit log entries with before and after values
    • CycloneDX VEX export per version
  3. Effective and regular security tests

    Annex I, Part II(3)Applies from 11 Dec 2027
    Official requirement
    Apply effective and regular tests and reviews of the security of the product.
    What your team does (interpretation)
    Decide which tests run per release and per period (SAST, dependency scanning, penetration tests, reviews), and keep the reports where an assessor can find them per product.
    Vellaci workflow
    Test reports attached to products and requirements in the evidence vault, with review dates; readiness controls show which are missing or overdue. How it works
    Evidence produced
    • Test reports linked to the product, with checksum and review date
    • Readiness control status per requirement
  4. Secure, timely and free security updates

    Annex I, Part II(7)–(8)Applies from 11 Dec 2027
    Official requirement
    Provide mechanisms to securely distribute updates so vulnerabilities are fixed or mitigated in a timely manner — automatically where applicable — and disseminate available security updates without delay and, unless otherwise agreed for a tailor-made product, free of charge, with advisory messages.
    What your team does (interpretation)
    Document how updates are signed, delivered and applied per product, and be able to show which release fixed which vulnerability and when it was made available.
    Vellaci workflow
    Secure update mechanism section per product in the technical documentation; fixed versions recorded on findings. How it works
    Evidence produced
    • Update mechanism description with version history
    • Finding → fixed version → release date
  5. Support period

    Article 13(8)Applies from 11 Dec 2027
    Official requirement
    Handle vulnerabilities effectively for the support period, and determine that period so it reflects the time the product is expected to be in use; it is at least five years unless the product is expected to be in use for less.
    What your team does (interpretation)
    Record a support end date and its rationale per product, keep handling vulnerabilities for every version still inside it, and plan what happens at end of support.
    Vellaci workflow
    Support period with rationale per product, end-of-support alerts, vulnerability handling per supported version. How it works
    Evidence produced
    • Support period and rationale on the product record
    • Version list showing which versions are still supported
  6. Cybersecurity risk assessment

    Article 13(2)–(3)Applies from 11 Dec 2027
    Official requirement
    Undertake an assessment of the cybersecurity risks of the product, take its outcome into account during planning, design, development, production, delivery and maintenance, document it and update it as appropriate during the support period.
    What your team does (interpretation)
    Write the risk assessment per product, link it to the Annex I controls it justifies, and revisit it when vulnerabilities or incidents change the picture.
    Vellaci workflow
    Risk assessment section in the per-product technical documentation workspace, with version history; per-product obligations view. How it works
    Evidence produced
    • Versioned risk assessment section with author and status
    • Link between findings and the assessment they updated
  7. Technical documentation

    Article 13(12)–(13); Article 31; Annex VIIApplies from 11 Dec 2027
    Official requirement
    Draw up the technical documentation before placing the product on the market, containing at least the elements in Annex VII, and keep it, with the EU declaration of conformity, at the disposal of market surveillance authorities for at least ten years after placing on the market or for the support period, whichever is longer.
    What your team does (interpretation)
    Assemble the Annex VII file progressively from records you already keep — SBOMs, vulnerability handling, risk assessment, support period, test reports — instead of writing it once before an audit.
    Vellaci workflow
    Fourteen Annex VII-oriented sections per product with status, version history and evidence links, exported as a ZIP technical package. How it works
    Evidence produced
    • Section versions with author and approval status
    • ZIP technical package (product record, SBOMs, sections, evidence index)

Build the Annex VII file from records you already keep.

Fourteen sections per product with version history, pre-linked to SBOMs, decisions, tests and evidence, exported as one package.