GitHub
TMA-GITHUB-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. Reported as a manual review item: no reliable read-only gh api check exists for this control.
Méthode de vérification
Méthode d'audit: Revue manuelle
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.
Méthode de correction
Méthode de correction: Recommandation ou correctif d'infrastructure
Sign every artifact produced with the build pipeline that created it. Configure the build pipeline to sign each artifact. Steps from GitHub Documentation: You can follow the steps below to sign artifacts in GitHub actions. The trick involves loading in your private key into GitHub Actions using the gpg command-line commands. Export your gpg private key from the system that you have created it. Find your key-id (using gpg --list-secret-keys --keyid-format=long) Export the gpg secret key to an ASCII file using gpg --export-secret-keys -a > secret.txt Edit secret.txt using a plain text editor, and replace all newlines with a literal "\n" until everything is on a single line Set up GitHub ...
Propriétés
- Systèmes d'exploitation
- Tous
- Étiquettes
- githubartifacts
- Référence
- CIS GitHub Benchmark v1.2.0 - 4.1.1 Ensure all artifacts are signed by the build pipeline itself