/
Kubernetes API Server Should Be Configured With Restricted Access

Kubernetes API Server Should Be Configured With Restricted Access

Description:

To ensure that only applications from allowed networks, machines, or subnets can access your cluster, restrict access to your Kubernetes API server. You can restrict access by defining authorized IP ranges, or by setting up your API servers as private clusters as explained in https://docs.microsoft.com/azure/aks/private-clusters

Solution/Reference: 

To manually configure authorized IP ranges, follow the steps in Secure access to the API server using authorized IP address ranges in Azure Kubernetes Service (AKS). If your existing cluster uses a Basic SKU Load Balancer, you'll need to redeploy or migrate to a new AKS cluster using the Standard SKU Load Balancer as explained in Moving from a basic SKU load balancer to standard SKU. If you decide not to redeploy, and you want to move these clusters to the 'not applicable' tab, follow the steps inCreate an exemption rule

Related content

Pod Security Policies Should be Defined on Kubernetes Services (Deprecated)
Pod Security Policies Should be Defined on Kubernetes Services (Deprecated)
More like this
Kubernetes Clusters Should Be Accessible Only Over HTTPS
Kubernetes Clusters Should Be Accessible Only Over HTTPS
More like this
Role-Based Access Control Should Be Used on Kubernetes Services
Role-Based Access Control Should Be Used on Kubernetes Services
More like this
Ensure Master authorized networks is set to Enabled on Kubernetes Engine Clusters
Ensure Master authorized networks is set to Enabled on Kubernetes Engine Clusters
More like this
Services Should Listen on Allowed Ports Only
Services Should Listen on Allowed Ports Only
More like this
Usage of Host Networking and Ports Should be Restricted
Usage of Host Networking and Ports Should be Restricted
More like this