Security questions to ask suppliers of vehicle and robot components
A buyer's list of questions for suppliers of connected components: SBOM, support period, update path, disclosure process and provenance of code.
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 buyer's list of questions for suppliers of connected components: SBOM, support period, update path, disclosure process and provenance of code.
Provenance asks whether a package traces back to its source. Learn how to read the sentence under that checklist item and verify it yourself.
The SolarWinds Orion backdoor shipped inside a signed update. What CISA says happened, what a signature proves, and what build integrity adds.
A dated walk through the SolarWinds Orion compromise, from the first test change in 2019 to discovery in December 2020, and the numbers to treat with care.
A dated list of well-known supply chain events from Heartbleed in 2014 to the XZ backdoor in 2024, with the one lesson each one is usually used to teach.
SLSA is a set of incremental guidelines for supply chain security, with Build Track levels 1 to 3. Learn what each level is for and how to start.
CISA's community document names six SBOM types: design, source, build, analyzed, deployed and runtime. What each captures and where each one is blind.
A keyless signature only means something if you verify the signer's identity. Here is what Cosign, Fulcio and Rekor each contribute and what to enforce.
Signatures show who signed, provenance shows how it was built, an SBOM shows what is inside. Here is what each answers and how they fit together.
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.