TMAegisBeta
Más reglas para gke

Google Kubernetes Engine (GKE)

TMA-GKE-4.1.2

Ensure access to Secrets is minimized and granted only where required

AltaNivel 1Revisión manualgke

Descripción

Kubernetes Secrets can contain sensitive application credentials, configuration values, certificates, and legacy service account tokens. Access to these secrets should be restricted to the smallest practical set of users, groups, service accounts, and workloads to reduce the risk of credential exposure, privilege escalation, and unauthorized access to cluster or external resources. The benchmark marks this recommendation Manual.

Cómo se verifica

Método de auditoría: Revisión manual

Esta recomendación no se puede verificar automáticamente. Un escaneo la lista con estas instrucciones cuando se pasa --include-manual.

Review RBAC permissions that grant read access to Secrets in GKE Standard clusters. Audit should identify where get, list, or watch permissions on the core API secrets resource are defined, how those permissions are assigned through bindings, and which users, groups, or service accounts receive the access. The review should also account for broad default roles, wildcard rules, default groups, and shared or default service accounts, because these can unintentionally expose Secrets beyond the intended operational need.

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

Remediate Secret access by replacing broad or unnecessary RBAC permissions with narrowly defined access that supports only the required workload, user, or operational function. The remediation process should focus on reducing get, list, and watch permissions on the core API secrets resource, especially where access is inherited through broad roles, wildcard rules, shared service accounts, or default service accounts. Changes should be validated before removal to avoid disrupting applications, controllers, operators, or required platform services. • Remove unnecessary Secret access by updating or replacing RBAC roles that grant get, list, or watch on secrets, especially where the access is inherited through wildcard resources or wildcard verbs • Replace broad Secret permissions with least privilege Roles or ClusterRoles that grant only the required API group, resource, and verb.

Propiedades

Sistemas operativos
Cualquiera
Etiquetas
gkepoliciesrbacsecrets
Referencia
CIS Google Kubernetes Engine (GKE) Benchmark v2.0.0 - 4.1.2 Ensure access to Secrets is minimized and granted only where required