규칙 탐색기
카탈로그의 모든 하드닝 규칙을 둘러보세요. 플랫폼, 심각도, 프로필 레벨 및 자동 점검 가능 여부로 필터링할 수 있습니다.
규칙 54개 찾음/ 전체 16,927개3페이지 중 1페이지
| ID | 제목 | 플랫폼 | 심각도 | 레벨 | 점검 |
|---|---|---|---|---|---|
| TMA-GKE-4.1.1 | Ensure the cluster-admin ClusterRole is only used when requiredgke · 레벨 1 | gke | 심각 | 1 | 수동 검토 |
| TMA-GKE-4.1.6 | Avoid granting cluster admin level access through the system:masters groupgke · 레벨 1 | gke | 심각 | 1 | 자동 |
| TMA-GKE-4.1.8 | Avoid binding RBAC roles to unauthenticated users and groupsgke · 레벨 2 | gke | 심각 | 2 | 자동 |
| TMA-GKE-5.8.3 | Ensure Legacy Authorization (ABAC) is Disabledgke · 레벨 1 | gke | 심각 | 1 | 자동 |
| TMA-GKE-4.1.2 | Ensure access to Secrets is minimized and granted only where requiredgke · 레벨 1 | gke | 높음 | 1 | 수동 검토 |
| TMA-GKE-4.1.4 | Ensure that default service accounts are not actively usedgke · 레벨 1 | gke | 높음 | 1 | 자동 |
| TMA-GKE-4.1.5 | Ensure service account tokens are mounted only when Pods require Kubernetes API accessgke · 레벨 1 | gke | 높음 | 1 | 수동 검토 |
| TMA-GKE-4.1.7 | Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes clustergke · 레벨 1 | gke | 높음 | 1 | 수동 검토 |
| TMA-GKE-4.1.9 | Avoid binding RBAC roles to all authenticated usersgke · 레벨 1 | gke | 높음 | 1 | 자동 |
| TMA-GKE-5.2.1 | Use custom least privilege service accounts for GKE node poolsgke · 레벨 1 | gke | 높음 | 1 | 자동 |
| TMA-GKE-5.3.1 | Enable application-layer Secrets encryption with Cloud KMS keysgke · 레벨 2 | gke | 높음 | 2 | 자동 |
| TMA-GKE-5.5.5 | Verify Shielded GKE Nodes are enabled for GKE clustersgke · 레벨 1 | gke | 높음 | 1 | 자동 |
| TMA-GKE-5.5.6 | Verify Shielded GKE Node integrity monitoring is enabledgke · 레벨 1 | gke | 높음 | 1 | 자동 |
| TMA-GKE-5.6.5 | Ensure private GKE nodes are configured without external IP addressesgke · 레벨 1 | gke | 높음 | 1 | 자동 |
| TMA-GKE-5.8.1 | Disable legacy client certificate authentication for the GKE API servergke · 레벨 1 | gke | 높음 | 1 | 자동 |
| TMA-GKE-3.1.1 | Ensure that the kubeconfig file permissions are set to 644 or more restrictivegke · 레벨 1 | gke | 보통 | 1 | 자동 |
| TMA-GKE-3.1.2 | Ensure that the kubelet kubeconfig file ownership is set to root:rootgke · 레벨 1 | gke | 보통 | 1 | 자동 |
| TMA-GKE-3.1.3 | Ensure that the kubelet configuration file has permissions set to 644gke · 레벨 1 | gke | 보통 | 1 | 자동 |
| TMA-GKE-3.1.4 | Ensure that the kubelet configuration file ownership is set to root:rootgke · 레벨 1 | gke | 보통 | 1 | 자동 |
| TMA-GKE-4.1.3 | Minimize wildcard use in Roles and ClusterRolesgke · 레벨 1 | gke | 보통 | 1 | 수동 검토 |
| TMA-GKE-4.2.1 | Enforce baseline or restricted Pod Security Standards on workload namespacesgke · 레벨 1 | gke | 보통 | 1 | 수동 검토 |
| TMA-GKE-4.3.1 | Enable NetworkPolicy enforcement with GKE Dataplane V2 or Calicogke · 레벨 1 | gke | 보통 | 1 | 수동 검토 |
| TMA-GKE-4.3.2 | Define default deny NetworkPolicies for each workload namespacegke · 레벨 2 | gke | 보통 | 2 | 자동 |
| TMA-GKE-4.4.1 | Prefer using secrets as files over secrets as environment variablesgke · 레벨 2 | gke | 보통 | 2 | 자동 |
| TMA-GKE-4.4.2 | Use Secret Manager for external workload secret storagegke · 레벨 2 | gke | 보통 | 2 | 수동 검토 |