Attach a custom in-toto predicate as a cosign attestation and enforce it with a Rego admission policy

domain: docs.sigstore.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Produce a custom predicate JSON document (e.g. internal compliance-check output) that is not one of cosign's built-in predicate types.
  2. Sign and attach it with cosign attest, setting the predicate file and type to custom, which wraps the predicate in an in-toto statement.
  3. Write a Rego policy that inspects the predicate portion of the attestation for required fields, such as a passing compliance-check status.
  4. Verify the attestation and evaluate the policy together with cosign verify-attestation, passing the Rego policy file and the custom type.
  5. Wire the verify-attestation call into a deployment gate (CI job or admission controller) so images without a passing custom attestation are rejected before promotion.

Known gotchas

Related routes

Attach a custom in-toto predicate attestation to an OCI image using cosign attest
docs.sigstore.dev · 5 steps · unrated
Understand in-toto attestation predicate types and choose the right one for your use case
slsa.dev · 6 steps · unrated
Generate and verify an in-toto attestation with a SLSA provenance predicate for a build artifact
security/compliance · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans