TMAegis
id

Penjelajah aturan

Jelajahi setiap aturan hardening di katalog. Filter menurut platform, tingkat keparahan, level profil, dan apakah pemeriksaan dapat diotomatisasi.

29 aturan ditemukandari 11.219Halaman 1 dari 2

IDJudulTingkat keparahan
TMA-GKE-AUTOPILOT-4.1.1Ensure the cluster-admin ClusterRole is only used when requiredgke-autopilot · Level 1Kritis
TMA-GKE-AUTOPILOT-4.1.6Avoid granting cluster admin level access through the system:masters groupgke-autopilot · Level 1Kritis
TMA-GKE-AUTOPILOT-4.1.8Avoid binding RBAC roles to unauthenticated users and groupsgke-autopilot · Level 2Kritis
TMA-GKE-AUTOPILOT-4.1.2Ensure access to Secrets is minimized and granted only where requiredgke-autopilot · Level 1Tinggi
TMA-GKE-AUTOPILOT-4.1.4Ensure that default service accounts are not actively usedgke-autopilot · Level 1Tinggi
TMA-GKE-AUTOPILOT-4.1.5Ensure service account tokens are mounted only when Pods require Kubernetes API accessgke-autopilot · Level 1Tinggi
TMA-GKE-AUTOPILOT-4.1.7Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes clustergke-autopilot · Level 1Tinggi
TMA-GKE-AUTOPILOT-4.1.9Avoid binding RBAC roles to all authenticated usersgke-autopilot · Level 1Tinggi
TMA-GKE-AUTOPILOT-5.3.1Enable application-layer Secrets encryption with Cloud KMS keysgke-autopilot · Level 2Tinggi
TMA-GKE-AUTOPILOT-4.1.3Minimize wildcard use in Roles and ClusterRolesgke-autopilot · Level 1Sedang
TMA-GKE-AUTOPILOT-4.3.1Use NetworkPolicy with built in GKE Dataplane V2 enforcementgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-4.4.1Use Secret Manager for external workload secret storagegke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-4.6.1Use namespaces to separate workload administration and resource governancegke-autopilot · Level 1Sedang
TMA-GKE-AUTOPILOT-5.1.1Enable Artifact Analysis scanning for Artifact Registry container imagesgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.1.2Grant least privilege IAM access to Artifact Registry repositoriesgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.1.3Enforce Binary Authorization for trusted GKE container image deploymentsgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.2.1Use a custom least privilege node service account for GKE Autopilotgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.4.1Enable VPC Flow Logs and Intranode Visibilitygke-autopilot · Level 1Sedang
TMA-GKE-AUTOPILOT-5.4.2Restrict GKE control plane access with authorized networksgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.4.3Use DNS based access or private GKE control plane endpointsgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.4.4Ensure private GKE nodes are configured without external IP addressesgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.4.5Use Google managed SSL certificates for GKE Ingress TLSgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.5.1Use Google Groups to centrally manage Kubernetes RBAC access for GKE clustersgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-5.6.1Use CMEK protected StorageClasses for GKE Persistent Disk volumesgke-autopilot · Level 2Sedang
TMA-GKE-AUTOPILOT-4.5.1Enforce image provenance using Binary Authorization for GKEgke-autopilot · Level 2Rendah