Update SBOM generation to meet new guidance from CISA
@sethmlarson ya está trabajando en esto.
Desde el 15/8/2024.
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 35.9k
- Métricas de merge de PR
- Métricas de PR pendientes
Descripción
Proposal:
CISA has published the third revision of SBOM guidance, which at the moment isn't approved but is headed towards final rounds of review. Currently our SBOMs met the old revision which is "Minimum Elements of an SBOM" published by NTIA.
The new guidance uses a "maturity level", ranging from minimum required to aspirational. Below I've used the "aspirational" maturity level for all the criteria.
I checked our SBOM documents against the document to see how much would be needed to follow this new set of guidance. It turns out, not too much! Here's the breakdown:
Elements that need more work:
- Author Name: We need to add an email address
- SBOM Type: We need to upgrade to SPDX 3 for this field
- Supplier Name: Need to double-check that these names conform. Also need to update where we add Heritage information.
- Unique Identifier: We're almost there, there's at least one project we should request a CPE for.
- Heritage: We don't encode this information today. Some of our components are slightly modified from upstream dependency, should be automatable.
- Relationship Completeness
- License
- Copyright Notice
Elements we already conform with:
- Timestamp
- Primary Component
- Component Name
- Component Version
- Cryptographic Hashes
- Relationships
- Redacted and Unknown Components and Attributes
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.