Many companies struggle with security when adopting Kubernetes. Because Kubernetes and containers present a new approach for deploying applications, operations and security teams question whether the applications and data will be secure when they adopt microservices, containers, and Kubernetes to develop and deploy applications. Many traditional security tools and processes no longer apply, while containers create new security blind spots and new attack surfaces, making visibility across containers and clusters an additional challenge. Similarly, developers must take responsibility for some of the new security challenges, a role they’re unaccustomed to and reluctant to embrace.
Get this whitepaper to learn some of the five things:
Granting access to the host node
Assuming operations is aligned with security
Running containers with known vulnerabilities
Expecting security by default using native controls
Moving to production before you are ready
