paperbot · PL 论文追踪

全部论文 待读 收藏

P2 VeriSBOM: Secure and Verifiable SBOM Sharing via Zero-Knowledge Proofs

VeriSBOM:基于零知识证明的安全可验证 SBOM 共享
ASE Proceedings of the 41st IEEE/ACM International Conference on Automated Software Engineering2026匹配度 2/10 · 该论文聚焦于使用零知识证明实现可验证的 SBOM 共享与策略合规检查,属于软件供应链安全与密码学验证方向,与用户关注的程序分析、LLM/Agent 交叉、浮点程序分析或贝叶斯程序分析几乎没有直接关系。虽然涉及“验证”和形式化密码学保证,但并非静态分析、程序验证或 LLM 辅助分析方向。引用 1 inbox
Gianpietro Castiglione, Shahriar Ebrahimi, Narges Khakpour
crossref: 2026-10-09

AI 速览

一句话:提出 VeriSBOM,用零知识证明实现不泄露敏感信息的可验证 SBOM 共享与策略合规检查。

SBOM 常包含敏感信息,组织不愿完整披露,但明文共享会破坏隐私与机密性。论文提出 VeriSBOM,一个无需信任的 SBOM 框架,利用零知识证明提供密码学可验证性:第三方可验证软件是否包含由官方包管理器分发的真实依赖,且这些依赖满足策略约束。验证过程除底层密码原语可靠性外无需信任 SBOM 发布者,第三方可基于公开密码承诺独立验证证明。作者设计并实现 VeriSBOM,分析其安全性,并在真实包注册表和 SBOM 上评估性能,同时评估可用性。

问题
SBOM 常包含敏感信息,明文共享会泄露隐私与机密性;第三方难以在不信任发布者的情况下验证依赖真实性与策略合规性。
方法
设计并实现 VeriSBOM,使用零知识证明和公开密码承诺,让第三方无需信任发布者即可验证依赖来自官方包管理器并满足策略约束。
评估
分析 VeriSBOM 的安全性,并在真实包注册表和 SBOM 上评估性能,同时开展可用性评估。
原文摘要(Abstract)

SBOMs often contain sensitive information that organizations are unwilling to disclose in full. To avoid disruption of privacy and confidentiality in delivering plaintext SBOMs, we present VeriSBOM, a trustless SBOM framework that provides cryptographic verifiability of SBOMs using zero-knowledge proofs, i.e., third-parties can validate if software contains authentic dependencies distributed by official package managers and that the same dependencies are compliant with policy constraints. The verification process requires no trust in the SBOM publisher beyond the soundness of the underlying primitives, and third parties can independently check proofs against the public cryptographic commitments. We design and implement VeriSBOM, analyze its security, evaluate its performance on real-world package registries and SBOMs, and evaluate its usability.

链接与引用

DOI 原文 · arXiv · DBLP

BibTeX
@inproceedings{abs-2602-13682,
  title = {VeriSBOM: Secure and Verifiable SBOM Sharing via Zero-Knowledge Proofs},
  author = {Gianpietro Castiglione and Shahriar Ebrahimi and Narges Khakpour},
  booktitle = {ASE},
  year = {2026},
  doi = {10.1145/3832783.3834432}
}