CyberStrikeus/CyberStrike - Page 54

cis-gke-v180-5-5-5

Ensure Shielded GKE Nodes are Enabled (Automated)

cis-gke-v180-5-5-6

Ensure Integrity Monitoring for Shielded GKE Nodes is Enabled (Automated)

cis-gke-v180-5-5-7

Ensure Secure Boot for Shielded GKE Nodes is Enabled (Automated)

cis-gke-v180-5-6-1

Enable VPC Flow Logs and Intranode Visibility (Automated)

cis-gke-v180-5-6-2

Ensure use of VPC-native clusters (Automated)

cis-gke-v180-5-6-3

Ensure Control Plane Authorized Networks is Enabled (Automated)

cis-gke-v180-5-6-4

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

cis-gke-v180-5-6-5

Ensure clusters are created with Private Nodes (Automated)

cis-gke-v180-5-6-6

Consider firewalling GKE worker nodes (Manual)

cis-gke-v180-5-6-7

Ensure use of Google-managed SSL Certificates (Automated)

cis-gke-v180-5-7-1

Ensure Logging and Cloud Monitoring is Enabled (Automated)

cis-gke-v180-5-7-2

Enable Linux auditd logging (Manual)

cis-gke-v180-5-8-1

Ensure authentication using Client Certificates is Disabled (Automated)

cis-gke-v180-5-8-2

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

cis-gke-v180-5-8-3

Ensure Legacy Authorization (ABAC) is Disabled (Automated)

cis-gke-v180-5-9-1

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

cis-gke-v180-5-9-2

Enable Customer-Managed Encryption Keys (CMEK) for Boot Disks (Automated)

cis-gke-v190-3-1-1

Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive (Automated)

cis-gke-v190-3-1-2

Ensure that the proxy kubeconfig file ownership is set to root:root (Automated)

cis-gke-v190-3-1-3

Ensure that the kubelet configuration file has permissions set to 644 (Automated)

cis-gke-v190-3-1-4

Ensure that the kubelet configuration file ownership is set to root:root (Automated)

cis-gke-v190-4-1-1

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

cis-gke-v190-4-1-10

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

cis-gke-v190-4-1-2

Minimize access to secrets (Manual)

cis-gke-v190-4-1-3

Minimize wildcard use in Roles and ClusterRoles (Manual)

cis-gke-v190-4-1-4

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

cis-gke-v190-4-1-5

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

cis-gke-v190-4-1-6

Avoid use of system:masters group (Automated)

cis-gke-v190-4-1-7

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

cis-gke-v190-4-1-8

Avoid bindings to system:anonymous (Automated)

cis-gke-v190-4-1-9

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

cis-gke-v190-4-2-1

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

cis-gke-v190-4-3-1

Ensure that the CNI in use supports Network Policies (Manual)

cis-gke-v190-4-3-2

Ensure that all Namespaces have Network Policies defined (Automated)

cis-gke-v190-4-4-1

Prefer using secrets as files over secrets as environment variables (Automated)

cis-gke-v190-4-4-2

Consider external secret storage (Manual)

cis-gke-v190-4-5-1

Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)

cis-gke-v190-4-6-1

Create administrative boundaries between resources using namespaces (Manual)

cis-gke-v190-4-6-2

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

cis-gke-v190-4-6-3

Apply Security Context to Pods and Containers (Manual)