AKS cluster should have network policy configured
High
Azure
General
aks-network-policy
Applies to
Microsoft.ContainerService/managedClusters
What CGPulse checks
A resource passes this rule when networkProfile.networkPolicy must be set. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure a network policy plugin to restrict pod-to-pod communication and reduce lateral movement risk. Set network policy (Azure or Calico) at cluster creation time. See: https://learn.microsoft.com/en-us/azure/aks/use-network-policies
CLI
az aks show --ids "{id}" --query "networkProfile.networkPolicy" -o tsvBicep
// Note: Network policy cannot be added to an existing cluster. Recreate with networkPolicy enabledTerraform
resource "azurerm_kubernetes_cluster" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
location = var.location
dns_prefix = "{name}"
network_profile {
network_plugin = "azure"
network_policy = "azure"
}
default_node_pool {
name = "default"
node_count = 1
vm_size = "Standard_D2s_v5"
}
identity { type = "SystemAssigned" }
}
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 Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes