While it’s important to ensure that the entire software supply chain is properly secured, there seems to be far more security buzz around Kubernetes than any other software platform. The widespread interest in Kubernetes makes sense: K8s can be used by both small applications (even those running on a local development machine) or big apps with huge clusters containing several thousand nodes—each requiring different security controls and policies. Kubernetes is also designed to make security easier to manage, especially when compared to other platforms.

Misconfigurations in a Kubernetes cluster might not be so harmful by themselves, but with other vulnerable components in the production environment (like the libraries used in the application or a malicious container), potential attackers can build a multi-step attack vector to orchestrate a breach. To counter this, Snyk has built a cloud-native security platform capable of continuously finding and fixing vulnerabilities across proprietary code and open source software. The platform allows developers to remediate container vulnerabilities and misconfigurations across Kubernetes, Terraform and even CloudFormation.

In this webinar live hack, we demonstrate some of the key security issues that affect your OpenShift workloads and how best to avoid those pitfalls. You’ll learn about:

• How common misconfigurations in a Kubernetes workload can be exploited by attackers
• Why it’s not enough to scan containers “at rest” — runtime context is critical to understanding blast radius
• How Snyk can be integrated early in a typical Kubernetes application life cycle to find (and fix!) vulnerabilities before they are deployed to a cluster