More Info:
Use network policies to isolate traffic in your cluster network.Risk Level
LowAddress
SecurityCompliance Standards
- APRA CPS 234 (Australia)
- BSI C5 (Germany)
- Brazil LGPD
- CCPA / CPRA (California)
- CIS Critical Security Controls v8
- CIS GKE
- CMMC 2.0
- CSA Cloud Controls Matrix v4
- DPDPA
- Digital Operational Resilience Act (EU)
- Essential 8
- ISO/IEC 27017
- ISO/IEC 27018
- ISO/IEC 27701
- KSA PDPL
- MAS Technology Risk Management (Singapore)
- MITRE ATT&CK (Cloud)
- NIS2 Directive
- NIST SP 800-171
- NYDFS 23 NYCRR 500
- SWIFT Customer Security Controls Framework
- Sarbanes-Oxley IT General Controls
- UK NCSC Cyber Assessment Framework
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
List namespaces that are missing NetworkPolicies (run on any machine with kubectl access):
Note the namespace names returned; each needs at least one NetworkPolicy.
-
For each namespace without a NetworkPolicy, create a default deny-all NetworkPolicy manifest file on your local machine (with kubectl access). Example for namespace
example-namespace: -
Apply the NetworkPolicy for that namespace (run on any machine with kubectl access):
-
(Optional but recommended) For application namespaces where you need traffic, design and apply more granular NetworkPolicies that allow required ingress/egress. Example allow ingress from same namespace for
example-namespace: -
Repeat steps 2–4 for each namespace reported in step 1, adjusting the
namespace:field and filenames accordingly. -
Verification (run on any machine with kubectl access):
Confirm the output is:
Using kubectl
Using kubectl
FOUND_NAMESPACE_WITHOUT_NETWORKPOLICY:devFOUND_NAMESPACE_WITHOUT_NETWORKPOLICY:prod
Automation
Automation

