Ensure GKE release channel is configured
Clusters should use release channels for managed version upgrades.
Security Impact
Clusters not on release channels require manual version management.
How to Remediate
Configure cluster to use Regular or Stable release channel.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your GCP environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Google Kubernetes Engine resources across your GCP projects every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS GCP v1.3.0, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- gcp-gke-12
- Service
- Google Kubernetes Engine
- Category
- Patch Management
- Severity
- MEDIUM
- CIS Benchmark
- 5.5.2
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free Trial