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 – Disable Legacy ABAC
- GKE – Enable Network Policy
- 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 – Enable Shielded Nodes
Secure Configuration Checks > GCP
This check ensures that the nodes of a Google Kubernetes Engine (GKE) cluster are Shielded GKE nodes with verified boot integrity. Shielded nodes check that a node starts from a trusted state and that nobody has tampered with its boot process. Autopilot clusters enforce this setting.
Check Details
- Resource: GKE Cluster
- Check: Enable shielded nodes
- Risk: Without Shielded GKE Nodes, an attacker who obtains node bootstrap credentials may be able to impersonate a node and gain unauthorized access to cluster resources, including sensitive secrets. Shielded GKE Nodes help prevent this by verifying node identity before the control plane accepts a node.
Remediation via Google Cloud Console
-
Log in to the Google Cloud Console and navigate to
Kubernetes Engine > Clusters.
- Click the affected GKE cluster.
- Under the Security section, locate Shielded GKE Nodes and click the Edit icon.
-
Select Enable Shielded GKE Nodes and click
Save Changes.
- Wait for the cluster update to complete. GKE recreates the worker nodes as Shielded VMs using a rolling update.
Additional recommendation: Google recommends enabling Secure Boot for all Standard cluster node pools and keeping Integrity Monitoring enabled. These are separate node-pool settings. Secure Boot should be tested with your workloads because it can prevent unsigned kernel modules from loading on Ubuntu nodes.
Remediation via Google Cloud CLI
-
Open the Google Cloud Console and launch
Cloud Shell.
-
List the GKE clusters that do not have shielded nodes enabled:
gcloud container clusters list \ --filter="NOT shieldedNodes.enabled=true" \ --format="table(name,location)"
-
Enable shielded nodes on the cluster:
gcloud container clusters update <CLUSTER_NAME> \ --location <LOCATION> \ --enable-shielded-nodes
-
Turn on integrity monitoring for each existing node pool:
gcloud container node-pools update <NODE_POOL_NAME> \ --cluster <CLUSTER_NAME> \ --location <LOCATION> \ --shielded-integrity-monitoring
-
Verify the settings:
gcloud container clusters describe <CLUSTER_NAME> \ --location <LOCATION> \ --format="value(shieldedNodes.enabled)" gcloud container node-pools describe <NODE_POOL_NAME> \ --cluster <CLUSTER_NAME> \ --location <LOCATION> \ --format="yaml(config.shieldedInstanceConfig)"
Replace
<CLUSTER_NAME>with the name of your GKE cluster,<LOCATION>with its region or zone, and<NODE_POOL_NAME>with the name of the node pool. The first command must returnTrue, and the second must showenableIntegrityMonitoring: true. Updating the nodes recreates them in a rolling update, so test your applications before you change a production cluster. You can also add--shielded-secure-bootto the node pool command. Secure Boot blocks unsigned kernel modules, so test any workload that loads custom modules first.
Default Value
Shielded GKE nodes are enabled by default on new clusters. Older Standard clusters can have them turned off. Autopilot clusters always use shielded nodes.
Updated on 09 November, 2026