Prefer using dedicated AKS Service Accounts

Kako se proverava

Metod provere: Ručni pregled

Ova preporuka se ne može proveriti automatski. Skeniranje je navodi sa ovim uputstvima kada prosledite --include-manual.

For each namespace, verify that workloads do not use the default service account unless required, and confirm that the default service account has no custom role bindings beyond baseline defaults. Review workload-specific service accounts to ensure permissions are scoped with least privilege, and confirm automountServiceAccountToken is disabled where token access is not needed.

Kako se ispravlja

Metod ispravke: Smernica ili zakrpa infrastrukture

Use a dedicated Kubernetes service account for each AKS workload that requires identity, and replace use of the namespace default service account wherever it is not explicitly required. Scope each service account to only the Kubernetes permissions and Azure resource access needed by that workload, and prevent service account tokens from being mounted into pods unless token-based access is required. 1. Create a separate Kubernetes service account for each workload or application boundary that requires distinct access. 2. Bind each service account only to the minimum required Kubernetes Role or ClusterRole, and avoid granting custom permissions to the namespace default service account. 3. Set automountServiceAccountToken: false for pods that do not need a service account token. 4.