Which VEX format should a software vendor publish?
A decision guide to publishing VEX as CSAF, CycloneDX or OpenVEX: what each carries, what customers tend to ask for, and how to avoid maintaining three.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
A decision guide to publishing VEX as CSAF, CycloneDX or OpenVEX: what each carries, what customers tend to ask for, and how to avoid maintaining three.
Advisory scanners cannot find true zero days. Here are the four approaches that can, what each needs from you, and how to judge claims about them.
A buyer's map of four supply chain attack classes, dependency confusion, hijacked maintainers, build compromise and bad updates, and the control for each.
A decision table for choosing SLSA Build L1, L2 or L3 based on who consumes your artifacts and what you can change on your build platform today.
Use serial number, version and timestamp to pick the right revision of a supplier SBOM, keep the old one, and avoid double counting findings.
A pre-send checklist of SBOM fields that can expose internal package names, registry URLs, file paths and tool details, and how to handle each one.
Use the purl type that matches where the library came from: conan, vcpkg, deb, rpm, apk, github or generic. A short decision table with the reasoning.
A table of which package managers run code from dependencies during install or build, what the documentation says, and what that means for malware risk.
Use a granular npm token limited to the packages you publish, with an expiry and IP limits. The settings explained, plus the 2FA bypass trap.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.