CyberStrikeus/CyberStrike - Page 55

cis-gke-v190-4-6-4

The default namespace should not be used (Manual)

cis-gke-v190-5-1-1

Ensure Image Vulnerability Scanning is enabled (Automated)

cis-gke-v190-5-1-2

Minimize user access to Container Image repositories (Manual)

cis-gke-v190-5-1-3

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

cis-gke-v190-5-1-4

Ensure only trusted container images are used (Manual)

cis-gke-v190-5-10-1

Ensure Kubernetes Web UI is Disabled (Automated)

cis-gke-v190-5-10-2

Ensure that Alpha clusters are not used for production workloads (Automated)

cis-gke-v190-5-10-3

Consider GKE Sandbox for running untrusted workloads (Automated)

cis-gke-v190-5-2-1

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

cis-gke-v190-5-2-2

Prefer using dedicated GCP Service Accounts and Workload Identity (Manual)

cis-gke-v190-5-3-1

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

cis-gke-v190-5-4-1

Ensure the GKE Metadata Server is Enabled (Automated)

cis-gke-v190-5-5-1

Ensure Container-Optimized OS (cos_containerd) is used for GKE node images (Automated)

cis-gke-v190-5-5-2

Ensure Node Auto-Repair is enabled for GKE nodes (Automated)

cis-gke-v190-5-5-3

Ensure Node Auto-Upgrade is enabled for GKE nodes (Automated)

cis-gke-v190-5-5-4

When creating New Clusters - Automate GKE version management using Release Channels (Automated)

cis-gke-v190-5-5-5

Ensure Shielded GKE Nodes are Enabled (Automated)

cis-gke-v190-5-5-6

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

cis-gke-v190-5-5-7

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

cis-gke-v190-5-6-1

Enable VPC Flow Logs and Intranode Visibility (Automated)

cis-gke-v190-5-6-2

Ensure use of VPC-native clusters (Automated)

cis-gke-v190-5-6-3

Ensure Control Plane Authorized Networks is Enabled (Automated)

cis-gke-v190-5-6-4

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

cis-gke-v190-5-6-5

Ensure clusters are created with Private Nodes (Automated)

cis-gke-v190-5-6-6

Consider firewalling GKE worker nodes (Manual)

cis-gke-v190-5-6-7

Ensure use of Google-managed SSL Certificates (Automated)

cis-gke-v190-5-7-1

Ensure Logging and Cloud Monitoring is Enabled (Automated)

cis-gke-v190-5-7-2

Enable Linux auditd logging (Manual)

cis-gke-v190-5-8-1

Ensure authentication using Client Certificates is Disabled (Automated)

cis-gke-v190-5-8-2

Manage Kubernetes RBAC users with groups in Google Workspace (Manual)

cis-gke-v190-5-8-3

Ensure Legacy Authorization (ABAC) is Disabled (Automated)

cis-gke-v190-5-9-1

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

cis-gke-v190-5-9-2

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

cis-k8s-v1110-1-1-1

Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)

cis-k8s-v1110-1-1-10

Ensure that the Container Network Interface file ownership is set to root:root (Manual)

cis-k8s-v1110-1-1-11

Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)

cis-k8s-v1110-1-1-12

Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)

cis-k8s-v1110-1-1-13

Ensure that the default administrative credential file permissions are set to 600 (Automated)

cis-k8s-v1110-1-1-14

Ensure that the default administrative credential file ownership is set to root:root (Automated)

cis-k8s-v1110-1-1-15

Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)