Establishing Provenance Before Coding: Traditional and Next-Gen Signing
<|reference_start|>Establishing Provenance Before Coding: Traditional and Next-Gen Signing: Software engineers integrate third-party components into their applications. The resulting software supply chain is vulnerable. To reduce the attack surface, we can verify the origin of components (provenance) before adding them. Cryptographic signatures enable this. This article describes traditional signing, its challenges, and changes introduced by next generation signing platforms<|reference_end|>
@article{schorlemmer2024establishing,
    title={Establishing Provenance Before Coding: Traditional and Next-Gen Signing},
    author={Taylor R. Schorlemmer, Ethan H. Burmane, Kelechi G. Kalu, Santiago
  Torres-Arias, James C. Davis},
    journal={arXiv preprint arXiv:2407.03949},
    year={2024},
    archivePrefix={arXiv},
    eprint={2407.03949},
    primaryClass={cs.CR cs.SE}
}