Explorador de reglas
Explore todas las reglas de endurecimiento del catálogo. Filtre por plataforma, severidad, nivel de perfil y si la verificación puede automatizarse.
54 reglas encontradasde 16.927Página 1 de 3
| ID | Título | Plataforma | Severidad | Nivel | Verificación |
|---|---|---|---|---|---|
| TMA-GKE-4.1.1 | Ensure the cluster-admin ClusterRole is only used when requiredgke · Nivel 1 | gke | Crítica | 1 | Revisión manual |
| TMA-GKE-4.1.6 | Avoid granting cluster admin level access through the system:masters groupgke · Nivel 1 | gke | Crítica | 1 | Automatizada |
| TMA-GKE-4.1.8 | Avoid binding RBAC roles to unauthenticated users and groupsgke · Nivel 2 | gke | Crítica | 2 | Automatizada |
| TMA-GKE-5.8.3 | Ensure Legacy Authorization (ABAC) is Disabledgke · Nivel 1 | gke | Crítica | 1 | Automatizada |
| TMA-GKE-4.1.2 | Ensure access to Secrets is minimized and granted only where requiredgke · Nivel 1 | gke | Alta | 1 | Revisión manual |
| TMA-GKE-4.1.4 | Ensure that default service accounts are not actively usedgke · Nivel 1 | gke | Alta | 1 | Automatizada |
| TMA-GKE-4.1.5 | Ensure service account tokens are mounted only when Pods require Kubernetes API accessgke · Nivel 1 | gke | Alta | 1 | Revisión manual |
| TMA-GKE-4.1.7 | Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes clustergke · Nivel 1 | gke | Alta | 1 | Revisión manual |
| TMA-GKE-4.1.9 | Avoid binding RBAC roles to all authenticated usersgke · Nivel 1 | gke | Alta | 1 | Automatizada |
| TMA-GKE-5.2.1 | Use custom least privilege service accounts for GKE node poolsgke · Nivel 1 | gke | Alta | 1 | Automatizada |
| TMA-GKE-5.3.1 | Enable application-layer Secrets encryption with Cloud KMS keysgke · Nivel 2 | gke | Alta | 2 | Automatizada |
| TMA-GKE-5.5.5 | Verify Shielded GKE Nodes are enabled for GKE clustersgke · Nivel 1 | gke | Alta | 1 | Automatizada |
| TMA-GKE-5.5.6 | Verify Shielded GKE Node integrity monitoring is enabledgke · Nivel 1 | gke | Alta | 1 | Automatizada |
| TMA-GKE-5.6.5 | Ensure private GKE nodes are configured without external IP addressesgke · Nivel 1 | gke | Alta | 1 | Automatizada |
| TMA-GKE-5.8.1 | Disable legacy client certificate authentication for the GKE API servergke · Nivel 1 | gke | Alta | 1 | Automatizada |
| TMA-GKE-3.1.1 | Ensure that the kubeconfig file permissions are set to 644 or more restrictivegke · Nivel 1 | gke | Media | 1 | Automatizada |
| TMA-GKE-3.1.2 | Ensure that the kubelet kubeconfig file ownership is set to root:rootgke · Nivel 1 | gke | Media | 1 | Automatizada |
| TMA-GKE-3.1.3 | Ensure that the kubelet configuration file has permissions set to 644gke · Nivel 1 | gke | Media | 1 | Automatizada |
| TMA-GKE-3.1.4 | Ensure that the kubelet configuration file ownership is set to root:rootgke · Nivel 1 | gke | Media | 1 | Automatizada |
| TMA-GKE-4.1.3 | Minimize wildcard use in Roles and ClusterRolesgke · Nivel 1 | gke | Media | 1 | Revisión manual |
| TMA-GKE-4.2.1 | Enforce baseline or restricted Pod Security Standards on workload namespacesgke · Nivel 1 | gke | Media | 1 | Revisión manual |
| TMA-GKE-4.3.1 | Enable NetworkPolicy enforcement with GKE Dataplane V2 or Calicogke · Nivel 1 | gke | Media | 1 | Revisión manual |
| TMA-GKE-4.3.2 | Define default deny NetworkPolicies for each workload namespacegke · Nivel 2 | gke | Media | 2 | Automatizada |
| TMA-GKE-4.4.1 | Prefer using secrets as files over secrets as environment variablesgke · Nivel 2 | gke | Media | 2 | Automatizada |
| TMA-GKE-4.4.2 | Use Secret Manager for external workload secret storagegke · Nivel 2 | gke | Media | 2 | Revisión manual |