TMA-GITLAB-4.1.1
Ensure all artifacts are signed by the build pipeline itself
Description
Configure the build pipeline to sign every artifact it produces and verify that each artifact has the appropriate signature. A cryptographic signature can be used to verify artifact authenticity. The signature created with a certain key is unique and not reversible, thus making it unique to the author. This means that an attacker tampering with a signed artifact will be noticed immediately using a simple verification step because the signature will change. Signing artifacts by the build pipeline that produces them ensures the integrity of those artifacts.
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.
Verify that the build pipeline signs every new artifact it produces and all artifacts are signed. There are many different signing tools or options each have there own method or commands to verify that the code or package created is signed.
How it is fixed
Fix method: Guidance or infrastructure patch
Sign every artifact produced with the build pipeline that created it. Configure the build pipeline to sign each artifact.
Properties
- Operating systems
- Any
- Tags
- ci-cddevsecopsgitlab
- Reference
- CIS GitLab Benchmark v1.0.1 - 4.1.1 Ensure all artifacts are signed by the build pipeline itself