规则浏览器
浏览目录中的每一条加固规则。可按平台、严重程度、配置级别以及是否支持自动化检查进行筛选。
找到 29 条规则共 8,597 条第 1 / 2 页
| ID | 标题 | 平台 | 严重程度 | 级别 | 检查方式 |
|---|---|---|---|---|---|
| TMA-GKE-AUTOPILOT-4.1.1 | Ensure the cluster-admin ClusterRole is only used when requiredgke-autopilot · 级别 1 | gke-autopilot | 严重 | 1 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.1.6 | Avoid granting cluster admin level access through the system:masters groupgke-autopilot · 级别 1 | gke-autopilot | 严重 | 1 | 自动化 |
| TMA-GKE-AUTOPILOT-4.1.8 | Avoid binding RBAC roles to unauthenticated users and groupsgke-autopilot · 级别 2 | gke-autopilot | 严重 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-4.1.2 | Ensure access to Secrets is minimized and granted only where requiredgke-autopilot · 级别 1 | gke-autopilot | 高 | 1 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.1.4 | Ensure that default service accounts are not actively usedgke-autopilot · 级别 1 | gke-autopilot | 高 | 1 | 自动化 |
| TMA-GKE-AUTOPILOT-4.1.5 | Ensure service account tokens are mounted only when Pods require Kubernetes API accessgke-autopilot · 级别 1 | gke-autopilot | 高 | 1 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.1.7 | Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes clustergke-autopilot · 级别 1 | gke-autopilot | 高 | 1 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.1.9 | Avoid binding RBAC roles to all authenticated usersgke-autopilot · 级别 1 | gke-autopilot | 高 | 1 | 自动化 |
| TMA-GKE-AUTOPILOT-5.3.1 | Enable application-layer Secrets encryption with Cloud KMS keysgke-autopilot · 级别 2 | gke-autopilot | 高 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-4.1.3 | Minimize wildcard use in Roles and ClusterRolesgke-autopilot · 级别 1 | gke-autopilot | 中 | 1 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.3.1 | Use NetworkPolicy with built in GKE Dataplane V2 enforcementgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.4.1 | Use Secret Manager for external workload secret storagegke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.6.1 | Use namespaces to separate workload administration and resource governancegke-autopilot · 级别 1 | gke-autopilot | 中 | 1 | 人工审核 |
| TMA-GKE-AUTOPILOT-5.1.1 | Enable Artifact Analysis scanning for Artifact Registry container imagesgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-5.1.2 | Grant least privilege IAM access to Artifact Registry repositoriesgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 人工审核 |
| TMA-GKE-AUTOPILOT-5.1.3 | Enforce Binary Authorization for trusted GKE container image deploymentsgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-5.2.1 | Use a custom least privilege node service account for GKE Autopilotgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-5.4.1 | Enable VPC Flow Logs and Intranode Visibilitygke-autopilot · 级别 1 | gke-autopilot | 中 | 1 | 自动化 |
| TMA-GKE-AUTOPILOT-5.4.2 | Restrict GKE control plane access with authorized networksgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-5.4.3 | Use DNS based access or private GKE control plane endpointsgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-5.4.4 | Ensure private GKE nodes are configured without external IP addressesgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 自动化 |
| TMA-GKE-AUTOPILOT-5.4.5 | Use Google managed SSL certificates for GKE Ingress TLSgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 人工审核 |
| TMA-GKE-AUTOPILOT-5.5.1 | Use Google Groups to centrally manage Kubernetes RBAC access for GKE clustersgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 人工审核 |
| TMA-GKE-AUTOPILOT-5.6.1 | Use CMEK protected StorageClasses for GKE Persistent Disk volumesgke-autopilot · 级别 2 | gke-autopilot | 中 | 2 | 人工审核 |
| TMA-GKE-AUTOPILOT-4.5.1 | Enforce image provenance using Binary Authorization for GKEgke-autopilot · 级别 2 | gke-autopilot | 低 | 2 | 人工审核 |