| name | cis-k8s-v1120-5.1.10 |
| description | Minimize access to the proxy sub-resource of nodes (Manual) |
| category | cis-k8s |
| version | 1.12.0 |
| author | cyberstrike-official |
| tags | ["cis","kubernetes","policies","rbac","service-accounts"] |
| cis_id | 5.1.10 |
| cis_benchmark | CIS Kubernetes Benchmark v1.12.0 |
| tech_stack | ["kubernetes"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
5.1.10 Minimize access to the proxy sub-resource of nodes (Manual)
Profile Applicability
Description
Users with access to the Proxy sub-resource of Node objects automatically have permissions to use the kubelet API, which may allow for privilege escalation or bypass cluster security controls such as audit logs.
The kubelet provides an API which includes rights to execute commands in any container running on the node. Access to this API is covered by permissions to the main Kubernetes API via the node object. The proxy sub-resource specifically allows wide ranging access to the kubelet API.
Direct access to the kubelet API bypasses controls like audit logging (there is no audit log of kubelet API access) and admission control.
Rationale
The ability to use the proxy sub-resource of node objects opens up possibilities for privilege escalation and should be restricted, where possible.
Audit Procedure
Review the users who have access to the proxy sub-resource of node objects in the Kubernetes API.
Remediation
Where possible, remove access to the proxy sub-resource of node objects.
References
- https://kubernetes.io/docs/concepts/security/rbac-good-practices/#access-to-proxy-subresource-of-nodes
- https://kubernetes.io/docs/reference/access-authn-authz/kubelet-authn-authz/#kubelet-authorization
CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|
| v8 | 6.8 Define and Maintain Role-Based Access Control | | | X |
| v7 | 14 Controlled Access Based on the Need to Know | | | |