Deepfence ThreatMapper vs Kyverno

Deepfence ThreatMapper is a self-hosted security tool that discovers production workloads and ranks threats by exploit risk. It maps pods, containers, applications, and infrastructure, then generates runtime software bills of materials for running workloads and operating systems and checks them against multiple vulnerability feeds. It also detects exposed keys, tokens, and passwords in containers and host filesystems, and evaluates infrastructure settings against CIS, PCI-DSS, HIPAA, and other benchmarks. The Threat Graph links vulnerability, secret, and compliance findings with network flows, security groups, and live status. Its management console runs in containers on a Docker host or dedicated Kubernetes cluster, providing HTTPS administration and API automation. One console can manage different workload types across on-premise and cloud deployments. Documented integrations include Slack, PagerDuty, Jira, Splunk, ELK, Sumo Logic, and AWS S3; image-build scanning supports CircleCI, Jenkins, and GitLab. The project is free under the Apache 2 license. Windows Server support is experimental and not suitable for production use.

Kyverno is a free, open-source policy engine for defining and enforcing policy as code in Kubernetes. Its stable policy types can validate, mutate, generate or delete resources, and verify container image signatures and attestations. The Kyverno CLI can test policies against Kubernetes resource manifests in CI before they are applied to a live cluster. Documentation describes use with Helm, YAML manifests, GitHub Actions and GitOps tools such as ArgoCD. Kyverno is installed in a Kubernetes cluster; Helm is recommended for production, and YAML manifests are also available. A standard installation requires an admission controller, while background, reports and cleanup controllers are optional. Production installations should use high availability mode. The project supports CEL-based policy types and describes applying Kubernetes-style policies outside Kubernetes as part of its mission. Its webhooks default to fail-closed, so matching requests can fail if the API server cannot reach Kyverno. The project documents Cosign signatures for images and manifests, and lists CLI binaries for Linux, macOS and Windows.