According to research done by ARMO, 100% of Kubernetes clusters that were tested contained at least one misconfiguration, while 65% had at least one high-severity misconfiguration. 50% of clusters had 14 or more failed security controls. According to Redhat research from 2023, 45% of respondents experienced security incidents or issues related to containers and/or Kubernetes due to misconfigurations.

Three security issues were reported on October 27th by the Kubernetes security community, all of them related to the popular NGINX ingress component.

In today’s world of limited time, we need to be laser-focused on our priorities. This goes double for mission-critical activities, like cybersecurity. We want to prioritize fixing the issues that have the most significant impact on our security posture. An attack path is like a roadmap for attackers, outlining the steps they can take to exploit security weaknesses.

Kubernetes is an open-source platform for governing clusters of containerized application services. Kubernetes automates the vital aspects of container lifecycle management, including scaling, replication, monitoring, and scheduling. The central component of Kubernetes is a cluster, which is itself made up of multiple physical or virtual machines.

Kubernetes is a container orchestration tool that helps with the deployment and management of containers. Within Kubernetes, a container runs logically in a pod, which can be represented as one instance of a running service. Pods are ephemeral and not self-healing, which makes them fragile. They can go down when an interruption occurs on the server, during a brief network problem, or due to a minimal memory issue—and it can bring down your entire application with it.

I had always wanted to use sidecars with Istio or Splunk forwarder in production, but as a Kubernetes maintainer, I knew there was no reliable way of telling Kubernetes to ensure sidecar containers were kept running before and after the main application. In this post I will share the twists and turns of my adventure in addressing this long-standing Kubernetes challenge.

We are excited to announce the preview release of Kubescape 3.0, the next generation of the CNCF Kubernetes security posture management tool. Kubescape 3.0 will add: Most of these features have landed already, with some being finished over the next few weeks. Get ARMO Platform.

Guest post originally published on Kubescape’s blog by Ben Hirschberg. Co-Founder and CTO at ARMO and a Kubescape maintainer. What do you get a piece of software for its second birthday? A brand new blog, of course! And cake. More on the cake later. Kubescape is an open-source Kubernetes security platform that helps you identify and fix security risks, misconfigurations and vulnerabilities in your Kubernetes clusters.

Prioritizing the security of your Kubernetes environment is of utmost importance. As organizations increasingly rely on containerization for their applications, the need for robust security measures is ever-growing. But security doesn’t work in isolation; it should seamlessly blend into your workflow. This is where the integration of ARMO Platform with collaboration tools like Microsoft Teams becomes invaluable.

Recently, the Kubernetes Security Response Committee disclosed three interrelated vulnerabilities affecting the Windows versions of Kubelet and the Kubernetes CSI proxy. These vulnerabilities pose a significant risk, allowing even users with limited permissions to escalate their privileges to administrator level on affected nodes.