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 and sign an SBOM for the released binaries #833

Closed
2 of 3 tasks
dadrus opened this issue Aug 4, 2023 · 0 comments · Fixed by #867
Closed
2 of 3 tasks

Generate and sign an SBOM for the released binaries #833

dadrus opened this issue Aug 4, 2023 · 0 comments · Fixed by #867
Labels
ci task related to the ci workflow feature Used for new features
Milestone

Comments

@dadrus
Copy link
Owner

dadrus commented Aug 4, 2023

Preflight checklist

Describe the background of your feature request

As high-profile cyberattacks continue to grow, many organizations request an SBOM, which can help them to identify components and assets which needs an update. Additionally, SBOM can help organizations improving their licensing compliance by providing detailed information about the associated licenses.

Indeed, providing SBOM is even mandatory for federal contracts.

Describe your idea

For the reasons, described above heimdall releases should include an SBOM. To have an attestation, the released SBOM shall be signed.

Are there any workarounds or alternatives?

Building an SBOM from the released container image, e.g. using syft.

Version

v0.11.0-alpha

Additional Context

No response

@dadrus dadrus added the feature Used for new features label Aug 4, 2023
@dadrus dadrus added this to the v0.12.0-alpha milestone Aug 4, 2023
@dadrus dadrus added the ci task related to the ci workflow label Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci task related to the ci workflow feature Used for new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant