Balance innovation and agility with security and compliance
risks using a 3-step process across all cloud infrastructure.
Step up business agility without compromising
security or compliance
Everything you need to become a Kubernetes expert.
Always for free!
Everything you need to know about Magalix
culture and much more
Identifying workload consistency across your cluster can be a never ending process. Multiply that process by the number of clusters you need to support, and you can guarantee you’ll be chasing your own tail in perpetuity. By default, Magalix KubeAdvisor ships with a governance policy that detects when your workloads are running with privileged mode enabled across one, or all of your cluster.
When logging into the Magalix console, find your cluster and drill down to Issues using the navigation bar on the left.
You’ll be brought to your Issues Dashboard. WIth all of our Issues, donut graphs highlight the total number of violations against the total number of governance policies, or Advisors. Locate Container running in Privileged Mode.
If you click on the issue, you can see an overview of how many entities are out of compliance along with a description of the Advisor.
Just like our Issues page, you will see graphs above totaling all the violations related to this advisor. Below, you’ll see each individual violation. After clicking on a violation, you can see the full breakdown in our Recommendation page.
In every policy, we give a brief explanation of our policy.
As a part of the violation, Magalix KubeAdvisor shows you your entity in YAML format. You can identify exactly where the problem is. In this case, search for privileged: true in your securityContext.
This area provides suggestions on how you can resolve the violation.
At the bottom, we also show you how long this entity has been in violation, giving you some insight into whether or not any new issues are a result of this violation.
Containers running in privilege mode are essentially the same as providing root access to the node. Unless you have a specific use case, most pods and containers don’t require privileged access to your Kubernetes nodes. Allowing this setting leaves you at risk for potential exploitation. This is why we enable this Advisor by default.
Prevent Kubernetes NetworkPolicy misconfigurations by enforcing policy as code