Skip to content

Commit 9909653

Browse files
authored
Merge pull request #34 from RedHatProductSecurity/clarify-sbom-type
Clarify SBOM type for release-time SBOMs
2 parents 97c6339 + 231167e commit 9909653

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

docs/sbom.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -56,13 +56,14 @@ components used during the build process to produce the final artifact as well a
5656
process itself. This SBOM type also aligns with the _Build_ SBOM type from CISA's guidance on
5757
[Types of SBOM Documents](https://www.cisa.gov/sites/default/files/2023-04/sbom-types-document-508c.pdf).
5858

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
6161
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_.
6465

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
6667
can be located after being released.
6768

6869
**Example**:

0 commit comments

Comments
 (0)