Other Articles
- Cloud SQL – Configure Private IP
- Cloud SQL – Monitor CPU Utilization
- Cloud SQL – Enable Deletion Protection
- Cloud SQL – Enable Disk Encryption
- Cloud SQL – Enable Automated Backups
- Cloud SQL – Enable Log Export
- Cloud SQL – Enforce Password Validation
- Cloud SQL – Protect From Internet Access
- Cloud SQL – Enforce Secure Transport
- Compute Engine – Block Project-Wide SSH Keys
- Compute Engine – Disable IP Forwarding
- Compute Engine – Disable Public IP Addresses
- Compute Engine – Disable Serial Port Access
- Compute Engine – Enable Confidential Computing
- Compute Engine – Enable OS Login
- Compute Engine – Enable Shielded VM
- Compute Engine – Restrict Default Service Account
- General – Deny Public Access to KMS Keys
- General – Enforce Duties Separation
- General – Enforce KMS Key Rotation
- General – Restrict Admin Roles on Service Accounts
- Cloud Run – Configure Timeout Settings
- Cloud Storage – Enable Bucket Encryption
- Cloud Storage – Enable Bucket Logging
- Cloud Storage – Enable Bucket Versioning
- Cloud Storage – Enforce Uniform Bucket-Level Access
- Cloud Storage – Restrict Public Access
- IAM Users – Enforce GCP-Managed Keys
- IAM Users – Rotate External User-Managed Service Account Keys
- GKE – Enable Private Nodes
- GKE – Restrict Control Plane Access
- GKE – Enable Workload Identity
- GKE – Enable Network Policy
- GKE – Enable Shielded Nodes
- GKE – Enable Node Auto-Upgrade and Auto-Repair
- GKE Cluster – Enable Cluster Logging
- General – Enable Cloud Audit Logs
- General – Configure a Log Sink
- General – Configure Log Bucket Retention
- Cloud SQL – Enable High Availability
- Cloud SQL – Configure Maintenance Window
- Cloud Storage – Configure Bucket Retention or Lifecycle
- General – Enable Security Command Center
- Compute Engine – Enable Instance Deletion Protection
- VPC Firewall – Restrict Public SSH and RDP Access
- VPC Firewall – Restrict Public Database Access
- VPC Network – Avoid the Default Network
- VPC Network – Enable Subnet Flow Logs
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
-
Log in to the Google Cloud Console and navigate to
Kubernetes Engine > Clusters.
- Select the affected GKE cluster.
- Open the cluster configuration and click Edit. Locate the Legacy Authorization setting.
-
Set Legacy Authorization to
Disabled.
- 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
-
Open the Google Cloud Console and launch
Cloud Shell.
-
List the GKE clusters that have legacy ABAC enabled:
gcloud container clusters list \ --filter="legacyAbac.enabled=true" \ --format="table(name,location)"
-
Disable legacy ABAC on the cluster:
gcloud container clusters update <CLUSTER_NAME> \ --location <LOCATION> \ --no-enable-legacy-authorization
-
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 orFalse. 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