How to Use Security As Code to Protect Egress (External) Connections in Kubernetes

Security as Code is one of the hottest topics in containers. It’s a natural follow on to infrastructure as code. It can be used to define run-time policies for Kubernetes deployments. Monitoring and preventing egress, or external connections, is critical for preventing data breaches and attacks. Creating security policy as code to allow or deny egress should be as simple, powerful and automated as possible. In this session, we will discuss several ways of enforcing egress control using open source tools such as Kubernetes Network Policy and OpenShift as well as NeuVector.