8000 docs: ADR-0009 SBOM Linking by lmphil · Pull Request #164 · bomctl/bomctl · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

docs: ADR-0009 SBOM Linking #164

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

Merged
merged 9 commits into from
Nov 25, 2024
Merged

docs: ADR-0009 SBOM Linking #164

merged 9 commits into from
Nov 25, 2024

Conversation

lmphil
Copy link
Contributor
@lmphil lmphil commented Sep 18, 2024

6. SBOM Linking

Date: 2024-09-18

Status

Proposed

Context

SBOM Document Linking (link command)

Bomctl needs the ability to create external references between documents. A use-case for this
feature could be a user that containerizes an application and then needs an SBOM for the new
container, with external references to the SBOMs of the container image and the application
binaries.

Another feature to discuss is the ability to express relationships between the components in the
SBOM.

Related issue: #81

Decision

TBD.

Consequences

✔️ Cross-referencing and tracking components will become easier. By allowing
external references and expressing relationships between components, tracking and understanding the
connections between various parts of a system will become more manageable. This will enable more
efficient analysis, such as impact assessment when making changes or upgrades.

✔️ Vulnerability scanning will be more thorough. With external references, it
will be easier to correlate SBOM components with known vulnerabilities in external repositories,
improving the overall security of the system.

Data validation and consistency will become harder. With external references, ensuring data
consistency and validating the accuracy of information from external sources could become more
challenging. Implementing robust validation and error-handling mechanisms will be crucial to
maintain data integrity.

Signed-off-by: Philippe <philippe.a.aviles@lmco.com>
@lmphil lmphil requested a review from a team as a code owner September 18, 2024 16:20
@ashearin ashearin added documentation Improvements or additions to documentation adr Architecture Decision Records use to decide architecture or implementation details of `bomctl` labels Sep 18, 2024
8000 @ashearin ashearin assigned lmphil Sep 18, 2024
Signed-off-by: Ian Dunbar-Hall <ian.dunbar-hall@lmco.com>
@jhoward-lm
Copy link
Contributor

The ADR ID 6 is already in use, can you update title to docs: ADR-0009 SBOM Linking, description header to 9. SBOM Linking, and corresponding markdown file name

Signed-off-by: Philippe <philippe.a.aviles@lmco.com>
…k-adr

Signed-off-by: Philippe <philippe.a.aviles@lmco.com>
@lmphil lmphil changed the title docs: SBOM Linking ADR docs: ADR-0009 SBOM Linking Oct 31, 2024
@idunbarh
Copy link
Member
idunbarh commented Nov 6, 2024

@bomctl/maintainers this needs to be revisited

Signed-off-by: Allen Shearin <allen.p.shearin@gmail.com>
@ashearin ashearin merged commit 4feaa42 into main Nov 25, 2024
9 checks passed
@ashearin ashearin deleted the sbom-link-adr branch November 25, 2024 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adr Architecture Decision Records use to decide architecture or implementation details of `bomctl` documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0