<p dir="auto"><a href="https://infosec.exchange/@joshbressers" rel= "nofollow">Josh</a> and <a href= "https://infosec.exchange/@kurtseifried" rel="nofollow">Kurt</a> talk about package identifiers. We break this down in the context of an OpenSSF response to a CISA paper on software identifications. The identifiers that get all the air time are purl, CPE, SWID, and OmniBOR. This is a surprisingly complex problem space. It feels easy, but it's not.</p> Show Notes <ul dir="auto"> <li><a href= "https://openssf.org/blog/2023/12/11/openssf-responds-to-the-cisa-rfc-on-software-identification-ecosystem-analysis/" rel="nofollow">OpenSSF CISA response</a></li> <li><a href= "https://github.com/package-url/purl-spec">purl</a></li> <li><a href="https://nvd.nist.gov/products/cpe" rel= "nofollow">CPE</a></li> <li><a href="https://omnibor.io/" rel="nofollow">OmniBOR</a></li> <li><a href= "https://csrc.nist.gov/projects/software-identification-swid" rel= "nofollow">SWID</a></li> </ul>

Episode 411 - The security tools that started it all

Open Source Security is a media project to help showcase and educate on open source security. Our goal is to give the community a platform educate both developers and users on how open source security works.

There's a lot of good work happening that doesn't get attention because there's no marketing department behind it, they don't have a developer relations team posting on LinkedIn every two hours. Let's focus on those people and teams then learn what they do and how they do it. The goal is to hear from the people doing the work, they know what's up, they have a lot to teach us. We just have to listen.