Ensure that Service Account Tokens are only mounted where necessary

Kako se proverava

Metod provere: Komanda ljuske

out=$(kubectl get pods -A -o go-template='{{range .items}}{{.metadata.namespace}} {{.metadata.name}}{{range .spec.volumes}} {{.name}}{{end}}{{"\n"}}{{end}}') || exit 1
bad=$(printf '%s\n' "$out" | awk -v ex='^(kube-system|kube-public|kube-node-lease|gatekeeper-system|azure-arc)$' 'NF && $1 !~ ex && ($0 ~ / kube-api-access-/)')
if [ -z "$bad" ]; then echo compliant; else printf '%s\n' "$bad" | head -n 25; fi

Očekivani izlaz

compliant

Kako se ispravlja

Metod ispravke: Smernica ili zakrpa infrastrukture

Apply the following steps to reduce unnecessary service account token mounting in AKS: • Set automountServiceAccountToken to false for pods and service accounts that do not require Kubernetes API access. AKS policy guidance states that this increases security by avoiding default token auto-mounting. • Update workloads to use a dedicated serviceAccountName only where a service account token is operationally required, instead of inheriting token behavior from the namespace default service account. AKS states that service account credentials are used by authorized pods to communicate with the API server. • For workloads that need Azure resource access, use Microsoft Entra Workload ID with explicit workload configuration rather than broad default token mounting. AKS documents that workload identity token projection is enabled only for explicitly configured pods.

Proverite ovaj računar

Pokrenite ovo na računaru za koji imate dozvolu za proveru. Skeniranje radi u režimu samo za čitanje.

tmaegis scan --target aks