# How AT&T Turns Signed Evidence into Deployment Decisions with Kyverno

DevFeed: [How AT&T Turns Signed Evidence into Deployment Decisions with Kyverno](<https://devfeed.tech/articles/how-at-t-turns-signed-evidence-into-deployment-decisions-with-kyverno-139209.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/18/how-att-turns-signed-evidence-into-deployment-decisions-with-kyverno/>)

Author: Sagar Kundral

Published: 2026-11-18T01:14:41.413057Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [audit](<https://devfeed.tech/topics/audit.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [at-t](<https://devfeed.tech/tags/at-t.md>), [attestations](<https://devfeed.tech/tags/attestations.md>), [cel](<https://devfeed.tech/tags/cel.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [image-verification](<https://devfeed.tech/tags/image-verification.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>), [policy-as-code](<https://devfeed.tech/tags/policy-as-code.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [rules](<https://devfeed.tech/tags/rules.md>), [sbom](<https://devfeed.tech/tags/sbom.md>), [sigstore](<https://devfeed.tech/tags/sigstore.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

## AI overview

AT&T uses Kyverno ImageValidatingPolicy rules in CEL to turn verified image attestations into environment-specific admission decisions: a signed image can pass in development and fail in production if it lacks required evidence. The policy verifies signatures before reading claims, checks who built the image, then applies destination requirements; promotion checks do not replace admission because requests, policies and time-sensitive evidence can differ. AT&T uses one engine for internal and approved upstream or vendor images, with explicit trust roots; support for GitHub's private Sigstore root arrived in Kyverno 1.19, and the talk recommends 1.19.2 or later for Enforce mode. A single-laptop benchmark showed fewer registry calls and lower latency in newer versions, but these are not production figures and should be measured with local policies and registries. The talk also recommends planning failure behavior and narrow, expiring exceptions; retaining per-request decision evidence; and rolling out through audit, remediation, tiered enforcement and gradual expansion.

## Source excerpt

AT&T verifies signed provenance and SBOM attestations with a Kyverno ImageValidatingPolicy in CEL, then applies each environment's rules at admission.