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,305–23,328 of 31,789 skills
- Cis K8s V200 4.2.3Ensure that the --client-ca-file argument is set as appropriate (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.2.2Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.2.14Ensure that the --seccomp-default parameter is set to true (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.2.13Ensure that a limit is set on pod PIDs (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.2.12Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.2.11Verify that the RotateKubeletServerCertificate argument is set to true (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.2.10Ensure that the --rotate-certificates argument is not set to false (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.2.1Ensure that the --anonymous-auth argument is set to false (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.9If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.8Ensure that the client certificate authorities file ownership is set to root:root (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.7Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.6Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.5Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.4If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.3If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.2Ensure that the kubelet service file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.10If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 4.1.1Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis K8s V200 3.2.2Ensure that the audit policy covers key security concerns (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 3.2.1Ensure that a minimal audit policy is created (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 3.1.3Bootstrap token authentication should not be used for users (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 3.1.2Service account token authentication should not be used for users (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 3.1.1Client certificate authentication should not be used for users (Manual)Votes: 0GitHub stars: 3,518
- Cis K8s V200 2.7Ensure that a unique Certificate Authority is used for etcd (Manual)Votes: 0GitHub stars: 3,518