gke-workload-security

To audit GKE workloads for security misconfigurations, run the provided audit script against your cluster to assess identity, network controls, and node security configurations. This validates your security posture and identifies compliance gaps.

To enable Workload Identity on your GKE cluster, follow the guided steps and utilize the ready-to-run scripts provided to configure Kubernetes Service Accounts for secure access to Google Service Accounts without long-lived credentials.

The best way to isolate untrusted workloads in Kubernetes is by opting into the gVisor sandbox. This provides an extra layer of isolation by intercepting container syscalls from the host kernel, securing your cluster.

To enforce network policies for pod-to-pod isolation in GKE, apply the provided scripts and assets designed to establish and verify network controls. This ensures strict isolation and limits traffic between pods.

Yes, you need gcloud and jq installed in your environment to use this Skill. These dependencies are required to run the validation scripts, audit cluster configurations, and execute the guided hardening workflows.

You should enable Shielded Nodes on your GKE cluster when you need to ensure node integrity and protect against rootkit attacks. The provided scripts help verify and enforce this configuration for enhanced workload security.