Other Articles

GKE – Disable Legacy ABAC

Secure Configuration Checks > GCP

This check ensures that Google Kubernetes Engine (GKE) clusters do not use legacy attribute-based access control (ABAC). Legacy ABAC grants permissions through a broad, predefined authorization policy. Kubernetes role-based access control (RBAC) should be used instead, allowing administrators to define specific permissions for users, groups, and service accounts.

Check Details

  • Resource: GKE Cluster
  • Check: Disable legacy ABAC
  • Risk: If legacy ABAC is enabled, identities authenticated to the Kubernetes API can receive broad permissions through the legacy authorization policy. This can allow compromised users or workloads to access or modify Kubernetes resources beyond their intended permissions.

Remediation via Google Cloud Console

  1. Log in to the Google Cloud Console and navigate to Kubernetes Engine > Clusters. GKE Clusters
  2. Select the affected GKE cluster.
  3. Open the cluster configuration and click Edit. Locate the Legacy Authorization setting.
  4. Set Legacy Authorization to Disabled. GKE Disable Legacy Authorization
  5. Click Save changes to apply the configuration.

Note: Legacy ABAC is disabled by default on new GKE clusters and cannot be enabled on Autopilot clusters. If the setting is already disabled, no changes are required.

Remediation via Google Cloud CLI

  1. Open the Google Cloud Console and launch Cloud Shell. GCP Cloud Shell
  2. List the GKE clusters that have legacy ABAC enabled:

    gcloud container clusters list \
    --filter="legacyAbac.enabled=true" \
    --format="table(name,location)"
    
  3. Disable legacy ABAC on the cluster:

    gcloud container clusters update <CLUSTER_NAME> \
    --location <LOCATION> \
    --no-enable-legacy-authorization
    
  4. Verify the setting:

    gcloud container clusters describe <CLUSTER_NAME> \
    --location <LOCATION> \
    --format=json | jq '.legacyAbac.enabled // false'
    

    Replace <CLUSTER_NAME> with the name of your GKE cluster and <LOCATION> with its region or zone. The command must return nothing or False. Once legacy ABAC is off, permissions come only from Kubernetes RBAC. Make sure that users, service accounts and applications that need access already have the right RBAC roles, and test them before you change a production cluster. The update also restarts the control plane, so the Kubernetes API can be briefly unavailable, especially on zonal clusters.

Default Value

Legacy ABAC is disabled by default on all new GKE clusters. It can be enabled on eligible Standard clusters, but cannot be enabled on Autopilot clusters. Google recommends keeping legacy ABAC disabled and using IAM and Kubernetes RBAC for access control.

Updated on 09 November, 2026