All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills0 installs16,544 views
- Cis Gke V170 5.2.2Prefer using dedicated GCP Service Accounts and Workload Identity (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.3.1Ensure Kubernetes Secrets are encrypted using keys managed in Cloud KMS (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.4.1Ensure the GKE Metadata Server is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.5.1Ensure Container-Optimized OS (cos_containerd) is used for GKE node images (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.5.2Ensure Node Auto-Repair is enabled for GKE nodes (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.5.3Ensure Node Auto-Upgrade is enabled for GKE nodes (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.5.4When creating New Clusters - Automate GKE version management using Release Channels (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.5.5Ensure Shielded GKE Nodes are Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.5.6Ensure Integrity Monitoring for Shielded GKE Nodes is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.5.7Ensure Secure Boot for Shielded GKE Nodes is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.6.1Enable VPC Flow Logs and Intranode Visibility (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.6.2Ensure use of VPC-native clusters (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.6.3Ensure Control Plane Authorized Networks is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.6.4Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.6.5Ensure clusters are created with Private Nodes (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.6.6Consider firewalling GKE worker nodes (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.6.7Ensure use of Google-managed SSL Certificates (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.7.1Ensure Logging and Cloud Monitoring is Enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.7.2Enable Linux auditd logging (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.8.1Ensure authentication using Client Certificates is Disabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.8.2Manage Kubernetes RBAC users with Google Groups for GKE (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.8.3Ensure Legacy Authorization (ABAC) is Disabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.9.1Enable Customer-Managed Encryption Keys (CMEK) for GKE Persistent Disks (PD) (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V170 5.9.2Enable Customer-Managed Encryption Keys (CMEK) for Boot Disks (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 3.1.1Ensure that the kubeconfig file permissions are set to 644 or more restrictive (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 3.1.2Ensure that the kubelet kubeconfig file ownership is set to root:root (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 3.1.3Ensure that the kubelet configuration file has permissions set to 644 (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 3.1.4Ensure that the kubelet configuration file ownership is set to root:root (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.1Ensure that the cluster-admin role is only used where required (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.10Avoid non-default bindings to system:authenticated (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.2Minimize access to secrets (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.3Minimize wildcard use in Roles and ClusterRoles (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.4Ensure that default service accounts are not actively used (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.5Ensure that Service Account Tokens are only mounted where necessary (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.6Avoid use of system:masters group (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.7Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.8Avoid bindings to system:anonymous (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.1.9Avoid non-default bindings to system:unauthenticated (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.2.1Ensure that the cluster enforces Pod Security Standard Baseline profile or stricter for all namespaces (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.3.1Ensure that the CNI in use supports Network Policies (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.3.2Ensure that all Namespaces have Network Policies defined (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.4.1Prefer using secrets as files over secrets as environment variables (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.4.2Consider external secret storage (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.5.1Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.6.1Create administrative boundaries between resources using namespaces (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.6.2Ensure that the seccomp profile is set to RuntimeDefault in the pod definitions (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.6.3Apply Security Context to Pods and Containers (Manual)Votes: 0GitHub stars: 2,182
- Cis Gke V180 4.6.4The default namespace should not be used (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 5.1.1Ensure Image Vulnerability Scanning is enabled (Automated)Votes: 0GitHub stars: 2,182
- Cis Gke V180 5.1.2Minimize user access to Container Image repositories (Manual)Votes: 0GitHub stars: 2,182