A Kubernetes cluster presents multiple potential attack surfaces: the cluster itself, a node running on the cluster, a pod running in the node, a container running in a pod. If you are managing your own Kubernetes cluster, you need to be aware of the security settings on your etcd, your API server, and your container build pipeline.

Many of the security risks of a Kubernetes cluster can be avoided by using the default settings of Kubernetes, or by using a managed Kubernetes service from a cloud provider or an infrastructure company. But it is useful to know about the fundamentals of operating a secure cluster, so that you can hopefully avoid falling victim to the most common vulnerabilities.

Liz Rice wrote the book Kubernetes Security with co-author Michael Hausenblas. Liz works at Aqua Security, a company that develops security tools for containerized applications. In today’s show, Liz gives an overview of the security risks of a Kubernetes cluster, and provides some best practices including secret management, penetration testing, and container lifecycle management.

Show Notes

• Kubernetes Security by Michael Hausenblas, Liz Rice – O’Reilly Media
• Open Source Security Podcast – Talking about Kubernetes and container security with Liz Rice
• Keynote: Running with Scissors – Liz Rice, Technology Evangelist, Aqua Security

The post Kubernetes Security with Liz Rice appeared first on Software Engineering Daily.