Skip to content
Slipwaydocs

Sigstore cosign

Sign images and verify signatures before deploy.

At a glance

Section titled “At a glance”
Category Security scanning
Authentication Keyless via job OIDC token, or KMS keys
Provider id cosign

What it does

Section titled “What it does”
  • Keyless signing with the job identity
  • Signature verification as a deploy gate
  • Attestation upload

Set up

Section titled “Set up”
  1. Add the scanner step to your pipeline (a uses: step or a container image).
  2. Upload the report (SARIF, JSON or SBOM) through the scan-report ingest API so Slipway can show findings on the run.
  3. Add a CEL policy gate on the environment, for example scan.critical == 0.

Configuration

Section titled “Configuration”

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

steps:
  - name: Sign
    run: cosign sign --yes ${{ needs.build.outputs.image }}
    # keyless: cosign exchanges $SLIPWAY_ID_TOKEN for a Fulcio certificate
permissions: { id_token: write }
Section titled “Related”