Benchmark: 5.3.2 Ensure that all Namespaces have Network Policies defined
Description
Use network policies to isolate traffic in your cluster network.
Running different applications on the same Kubernetes cluster creates a risk of one compromised application attacking a neighboring application. Network segmentation is important to ensure that containers can communicate only with those they are supposed to. A network policy is a specification of how selections of pods are allowed to communicate with each other and other network endpoints.
Network Policies are namespace scoped. When a network policy is introduced to a given namespace, all traffic not allowed by the policy is denied. However, if there are no network policies in a namespace all traffic will be allowed into and out of the pods in that namespace.
Remediation
Follow the documentation and create NetworkPolicy objects as you need them. By default, network policies are not created.
References
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-kubernetes-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select 5.3.2 Ensure that all Namespaces have Network Policies defined.
Run this benchmark in your terminal:
powerpipe benchmark run kubernetes_compliance.benchmark.cis_kube_v120_v100_5_3_2Snapshot and share results via Turbot Pipes:
powerpipe benchmark run kubernetes_compliance.benchmark.cis_kube_v120_v100_5_3_2 --shareControls
- Namespaces should have a default network policy to deny all egress traffic
- Namespaces should have a default network policy to deny all ingress traffic
- Network policies should not have a default policy to allow all egress traffic
- Network policies should not have a default policy to allow all ingress traffic