Skip to main content

๐Ÿ›ก๏ธ Google GKE Cluster Control Plane Authorized Networks are disabled๐ŸŸข

  • Contextual name: ๐Ÿ›ก๏ธ Cluster Control Plane Authorized Networks are disabled๐ŸŸข
  • ID: /ce/ca/google/gke/cluster-authorized-networks
  • Tags:
  • Policy Type: COMPLIANCE_POLICY
  • Policy Categories: SECURITY

Logicโ€‹

Descriptionโ€‹

Open File

Descriptionโ€‹

This policy identifies Google GKE Clusters where Control Plane Authorized Networks are not enabled. Enabling this feature restricts access to the clusterโ€™s control plane to a defined allowlist of trusted IP addresses.

Rationaleโ€‹

Control Plane Authorized Networks improve cluster security by limiting which IP addresses can access the Kubernetes API server.

Key benefits include:

  • Restricts external, non-GCP access to a specified set of IP addresses (e.g., corporate office ranges), reducing exposure in the event of a vulnerability in authentication or authorization mechanisms.
  • Helps mitigate risks from leaked master certificates by ensuring they cannot be used from unauthorized IP ranges.
  • Allows administrators to enforce strict access policies while still permitting trusted GCP traffic (e.g., Compute Engine VMs).

Impactโ€‹

When implementing Control Plane Authorized Networks, ensure all required networks are included in the allowlist, otherwise legitimate external access to the clusterโ€™s control plane may be inadvertently blocked.

... see more

Remediationโ€‹

Open File

Remediationโ€‹

Enable Control Plane Authorized Networksโ€‹

Using gcloud CLIโ€‹

To enable Control Plane Authorized Networks for an existing cluster, run the following command:

```sh
gcloud container clusters update <cluster_name> \
--location {{location}} \
--enable-master-authorized-networks
```

You can also specify the allowed IP ranges using the --master-authorized-networks flag. This flag accepts a comma-separated list of CIDR blocks (up to 100 for private clusters, 50 for public clusters).

These authorized networks define the IP addresses permitted to access your clusterโ€™s control plane via HTTPS.

policy.yamlโ€‹

Open File

Linked Framework Sectionsโ€‹

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
๐Ÿ’ผ CIS GKE v1.8.0 โ†’ ๐Ÿ’ผ 5.6.3 Ensure Control Plane Authorized Networks is Enabled (Automated)1no data
๐Ÿ’ผ Cloudaware Framework โ†’ ๐Ÿ’ผ Secure Access57no data
๐Ÿ’ผ PCI DSS v3.2.1 โ†’ ๐Ÿ’ผ 1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment, and specifically deny all other traffic.1056no data
๐Ÿ’ผ PCI DSS v3.2.1 โ†’ ๐Ÿ’ผ 1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.620no data
๐Ÿ’ผ PCI DSS v3.2.1 โ†’ ๐Ÿ’ผ 1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.20no data
๐Ÿ’ผ PCI DSS v3.2.1 โ†’ ๐Ÿ’ผ 1.3.5 Permit only โ€œestablishedโ€ connections into the network.20no data
๐Ÿ’ผ PCI DSS v4.0.1 โ†’ ๐Ÿ’ผ 1.3.1 Inbound traffic to the CDE is restricted.56no data
๐Ÿ’ผ PCI DSS v4.0.1 โ†’ ๐Ÿ’ผ 1.3.2 Outbound traffic from the CDE is restricted.56no data
๐Ÿ’ผ PCI DSS v4.0.1 โ†’ ๐Ÿ’ผ 1.4.2 Inbound traffic from untrusted networks to trusted networks is restricted.20no data
๐Ÿ’ผ PCI DSS v4.0 โ†’ ๐Ÿ’ผ 1.3.1 Inbound traffic to the CDE is restricted.756no data
๐Ÿ’ผ PCI DSS v4.0 โ†’ ๐Ÿ’ผ 1.3.2 Outbound traffic from the CDE is restricted.56no data
๐Ÿ’ผ PCI DSS v4.0 โ†’ ๐Ÿ’ผ 1.4.2 Inbound traffic from untrusted networks to trusted networks is restricted.720no data