Skip to main content
Compliance · High severity

Cluster Network Policy Not Enforced

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.

2clouds covered
Highseverity
Compliancewhere it shows up
Manualfix, steps written out

AWSGoogle CloudKubernetes

Found, explained, handed over.

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

01

Detect

ZopNight checks this automatically across AWS and Google Cloud, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Enforce a network policy on EKS cluster.

03

Fix

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

Applies to
EKS Clusters on AWS, GKE Clusters on Google Cloud
The fix, by hand on AWS
  1. EKS → Cluster → Add-ons → upgrade aws-vpc-cni to a version supporting NetworkPolicy (≥1.14).
  2. Enable network policy on the VPC CNI: set enableNetworkPolicy=true in the aws-vpc-cni add-on configuration (or install Calico / Cilium for more advanced policy features).
  3. Apply a default-deny NetworkPolicy per namespace (deny all ingress + egress).
  4. Layer namespace-specific allow rules for required service-to-service paths.
  5. Validate with a temporary curl pod that traffic is blocked where expected, then re-run discovery. The finding is re-evaluated from the VPC CNI add-on's live enableNetworkPolicy value, so no manual tag suppresses it.
  6. If you enforce policy via Calico or Cilium instead (VPC CNI enableNetworkPolicy stays false to avoid conflicting engines), set meta["network_policy_managed_externally"]=true on the resource so the rule abstains.

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 IDs
RC-064 RC-125
Full reference

EKS Cluster Network Policy Not Enforced GKE Cluster Network Policy Not Enforced

Related checks

GKE Control Plane Master Authorized Networks DisabledGoogle CloudGKE Cluster Logging DisabledGoogle CloudGKE Cluster Monitoring DisabledGoogle CloudGKE Cluster Not PrivateGoogle CloudEKS Cluster Autoscaling Not ConfiguredAWSEKS Control Plane Logging DisabledAWS

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·