More Info:
Verifies each application namespace has a default-deny ingress NetworkPolicy. Without one, every pod is reachable from every other pod.Risk Level
HighAddress
SecurityCompliance Standards
- Cloudanix Best Practice
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
List non-system namespaces that are missing a default-deny ingress NetworkPolicy (run on any machine with kubectl access):
-
For one non-compliant namespace (replace
your-namespacewith the actual name), create a manifest file defining a default-deny ingress NetworkPolicy (run on any machine with kubectl access): -
Apply the default-deny ingress NetworkPolicy for that namespace (run on any machine with kubectl access):
-
Repeat steps 2–3 for each non-system namespace reported in step 1, changing the filename and the
namespace:field (run on any machine with kubectl access). -
(Optional but recommended) Define additional, more specific NetworkPolicies in each namespace to allow only the necessary ingress flows for your applications (run on any machine with kubectl access, using your own manifests and requirements):
-
Verify that every non-system namespace now has at least one default-deny ingress NetworkPolicy (run on any machine with kubectl access):
Using kubectl
Using kubectl
Automation
Automation

