Skip to content

Commit bbf5ba9

Browse files
committed
Adding another blog post from LinkedIn
1 parent 95d7872 commit bbf5ba9

2 files changed

Lines changed: 43 additions & 0 deletions

File tree

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
+++
2+
author = "Jason Smith"
3+
title = "Why SBOMs Are Not One-and-Done πŸ“¦πŸ”„"
4+
date = "2025-05-25"
5+
linkedin = "https://www.linkedin.com/posts/j28smith_sbom-cybersecurity-softwaresupplychain-activity-7325922851973189634-o0SG"
6+
image = "img/thirdparty/2025-05-25-SBOMLifecycle.jpeg"
7+
+++
8+
9+
βœ… You've generated an SBOM. Congratulations!
10+
11+
But here's the truth. An SBOM is not a report you create once and tuck away. Modern software changes constantly. New features, updated libraries, security patches, refactored code... All of this reshapes your software supply chain.
12+
13+
That means your SBOM must evolve alongside your software. Here's why a one-and-done SBOM isn't enough:
14+
15+
πŸ”„ Continuous delivery = continuous change
16+
17+
* Your software isn't static. Your SBOM can't be static either.
18+
19+
⚠️ New risks appear every day
20+
21+
* A library that was safe last month might have a critical vulnerability today.
22+
23+
πŸ“Š Compliance requirements keep shifting
24+
25+
* Regulators, customers, and partners increasingly expect current SBOMs, not historical snapshots.
26+
27+
πŸ” Trust is only as strong as verification
28+
29+
* It's not enough to just have an SBOM. You need to be able to prove it's authentic. Signing SBOMs and using cryptographic verification ensures they haven't been tampered with.
30+
31+
πŸ—οΈ Automation is key
32+
33+
* To keep up, SBOM generation needs to be integrated into your CI/CD pipelines - not left as a manual task.
34+
35+
Key takeaway:
36+
37+
If you're not updating your SBOM regularly, you're not really managing your software supply chain. And let's be honest, if you don't have your SBOM generation automated it is already out of date.
38+
39+
Are you automating SBOM generation or piecing it together manually? Are you signing them? What's worked (or hasn't worked) for your team?
40+
41+
If this or any of my past SBOM posts have resonated, drop a comment, I'd love to hear what you think!! πŸ’¬πŸ‘‡
42+
43+
#SBOM #CyberSecurity #SoftwareSupplyChain #DevSecOps #OpenSourceSecurity #SupplyChainSecurity #ContinuousDelivery #DigitalTrust #SoftwareIntegrity #SecureDevelopment
29.4 KB
Loading

0 commit comments

Comments
Β (0)