Deepfence ThreatMapper vs KubeArmor
Deepfence ThreatMapper
threatmapper.orgKubeArmor
kubearmor.ioSide by side
| Figure | Deepfence ThreatMapper | KubeArmor |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Container Security Software | 8.3 (#7) | 8.6 (#4) |
| Integrations | Documented integrations include Slack, PagerDuty, Jira, Splunk, ELK, Sumo Logic and AWS S3. | Project repositories include OpenTelemetry, Prometheus, Kafka, Grafana, ELK dashboards, a GitHub Action, and a Rancher UI extension. |
| Purpose | ThreatMapper hunts for hidden threats in production platforms and ranks them by risk of exploit. | KubeArmor is an open-source, cloud-native runtime security system that hardens workloads and enforces security policies. |
Plans
In their own words
Deepfence ThreatMapper
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.
KubeArmor
KubeArmor is an open-source runtime security system for enforcing policies on cloud-native workloads. It uses Linux Security Modules such as AppArmor, SELinux, and BPF-LSM, with eBPF for alerts, telemetry, and container-process tracking. Policies can restrict process execution, file access, networking operations, and resource use. Container policies support Allow, Audit, and Block actions, with Block as the default; system-call monitoring is audit-only. Kubernetes policies can target pods through labels and label expressions, and rules can match paths, network protocols, capabilities, and system calls. The deployment matrix covers Kubernetes, non-Kubernetes containers, virtual machines, and bare-metal hosts. It lists Kubernetes environments including GKE, AKS, OKE, IKS, EKS, OpenShift, Rancher, and DigitalOcean Kubernetes, but support varies by operating system, architecture, and enforcement mode. Some environments are observability-only, and VMware Tanzu entries are under construction. KubeArmor is a community-governed CNCF Sandbox project. The free plan is free; installation guidance uses Helm and kubectl.