Ensure all artifacts are signed by the build pipeline itself

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. 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 ...