Skip to content

Commit c110536

Browse files
committed
Add blog post: SBOM Signature Storage Tax
1 parent 3190a63 commit c110536

2 files changed

Lines changed: 47 additions & 0 deletions

File tree

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
+++
2+
author = "Jason Smith"
3+
title = "The SBOM Signature 'Storage Tax': Money Talks πŸ’°πŸ“‰"
4+
date = "2026-02-23"
5+
linkedin = "https://www.linkedin.com/posts/j28smith_finops-eu-cra-activity-7431724688411754496-7VnP"
6+
image = "img/thirdparty/2026-02-23-sbom-signature-storage-tax.png"
7+
+++
8+
9+
Over the last few weeks, I've been deep in the weeds of technical best practices for signing SBOMs. I've discussed
10+
JSF, JCS, property exclusion, and how we move toward data-aware integrity for better interoperability. πŸ”
11+
12+
But beyond the technical elegance of a resilient signature, there is a much simpler driver for this work: The Bottom
13+
Line. πŸ’³
14+
15+
Currently, most organizations sign SBOMs as binary blobs. This means you are signing the file (the container), not the
16+
data (the content). If you change a single space or minify the file for storage, the signature breaks. ❌
17+
18+
This comes with a massive economic cost. πŸ’Έ
19+
20+
With regulations like the EU Cyber Resilience Act (CRA) mandating that manufacturers store SBOMs for 10+ years,
21+
storage is no longer a round-off error in your cloud budget. β˜οΈπŸ’΅
22+
23+
The realities of the SBOM binary blob signature storage tax... πŸ‘€
24+
25+
## πŸ’Ύ Storage Inefficiency
26+
27+
Binary blob signatures prevent you from minifying your data. You are forced to store every space and newline to keep
28+
the signature valid.
29+
30+
## πŸ“ˆ The 40% Premium
31+
32+
My initial estimates show that signing "pretty-printed" SBOMs results in ~ 40% higher storage costs (or more) compared
33+
to data-aware signing.
34+
35+
## ⏳ 10-Year Compounding
36+
37+
Across thousands of builds and a decade of mandatory retention, that "formatting debt" turns into a significant
38+
long-term financial liability.
39+
40+
Technical specifications help with interoperability, but money talks. Data-aware signing isn't just about better
41+
security, it's about avoiding a decade-long storage tax. 🏦
42+
43+
I brought up this point during my last presentation at the [OpenSSF](https://openssf.org/) SBOM Everywhere SIG meeting
44+
and the shift in the room was noticeable. It's a powerful reminder that while technical specs drive interoperability,
45+
economic impact drives adoption. πŸš€
46+
47+
\#FinOps \#EU \#CRA \#SBOM \#SupplyChainSecurity \#CloudCosts \#OpenSSF \#DevSecOps \#CyberResilienceAct
4.1 MB
Loading

0 commit comments

Comments
Β (0)