KubeArmor already has support for K8s orchestrated and Bare-Metal/VM workloads. With v0.6 stable release, it will also support un-orchestrated containerized workloads. KubeArmor supports both observability and policy enforcement. KubeArmor has completed a POC with LFEdge Open Horizon project.
KubeArmor already has support for K8s orchestrated and Bare-Metal/VM workloads. With the v0.6 stable release, KubeArmor will also support un-orchestrated containerized workloads. KubeArmor supports both observability and policy enforcement in this mode.
The need for supporting non-orchestrated containers?
KubeArmor recently did a POC with LFEdge Open Horizon project. Open Horizon supports using containerized workloads on the edge such that multiple applications from different vendors could be deployed on the edge node as different containers. It is imperative that the security aspects of such a multi-tenant solution needs to be taken into consideration. It is required that the security gaps in one of the container should not lead to compromises in other containers or at the host level. Container isolation and hardening has to be ensured such that the blast radius and containment of security flaws is localized.
Path to Zero Trust Edge
Discovering and enforcing least-permissive policies...
For the enforcement, KubeArmor generates AppArmor profiles for individual containers based on the policy specified. The containers are required to start with the AppArmor profiles attached (using security-opt apparmor='profile-name'). These profiles can later be dynamically updated by KubeArmor to insert, modify or remove the AppArmor enforcement. Un-orchestrated workloads have a real use case in edge devices where orchestration is hard due to resource restrictions. KubeArmor can now help protect such environment.
Introducing a lenient way to whitelisting policies
Whitelisting is a security strategy where you predefine all the entities that are to be permitted to execute and access resources. It is a fairly extreme containment measure that, if properly implemented, can prevent many security issues. KubeArmor supports whitelisting by leveraging "Allow" Action in the Policy Specification. But as mentioned it's an extreme containment measure and is fairly hard to implement. What if we want to confine what processes a particular resource can be accessed by. With v0.6 release, KubeArmor has a way to confine what processes a particular resource can be accessed by.
- dir: /run/secrets/kubernetes.io/serviceaccount/ recursive: true action: Block # Block access to service account token to everyone
- dir: /
- dir: /run/secrets/kubernetes.io/serviceaccount/ recursive: true fromSource:
- path: /bin/cat # Allow access to service account token to only cat
- dir: / recursive: true # Allow all other process execution in general
Service Account Tokens are automounted to Pods, it helps provide better access to the Kubernetes API server. But this token becomes problematic if an attacker gains access to a container via some other exploit. We can set automountServiceAccountToken: false but for Pods where Service Account Tokens are needed, the token is still exposed to all the entities available inside the pod. The above KubeArmor Policy helps restrict the access to Service Account Token to some particular binaries (in this case /bin/cat).
kArmor Probe, get support/insights for KubeArmor
If we run karmor probe when KubeArmor is not available. It does a precheck to know if KubeArmor will be supported in the environment and what KubeArmor features will be supported e.g: observability, enforcement, etc...
If KubeArmor is running in some form, karmor probe extracts insights from running KubeArmor like what all elements are being enforced and how is KubeArmor configured to run.
In v0.6, we profiled KubeArmor using pprof and did some major performance improvements such as:
- Optimizing container monitor
When Containerd is being used as the runtime, KubeAmor uses the containerd client for monitoring containers in the cluster. However, the container monitor was looking for new containers too frequently and calling a particular time consuming method. Reducing this frequency saved us a lot of CPU cycles.
- Memory usage improvements due to migration to Cilium ebpf
With the migration to Cilium eBPF we decreased KubeArmor's memory usage. Checkout BCC deprectation in favor of cilium/ebpf section for more details.
- Increasing perf buffer size
In addition to CPU and memory optimizations we have increased our perf buffer size to prevent events loss due to high events rate.
- Result We were able to reduce KubeArmor resource consumption drastically from:
to this 🚀
To discover all the improvements that we implemented please checkout this wiki article Performance improvements in v0.6
Ability to watch for system calls events
Starting from v0.6, KubeArmor introduced the ability to explicitly monitor for system calls and alert based on rules set by the user. The system calls rules matching engine offers multiple options for our users to slice and dice system calls to obtain useful information about their systems.
How can I leverage this new functionality ?
Our users can set policies to alerts for system call based on many criterion such as:
- system call name
- system call source (binary or directory)
- system call target (binary or directory)
Real life example
In this example we want to watch for file deletions via the unlink system calls that impacts any directory under /home/.
"UpdatedTime": "2022-08-31T09:02:55.841537Z", "ClusterName": "default",
"Source": "/bin/rmdir home/jane-doe/",
For more information, Please checkout our policy specification documentation.
KubeArmorPolicy specification: https://docs.kubearmor.com/kubearmor/getting-started/security_policy_specification
KubeArmorHostPolicy specification: https://docs.kubearmor.com/kubearmor/getting-started/host_security_policy_specification
Migrating to libbpf from BCC
KubeArmor uses eBPF to trace various kernel events and gain visibility on what's happening. We have been leveraging the BCC (BPF Compiler Collection) Framework to interact with the kernel through eBPF. BCC is going to great lengths to simplify BPF developer’s life, but sometimes that extra convenience gets in the way and makes it actually harder to figure out what’s wrong and how to fix it.
BCC includes Clang and LLVM with it and executes compilation from the main program at runtime causing sudden heavy resource utilisation which sometimes result crashes in our container due resource limitations. Also there was an added dependency on Kernel Headers which needed to be manually installed on the Host and made available to KubeArmor for it's working.
In this release, we have migrated off from BCC to libbpf and cilium/ebpf, decoupled compilation of eBPF Object files from main KubeArmor container to an init container. Some benefits that come with this migration include:
- No sudden outbursts of resource utilisation in the main container
- Lower Resource Utilisation
- No Dependency on Kernel Header if kernel supports BTF ( BPF Type Format ). BTF is generally available on kernel version > 5.2, for kernel's without BTF information we still require Kernel Headers.
- No CGO dependency in KubeArmor binary, making our systemd releases more portable and not dependent on certain glibc versions anymore.
- Lighter KubeArmor binary with reduced attack surface, due to removal of the llvm toolchain and BCC from the kubearmor container.
Extend KubeArmor support on OpenShift and RKE
With the v0.5 release, KubeArmor already supports cri-o. With this release we have successfully tested KubeArmor on OpenShift on RHEL 8.4 (kernel 4.18) in observability/audit mode. RHEL 8.4 is shipped with SELinux as the LSM and KubeArmor supports SELinux only for host-based policy enforcement. This work was done by Vikas Verma as part of LFX Mentorship Program.
KubeArmor now supports Rancher RKE in both observability and enforcement mode.
Note KubeArmor is currently not tested for RKE deployed on host using a Docker container.