The Kubernetes Bench for Security is a Go application that checks whether Kubernetes is deployed according to security best practices.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
dependabot[bot] 246205a0fb
build(deps): bump github.com/aws/aws-sdk-go-v2/service/securityhub
4 天之前
.github build(deps): bump golangci/golangci-lint-action from 3 to 4 (#1568) 1 月之前
cfg update rke-cis-1.24 benchmarks: corrected errors and tests (#1570) 1 月之前
check chore: remove refs to deprecated io/ioutil (#1504) 4 月之前
cmd chore: remove refs to deprecated io/ioutil (#1504) 4 月之前
docs support CIS Kubernetes Benchmark v1.8.0 (#1527) 4 月之前
hack Adding eks-stig-kubernetes-v1r6 (#1266) 2 年之前
hooks adds kube-bench version to docker build hook (#524) 4 年之前
integration/testdata fix wrong use of flag in test_items found in 4.13 and 4.14 (#1528) 4 月之前
internal/findings Migrate to aws-sdk-go-v2 (#1268) 2 年之前
.gitignore release: prepare v0.6.7-rc1 (#1136) 2 年之前
.golangci.yaml chore(lint): setup golangci-lint (#1144) 2 年之前
.goreleaser.yml add darwin builds (#1428) 12 月之前
.yamllint.yaml Support Linting YAML as part of Travis CI build (#554) 4 年之前
CONTRIBUTING.md Adding eks-stig-kubernetes-v1r6 (#1266) 2 年之前
Dockerfile build(deps): bump golang from 1.21.6 to 1.22.0 (#1569) 1 月之前
Dockerfile.fips.ubi build(deps): bump golang from 1.21.6 to 1.22.0 (#1569) 1 月之前
Dockerfile.ubi build(deps): bump golang from 1.21.6 to 1.22.0 (#1569) 1 月之前
LICENSE Initial commit 7 年之前
NOTICE Create NOTICE (#199) 5 年之前
OWNERS Create OWNERS 7 年之前
README.md updates to the readme 6 月之前
codecov.yml Improve Proxykubeconfig tests (#708) 4 年之前
entrypoint.sh Set -e to fail fast 6 年之前
fipsonly.go chore: add fips compliant images (#1473) 8 月之前
go.mod build(deps): bump github.com/aws/aws-sdk-go-v2/service/securityhub 4 天之前
go.sum build(deps): bump github.com/aws/aws-sdk-go-v2/service/securityhub 4 天之前
job-ack.yaml fix: fully qualified image names (#1206) 2 年之前
job-aks.yaml fix: fully qualified image names (#1206) 2 年之前
job-eks-asff.yaml support CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v1.2.0 (#1449) 10 月之前
job-eks-stig.yaml Adding eks-stig-kubernetes-v1r6 (#1266) 2 年之前
job-eks.yaml support CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v1.2.0 (#1449) 10 月之前
job-gke.yaml fix: fully qualified image names (#1206) 2 年之前
job-iks.yaml fix: fully qualified image names (#1206) 2 年之前
job-master.yaml job.yaml: Adding /var/lib/cni mounts for proper CIS 1.1.9 and 1.1.0 checking (#1547) 2 月之前
job-node.yaml job.yaml: Adding /var/lib/cni mounts for proper CIS 1.1.9 and 1.1.0 checking (#1547) 2 月之前
job-tkgi.yaml add support VMware Tanzu(TKGI) Benchmarks v1.2.53 (#1452) 10 月之前
job.yaml release: prepare v0.7.2 (#1578) 4 週之前
main.go Fix issue #16 about supporting verbosity. 7 年之前
makefile chore: add fips compliant images (#1473) 8 月之前
mkdocs.yml Fixing typos (#899) 3 年之前

README.md

GitHub Release Downloads Docker Pulls Go Report Card Build Status License Coverage Status

kube-bench logo

kube-bench is a tool that checks whether Kubernetes is deployed securely by running the checks documented in the CIS Kubernetes Benchmark.

Tests are configured with YAML files, making this tool easy to update as test specifications evolve.

Kubernetes Bench for Security

CIS Scanning as part of Trivy and the Trivy Operator

Trivy, the all in one cloud native security scanner, can be deployed as a Kubernetes Operator inside a cluster. Both, the Trivy CLI, and the Trivy Operator support CIS Kubernetes Benchmark scanning among several other features.

Quick start

There are multiple ways to run kube-bench. You can run kube-bench inside a pod, but it will need access to the host's PID namespace in order to check the running processes, as well as access to some directories on the host where config files and other files are stored.

The supplied job.yaml file can be applied to run the tests as a job. For example:

$ kubectl apply -f job.yaml
job.batch/kube-bench created

$ kubectl get pods
NAME                      READY   STATUS              RESTARTS   AGE
kube-bench-j76s9   0/1     ContainerCreating   0          3s

# Wait for a few seconds for the job to complete
$ kubectl get pods
NAME                      READY   STATUS      RESTARTS   AGE
kube-bench-j76s9   0/1     Completed   0          11s

# The results are held in the pod's logs
kubectl logs kube-bench-j76s9
[INFO] 1 Master Node Security Configuration
[INFO] 1.1 API Server
...

For more information and different ways to run kube-bench see documentation

Please Note

  1. kube-bench implements the CIS Kubernetes Benchmark as closely as possible. Please raise issues here if kube-bench is not correctly implementing the test as described in the Benchmark. To report issues in the Benchmark itself (for example, tests that you believe are inappropriate), please join the CIS community.

  2. There is not a one-to-one mapping between releases of Kubernetes and releases of the CIS benchmark. See CIS Kubernetes Benchmark support to see which releases of Kubernetes are covered by different releases of the benchmark.

By default, kube-bench will determine the test set to run based on the Kubernetes version running on the machine.

Contributing

Kindly read Contributing before contributing. We welcome PRs and issue reports.

Roadmap

Going forward we plan to release updates to kube-bench to add support for new releases of the CIS Benchmark. Note that these are not released as frequently as Kubernetes releases.