TMA-AKS-4.1.2
Ensure access to Secrets is minimized and granted only where required
Description
Verify that access to Kubernetes Secret objects in AKS are granted to only identities with a defined purpose. The review should include Azure RBAC for Kubernetes Authorization assignments, Kubernetes RBAC roles and bindings, and service account permissions, with particular attention to permissions that allow get, list, or watch access to secrets, because those permissions expose sensitive namespace-scoped data. The benchmark marks this recommendation Manual.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
Review the users who have get, list or watch access to secrets objects in the Kubernetes API.
How it is fixed
Fix method: Guidance or infrastructure patch
Where possible, remove get, list and watch access to secret objects in the cluster.
Properties
- Operating systems
- Any
- Tags
- akspoliciesrbacsecrets
- Reference
- CIS Azure Kubernetes Service (AKS) Benchmark v2.0.0 - 4.1.2 Ensure access to Secrets is minimized and granted only where required