Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/Other Security Considerations/104 of 115

8.7Enable role-based access control (RBAC) within Azure Kubernetes Services

Control family: Other Security Considerations

Control description

Ensure that RBAC is enabled on all Azure Kubernetes Services Instances

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Kubernetes role-based access control limits what each user and workload can do inside an AKS cluster. Without it, anyone who can reach the API has full control. It is on by default for new clusters and can't be switched on later, so clusters without it are rebuilt.

Before you start

The same on every cloud, before the steps in the tabs.

  • Agree how people get access to AKS clusters (Microsoft Entra groups mapped to Kubernetes roles) and who approves cluster-admin access.

Evidence

  • The cluster access standard

On Azure the tasks check each AKS cluster's authentication settings, rebuild any without Kubernetes RBAC, and keep it checked with the CIS standard.

Task 1Check each cluster uses Kubernetes RBAC

  1. Sign in to the Azure portal at portal.azure.com and open Kubernetes services, then a cluster.
  2. Select Settings > Security configuration (or Cluster configuration).
  3. Under Authentication and Authorization, confirm it shows Kubernetes RBAC, ideally with Microsoft Entra ID authentication (or Azure RBAC).
  4. For a cluster without it, create a replacement cluster with Kubernetes RBAC and move the workloads, then delete the old one.
  5. Check it: every cluster shows Kubernetes RBAC on.

Task 2Keep it checked with the CIS v1.4.0 standard in Defender for Cloud

  1. Open Microsoft Defender for Cloud > Regulatory compliance and select Manage compliance policies.
  2. Select the subscription, select Security policies, find CIS Microsoft Azure Foundations Benchmark v1.4.0 and toggle its status to On (once per subscription).
  3. Back on Regulatory compliance, open the CIS Microsoft Azure Foundations Benchmark v1.4.0 standard and expand recommendation 8.7.
  4. Open the assessment for Role-Based Access Control (RBAC) should be used on Kubernetes Services and fix the resources it lists as non-compliant.
  5. Check it: every resource under recommendation 8.7 shows as passing after the next evaluation.

Evidence

  • The Authentication and Authorization setting of each AKS cluster
  • The CIS v1.4.0 standard, with recommendation 8.7 passing

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.