GitOps Security - Because Git Commits Shouldn't Deploy Vulnerable Containers

GitOps delivers on its promise for deployment velocity: immutable infrastructure, Git as the source of truth, one-way automated sync from repository to cluster. ArgoCD and Flux are the standard tools. But most GitOps implementations treat security as a post-deployment concern — images are deployed first, scanned later (sometimes never). The result is a fast, automated path to production that works equally well for vulnerabilities.

When you automate deployment, you also automate risk — unless you build cryptographic verification gates into the pipeline.

This session exposes the four critical security gaps in a standard GitOps workflow and demonstrates how to close each one with open source tools, without adding friction to the developer experience:

• Gap 1 — Unsigned images: anyone with registry push access can deploy anything. Fix: Cosign image signing + Kyverno admission policy blocking unsigned images before the pod starts.

• Gap 2 — Unverified manifests: a tampered manifest in Git deploys silently. Fix: ArgoCD sync verification with cryptographic manifest integrity checks.

• Gap 3 — Policy drift: what Kyverno allows at deploy time diverges from your security policy over time. Fix: OPA / Gatekeeper as the persistent policy anchor.

• Gap 4 — No image audit trail: who deployed what image, from which commit, when. Fix: in-toto attestations stored alongside the image in OCI registries.

Live demo: a complete commit-to-deploy flow — Cosign signing, Kyverno ClusterPolicy enforcement, and a forced admission block when an unsigned image is referenced in an ArgoCD-managed manifest.

Note on format: demonstrating four integrated security layers end-to-end requires the 20-minute Standard Session slot. The value is seeing how these FOSS tools work together as one system, not in isolation.

All tools are CNCF or CNCF-sandbox projects, open source under Apache 2.0. 

1. A map of the four critical security gaps in a standard ArgoCD/Flux GitOps pipeline — and the specific open source tool (Kyverno, Cosign, OPA, in-toto) that closes each one.

2. A ready-to-apply Kyverno ClusterPolicy that blocks unsigned or unverified container images at Kubernetes admission time — copy-paste ready, demonstrated live against a running cluster.

3. The complete GitOps security architecture — Cosign signing + Kyverno enforcement + OPA policy + in-toto attestations — working as one automated system, without adding any manual steps to the developer commit workflow.