Skip to main content
Compliance · Critical severity

GKE Control Plane Master Authorized Networks Disabled

The cluster's API server accepts connections from any address, so a leaked credential can be used from anywhere in the world.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

Google Cloudprovider
Criticalseverity
Compliancewhere it shows up
Manualfix, steps written out

Google CloudKubernetes

Found, explained, handed over.

Where the estate departs from your policies, frameworks and tagging rules.

01

Detect

ZopNight checks this automatically across Google Cloud, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Enable master authorized networks on GKE cluster.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
GKE Clusters on Google Cloud
The fix, by hand
  1. Confirm the control-plane endpoint is currently unrestricted: gcloud container clusters describe ‹name› --location=‹loc› --format='value(masterAuthorizedNetworksConfig.enabled)'.
  2. Enable Master Authorized Networks and restrict access to your known admin / CI CIDR blocks: gcloud container clusters update ‹name› --location=‹loc› --enable-master-authorized-networks --master-authorized-networks=‹CIDR1›,‹CIDR2›.
  3. Consider making the control-plane endpoint private as well: add --enable-private-endpoint (requires a private cluster).
  4. Verify access still works from an allowed network: gcloud container clusters get-credentials ‹name› --location=‹loc› then kubectl get nodes.
  5. Audit the control-plane / API-server access logs for unexpected source IPs before and after the change.

These are the steps the finding carries in the product.

Category
Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
Where it appears
The Compliance tab of Recommendations, with every affected resource listed.
Rule ID
RC-1223
Full reference

GKE Control Plane Master Authorized Networks Disabled

Related checks

Cluster Network Policy Not EnforcedAWS, Google CloudGKE Cluster Logging DisabledGoogle CloudGKE Cluster Monitoring DisabledGoogle CloudGKE Cluster Not PrivateGoogle CloudGKE Cluster Alias IPs Not EnabledGoogle CloudGKE Node Auto-Upgrade Not ConfiguredGoogle Cloud

See the compliance findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Start freeExplore the playground

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·