Skip to main content
All attestations are bundled in a SigStore bundle and signed before being sent to Chainloop. This happens transparently while performing a chainloop attestation push command. Verification of the attestation integrity is done through the workflow run describe --verify true command to verify an online attestation, or attestation verify --bundle bundle.json to verify a downloaded attestation bundle. The signing and verification methods used by Chainloop CLI will depend on the different options provided. These are the various signing and verification methods currently supported by Chainloop:
Some of these signing methods are inherited from the amazing Sigstore community products. Please make sure to check their documentation on the usage of the --key argument for key references.

​
Signing with a local key

These methods require setting up a key and/or KMS authentication in the local environment (laptop, CI system …).

​
Keyless signing

These methods don’t require any special setup in the client. For the verification command, you must make sure you get the CA certificate chain out-of-band, as it will be required to validate the ephemeral signing certificate.

​
Bundles

When signing with a verification method that supports it (like keyless with ephemeral certificates), you can download the verification material used for signing, to be used later during the verification process. Get the bundle from the attestation:
And verify it:
Also note that chainloop wf run describe already detects a verifiable attestation and tries to perform the verification automatically. In these cases, you’ll see “Verified: true” in the command output.

​
Timestamp Service

Chainloop can be configured to send the attestation signature to a timestamp service (TSA) and include the result as part of the attestation bundle. If available, the TSA signature will be used during the verification process.