What changed in the platform, what you need to do about it, and what stayed the same. Written for the people who use CVD Portal, not for the changelog.
The Readiness page and the dashboard now show which CRA requirements apply today and which apply from 11 December 2027. Partners can link a client to one form, and a browser tab can no longer save into the wrong workspace.
The Compliance plan now includes every MCP tool. Article 14 records the two severe-incident tests. The product page has one progress path, and SBOM pushes update findings at once.
The technical file now builds key sections from your records and states its status. Drafts are checked, gaps go to Jira or GitHub, and one search covers every product.
The SBOM validator now reads SPDX 3 tool information, SPDX 3 dependency relationships and nested CycloneDX components, so fewer correct SBOMs get a wrong verdict.
You can now record VEX statements on SBOM findings, share SBOM and HBOM files on the trust portal, choose your notifications, and switch off the hosted portal.
Link evidence across Annex I requirements, track the ENISA secure-by-design playbooks per product, complete your declaration, and keep your SBOM current from GitHub.
You can now publish security advisories from a resolved report, set your own response targets, draft Article 14 fields per stage, and see real SBOM exposure.
One form now writes your vulnerability handling procedure. You can show your readiness on a public page, build an SBOM from a manifest, and pre-fill your ENISA report.
CVD Portal is live. You get a public portal where researchers report vulnerabilities, a published disclosure policy, and a dashboard to triage, score and record each report.