Amazon EKS
TMA-EKS-4.1.9
Minimize access to create persistent volumes
Description
Permission to create persistent storage in EKS should be granted only where it is required. In EKS, this includes direct creation of PersistentVolume objects and, more commonly, the ability to trigger dynamic provisioning through PersistentVolumeClaim and StorageClass use, because EKS storage integrations such as the Amazon EBS CSI driver and EKS Auto Mode can automatically provision backing storage when applications request it. The benchmark marks this recommendation Manual.
How it is checked
Audit method: Manual review
Review EKS RBAC to identify any users, groups, or service accounts that can create PersistentVolume, PersistentVolumeClaim, or StorageClass resources. In EKS, this review should give particular attention to PersistentVolumeClaim and StorageClass permissions because persistent storage is commonly provisioned dynamically through CSI drivers and EKS storage integrations rather than by manually creating PersistentVolume objects.
How it is fixed
Fix method: Guidance or infrastructure patch
Remove persistent-storage creation rights from any user, group, or service account that does not require them, and replace broad assignments with the lowest-privilege role and narrowest scope possible. In EKS, prioritize PersistentVolumeClaim and StorageClass permissions because persistent storage is commonly provisioned dynamically through CSI drivers rather than by manually creating PersistentVolume objects. Limit direct PersistentVolume and StorageClass administration to approved administrators, and allow workloads to use only the PersistentVolumeClaim access required for approved storage classes. After changes are made, verify that required applications can still provision storage through the intended CSI driver path.
Properties
- Operating systems
- Any
- Tags
- ekspoliciesrbac
- Reference
- CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v2.0.0 - 4.1.9 Minimize access to create persistent volumes