CRA evidence management: what to keep, for how long, and how to keep it provable

CRA evidence management means keeping, for at least ten years after a product is placed on the market, the records that show how each obligation was met: technical documentation, the EU declaration of conformity, SBOMs, vulnerability-handling decisions, test reports, advisories, reporting submissions and update history — each attributable to a person and a time, unchanged since it was created, linked to the product and requirement it evidences, and retrievable on request.

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

Share:LinkedInXE-mail

Key facts

Retention
Technical documentation and the declaration of conformity: at least ten years after placing on the market or the support period, whichever is longer (Art. 13(13); Art. 31)
Who asks
Market surveillance authorities (Art. 52), notified bodies (Art. 32), customers in procurement, auditors
What makes it count
Provenance (who, when), integrity (unchanged), linkage (which product, which requirement), retrievability (on request)
Where it fails
Shared drives, chat threads and ticket comments — findable today, unprovable in 2031

The problem this solves

Most of the work the CRA requires already happens in some form: dependencies are updated, tests are run, incidents are handled. What is missing is proof — in the form an authority or a customer's security review will accept, years later, from people who may no longer be at the company. A statement of compliance without records is an assertion; a record without provenance, integrity and linkage is a file.

What must be evidenced

ObligationRecordsTypical source
Technical documentation (Art. 31, Annex VII)Product description, risk assessment, design and vulnerability-handling information, test reports, standards applied, declaration of conformityDocumentation workspace per product
Vulnerability handling (Annex I Part II)SBOM per version, triage decisions with reasons, remediation records, VEX statements, advisories, update logsPipeline, vulnerability workflow, release process
Reporting (Art. 14)Awareness confirmation and rule, reportability review with rationale, submitted content, ENISA platform receipts, user communications, final reportReporting case records
Support period (Art. 13(8))Determination with rationale per product, public statementProduct registry
Secure development (Annex I Part I)Threat models, security requirements, test plans and results, release gatesEngineering process
Disclosure (Annex I Part II(5)–(6))Policy versions, security.txt history, intake log with response timesPSIRT / security mailbox
Conformity (Art. 32)Procedure decision, notified-body correspondence, certificates, declaration, CE markingCompliance function

Four properties of a record that counts

  1. Provenance: who created or decided it and when, captured by the system rather than typed into a document.
  2. Integrity: a checksum at creation and an append-only history, so a record can be shown to be unchanged — or every change shown.
  3. Linkage: the product, the version, the requirement and, where relevant, the finding or case the record evidences.
  4. Retrievability: findable by product and requirement, exportable with an index and integrity manifest, within days of a request — not weeks of archaeology.

Retention in practice

Ten years is longer than most tools, contracts and employees last. Plan for it explicitly: a retention category per record kind (regulatory minimum, contractual, internal), a policy that enforces the minimum rather than a default deletion, legal hold for anything tied to an open case or dispute, and a complete export that does not depend on the vendor still existing. A read-only, exportable workspace after a subscription ends is part of that plan — evidence that disappears with an invoice is not evidence.

An operating routine

  1. Decide the evidence set per requirement once (the table above is a starting point) and assign an owner to each.
  2. File evidence as a by-product of the workflow — the SBOM when it is ingested, the decision when it is made, the receipt when the notification is submitted — not in a quarterly clean-up.
  3. Classify each record (public, internal, confidential, restricted) and set a review date for documents that go stale (policies, risk assessments).
  4. Run a retrieval drill twice a year: pick a product and a requirement, and time how long it takes to produce the evidence pack.
  5. Export the complete set at least yearly and store the manifest outside the platform.

What Vellaci does — and what it leaves to you

Vellaci's evidence vault stores private, checksummed files and links tied to products, versions, requirements, findings, incidents and reporting cases, with classification, review dates, retention categories with regulatory minimums, legal hold and an append-only, hash-chained audit log. Reporting submissions are frozen, signed snapshots; awareness times keep every revision. A complete organisation export — JSON per table, audit CSV, evidence index, integrity manifest — is available at any time, and a lapsed subscription keeps the workspace readable and exportable. What counts as sufficient evidence for a given obligation, and whether a record is legally adequate, remain judgements for your organisation and its advisers.

Where to start

The free assessment on this site asks how decisions, SBOMs, tests and updates are retained today and returns, for every gap, the evidence a manufacturer would need to produce. Teams usually begin with the two record sets that are already being generated but not kept — SBOMs per release and triage decisions — and add the reporting runbook and documentation structure next.

Frequently asked questions

Is a spreadsheet or a shared drive acceptable evidence?
It can be, if you can show who changed what and when, that the content is unchanged since, and that it links to the product and requirement. In practice that is hard to demonstrate for a shared drive years later; systems that capture provenance and integrity automatically make the same records defensible.
Do we need to keep evidence for products we no longer sell?
Yes, for at least ten years after each product was placed on the market (or for the support period if longer). Retention is per product, and the obligation outlives the sales period.
What does an authority actually ask for?
Market surveillance authorities can request the technical documentation, the declaration of conformity and information demonstrating conformity — in practice the risk assessment, vulnerability-handling records, test reports and, for reportable events, the reporting history. Being able to produce a coherent pack quickly is itself part of the impression you make.
How does this relate to ISO 27001 or SOC 2 evidence?
Those frameworks evidence the organisation's information security management; the CRA evidences the product's cybersecurity and the manufacturer's handling processes. Records overlap (policies, testing), but CRA evidence must be linked to specific products and versions, which management-system evidence usually is not.

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. 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
  2. Report actively exploited vulnerabilities

    Article 14(1)–(2)Applies since 11 Sep 2026
    Official requirement
    Notify any actively exploited vulnerability contained in the product to the CSIRT designated as coordinator and to ENISA via the single reporting platform: early warning within 24 hours of becoming aware, notification within 72 hours, final report no later than 14 days after a corrective or mitigating measure is available.
    What your team does (interpretation)
    Decide who confirms awareness and reportability, record when they did it and in which timezone, and have the content of each stage ready before the clock runs out.
    Vellaci workflow
    Explicit CRA review on every finding, reporting case with server-computed 24 h / 72 h / final-report deadlines, staged and prefilled forms. How it works
    Evidence produced
    • Reportability decision with rationale and reviewer
    • Confirmed awareness time and timezone
    • Frozen revision of each submitted stage with SRP reference
  3. 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)

Keep evidence that will still prove something in 2037.

Checksummed records linked to products, versions and requirements, an append-only audit log, and a complete export at any time.