TMA-GITLAB-4.3.1
Ensure all signed artifacts are validated upon uploading the package registry
Description
Validate artifact signatures before uploading to the package registry. Cryptographic signature is a tool to verify artifact authenticity. Every artifact is supposed to be signed by its creator in order to confirm that it was not compromised before reaching the client. Validating an artifact signature before delivering it is another level of protection which ensures the signature has not been changed, meaning no one tried or succeeded in tampering with the artifact. This creates trust between the supplier and the client.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
Ensure every artifact in the package registry has been validated with its signature. 1. On the left sidebar, select Search or go to and find your project. o To review commits for a project, select Code > Commits. o To review commits for a merge request, select Code > Merge requests, then select your merge request. 2. Select Commits. 3. Identify the commit you want to review. Signed commits show either a Verified or Unverified badge, depending on the verification status of the signature. Unsigned commits do not display a badge.
How it is fixed
Fix method: Guidance or infrastructure patch
Validate every artifact with its signature before uploading it to the package registry. It is recommended to do so automatically.
Properties
- Operating systems
- Any
- Tags
- devsecopsgitlab
- Reference
- CIS GitLab Benchmark v1.0.1 - 4.3.1 Ensure all signed artifacts are validated upon uploading the package registry