All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 31,788
- 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 22,849–22,872 of 31,788 skills
- Cis Ocp V160 4.1.8Ensure that the client certificate authorities file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.7Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.6Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.5Ensure that the --kubeconfig kubelet.conf file permissions are set to 644 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.4If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.3If proxy kube proxy configuration file exists ensure permissions are set to 644 or more restrictive (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.2Ensure that the kubelet service file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.10Ensure that the kubelet configuration file ownership is set to root:root (Automated)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 4.1.1Ensure that the kubelet service file permissions are set to 644 or more restrictive (Automated)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 3.2.2Ensure that the audit policy covers key security concerns (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 3.2.1Ensure that a minimal audit policy is created (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 3.1.1Client certificate authentication should not be used for users (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 2.7Ensure that a unique Certificate Authority is used for etcd (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 2.6Ensure that the --peer-auto-tls argument is not set to true (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 2.5Ensure that the --peer-client-cert-auth argument is set to true (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 2.4Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 2.3Ensure that the --auto-tls argument is not set to true (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 2.2Ensure that the --client-cert-auth argument is set to true (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 2.1Ensure that the --cert-file and --key-file arguments are set as appropriate (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 1.4.2Verify that the scheduler API service is protected by RBAC (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 1.4.1Ensure that the healthz endpoints for the scheduler are protected by RBAC (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 1.3.5Ensure that the --bind-address argument is set to 127.0.0.1 (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 1.3.4Ensure that the --root-ca-file argument is set as appropriate (Manual)Votes: 0GitHub stars: 3,518
- Cis Ocp V160 1.3.3Ensure that the --service-account-private-key-file argument is set as appropriate (Manual)Votes: 0GitHub stars: 3,518