-
Notifications
You must be signed in to change notification settings - Fork 173
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
Communicate Feature - Convert SBOM to security compliant formats .spdx or .cyclone.dx #1387
Closed
2 of 5 tasks
Labels
documentation 📘
Improvements or additions to documentation
Comments
Racer159
added a commit
that referenced
this issue
Mar 2, 2023
## Description - [x] - Made list formatting consistent with Docs Style Guide - [x] - Added new feature to feature list ( Convert SBOM JSON file into other formats (.xpdx or .cyclone.dx) to meet government compliance.) ## Related Issue Fixes #1387 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) --------- Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com>
Noxsios
pushed a commit
that referenced
this issue
Mar 8, 2023
## Description - [x] - Made list formatting consistent with Docs Style Guide - [x] - Added new feature to feature list ( Convert SBOM JSON file into other formats (.xpdx or .cyclone.dx) to meet government compliance.) ## Related Issue Fixes #1387 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) --------- Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com>
Noxsios
pushed a commit
that referenced
this issue
Mar 8, 2023
## Description - [x] - Made list formatting consistent with Docs Style Guide - [x] - Added new feature to feature list ( Convert SBOM JSON file into other formats (.xpdx or .cyclone.dx) to meet government compliance.) ## Related Issue Fixes #1387 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) --------- Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com> Signed-off-by: razzle <harry@razzle.cloud>
Racer159
added a commit
that referenced
this issue
Mar 8, 2023
## Description - [x] - Made list formatting consistent with Docs Style Guide - [x] - Added new feature to feature list ( Convert SBOM JSON file into other formats (.xpdx or .cyclone.dx) to meet government compliance.) ## Related Issue Fixes #1387 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) --------- Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com> Signed-off-by: Wayne Starr <me@racer159.com>
Racer159
changed the title
Communicate Feature - Convert SBOM to security compliant formats .xpdx or .cyclone.dx
Communicate Feature - Convert SBOM to security compliant formats .spdx or .cyclone.dx
Mar 19, 2023
Completed in #1688 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current State
I spoke with someone who works in defense cyber security about SBOM. They were very eager and concerned about the format type for SBOM to meet compliance. The conversation could not proceed much past them knowing what formats Zarf supported for SBOM - indicating that it is important to potential users to know upfront if SBOM supports file formats that are compliant with government controls.
As a potential Zarf users - I would like to easily be able to find information on what SBOM file formats Zarf supports. This is important to my contract requires me to have an SBOM in a compliant format (.spdx or .cyclone.dx) to delivery my software to a controlled system.
Describe the solution you'd like
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: