/
Role-Based Access Control Should Be Used on Kubernetes Services

Role-Based Access Control Should Be Used on Kubernetes Services

Description:

To provide granular filtering on the actions that users can perform, use Role-Based Access Control (RBAC) to manage permissions in Kubernetes Service Clusters and configure relevant authorization policies. 

Solution/Reference: 

To Use Role-Based Access Control (RBAC) you must recreate your Kubernetes Service cluster and enable RBAC during the creation process. Creating a Kubernetes Service with RBAC enabled can be done via the portal as follows:
1. Go to Azure Kubernetes Services.
2. Select 'Add' and enter your cluster's configuration.
3. In the 'Authentication' tab, verify that the 'Enable RBAC' setting is set to 'Yes'.



For more information, see Azure role-based access control.

Related content

Pod Security Policies Should be Defined on Kubernetes Services (Deprecated)
Pod Security Policies Should be Defined on Kubernetes Services (Deprecated)
More like this
Ensure Legacy Authorization is set to Disabled on Kubernetes Engine Clusters
Ensure Legacy Authorization is set to Disabled on Kubernetes Engine Clusters
More like this
Azure Policy Add-on for Kubernetes Should be Installed and Enabled on Your Clusters
Azure Policy Add-on for Kubernetes Should be Installed and Enabled on Your Clusters
More like this
Kubernetes API Server Should Be Configured With Restricted Access
Kubernetes API Server Should Be Configured With Restricted Access
More like this
Privileged Containers Should be Avoided
Privileged Containers Should be Avoided
More like this
Container With Privilege Escalation Should Be Avoided
Container With Privilege Escalation Should Be Avoided
More like this