Minimize wildcard use in Roles and ClusterRoles

보통레벨 1수동 검토gke

설명

Kubernetes Roles and ClusterRoles define what actions users, groups, and service accounts can perform against Kubernetes API resources. Wildcard permissions should be minimized because the * character applies broadly across API groups, resources, or verbs and can grant more access than intended. Roles should explicitly define only the API groups, resources, and verbs required for the subject’s function. The benchmark marks this recommendation Manual.

점검 방법

감사 방식: 수동 검토

이 권장 사항은 자동으로 점검할 수 없습니다. --include-manual 옵션을 전달하면 스캔 결과에 이 지침과 함께 표시됩니다.

Review Kubernetes RBAC roles in GKE Standard clusters to identify wildcard permissions in Roles and ClusterRoles. The audit should check for * in apiGroups, resources, or verbs, because wildcard permissions can unintentionally grant access to current or future Kubernetes APIs, resources, custom resources, or actions. After identifying wildcard rules, review the related RoleBinding and ClusterRoleBinding objects to determine which users, groups, or service accounts receive the permissions.

조치 방법

조치 방식: 가이드 또는 인프라 패치

Replace wildcard permissions with explicit RBAC rules that define only the required API groups, resources, and verbs. Remediation should focus on preserving required access while removing broad * grants that could expand privileges as APIs, resources, or CRDs are added. Validate affected users, workloads, controllers, and automation before removing wildcard access. GKE RBAC guidance recommends least privilege role design and avoiding wildcard permissions.

속성

운영 체제: 모두
태그: gkepoliciesrbac
참고 자료: CIS Google Kubernetes Engine (GKE) Benchmark v2.0.0 - 4.1.3 Minimize wildcard use in Roles and ClusterRoles