Kubernetes security: 4 tips to manage risks
As you bear down on Kubernetes security, use these strategies to avoid missteps in work with containers and orchestration
As Kubernetes’ popularity grows with IT teams, so does its allure to bad actors. That’s just the way of things in technology: More users, larger target.
Don’t expect this to do much to stem enterprise enthusiasm for Kubernetes, though. Its appeal outweighs the risks. There are some key areas for IT teams to proactively focus on when it comes to Kubernetes security, as we recently covered. There’s also plenty of good news on the security front, in the form of expert, from-the-trenches advice on how to unlock Kubernetes’ potential in a secure manner.
Here are four ways to ensure your move to containers and orchestration, and your ongoing work with them, avoids security missteps…
Chris Roberts, an adviser at Attivo Networks, concurs that role-based access control (RBAC) must be enabled for robust Kubernetes security, and adds that many elements of a strong security posture remain relevant in container environments: Good policies, procedures, and controls at the user, application, and network layer; separate and segmentation (including firewalls) where possible; rotating encryption keys; and strong education and integrations among different roles and teams.
Roberts also notes the strength of Linux’s native security controls: “Use them whenever possible,” he says.
Finally, Roberts points to a container-specific element of privilege: Root in containers.
“Containers don’t all have to be root,” Roberts says. “If they don’t need it, don’t give it.”