We Value Your Privacy

We use technology such as cookies on our website, and through our partners, to personalize content and ads, provide social media features, and analyse our traffic. To find out more, read our privacy policy and Cookie Policy. Please also see our Terms and Conditions of Use. By accepting these terms you agree to your information being processed by Inbox Insight, its Partners or future partners, that you are over 18, and may receive relevant communications through this website, phone, email and digital marketing. For more information on how we process your data, or to opt out, please read our privacy policy. Our policies and partners are subject to change so please check back regularly to stay up to date with our terms of use and processing.

Accept Terms Settings
x

Please Sign-In to Access this Report

To access other reports on the platform please sign in with your username and password, or register for a free account to get unlimited access and insight customized for you.

Report ReversingLabs

How & Why NIST is Driving SBOM Evolution

Understanding the Requirement for Software Bills of Material (SBOM) in Executive Order 14028

The NIST-published guidance for complying with the Cybersecurity Executive Order, asks makers of commercial off-the-shelf (COTS) and government off-the-shelf (GOTS) software to: “Collect, maintain, and share provenance data for all components and other dependencies of each software release (e.g., in a Software Bill of Materials [SBOM]).” In short, every software supplier to federal agencies now has two deliverables - the software and a Software Bill of Materials.

Report Snap Shot

Download our guide and get insight into:    

  • The National Institute of Standards (NIST) role in the EO
  • Why the EO includes SBOM requirements
  • The evolution and the future of SBOM

 

Related Content