Add automatic SBOM generation on CycloneDX format #594
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes introduced with this PR
The work introduced via this pull request focuses on modifying the build process on the
main.yml
andgoreleaser.yml
files to automatically generate a Software Bill of Materials as suggested on this issue.A new artifact
containerssh.cdx.sbom
is created at each release. The artifact's checksum is stored in the checksum file, so it can be verified considering the checksum file is signed. Thanks to this, the SBOM file will also be included in the provenance generation process.We decided to use the OWASP CycloneDX SBOM standard, approved by the NTIA as you can see in their report. It is a relatively new, fully automated, security-focused lightweight SBOM standard which provides many tools such as the SBOM generator for Go modules, as well as Github actions for a smooth integration into the existing workflow.
If you have any question, feel free to contact us.
By contributing to this repository, I agree to the contribution guidelines.