Ross ROSS = Recommend OSS · open-source software intelligence for agents

kubearmor/KubeArmor

Runtime Security Enforcement System. Workload hardening/sandboxing and implementing least-permissive policies made easy leveraging LSMs (LSM-BPF, AppArmor). observed · 2026-08-28

github.com/kubearmor/KubeArmor · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

97/100

  • Activity 99
  • Release rhythm 93
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 10
  • age_days: 2107
  • days_rel: 51
  • days_push: 7
  • n_releases_24m: 40

Full methodology

Adoption not part of the score

2588 stars · 522 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

KubeArmor is a cloud-native runtime security enforcement system that restricts process execution, file access, and networking behavior of pods, containers, and nodes at the system level. It leverages Linux Security Modules (AppArmor, SELinux, BPF-LSM) to enforce user-specified policies and uses eBPF to generate rich alerts and telemetry events with container, pod, and namespace identities.

Use cases

  • enforce least-permissive process and network whitelisting for kubernetes pods
  • harden container workloads against MITRE, STIG, and CIS based attack techniques
  • sandbox pods and containers without modifying pod specs or host configuration
  • monitor and audit process executions, file accesses, and network connections in containers
  • protect sensitive assets like cert bundles and raw database tables from unauthorized access
  • profile system calls and application behavior for security visibility
  • enforce runtime security policies on VMs and bare-metal hosts via systemd mode

When to choose

  • you need inline, proactive runtime enforcement rather than post-attack detection
  • you run Kubernetes across clouds with inconsistent default LSMs and want a unified policy layer
  • you want to apply least-permissive access controls to containers without changing application code

When to avoid

  • you only need static image scanning or CI/CD vulnerability checks rather than runtime enforcement
  • your hosts or kernels lack support for AppArmor, SELinux, or BPF-LSM
  • you need runtime security for non-Linux platforms such as Windows or macOS

Facets

service · maturity active

security monitoring alerting container-runtime middleware security cloud-computing monitoring self-hosted go self-hosted runtime-security lsm apparmor ebpf bpf-lsm selinux workload-hardening sandboxing least-permissive cncf daemonset policy-enforcement containers devops linux kubernetes docker

4 sources

Member repositories

RepositoryRoleHealth v2
kubearmor/KubeArmormain97

For agents

markdown · JSON · MCP: product_card(name="kubearmor/KubeArmor")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem