Kubernetes network policies 101: Shifting network security left

Containers and Kubernetes pose a unique set of network security challenges. Container-to-container (or pod-to-pod) communication was allowed by design to keep things simple. However, if a container is breached, the ability for a malicious actor to move laterally within the environment is directly related to how broadly that container can communicate with other containers. By default this includes each and every container across the cluster, including sensitive control plane containers. Kubernetes introduced network policies to provide the much needed control, but operationalizing this mechanism is not a trivial task. Not only is the technology itself hard, it is also unclear who in the organization owns this, and how it should fit with existing GitOps processes. Tune in where we discuss how to address the challenges of securing network communication using automation to establish an effective GitOps process.