Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Barriers to Adoption #16

Closed
wants to merge 1 commit into from
Closed

Add Barriers to Adoption #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,15 @@ The Federal Government exists at every point of the Software Delivery Lifecycle,
- ![](https://www.nist.gov/sites/default/files/styles/2800_x_2800_limit/public/images/2021/07/09/software-verification-timeline.png)
- [Minimum Standards for Federal Government End Users](https://www.nist.gov/itl/executive-order-improving-nations-cybersecurity/recommended-minimum-standard-vendor-or-developer)

## Current Barriers to Adoption

- Community Adoption
- Every single software supplier must provide a comprehensive, accurate, and up-to-date SBOM for every single software product they offer, commercial or open-source. If a supplier does not provide a complete, accurate, and up-to-date SBOM; then downstream consumers will have a harder time meeting SBOM requirements and identifying vulnerabilities in their software.
- Standards Diversion
- There are many different standards for SBOMs and vendors who are free to choose the best one that fits their use case. In most scenarios, there are 3 different commonly identified End Users with different user requirements cited. This can cause certain interoperability issues between certain formats, depending on the situation.
- SBOM Security
- SBOMs need to be secured from tampering and tampering attacks. Most SBOM generation pipelines are integrated into DevSecOps tooling, performing integration checking and digital signature verification. Currently, there are numerous product options availible, however, there is limited guidance available to ensure that SBOMs are available securely.
- Few large-scale working examples of SBOM configurations and deployments.

##
**Prior Work**
Expand Down