File tree Expand file tree Collapse file tree 1 file changed +6
-5
lines changed Expand file tree Collapse file tree 1 file changed +6
-5
lines changed Original file line number Diff line number Diff line change @@ -56,13 +56,14 @@ components used during the build process to produce the final artifact as well a
56
56
process itself. This SBOM type also aligns with the _ Build_ SBOM type from CISA's guidance on
57
57
[ Types of SBOM Documents] ( https://www.cisa.gov/sites/default/files/2023-04/sbom-types-document-508c.pdf ) .
58
58
59
- _ Release-time_ SBOMs are generated when an artifact is released or published. These SBOMs build upon build-time
60
- SBOMs by incorporating additional metadata, such as the repositories or locations where the artifact is
59
+ _ Release-time_ SBOMs are created when an artifact is released or published. These SBOMs build upon build-time
60
+ SBOMs by incorporating additional metadata, such as the repositories or locations where an artifact is
61
61
published, and associating it with the relevant product information if there is any. Release-time SBOMs reflect the
62
- state of the software as it is distributed to end users. This SBOM type is close to the _ Deployed_ type as defined
63
- by CISA, but it reflects the state of the product that _ would_ be installed by a given end user.
62
+ state of the software as it is distributed to end users. This SBOM type should still be considered as a _ Build_ SBOM
63
+ as defined by CISA, but it simply includes additional metadata that is not available during the build process and is
64
+ added later on. For lack of a better term, we could call these _ Curated Build SBOMs_ .
64
65
65
- Red Hat's publicly available SBOMs are of the " release-time" type, including details about where an artifact
66
+ Red Hat's publicly available SBOMs are of the release-time type, including details about where an artifact
66
67
can be located after being released.
67
68
68
69
** Example** :
You can’t perform that action at this time.
0 commit comments