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 Shielded Nodes
- GKE – Enable Node Auto-Upgrade and Auto-Repair
- 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 Cluster – Enable Cluster Logging
Secure Configuration Checks > GCP
This check ensures that GKE clusters send system component, workload and API server logs to Cloud Logging. These logs show what runs in the cluster and who changes it.
Check Details
- Resource: GKE Cluster
- Check: Enable cluster logging
- Risk: Without these logs, attacks and faults can go unseen. There is also no record to use in an investigation.
Remediation via Google Cloud Console
-
Log in to the Google Cloud Console and navigate to
Kubernetes Engine > Clusters.
- Click the affected GKE cluster.
-
Open the Details tab and locate the
Features section. Find Logging
and click Edit Logging.
-
Under Components, select:
- System
- Workloads
- API server
- Click OK and then click Save Changes to apply the configuration.
Note: System logging is required for GKE log collection. Workload and API server logging are optional components that you can enable according to your monitoring requirements. Enabling or changing control-plane component logging restarts the control plane. During this restart, zonal Standard clusters can become temporarily unavailable; regional and Autopilot control planes remain available.
Remediation via Google Cloud CLI
-
Open the Google Cloud Console and launch
Cloud Shell.
-
Update the cluster to send system, workload and API server logs to Cloud Logging:
gcloud container clusters update <CLUSTER_NAME> \ --location <LOCATION> \ --logging=SYSTEM,WORKLOAD,API_SERVER
Replace
<CLUSTER_NAME>with your cluster name and<LOCATION>with its zone or region. The Cloud Logging API must be enabled in the project. -
Verify the logging components:
gcloud container clusters describe <CLUSTER_NAME> \ --location <LOCATION> \ --format="value(loggingConfig.componentConfig.enableComponents)"
Default Value
By default, new GKE clusters send system and workload logs to Cloud Logging. API server logs are not collected unless you add them.
Updated on 09 November, 2026