CyberStrikeus/CyberStrike - Page 49

cis-gke-autopilot-v100-4-1-2

Minimize access to secrets (Automated)

cis-gke-autopilot-v100-4-1-3

Minimize wildcard use in Roles and ClusterRoles (Automated)

cis-gke-autopilot-v100-4-1-4

Ensure that default service accounts are not actively used (Automated)

cis-gke-autopilot-v100-4-1-5

Ensure that Service Account Tokens are only mounted where necessary (Automated)

cis-gke-autopilot-v100-4-1-6

Avoid use of system:masters group (Automated)

cis-gke-autopilot-v100-4-1-7

Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)

cis-gke-autopilot-v100-4-1-8

Avoid bindings to system:anonymous (Automated)

cis-gke-autopilot-v100-4-1-9

Avoid non-default bindings to system:unauthenticated (Automated)

cis-gke-autopilot-v100-4-2-1

Ensure that the cluster enforces Pod Security Standard Baseline profile or stricter for all namespaces (Manual)

cis-gke-autopilot-v100-4-3-1

Ensure that all Namespaces have Network Policies defined (Automated)

cis-gke-autopilot-v100-4-4-1

Consider external secret storage (Manual)

cis-gke-autopilot-v100-4-5-1

Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)

cis-gke-autopilot-v100-4-6-1

Create administrative boundaries between resources using namespaces (Manual)

cis-gke-autopilot-v100-4-6-2

Ensure that the seccomp profile is set to RuntimeDefault in the pod definitions (Automated)

cis-gke-autopilot-v100-4-6-3

Apply Security Context to Pods and Containers (Manual)

cis-gke-autopilot-v100-4-6-4

The default namespace should not be used (Automated)

cis-gke-autopilot-v100-5-1-1

Ensure Image Vulnerability Scanning is enabled (Automated)

cis-gke-autopilot-v100-5-1-2

Minimize user access to Container Image repositories (Manual)

cis-gke-autopilot-v100-5-1-3

Minimize cluster access to read-only for Container Image repositories (Manual)

cis-gke-autopilot-v100-5-1-4

Ensure only trusted container images are used (Automated)

cis-gke-autopilot-v100-5-2-1

Ensure GKE clusters are not running using the Compute Engine default service account (Automated)

cis-gke-autopilot-v100-5-3-1

Ensure Kubernetes Secrets are encrypted using keys managed in Cloud KMS (Automated)

cis-gke-autopilot-v100-5-4-1

Enable VPC Flow Logs and Intranode Visibility (Automated)

cis-gke-autopilot-v100-5-4-2

Ensure Control Plane Authorized Networks is Enabled (Automated)

cis-gke-autopilot-v100-5-4-3

Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Automated)

cis-gke-autopilot-v100-5-4-4

Ensure clusters are created with Private Nodes (Automated)

cis-gke-autopilot-v100-5-4-5

Ensure use of Google-managed SSL Certificates (Automated)

cis-gke-autopilot-v100-5-5-1

Manage Kubernetes RBAC users with Google Groups for GKE (Manual)

cis-gke-autopilot-v100-5-6-1

Enable Customer-Managed Encryption Keys (CMEK) for GKE Persistent Disks (PD) (Manual)

cis-gke-autopilot-v100-5-7-1

Enable Security Posture (Manual)

cis-gke-autopilot-v120-4-1-1

Ensure that the cluster-admin role is only used where required (Automated)

cis-gke-autopilot-v120-4-1-10

Avoid non-default bindings to system:authenticated (Automated)

cis-gke-autopilot-v120-4-1-2

Minimize access to secrets (Automated)

cis-gke-autopilot-v120-4-1-3

Minimize wildcard use in Roles and ClusterRoles (Automated)

cis-gke-autopilot-v120-4-1-4

Ensure that default service accounts are not actively used (Automated)

cis-gke-autopilot-v120-4-1-5

Ensure that Service Account Tokens are only mounted where necessary (Automated)

cis-gke-autopilot-v120-4-1-6

Avoid use of system:masters group (Automated)

cis-gke-autopilot-v120-4-1-7

Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)

cis-gke-autopilot-v120-4-1-8

Avoid bindings to system:anonymous (Automated)

cis-gke-autopilot-v120-4-1-9

Avoid non-default bindings to system:unauthenticated (Automated)