Skip to content

Commit ff8e616

Browse files
committed
Adding blog post
1 parent 4ea63eb commit ff8e616

2 files changed

Lines changed: 51 additions & 0 deletions

File tree

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
+++
2+
author = "Jason Smith"
3+
title = "🔏 SBOM Signing ≠ Security"
4+
date = "2025-06-08"
5+
linkedin = "https://www.linkedin.com/posts/j28smith_sbom-softwaresecurity-supplychainsecurity-activity-7341132648515346437-FqBE/"
6+
image = "img/thirdparty/2025-06-08-sbom-signing-checklist.jpeg"
7+
+++
8+
9+
🔏 SBOM Signing ≠ Security
10+
11+
Just because an SBOM is signed doesn't mean it's safe.
12+
13+
Signing is still important though. It gives you integrity. You know the SBOM wasn't tampered with after it was produced.
14+
15+
But integrity ≠ trustworthiness.
16+
17+
Here's why:
18+
19+
🧱 Garbage In, Garbage Out
20+
21+
If the SBOM was generated incorrectly, with missing or outdated components, signing it just seals in the errors.
22+
23+
🎭 Signed ≠ Honest
24+
25+
A signature only tells you who signed the SBOM. It says nothing about whether they were truthful, competent, or even authorized to sign it.
26+
27+
📅 Is It Still Current?
28+
29+
Software changes fast. An SBOM signed last week may already be outdated. If you can't link the SBOM to a specific build artifact or verify it's up to date, the signature alone doesn’t help.
30+
31+
⚖️ Trust is Contextual
32+
33+
Do you trust the signer? Are they using your keys, their own, or a third-party authority? Just because something can be verified doesn’t mean you'll trust what it says.
34+
35+
✅ Signing is a Baseline, Not a Guarantee
36+
37+
Think of signing as the "tamper-evident seal". Useful, but only meaningful if the package was accurate, complete, and fresh when sealed.
38+
39+
🤔 The takeaway?
40+
41+
Signed SBOMs are better than unsigned ones. But we need complete, current, and verifiable SBOMs, ideally linked to build systems and verified by trusted parties.
42+
43+
💬👇 Would love to hear:
44+
45+
❓ How are you validating SBOM accuracy and provenance today?
46+
47+
❓ Does signing increase your trust?
48+
49+
❓ What else would increase your trust?
50+
51+
hashtag#SBOM hashtag#SoftwareSecurity hashtag#SupplyChainSecurity hashtag#DigitalSignatures hashtag#SecureDevelopment hashtag#DevSecOps hashtag#ApplicationSecurity hashtag#SoftwareIntegrity hashtag#CyberSecurity
61.8 KB
Loading

0 commit comments

Comments
 (0)