All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 31,789
- 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,377–23,400 of 31,789 skills
- Cis K8s V200 1.1.6Ensure that the scheduler pod specification file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.5Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.4Ensure that the controller manager pod specification file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.3Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.21Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.20Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.2Ensure that the API server pod specification file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.19Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.18Ensure that the controller-manager.conf file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.17Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.16Ensure that the scheduler.conf file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.15Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.14Ensure that the default administrative credential file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.13Ensure that the default administrative credential file permissions are set to 600 (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.12Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.11Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.10Ensure that the Container Network Interface file ownership is set to root:root (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 1.1.1Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V1120 5.6.4The default namespace should not be used (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V1120 5.6.3Apply Security Context to Your Pods and Containers (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V1120 5.6.2Ensure that the seccomp profile is set to docker/default in your pod definitions (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V1120 5.6.1Create administrative boundaries between resources using namespaces (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V1120 5.5.1Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V1120 5.4.2Consider external secret storage (Manual)Votes: 0GitHub stars: 3,518