CRA vulnerability management · VEX
Vulnerability management under the Cyber Resilience Act.
The CRA requires manufacturers to identify and document components and vulnerabilities, handle and remediate vulnerabilities during the support period, and report certain actively exploited vulnerabilities and severe incidents. Vellaci connects SBOM exposure, intelligence, human review, remediation, VEX and evidence in one product workflow.
At a glance
- Who is this for?
- Product-security engineers and PSIRT leads who triage findings across many products and versions and must justify every decision.
- What problem does it remove?
- Scanner alerts without product context, 'not affected' decisions without reasons, and no explicit answer to whether Article 14 could apply.
- Where does it fit in the workflow?
- Between your scanners and your release process: findings are matched to shipped versions, decided by a named person, routed to your tracker and, when exploited, handed to the reporting workflow.
- What evidence does it produce?
- Decision history with reviewer, reason and timestamp
- CRA reportability review per finding
- Remediation owner, due date and fixed version
- CycloneDX VEX per product version
- How does implementation work?
- Upload one SBOM or connect the GitHub App; findings appear ranked by exploitation evidence. Triage states, reasons and remediation SLAs are configured during onboarding or the Readiness engagement.
- What does it connect to?
- GitHub App (releases, dependency-graph SBOMs)
- GitLab
- Jira and Linear (remediation tasks)
- Slack, Microsoft Teams, PagerDuty, signed webhooks (deadline and exploitation alerts)
- OSV, GitHub advisories, CISA KEV, FIRST EPSS
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.
Intelligence with provenance
CVSS, EPSS, known-exploitation signals (CISA KEV), fix availability, references and source feeds, each with the time it was fetched. KEV is a signal, never a legal determination.
Triage states
New, needs review, affected, not affected, mitigated, fixed, accepted risk, false positive, archived — with reasons required for not affected, accepted risk and false positive.
CRA review
Could this qualify as an actively exploited vulnerability under Article 14? Not reviewed → potentially reportable → confirmed or not reportable, with rationale, reviewer, timestamp and awareness time.
Remediation
Owner, deadline, fixed version, mitigation and ticket links (Jira, Linear); tasks can be created from any finding and tracked to closure.
VEX
Assessments map to affected / not affected / fixed / under investigation with justification, ready for CycloneDX VEX export per product version.
Immutable history
Every status change, review and remediation update is appended to the decision history and the hash-chained audit log.
Regulation → operation → workflow → evidence
What the CRA expects vulnerability handling to look like.
Annex I Part II lists the vulnerability-handling requirements manufacturers must meet for the whole support period; Article 13(7) asks for systematic documentation and Article 14 for reporting of actively exploited vulnerabilities. Each row below shows the requirement, what your team does, the Vellaci workflow and the evidence left behind.
Vulnerability queue. Findings ranked by priority with KEV, EPSS, triage state and reason, CRA review answer and remediation owner.
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
- 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
- Official requirement
- In relation to the risks posed, address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, provide security updates separately from functionality updates.
- What your team does (interpretation)
- Every matched vulnerability gets a human decision — affected, not affected, fixed, accepted — with a reason, an owner and, if affected, a remediation target and the version that fixes it.
- Vellaci workflow
- Triage with mandatory reasons, explainable priority (CVSS, EPSS, KEV, exposure), remediation owner and due date, Jira and Linear ticket links. How it works
- Evidence produced
- Decision history per finding with reviewer and timestamp
- Remediation owner, due date and fixed version
- Linked tickets
- 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
- Official requirement
- Once a security update has been made available, share and publicly disclose information about fixed vulnerabilities, including a description, the affected products, impact, severity and information helping users remediate; publication may be delayed in duly justified cases.
- What your team does (interpretation)
- Tie each advisory to the finding and the fix release, and record when and where it was published — or why publication was delayed.
- Vellaci workflow
- Fixed versions recorded on findings; CycloneDX VEX export for customers and downstream integrators. How it works
- Evidence produced
- Fixed version linked to the finding
- Exported VEX document
- Publication or delay rationale
- 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
- 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
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
- 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
VEX under the CRA
VEX: the decision, in a format your customers can consume.
An SBOM tells a customer which components a version contains. A VEX statement tells them whether a known vulnerability actually affects that version, and why.
Official requirement
The CRA does not name VEX. It requires manufacturers to identify and document components and vulnerabilities (Annex I Part II(1)), to document vulnerabilities systematically (Article 13(7)) and to disclose information about fixed vulnerabilities once an update is available (Annex I Part II(4)).
Interpretation
Customers and authorities will ask about specific CVEs in specific versions. A per-version VEX statement with a justification answers that question with the evidence attached, instead of an e-mail thread — and stops the same question being triaged twice.
Vellaci workflow
Triage states map to affected, not affected, fixed and under investigation, with CycloneDX 1.5 justification codes (code not present, code not reachable, protected at runtime, …) and responses. Statements are exported as CycloneDX VEX per product and version.
Read the VEX vs SBOM guide or the VEX documentation. Sources: CISA minimum requirements for VEX, CycloneDX specification.
FAQ
Triage questions, answered.
- How is this different from a dependency scanner?
- A scanner tells you a component has a CVE. Vellaci tells you which products and versions on the EU market ship it, whether exploitation evidence exists, who owns the decision, what was decided and why, whether Article 14 could apply, and what evidence supports all of that. Scanners produce alerts; manufacturers need decisions with names and timestamps.
- What does 'priority' mean in Vellaci?
- An explainable score combining CVSS severity, EPSS exploitation probability, CISA KEV listing, fix availability and your product's exposure context (network-exposed, safety-relevant, placed on the market). Every factor is shown next to the score; nothing is a black box, and the score never replaces the human reportability review.
- Why are reasons mandatory for 'not affected' and 'accepted risk'?
- Because those are the decisions an auditor, a customer or a market surveillance authority will ask about. A 'not affected' without a justification is a liability; with one — the vulnerable function is not reachable, the component is compiled out, a compensating control exists — it is a VEX statement and evidence of due diligence.
- Does Vellaci decide what is 'actively exploited' under the CRA?
- No. It surfaces evidence — a KEV listing, a high EPSS score, an exploitation report — and asks a named reviewer to record whether the vulnerability is potentially reportable, confirmed reportable or not reportable, with rationale and the awareness time. The regulation's definition (Article 3(42)) and your legal advisers govern the threshold.
- Can we export VEX?
- Yes. Assessments map to affected / not affected / fixed / under investigation with justification codes and are exported as CycloneDX VEX documents per product version, so downstream customers can consume your statements automatically.
- Does the CRA require VEX?
- No article of Regulation (EU) 2024/2847 names VEX. The CRA requires manufacturers to document vulnerabilities and components (Annex I Part II(1), Article 13(7)) and to disclose information about fixed vulnerabilities (Annex I Part II(4)). VEX is a practical, machine-readable way to communicate and evidence those product-specific decisions; it is not a conformity certificate.
Read next
- Guide
CVSS vs EPSS vs KEV: prioritising vulnerabilities under the CRA
Three signals answer three different questions: how bad exploitation would be (CVSS), how likely it is soon (EPSS) and whether it is already happening (CISA KEV). What each one measures, its limits, and how to combine them into a triage policy and an Article 14 reportability review.
- Guide
VEX vs SBOM: component inventory and exploitability context
A concise technical comparison of SBOM and VEX, how component matching leads to product-specific exploitability statements, and what each artifact can and cannot establish.
- Guide
SBOM guide for the CRA: formats, minimum content and operations
CycloneDX versus SPDX, what a CRA-oriented SBOM must contain, which tools generate one per ecosystem, how to keep it current per release, how to share it, and how it feeds vulnerability handling and VEX.
- Guide
CRA Article 14 reporting obligations: a practical guide for manufacturers
What must be reported under Article 14 of the Cyber Resilience Act, by whom, to whom and when — the 24-hour early warning, 72-hour notification and final report — and how to operationalise it now that the obligation is in force (since 11 September 2026).
- Docs
Triage workflow
Statuses, reasons, bulk actions, tickets.
- Docs
Intelligence and priority
Sources, provenance, EPSS, exploitation evidence, priority model.
- Docs
VEX
Per-product exploitability statements and signed CycloneDX VEX documents.
Stop triaging in spreadsheets.
Connect exposure, decisions, deadlines and evidence.