Penjelajah aturan
Jelajahi setiap aturan hardening di katalog. Filter menurut platform, tingkat keparahan, level profil, dan apakah pemeriksaan dapat diotomatisasi.
54 aturan ditemukandari 11.219Halaman 1 dari 3
| ID | Judul | Platform | Tingkat keparahan | Level | Pemeriksaan |
|---|---|---|---|---|---|
| TMA-GKE-4.1.1 | Ensure the cluster-admin ClusterRole is only used when requiredgke · Level 1 | gke | Kritis | 1 | Tinjauan manual |
| TMA-GKE-4.1.6 | Avoid granting cluster admin level access through the system:masters groupgke · Level 1 | gke | Kritis | 1 | Otomatis |
| TMA-GKE-4.1.8 | Avoid binding RBAC roles to unauthenticated users and groupsgke · Level 2 | gke | Kritis | 2 | Otomatis |
| TMA-GKE-5.8.3 | Ensure Legacy Authorization (ABAC) is Disabledgke · Level 1 | gke | Kritis | 1 | Otomatis |
| TMA-GKE-4.1.2 | Ensure access to Secrets is minimized and granted only where requiredgke · Level 1 | gke | Tinggi | 1 | Tinjauan manual |
| TMA-GKE-4.1.4 | Ensure that default service accounts are not actively usedgke · Level 1 | gke | Tinggi | 1 | Otomatis |
| TMA-GKE-4.1.5 | Ensure service account tokens are mounted only when Pods require Kubernetes API accessgke · Level 1 | gke | Tinggi | 1 | Tinjauan manual |
| TMA-GKE-4.1.7 | Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes clustergke · Level 1 | gke | Tinggi | 1 | Tinjauan manual |
| TMA-GKE-4.1.9 | Avoid binding RBAC roles to all authenticated usersgke · Level 1 | gke | Tinggi | 1 | Otomatis |
| TMA-GKE-5.2.1 | Use custom least privilege service accounts for GKE node poolsgke · Level 1 | gke | Tinggi | 1 | Otomatis |
| TMA-GKE-5.3.1 | Enable application-layer Secrets encryption with Cloud KMS keysgke · Level 2 | gke | Tinggi | 2 | Otomatis |
| TMA-GKE-5.5.5 | Verify Shielded GKE Nodes are enabled for GKE clustersgke · Level 1 | gke | Tinggi | 1 | Otomatis |
| TMA-GKE-5.5.6 | Verify Shielded GKE Node integrity monitoring is enabledgke · Level 1 | gke | Tinggi | 1 | Otomatis |
| TMA-GKE-5.6.5 | Ensure private GKE nodes are configured without external IP addressesgke · Level 1 | gke | Tinggi | 1 | Otomatis |
| TMA-GKE-5.8.1 | Disable legacy client certificate authentication for the GKE API servergke · Level 1 | gke | Tinggi | 1 | Otomatis |
| TMA-GKE-3.1.1 | Ensure that the kubeconfig file permissions are set to 644 or more restrictivegke · Level 1 | gke | Sedang | 1 | Otomatis |
| TMA-GKE-3.1.2 | Ensure that the kubelet kubeconfig file ownership is set to root:rootgke · Level 1 | gke | Sedang | 1 | Otomatis |
| TMA-GKE-3.1.3 | Ensure that the kubelet configuration file has permissions set to 644gke · Level 1 | gke | Sedang | 1 | Otomatis |
| TMA-GKE-3.1.4 | Ensure that the kubelet configuration file ownership is set to root:rootgke · Level 1 | gke | Sedang | 1 | Otomatis |
| TMA-GKE-4.1.3 | Minimize wildcard use in Roles and ClusterRolesgke · Level 1 | gke | Sedang | 1 | Tinjauan manual |
| TMA-GKE-4.2.1 | Enforce baseline or restricted Pod Security Standards on workload namespacesgke · Level 1 | gke | Sedang | 1 | Tinjauan manual |
| TMA-GKE-4.3.1 | Enable NetworkPolicy enforcement with GKE Dataplane V2 or Calicogke · Level 1 | gke | Sedang | 1 | Tinjauan manual |
| TMA-GKE-4.3.2 | Define default deny NetworkPolicies for each workload namespacegke · Level 2 | gke | Sedang | 2 | Otomatis |
| TMA-GKE-4.4.1 | Prefer using secrets as files over secrets as environment variablesgke · Level 2 | gke | Sedang | 2 | Otomatis |
| TMA-GKE-4.4.2 | Use Secret Manager for external workload secret storagegke · Level 2 | gke | Sedang | 2 | Tinjauan manual |