Free local worksheet · product cybersecurity
CRA risk assessment template for one product.
Create a structured product cybersecurity risk assessment draft for a software or connected product. Record intended use, threat scenarios, controls, residual risk, owners and evidence, then download the draft for your team's review.
What is a CRA product cybersecurity risk assessment? The Cyber Resilience Act requires manufacturers to assess cybersecurity risks associated with a product with digital elements and take the assessment into account during planning, design, development, production, delivery and maintenance. The outcome informs how the product's essential cybersecurity requirements apply and is part of technical documentation.
This worksheet helps a team organise that reasoning. It does not prescribe a risk method, invent legal thresholds or determine that a product is compliant. Document your method and product-specific decisions, and have the result reviewed by the people responsible for product security and regulatory interpretation.
1 · Product context
Describe the product and its use.
2 · Risk scenarios
Record the reasoning and evidence.
Draft output
Product risk record
1 scenario recorded · 0 with a team-assessed residual-risk band · review 2026-10-26
- Scenario 1Product asset or function not enteredResidual: Not assessed
4 · Review and retain
What this worksheet does
It organises product use context, risk reasoning, controls, residual risk and evidence for human review. It does not calculate risk, determine CRA applicability, decide conformity or certify compliance. Review the assessment as the product, threat landscape and supporting evidence change.
Method and source
A record, not a legal score
The browser draft uses no formula or automated legal conclusion. It preserves what your team enters in this browser and exports a JSON worksheet only when you choose to download it.
Last verified 29 September 2026 against the Official Journal text of Regulation (EU) 2024/2847.
Read next
- Guide
CRA cybersecurity risk assessment: what Article 13 and Annex VII require
The cybersecurity risk assessment is the hinge of CRA compliance: it decides how each Annex I requirement applies to a product and must sit in the technical documentation. What Article 13 requires it to contain, a method that produces evidence, a worked example, reusable standards and when to update it.
- Guide
CRA requirements for manufacturers: Article 13 obligations and Annex I
Every obligation the Cyber Resilience Act places on manufacturers — the 25 paragraphs of Article 13, the product properties and vulnerability-handling requirements of Annex I, Article 14 reporting — plus the duties of importers, distributors and open-source stewards, and what applies now versus from December 2027.
- Guide
CRA technical documentation: what Annex VII requires and how to keep it current
The contents of the technical documentation under Article 31 and Annex VII — product description, design and vulnerability-handling processes, risk assessment, support period, standards, test reports, declaration and SBOM — with a structure you can maintain per product for ten years.
- Docs
Product registry
Products, versions, lifecycle, classification, exposure context.
- Docs
SBOM ingestion
Upload, GitHub, GitLab, CI/CD and the API.
- Docs
VEX
Per-product exploitability statements and signed CycloneDX VEX documents.
- Free tool
SBOM validator and viewer
Validate a CycloneDX or SPDX SBOM, view its components, check NTIA minimum elements and look up known vulnerabilities in OSV.dev.