Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 602

Kyverno

What is Kyverno?

KyvernoKyverno is a CNCF Kubernetes policy engine that validates, mutates, and generates resources using policies written as native Kubernetes YAML rather than a new DSL.


Kyverno installs as an admission webhook and runs ClusterPolicy or Policy CRs expressed in YAML with selector, match, validate, mutate, generate and verifyImages rules. Because the policy language matches Kubernetes object structure, teams familiar with manifests can author rules without learning Rego. Kyverno also handles image verification (Cosign/Notation), background scans of existing resources, exception workflows, and generation of dependent objects (NetworkPolicy, RoleBinding) when new namespaces appear. It is commonly used to enforce Pod Security Standards, image-signing, label conventions, and supply-chain attestations, and competes with OPA Gatekeeper for the same admission-policy space.

Examples

  1. 01

    A Kyverno policy that auto-generates a default-deny NetworkPolicy in every new namespace.

  2. 02

    verifyImages policy requiring all container images to carry a valid Cosign signature.

Frequently asked questions

What is Kyverno?

Kyverno is a CNCF Kubernetes policy engine that validates, mutates, and generates resources using policies written as native Kubernetes YAML rather than a new DSL. It belongs to the Cloud Security category of cybersecurity.

What does Kyverno mean?

Kyverno is a CNCF Kubernetes policy engine that validates, mutates, and generates resources using policies written as native Kubernetes YAML rather than a new DSL.

How does Kyverno work?

Kyverno installs as an admission webhook and runs ClusterPolicy or Policy CRs expressed in YAML with selector, match, validate, mutate, generate and verifyImages rules. Because the policy language matches Kubernetes object structure, teams familiar with manifests can author rules without learning Rego. Kyverno also handles image verification (Cosign/Notation), background scans of existing resources, exception workflows, and generation of dependent objects (NetworkPolicy, RoleBinding) when new namespaces appear. It is commonly used to enforce Pod Security Standards, image-signing, label conventions, and supply-chain attestations, and competes with OPA Gatekeeper for the same admission-policy space.

How do you defend against Kyverno?

Defences for Kyverno typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for Kyverno?

Common alternative names include: Kyverno Policy, ClusterPolicy.

Related terms