Ensure GKE cluster uses private endpoint
GKE control plane should use private endpoint to restrict API access.
Security Impact
Public endpoints expose the Kubernetes API to the internet.
How to Remediate
Enable private endpoint for the cluster. Configure authorized networks.
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, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- gcp-gke-2
- Service
- Google Kubernetes Engine
- Category
- Network Security
- Severity
- HIGH
- CIS Benchmark
- 5.6.4
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free Trial