Product security
The operating layer between engineering and compliance.
Vellaci's wedge is product security plus CRA operations: the primitives are products, requirements, evidence, technical assets, incidents, workflows, deadlines and an audit trail. Engineering keeps its tools; compliance gets a system of record; auditors get a trail they can follow.
At a glance
- Who is this for?
- Product owners and compliance leads who own the product registry, classification, support periods and disclosure policy.
- What problem does it remove?
- Product-level obligations — classification, support period, CVD policy, documentation — decided once in a meeting and never recorded with the reasoning.
- Where does it fit in the workflow?
- The product record every other workflow attaches to: classification, support period, owners, versions and obligations per product.
- What evidence does it produce?
- Classification with reasoning and approver
- Support period with rationale
- CVD contact point, policy URL and response targets
- Per-product obligation status
- How does implementation work?
- Self-serve: a free Evaluation workspace (1 product, 3 seats) runs the full workflow on your own SBOM the same day. Assisted: Vellaci Readiness (from €4,900) configures scope, products, SBOMs, workflows and the reporting runbook with you in four to six weeks.
- What does it connect to?
- GitHub App (releases, dependency-graph SBOMs)
- GitLab
- CSV product import
- REST API and CLI
What happens after you request a demo?
- We reply within two business days with two proposed times.
- A live walkthrough with a Vellaci operator on the seeded demo workspace, focused on your products and your reporting path.
- If it fits, a written proposal: plan, implementation package, deliverables, prerequisites and exclusions. If it does not, we say so.
What happens after you sign up?
- Confirm your e-mail and create the workspace — no credit card for the free Evaluation.
- Add a product and upload one SBOM (UI, API, CLI or GitHub).
- See matched vulnerabilities ranked by exploitation evidence and run your first CRA review; subscribe only when you choose a plan.
Product registry
Lifecycle from draft to withdrawn, owners and security owners, classification with reasoning and approval, EU market availability by Member State, repositories, versions and tags.
Classification
Annex III Class I / Class II and Annex IV categories matched against declared core functions, with Annex references, an approver and an override rationale stored on the product.
Support periods
Start, end, expected lifetime and rationale per product, with end-of-support alerts and the Article 13(8) baseline shown in context.
Coordinated disclosure
Contact point, security.txt status, disclosure policy generated from an editable template aligned with ISO/IEC 29147, SLAs and intake instructions.
Technical documentation
Fourteen Annex VII-oriented sections per product with version history, exportable as a ZIP technical package for notified bodies or authorities.
Readiness framework
Configurable requirements across twelve domains with owners, evidence, review dates and weighted scoring — a management view, never a certificate.
Policies and templates
CVD policy, secure development policy, update policy and incident runbook templates versioned with approvals.
Exports and portability
PDF, CSV, JSON and ZIP reports; a complete organisation export at any time; public API and CLI. Your data, no lock-in.
Manufacturer obligations
Article 13 in operational terms.
The product-level obligations of Article 13 and Annex I: what the regulation says, what your team does, the Vellaci workflow and the evidence it leaves. Documentation obligations are covered in depth on the technical documentation page.
Product registry. The product registry: classification with reasoning, lifecycle, support period, owners, versions and SBOM status per product.
See this screen with sample dataHow 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.
- Official requirement
- Exercise due diligence when integrating components sourced from third parties, including free and open-source software, so that they do not compromise the product's cybersecurity.
- What your team does (interpretation)
- Know which third-party and open-source components each version ships, watch them for new vulnerabilities over the support period, and record why a risky component was accepted.
- Vellaci workflow
- Component catalogue across all SBOMs with product usage, continuously matched against OSV and GitHub advisories, enriched with CISA KEV and EPSS. How it works
- Evidence produced
- Which products and versions ship a component
- Match history with source and fetch time
- Recorded risk acceptance with reason
Coordinated vulnerability disclosure and contact address
Annex I, Part II(5)–(6)Applies from 11 Dec 2027- Official requirement
- Put in place and enforce a policy on coordinated vulnerability disclosure, and facilitate the sharing of information about potential vulnerabilities, including by providing a contact address for reporting them.
- What your team does (interpretation)
- Publish a reachable intake channel (for example security.txt), a disclosure policy with response targets, and keep a record of reports received and how they were handled.
- Vellaci workflow
- CVD settings per organisation: vulnerability contact, reporting URL, security.txt status, published policy URL, intake instructions and acknowledge / triage / fix targets; policy template aligned with ISO/IEC 29147. How it works
- Evidence produced
- Recorded contact point, security.txt and policy URL
- Response targets (acknowledge, triage, fix)
- Changes to the settings in the audit log
- 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
- 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
- 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)
FAQ
Product-security questions, answered.
- What is the support period and who decides it?
- Article 13(8) requires manufacturers to determine a support period that reflects the time the product is expected to be in use, taking into account user expectations, the nature of the product and relevant Union law; it should be at least five years unless the product is expected to be used for a shorter time. The manufacturer decides and documents the rationale. Vellaci records start, end, expected lifetime and rationale per product and alerts before end of support.
- What goes into the technical documentation?
- Annex VII: a general description of the product, its intended purpose and versions; a description of the design, development and vulnerability-handling processes; the cybersecurity risk assessment; the support period; the standards applied; test reports; the EU declaration of conformity; and, where applicable, the SBOM. Vellaci structures fourteen sections per product with version history and evidence links, exportable as a technical package.
- Do we have to publish our SBOM?
- No. The SBOM is part of the technical documentation and must be available to market surveillance authorities on request. Many manufacturers share it with customers under agreement; Vellaci lets you export it per version when you choose to.
- What does the readiness score mean?
- A weighted operational view across governance, risk, secure development, vulnerability management, SBOM, disclosure, updates, incidents, reporting, documentation, support and conformity — each requirement with an owner, status, evidence and review date. It is a management instrument to see gaps and progress. It is not a legal certification and Vellaci never presents it as one.
Read next
- Guide
CRA product classification: default, important (Class I / II) and critical
How Annex III and Annex IV categories work, the core-functionality test, what changes for conformity assessment under Article 32, edge cases, and how to document a classification decision that will survive scrutiny.
- Guide
The CRA support period: how long, how to decide and what to publish
Article 13(8) requires a support period of at least five years unless the product is used for less, during which vulnerabilities are handled and security updates provided. How to determine it, document the rationale, publish it and manage end of support.
- 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.
- Guide
Coordinated vulnerability disclosure under the CRA: policy, intake and security.txt
Annex I Part II requires manufacturers to enforce a coordinated vulnerability disclosure policy and publish a contact address. What the policy must contain, how to align it with ISO/IEC 29147 and 30111, how to run intake, and how it connects to Article 14.
- Docs
Product registry
Products, versions, lifecycle, classification, exposure context.
- Docs
Roles and permissions
Owner, admin, security, compliance, engineer, auditor, external advisor.
- Free tool
security.txt generator
An RFC 9116 security.txt for your vulnerability contact point.
Make product security auditable.
From a dependency to a decision to evidence — with names and timestamps.