It's more than common today to be bombarded with articles and pontification about the importance of a software bill of materials (SBOM), why it's now so high-profile, what should be included in an SBOM, who owns its production, how it gets produced, and other persistent questions.

Take ten minutes to hear from this expert panel on where organizations should spend their time and effort when it comes to SBOMs.

"The SBOM itself gives you a structured way to access information. It let's you know what's there, what is it, what version is it, where did it come from, and what terms does it haveā€¦Once you have that information about that software that either you ingest or you're about to ship, you have to have things that you do with that information and that's where SBOM ends and you're on to another aspect of managing your security."

Shane Coughlan, Linux Foundation

Hear more from this high-profile panel of professionals:

  • Shane Coughlan, OpenChain General Manager, Linux Foundation
  • Russ Eling, Founder, OSS Consultants
  • Stephen Gillespie, Partner, Fenwick
  • Marcus Lucero, Sr. Open Source Analyst, Revenera
  • Heather Meeker, General Partner, OSS Capital
  • Alex Rybak, Sr. Director of Product Management, Revenera


Product Interest (Select all that apply)