CSAF, VEX and security advisories: what should you publish?
By SBOMBox SBOM experts · · 3 min readShort answer: VEX is the message ('CVE-X does not affect product Y, because the vulnerable code is not reachable'). CSAF is one envelope for advisories, and it has a VEX profile. You can also express VEX in CycloneDX or OpenVEX. Pick the format your customers can consume, and publish consistently.
What CSAF is
The Common Security Advisory Framework is an OASIS standard. CSAF 2.0, released in November 2022, replaces prose advisories with structured JSON: publisher details, a product tree, and for each vulnerability its status, remediation and scores. Red Hat, Microsoft and others publish CSAF advisories, and CISA recommends machine-readable advisories based on CSAF.
What VEX is
VEX (Vulnerability Exploitability eXchange) tells someone holding your SBOM whether a known vulnerability affects your product. The statuses are not affected, affected, fixed and under investigation. See What is VEX? for the basics.
How they relate
- CSAF has five profiles, one of which is VEX. A CSAF VEX document is VEX in CSAF form.
- CycloneDX supports VEX natively, either inside an SBOM or as a separate document.
- OpenVEX is a minimal, standalone VEX format.
- They carry the same idea. The difference is tooling, and what your customers' scanners can ingest.
Which to use
- Selling to enterprises or industrial buyers who already ingest vendor advisories? Publish CSAF, including CSAF VEX.
- Your customers consume CycloneDX SBOMs? CycloneDX VEX alongside the SBOM is simplest.
- Open-source project with lightweight needs? OpenVEX is easy to produce and read.
Where the CRA comes in
The CRA requires manufacturers to address vulnerabilities without delay, share information about fixed vulnerabilities, and have a coordinated vulnerability disclosure policy. It does not mandate CSAF, but machine-readable advisories make every one of those duties easier to evidence. Commentators widely see CSAF as aligned with the CRA's direction.
What a good advisory contains
- The affected products and exact versions, using the same identifiers as your SBOM (package URLs or CPEs).
- The vulnerability identifier, such as a CVE, and a severity score.
- The status for each product version, and the fixed version where there is one.
- Remediation or mitigation steps, and a revision history so readers know what changed.
A sensible default
Record a VEX decision for every vulnerability that matches your SBOM, with a justification. Publish advisories for vulnerabilities you have fixed. Keep both tied to the release they describe. SBOMBox stores VEX decisions next to each release's SBOM so the evidence trail stays in one place; see the CRA workspace.