Ensure a signed Software Bill of Materials (SBOM) of the code is supplied

ÉlevéeNiveau 1Revue manuellegitlab

Description

A Software Bill of Materials (SBOM) is a file that specifies each component of software or a build process. When using a dependency, demand its SBOM and ensure it is signed for validation purposes. A Software Bill of Materials (SBOM) creates trust between its provider and its users by ensuring that the software supplied is the software described, without any potential interference in between. Signing an SBOM creates a checksum for it, which will change if the SBOM's content was changed. With that checksum, a software user can be certain nothing had happened to it during the supply chain, engendering trust in the software. When there is no such trust in the software, the risk surface is increased because one cannot know if the software is potentially vulnerable. Demanding a signed SBOM and validating it decreases that risk.

Méthode de vérification

Méthode d'audit: Revue manuelle

Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --include-manual.

For every artifact supplied, ensure it has a validated, signed Software Bill of Materials. To view the SBOMs associated with your projects, Navigate to Secure --> Dependency list You may export the SBOM in .json format.

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

For every artifact supplied, require and verify a signed Software Bill of Materials from its supplier. 1. To create an SBOM, you must run a dependency scan. 2. Enable dependency scanning, and an SBOM will be automatically generated for your project.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: devsecopsgitlabsbom
Référence: CIS GitLab Benchmark v1.0.1 - 3.1.6 Ensure a signed Software Bill of Materials (SBOM) of the code is supplied