Cloud Edition
Govern every cluster with Kyverno. Prove it at audit time.
Policies, exceptions, image risk and compliance in one place. From the creators of Kyverno.
Policy as code, on every cluster.
Sync policy sets from Git and roll them out where they belong.
- GitOps sync and auto-deploy
- Target clusters by label
- Curated policy sets from the Kyverno team
- Scan repos and CI pipelines
Exceptions with guardrails.
Approved, time-boxed and audited. Fixes go to the owners.
- Scoped to namespace, cluster, repo or resource
- Expire after a day, week or month
- Approval rules with reviewers and MFA
- Jira tickets and fix suggestions
ns: batch-legacy in prod-us-east · policy disallow-host-pathSee which vulnerable images are running.
CVEs, policy violations and workloads in one view.
- CVEs by severity for every image
- Policy violations alongside CVEs
- Where each image runs
- Violations by cluster and namespace
| Image | Crit | High | Med | Policy | Running |
|---|---|---|---|---|---|
payments/apiv3.8.1 | 6 | 21 | 14 | 2 | 8 |
library/nginx1.25.3 | 4 | 17 | 9 | – | 23 |
ml/feature-store2024.11 | 3 | 12 | 20 | 1 | 3 |
platform/ingressv1.10.0 | 1 | 6 | 5 | – | 12 |
Audit evidence, always current.
Policies map to controls, so every scan updates your score.
- CIS, Pod Security, PCI DSS, NIST and custom standards
- Policy and manual control coverage
- Per cluster, namespace or repo
- Scheduled reports by email
Ask Copilot. It knows how everything connects.
A context graph links clusters, workloads, images, policies and owners, so Copilot can answer questions across all of them.
searchResource, listNamespaces ›payments6ingress3ml-batch2monitoring1payments has the most: all 6 are in payments/api:3.8.1, run by payments-api (8 pods) and owned by team checkout. The same workload also violates disallow-privileged, mapped to PCI DSS 2.2.
Fix first: move to 3.9.0 and drop the privileged flag. Want me to draft the change?
AI agents on your platform team.
Agents take on the ongoing checks and hand back the fixes.
- Security, compliance, cost and troubleshooting agents
- On demand or on a schedule
- Read-only analysis, fixes as pull requests
- Reports to Slack, email and Copilot
Take Control Hub further.
Nirmata Assistant
Write and test Kyverno policies from your terminal or IDE.
Install nctl → Enterprise KyvernoHardened Kyverno in every cluster
Hardened, enterprise-grade Kyverno.
See Enterprise Kyverno →Bring every cluster under one set of policies.
Connect a cluster and see your compliance standing.
