You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For creating a document which is related to the security contexts, we have to present the software bill of materials.
Without this type of documents, the newbies, who wants to grasp security aspects, didn't get understand about it.
Hi Hiroshi besides the SBOM and any further feedback from other mainters, I don't believe we have any further documents required. The OpenSFF mentioned in our discussion on github is a security standard met by Fluentd correct?
Describe the bug
For creating a document which is related to the security contexts, we have to present the software bill of materials.
Without this type of documents, the newbies, who wants to grasp security aspects, didn't get understand about it.
ref: https://edu.chainguard.dev/open-source/sbom/what-makes-a-good-sbom/
Link to the problematic documentation
None. There is no articles for it.
Expected explanation
This SBOM receipt can be generated by
docker sbom
easily for now.ref: https://docs.docker.com/engine/sbom/
The description of software bill of material is:
https://www.ntia.gov/files/ntia/publications/howto_guide_for_sbom_generation_v1.pdf
Additional context
Currently, the SBOM files can be created by:
The text was updated successfully, but these errors were encountered: