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.

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

Generate a Software bill of materials in CI/CD Pipeline #85

Open
vidyambala opened this issue Feb 2, 2022 · 0 comments
Open

Generate a Software bill of materials in CI/CD Pipeline #85

vidyambala opened this issue Feb 2, 2022 · 0 comments

Comments

@vidyambala
Copy link
Contributor

Benefit/Result/Outcome

An SBOM is useful to producers and consumers of software, as it provides software transparency, software integrity, and software identity benefits. Here is a bit about each:

Software transparency: SBOMs provide a list of ingredients used in the creation of a piece of software, such as open source software, components, and potentially even build tools. This enables producers and consumers to better inventory and evaluate license and vulnerability risk.
Software integrity: While code signing is still the industry standard for trusting software and its integrity, SBOMs contain package and file checksums to enable consumers to validate the hashes, which can be useful in scenarios when signatures aren’t present.
Software identity: When vulnerabilities (CVEs) are created, they are assigned to a Common Platform Enumeration (CPE) identifier, which can have issues attributing a CPE to a specific piece of software. Software IDs within SBOMs provide a much more accurate way to identify software.

Description

Write a description of how the outcome might be achieved.

Acceptance Criteria

Level of Effort : M-L

Use the T-Shirt sizing "XS, S, M, L, XL, XXL" scale to estimate the level of effort to complete this issue. XS is 1/2 day effort, S is a single day effort, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant