Minimize wildcard use in Roles and ClusterRoles

OrtaDüzey 1Manuel incelemeeks

Açıklama

Verify that Kubernetes Role and ClusterRole objects in EKS do not use wildcard entries such as * for verbs, resources, or apiGroups unless a documented administrative or platform requirement exists. The review should also include the RoleBinding and ClusterRoleBinding objects that assign those roles to users, groups, or service accounts, because EKS can authorize access through both access entries and native Kubernetes RBAC, and principals can ... The benchmark marks this recommendation Manual.

Nasıl denetlenir

Denetim yöntemi: Manuel inceleme

Bu öneri otomatik olarak denetlenemez. --include-manual parametresini verdiğinizde tarama bunu bu talimatlarla birlikte listeler.

Begin by reviewing custom Kubernetes Role and ClusterRole objects in EKS to identify any use of wildcard entries such as * for verbs, resources, or apiGroups. In EKS, this review should cover native RBAC objects, access entries that reference Kubernetes groups, service accounts, and any remaining aws-auth mappings, because EKS supports access through both access entries and Kubernetes RBAC, and it also creates its own platform RBAC objects that should be distinguished from customer-defined permissions.

Nasıl düzeltilir

Düzeltme yöntemi: Kılavuz veya altyapı yaması

Start by replacing wildcard permissions in custom Role and ClusterRole objects with explicitly enumerated verbs, resources, and apiGroups that match the approved operational need. In EKS, this remediation should focus on customer-managed RBAC objects, the bindings that assign them, access entries that reference Kubernetes groups, and service accounts used by workloads or cluster components. EKS guidance favors fine-grained access through access entries and least-privilege review of RBAC permissions, especially for service accounts used by add-ons, DaemonSets, and CSI drivers. • Replace wildcard values in custom Role and ClusterRole rules with the specific verbs, resources, and apiGroups the function actually requires.

Özellikler

İşletim sistemleri: Herhangi biri
Etiketler: ekspoliciesrbac
Referans: CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v2.0.0 - 4.1.3 Minimize wildcard use in Roles and ClusterRoles