Ensure Network Policy is Enabled and set as appropriate

보통레벨 1자동aks

설명

In AKS, the cluster should have a supported network policy engine enabled and the resulting policy model should be configured to enforce the intended pod-level traffic restrictions. Network policies in AKS are used to allow or deny traffic between pods based on selectors such as namespace, labels, and ports. Requires the az CLI (logged in) with read access to the cluster named by AKS_RG and AKS_NAME. Passes when networkProfile.networkPolicy is azure, calico or cilium.

점검 방법

감사 방식: 셸 명령

shell

p=$(az aks show --resource-group "${AKS_RG:?set AKS_RG}" --name "${AKS_NAME:?set AKS_NAME}" --query networkProfile.networkPolicy -o tsv) || exit 1
case "$p" in ""|none|None|null) echo "noncompliant: networkPolicy=${p:-null}";; *) echo compliant;; esac

예상 출력: compliant

조치 방법

조치 방식: 가이드 또는 인프라 패치

Align each AKS cluster to an approved network policy baseline based on the networkProfile audit results. If networkPolicy is none or null, enable a supported policy capability so pod-to-pod traffic is no longer unmanaged by default. For new Linux-based AKS deployments, the preferred target state is Azure CNI Powered by Cilium with Cilium network policy, because it provides Kubernetes-native policy enforcement on an eBPF dataplane and is the recommended direction for new deployments. For existing clusters, treat remediation as a planned networking migration and standardization effort. Move clusters from nonpreferred engines to the approved target state, validate policy behavior after the change, and stage the migration when the cluster must first move to a different Azure CNI IPAM mode before adopting the target dataplane.

속성

운영 체제: 모두
태그: aksmanaged-servicesnetwork
참고 자료: CIS Azure Kubernetes Service (AKS) Benchmark v2.0.0 - 5.4.4 Ensure Network Policy is Enabled and set as appropriate

이 호스트 점검하기

감사 권한이 있는 시스템에서 실행하세요. 스캔은 읽기 전용입니다.

shell

tmaegis scan --target aks