Kubernetes clusters must restrict public API access
High
Cross-cloud
General
aks-no-public-access
Applies to
Microsoft.ContainerService/managedClustersAWS::EKS::Cluster
What CGPulse checks
A resource passes this rule when apiServerAccessProfile.enablePrivateCluster must equal true OR endpointPrivateAccess must equal true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Enable private API server access to restrict cluster management to the private network. See: https://learn.microsoft.com/en-us/azure/aks/private-clusters
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Cross-cloud rules
- Block storage volumes must be encrypted
- Cache service security hardening
- Cache services must enforce TLS encryption in transit
- Container registry security hardening
- Database authentication must use managed identities
- Databases must not be publicly accessible
- IAM password policy must require minimum length of 14
- Key management service security hardening