Minimize access to create persistent volumes (Manual)
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-eks-v180-4.1.9 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Eks V180 4.1.9?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-eks-v180-4-1-9)More formats (shields.io, HTML) on the badges page.
---
name: cis-eks-v180-4.1.9
description: "Minimize access to create persistent volumes (Manual)"
category: cis-eks
version: "1.8.0"
author: cyberstrike-official
tags: [cis, eks, kubernetes, aws, rbac, persistent-volumes, privilege-escalation]
cis_id: "4.1.9"
cis_benchmark: "CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v1.8.0"
tech_stack: [kubernetes, aws, eks]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 4.1.9 Minimize access to create persistent volumes (Manual)
## Profile Applicability
- Level 1
## Description
The ability to create persistent volumes in a cluster can provide an opportunity for privilege escalation, via the creation of `hostPath` volumes. As persistent volumes are not covered by Pod Security Admission, a user with access to create persistent volumes may be able to get access to sensitive files from the underlying host even where restrictive Pod Security Admission policies are in place.
## Rationale
The ability to create persistent volumes in a cluster opens up possibilities for privilege escalation and should be restricted, where possible.
## Audit Procedure
Review the users who have create access to `PersistentVolume` objects in the Kubernetes API.
```bash
kubectl get clusterrolebindings -o json | jq -r '.items[] | select(.roleRef.kind=="ClusterRole") | select(.subjects[]?.kind=="User" or .subjects[]?.kind=="Group" or .subjects[]?.kind=="ServiceAccount") | .metadata.name + " -> " + .roleRef.name'
```
## Remediation
Where possible, remove `create` access to `PersistentVolume` objects in the cluster.
## Default Value
By default, the cluster-admin ClusterRole has access to create PersistentVolume objects.
## References
1. https://kubernetes.io/docs/concepts/security/rbac-good-practices/#persistent-volume-creation
## CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------------------------------------- | ---- | ---- | ---- |
| v8 | 6.8 Define and Maintain Role-Based Access Control | | | ● |
## Profile Applicability
- Level 1
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!