CSAF VEX Remediations and Threats: What Trivy Gets Wrong
CSAF 2.0 puts the fix, the workaround, the restart cost and the reason a product is not affected in two arrays: remediations and threats. Here is what …
Tag
CSAF 2.0 puts the fix, the workaround, the restart cost and the reason a product is not affected in two arrays: remediations and threats. Here is what …
OpenVEX v0.2.0 defines 13 statement fields, but Trivy v0.76.2 acts on two of them: status and justification, from the matching statement with the …
A source-checked guide to vexctl v0.4.4: the create, add, merge and attest commands, the validation rules they enforce, why merge keeps every …
How Trivy's --vex oci finds an OpenVEX document attached to a container image: the three registry layouts it reads, the in-toto.io/predicate-type …
An OpenVEX statement suppresses a finding only when its products, subcomponents and purls line up with what the scanner found. Here is how the go-vex …
A CSAF VEX file never puts a purl next to a status. Product IDs in product_status point into the product_tree, often through relationships. Here is …
CycloneDX VEX uses six analysis states and nine justifications; OpenVEX and CSAF use four statuses and five justifications. Here is a field-by-field …
A six-step patch-decision flow that takes a scanner finding from CVE record to ticket: check the record state, confirm you are affected, apply …