The race to secure Kubernetes at run time

For software developers who primarily build their applications as a set of microservices deployed using containers and orchestrated with Kubernetes, a whole new set of security considerations has emerged beyond the build phase.

Unlike hardening a cluster, defending at run time in containerized environments has to be dynamic: constantly scanning for unexpected behaviors within a container after it goes into production, such as connecting to an unexpected resource or creating a new network socket.

To read this article in full, please click here