Skip to main content
Compliance · High severity

AKS Cluster Network Policy Not Enabled

Every pod can reach every other pod, so one compromised container has a clear path to the rest of the cluster.

Sign inExplore the playground

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

Azureprovider
Highseverity
Compliancewhere it shows up
Manualfix, steps written out

AzureKubernetes

Found, explained, handed over.

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

01

Detect

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

02

Explain

Every finding says exactly what to change: Recreate AKS cluster with a network policy.

03

Fix

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

Applies to
AKS Clusters on Azure
The fix, by hand
  1. Network policy cannot be enabled on an existing AKS cluster. Plan a blue/green migration.
  2. Create a new AKS cluster with --network-dataplane cilium (Azure CNI Powered by Cilium; Microsoft's recommended option, native NetworkPolicy support) or --network-policy azure. Calico is in maintenance mode for new clusters.
  3. Re-import existing ingress + DNS configuration into the new cluster.
  4. Author Kubernetes NetworkPolicy manifests starting with default-deny per namespace, then allowlist required traffic.
  5. Migrate workloads namespace-by-namespace; verify pod-to-pod connectivity using kubectl exec reachability checks.
  6. Decommission the old cluster once cutover is stable.

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-1350
Full reference

AKS Cluster Network Policy Not Enabled

Related checks

AKS Cluster RBAC Not EnabledAzureAKS Cluster API Server Not PrivateAzureAKS Cluster Diagnostic Logging Not EnabledAzureAKS Cluster Monitoring Not EnabledAzureACM Certificate Expiring SoonAWSAzure NSG Open to InternetAzure

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·