All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 31,791
- 1,325
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse security skills
Showing 23,977–24,000 of 31,791 skills
- Cis Gke V170 3.1.1Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.7.1Enable Security Posture (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.6.1Enable Customer-Managed Encryption Keys (CMEK) for GKE Persistent Disks (PD) (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.5.1Manage Kubernetes RBAC users with Google Groups for GKE (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.4.5Ensure use of Google-managed SSL Certificates (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.4.4Ensure clusters are created with Private Nodes (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.4.3Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.4.2Ensure Control Plane Authorized Networks is Enabled (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.4.1Enable VPC Flow Logs and Intranode Visibility (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.3.1Ensure Kubernetes Secrets are encrypted using keys managed in Cloud KMS (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.2.1Ensure GKE clusters are not running using the Compute Engine default service account (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.1.4Ensure only trusted container images are used (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.1.3Minimize cluster access to read-only for Container Image repositories (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.1.2Minimize user access to Container Image repositories (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 5.1.1Ensure Image Vulnerability Scanning is enabled (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.6.4The default namespace should not be used (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.6.3Apply Security Context to Pods and Containers (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.6.2Ensure that the seccomp profile is set to RuntimeDefault in the pod definitions (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.6.1Create administrative boundaries between resources using namespaces (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.5.1Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.4.1Consider external secret storage (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.3.1Ensure that all Namespaces have Network Policies defined (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.2.1Ensure that the cluster enforces Pod Security Standard Baseline profile or stricter for all namespaces (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke Autopilot V130 4.1.9Avoid non-default bindings to system:unauthenticated (Automated)Votes: 0GitHub stars: 3,518