<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sbom on CuraSec</title><link>https://curasec.metacog.co.kr/tags/sbom/</link><description>Recent content in Sbom on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 18:11:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/sbom/index.xml" rel="self" type="application/rss+xml"/><item><title>TrustBOM: Zero-Knowledge Proofs for Confidentiality-Preserving SBOMs</title><link>https://curasec.metacog.co.kr/insights/2026-09-21-trustbom-a-scalable-architecture-for-confidentiality-preserv/</link><pubDate>Mon, 21 Sep 2026 18:11:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-21-trustbom-a-scalable-architecture-for-confidentiality-preserv/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel architecture using ZK non-membership proofs lets you attest vulnerability or license absence to downstream consumers without exposing your full dependency graph — worth tracking as a future pattern for cross-org SBOM sharing in CI/CD pipelines.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Confidentiality concerns are a documented barrier to SBOM adoption across vendor relationships; this research validates that cryptographic approaches may eventually resolve the tension between supply chain transparency mandates and IP protection — useful context for future SBOM policy and vendor attestation strategy.&lt;/li>
&lt;/ul></description></item></channel></rss>