All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills0 installs16,544 views
- Cis Gke V190 4.5.1Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 4.6.1Create administrative boundaries between resources using namespaces (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 4.6.2Ensure that the seccomp profile is set to RuntimeDefault in the pod definitions (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 4.6.3Apply Security Context to Pods and Containers (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 4.6.4The default namespace should not be used (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.1.1Ensure Image Vulnerability Scanning is enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.1.2Minimize user access to Container Image repositories (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.1.3Minimize cluster access to read-only for Container Image repositories (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.1.4Ensure only trusted container images are used (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.10.1Ensure Kubernetes Web UI is Disabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.10.2Ensure that Alpha clusters are not used for production workloads (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.10.3Consider GKE Sandbox for running untrusted workloads (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.10.4Enable Security Posture (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.2.1Ensure GKE clusters are not running using the Compute Engine default service account (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.2.2Prefer using dedicated GCP Service Accounts and Workload Identity (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.3.1Ensure Kubernetes Secrets are encrypted using keys managed in Cloud KMS (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.4.1Ensure the GKE Metadata Server is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.5.1Ensure Container-Optimized OS (cos_containerd) is used for GKE node images (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.5.2Ensure Node Auto-Repair is enabled for GKE nodes (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.5.3Ensure Node Auto-Upgrade is enabled for GKE nodes (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.5.4When creating New Clusters - Automate GKE version management using Release Channels (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.5.5Ensure Shielded GKE Nodes are Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.5.6Ensure Integrity Monitoring for Shielded GKE Nodes is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.5.7Ensure Secure Boot for Shielded GKE Nodes is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.6.1Enable VPC Flow Logs and Intranode Visibility (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.6.2Ensure use of VPC-native clusters (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.6.3Ensure Control Plane Authorized Networks is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.6.4Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.6.5Ensure clusters are created with Private Nodes (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.6.6Consider firewalling GKE worker nodes (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.6.7Ensure use of Google-managed SSL Certificates (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.7.1Ensure Logging and Cloud Monitoring is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.7.2Enable Linux auditd logging (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.8.1Ensure authentication using Client Certificates is Disabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.8.2Manage Kubernetes RBAC users with groups in Google Workspace (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.8.3Ensure Legacy Authorization (ABAC) is Disabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.9.1Enable Customer-Managed Encryption Keys (CMEK) for GKE Persistent Disks (PD) (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V190 5.9.2Enable Customer-Managed Encryption Keys (CMEK) for Boot Disks (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.1Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.10Ensure that the Container Network Interface file ownership is set to root:root (Manual)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.11Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.12Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.13Ensure that the default administrative credential file permissions are set to 600 (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.14Ensure that the default administrative credential file ownership is set to root:root (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.15Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.16Ensure that the scheduler.conf file ownership is set to root:root (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.17Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.18Ensure that the controller-manager.conf file ownership is set to root:root (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.19Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)Votes: 0GitHub stars: 2,182
- Cis K8s V1110 1.1.2Ensure that the API server pod specification file ownership is set to root:root (Automated)Votes: 0GitHub stars: 2,182