Cis Aks V170 4.4.2

4.4.2 Ensure that all Namespaces have Network Policies defined (Automated)

Profile Applicability

• Level 2

Description

Use network policies to isolate traffic in your cluster network.

Rationale

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.

Once there is any Network Policy in a namespace selecting a particular pod, that pod will reject any connections that are not allowed by any Network Policy. Other pods in the namespace that are not selected by any Network Policy will continue to accept all traffic.

Impact

Once there is any Network Policy in a namespace selecting a particular pod, that pod will reject any connections that are not allowed by any Network Policy. Other pods in the namespace that are not selected by any Network Policy will continue to accept all traffic.

Audit

Run the below command and review the NetworkPolicy objects created in the cluster.

kubectl get networkpolicy --all-namespaces

Ensure that each namespace defined in the cluster has at least one Network Policy.

Remediation

Follow the documentation and create NetworkPolicy objects as you need them.

Default Value

By default, network policies are not created.

References

1. https://kubernetes.io/docs/concepts/services-networking/networkpolicies/
2. https://octetz.com/posts/k8s-network-policy-apis
3. https://kubernetes.io/docs/tasks/configure-pod-container/declare-network-policy/
4. https://docs.microsoft.com/security/benchmark/azure/security-controls-v2-network-security#ns-1-implement-security-for-internal-traffic

CIS Controls