--- title: Workload Identity Meets Supply Chain Security:... description: Teleport has integrated Sigstore into its Machine & Workload Identity product, allowing container image signatures and attestations to be checked as part of... canonical: https://daily.dev/posts/workload-identity-meets-supply-chain-security-teleport-s-sigstore-integration-m4nmhji1g twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Workload Identity Meets Supply Chain Security: Teleport's Sigstore Integration | daily.dev og:description: Teleport has integrated Sigstore into its Machine & Workload Identity product, allowing container image signatures and attestations to be checked as part of... og:url: https://daily.dev/posts/workload-identity-meets-supply-chain-security-teleport-s-sigstore-integration-m4nmhji1g og:image: https://api.daily.dev/og/posts/M4nMhJI1G.png og:image:alt: Workload Identity Meets Supply Chain Security: Teleport's Sigstore Integration og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Workload Identity Meets Supply Chain Security: Teleport's Sigstore Integration **[Teleport](https://daily.dev/sources/teleport)** · 9 min read · 0 upvotes · 0 comments ## Summary Teleport has integrated Sigstore into its Machine & Workload Identity product, allowing container image signatures and attestations to be checked as part of workload attestation before issuing SPIFFE-compliant SVIDs. The post explains Sigstore's keyless signing model using Fulcio and the Rekor transparency log, then walks through configuring a SigstorePolicy that requires GitHub Actions provenance attestations, wiring it into a WorkloadIdentity rule, and enabling tbot's Sigstore attestor. A demo shows a compromised container image being denied SVID issuance and blocked from accessing S3 because it lacks the required SLSA provenance attestation. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I require signed container images before issuing a workload identity credential in Teleport? Create a SigstorePolicy resource describing trusted signers and required attestations, reference it via the sigstore.policy_satisfied function inside a WorkloadIdentity rule's allow expression, and enable tbot's Sigstore attestor in the workload-identity-api service config so it discovers image signatures from an OCI registry before issuing SVIDs. _See how teams enforce signed-image policies with Teleport's Sigstore integration through daily.dev._ ### What is Sigstore's keyless signing approach and why does it avoid managing signing keys? Sigstore's keyless mode uses single-use certificates bound to an OIDC identity, such as a Google account or GitHub Actions token, instead of long-lived signing keys. Cosign generates a key pair, gets a short-lived X.509 certificate from Fulcio after verifying the OIDC token, signs the artifact, then discards the private key, with the signature recorded in the public Rekor transparency log. _Developers weighing signing approaches can track supply chain security tooling changes on daily.dev._ ### How does Teleport detect and block a compromised container image at runtime? tbot discovers the running container's image digest via the Kubernetes, Docker, or Podman API, queries the OCI registry for signatures and attestations, and sends them to the Teleport auth server, which evaluates the SigstorePolicy. If the required attestation, like SLSA provenance, is missing, the auth server refuses to issue the SVID, blocking the workload from obtaining credentials such as AWS access via Roles Anywhere. _Engineers hardening CI/CD pipelines can follow supply chain defense patterns like this on daily.dev._ ## Similar posts on daily.dev - [Signing and verifying container images with Cosign and Sigstore](https://daily.dev/posts/signing-and-verifying-container-images-with-cosign-and-sigstore-py88l4cfh) · Security Boulevard · 0 upvotes · 0 comments - [TEE-backed zero trust: Integrating SPIRE with confidential containers](https://daily.dev/posts/tee-backed-zero-trust-integrating-spire-with-confidential-containers-luit92ipq) · Red Hat Developer · 0 upvotes · 0 comments - [Workload And Agentic Identity at Scale: Insights From CyberArk's Workload Identity Day Zero](https://daily.dev/posts/workload-and-agentic-identity-at-scale-insights-from-cyberark-s-workload-identity-day-zero-xyj2rtiw5) · GitGuardian · 0 upvotes · 0 comments - [Sign OCI containers & other artifacts using Sigstore Cosign & CircleCI OIDC tokens](https://daily.dev/posts/sign-oci-containers-other-artifacts-using-sigstore-cosign-circleci-oidc-tokens-dibffmehm) · CircleCI · 1 upvotes · 0 comments - [Signing is for the bad days](https://daily.dev/posts/signing-is-for-the-bad-days-x6tdcvkg1) · Andrew Nesbitt · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security) [View this post on daily.dev](https://daily.dev/posts/workload-identity-meets-supply-chain-security-teleport-s-sigstore-integration-m4nmhji1g) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Workload Identity Meets Supply Chain Security: Teleport's Sigstore Integration","url":"https://daily.dev/posts/workload-identity-meets-supply-chain-security-teleport-s-sigstore-integration-m4nmhji1g","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/workload-identity-meets-supply-chain-security-teleport-s-sigstore-integration-m4nmhji1g"},"datePublished":"2026-08-23T12:19:23.460Z","dateModified":"2026-08-23T12:36:41.457Z","description":"Teleport has integrated Sigstore into its Machine & Workload Identity product, allowing container image signatures and attestations to be checked as part of...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/workload-identity-meets-supply-chain-security-teleport-s-sigstore-integration-m4nmhji1g","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"Workload Identity Meets Supply Chain Security: Teleport's Sigstore Integration"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/workload-identity-meets-supply-chain-security-teleport-s-sigstore-integration-m4nmhji1g#faq","mainEntity":[{"@type":"Question","name":"How can I require signed container images before issuing a workload identity credential in Teleport?","acceptedAnswer":{"@type":"Answer","text":"Create a SigstorePolicy resource describing trusted signers and required attestations, reference it via the sigstore.policy_satisfied function inside a WorkloadIdentity rule's allow expression, and enable tbot's Sigstore attestor in the workload-identity-api service config so it discovers image signatures from an OCI registry before issuing SVIDs. See how teams enforce signed-image policies with Teleport's Sigstore integration through daily.dev."}},{"@type":"Question","name":"What is Sigstore's keyless signing approach and why does it avoid managing signing keys?","acceptedAnswer":{"@type":"Answer","text":"Sigstore's keyless mode uses single-use certificates bound to an OIDC identity, such as a Google account or GitHub Actions token, instead of long-lived signing keys. Cosign generates a key pair, gets a short-lived X.509 certificate from Fulcio after verifying the OIDC token, signs the artifact, then discards the private key, with the signature recorded in the public Rekor transparency log. Developers weighing signing approaches can track supply chain security tooling changes on daily.dev."}},{"@type":"Question","name":"How does Teleport detect and block a compromised container image at runtime?","acceptedAnswer":{"@type":"Answer","text":"tbot discovers the running container's image digest via the Kubernetes, Docker, or Podman API, queries the OCI registry for signatures and attestations, and sends them to the Teleport auth server, which evaluates the SigstorePolicy. If the required attestation, like SLSA provenance, is missing, the auth server refuses to issue the SVID, blocking the workload from obtaining credentials such as AWS access via Roles Anywhere. Engineers hardening CI/CD pipelines can follow supply chain defense patterns like this on daily.dev."}}]} ```