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,929–23,952 of 31,791 skills
- Cis Gke V170 5.5.3Ensure Node Auto-Upgrade is enabled for GKE nodes (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.5.2Ensure Node Auto-Repair is enabled for GKE nodes (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.5.1Ensure Container-Optimized OS (cos_containerd) is used for GKE node images (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.4.1Ensure the GKE Metadata Server is Enabled (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.3.1Ensure Kubernetes Secrets are encrypted using keys managed in Cloud KMS (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.2.2Prefer using dedicated GCP Service Accounts and Workload Identity (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.2.1Ensure GKE clusters are not running using the Compute Engine default service account (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.10.5Enable Security Posture (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.10.4Ensure use of Binary Authorization (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.10.3Consider GKE Sandbox for running untrusted workloads (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.10.2Ensure that Alpha clusters are not used for production workloads (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.10.1Ensure Kubernetes Web UI is Disabled (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.1.4Ensure only trusted container images are used (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.1.3Minimize cluster access to read-only for Container Image repositories (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.1.2Minimize user access to Container Image repositories (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 5.1.1Ensure Image Vulnerability Scanning is enabled (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.6.4The default namespace should not be used (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.6.3Apply Security Context to Pods and Containers (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.6.2Ensure that the seccomp profile is set to RuntimeDefault in the pod definitions (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.6.1Create administrative boundaries between resources using namespaces (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.5.1Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.4.2Consider external secret storage (Manual)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.4.1Prefer using secrets as files over secrets as environment variables (Automated)Votes: 0GitHub stars: 3,518
- Cis Gke V170 4.3.2Ensure that all Namespaces have Network Policies defined (Automated)Votes: 0GitHub stars: 3,518