Build or buy SBOM generation: when open source tooling is enough
When a free open source SBOM generator in CI is enough, and when a platform earns its place: storage, matching, sharing, and who does the work.
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.
When a free open source SBOM generator in CI is enough, and when a platform earns its place: storage, matching, sharing, and who does the work.
Build one artifact, record its digest, and promote that exact artifact from test to production. Rebuilding per environment breaks what you tested.
For networks with no internet, review packages outside, import them as a checked bundle and record what came in. Steps, controls and arrival checks.
A scanner with repo access is a target. How to limit what a compromised vendor could reach: token scopes, repo selection, expiry, rotation and monitoring.
Add an attestation step after your image build, grant id-token, attestations and packages write, push by digest, then check it with gh attestation verify.
OCI referrers let a registry link an SBOM, signature or attestation to an image digest. What the subject field does and how clients find attachments.
Attest or sign the SBOM against the image digest. Cosign docs advise a small predicate pointing at the SBOM instead of embedding it. Steps and trade offs.
dotnet tools are NuGet packages that run as programs. Pin versions in a local tool manifest, restore from trusted sources and avoid shared install paths.
dbt Hub packages are third-party code that runs against your warehouse. Here is what the dbt docs say about trust and how to install them with care.
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.