How do you sign and verify a Helm chart with provenance?
Helm uses PGP and a .prov file to prove a chart archive is intact and who signed it. Commands, what the file holds, and what it does not prove.
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.
Helm uses PGP and a .prov file to prove a chart archive is intact and who signed it. Commands, what the file holds, and what it does not prove.
Treat a vendor update as an incoming release: verify its source and hash, inspect its contents or SBOM, test in staging, and keep the intake record.
Layer versions are immutable, so a fix means publishing a new version and attaching it to every function. A step by step rollout with checks.
A field by field guide to SLSA build provenance: buildType, externalParameters, resolvedDependencies, builder id and runDetails, and which ones to verify.
go.sum lists a checksum for each module version Go has used, so a changed download is caught. Learn how to read its lines and what to review in a diff.
Name each SBOM by release ID and artifact digest, give it a unique serial number, store it read-only beside the release, and never overwrite an old one.
Merge per service SBOMs into one product SBOM with a flat or hierarchical merge. See when each fits and what every input file needs before you start.
Count suppliers with an SBOM, then measure freshness, validity and usable identifiers. Five metrics show if an SBOM program is real or just files.
A step by step method to turn SBOM components into vulnerability findings: normalize identifiers, query advisories, test version ranges, then enrich.
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.