1
0
mirror of https://github.com/aquasecurity/kube-bench.git synced 2024-11-13 19:29:02 +00:00
The Kubernetes Bench for Security is a Go application that checks whether Kubernetes is deployed according to security best practices.
Go to file
2023-05-21 15:46:16 +03:00
.github chore: publish ubi based image (#1412) 2023-04-05 13:02:36 +03:00
cfg support CIS Kubernetes Benchmark v1.7.0 (#1424) 2023-05-21 15:46:16 +03:00
check replace with constant (#1445) 2023-05-16 11:41:49 +03:00
cmd support CIS Kubernetes Benchmark v1.7.0 (#1424) 2023-05-21 15:46:16 +03:00
docs support CIS Kubernetes Benchmark v1.7.0 (#1424) 2023-05-21 15:46:16 +03:00
hack Adding eks-stig-kubernetes-v1r6 (#1266) 2022-09-14 17:40:48 +03:00
hooks
integration/testdata Adding eks-stig-kubernetes-v1r6 (#1266) 2022-09-14 17:40:48 +03:00
internal/findings Migrate to aws-sdk-go-v2 (#1268) 2022-10-03 08:52:06 +03:00
.gitignore release: prepare v0.6.7-rc1 (#1136) 2022-04-03 12:00:08 +03:00
.golangci.yaml chore(lint): setup golangci-lint (#1144) 2022-04-05 16:25:45 +03:00
.goreleaser.yml add darwin builds (#1428) 2023-04-18 21:15:05 +03:00
.yamllint.yaml
codecov.yml
CONTRIBUTING.md Adding eks-stig-kubernetes-v1r6 (#1266) 2022-09-14 17:40:48 +03:00
Dockerfile chore: publish ubi based image (#1412) 2023-04-05 13:02:36 +03:00
Dockerfile.ubi chore: Add license file for ubi image (#1425) 2023-04-17 16:07:31 +03:00
entrypoint.sh
go.mod build(deps): bump github.com/aws/aws-sdk-go-v2 from 1.17.6 to 1.18.0 (#1433) 2023-05-20 18:45:31 +03:00
go.sum build(deps): bump github.com/aws/aws-sdk-go-v2 from 1.17.6 to 1.18.0 (#1433) 2023-05-20 18:45:31 +03:00
job-ack.yaml fix: fully qualified image names (#1206) 2022-06-17 18:01:32 +03:00
job-aks.yaml fix: fully qualified image names (#1206) 2022-06-17 18:01:32 +03:00
job-eks-asff.yaml Support CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v1.1.0 (#1222) 2022-09-15 09:04:54 +03:00
job-eks-stig.yaml Adding eks-stig-kubernetes-v1r6 (#1266) 2022-09-14 17:40:48 +03:00
job-eks.yaml Support CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v1.1.0 (#1222) 2022-09-15 09:04:54 +03:00
job-gke.yaml fix: fully qualified image names (#1206) 2022-06-17 18:01:32 +03:00
job-iks.yaml fix: fully qualified image names (#1206) 2022-06-17 18:01:32 +03:00
job-master.yaml Update job-master.yaml for K8s 1.24.x labels/tolerations (#1250) (#1251) 2022-08-21 09:25:15 +03:00
job-node.yaml fix: fully qualified image names (#1206) 2022-06-17 18:01:32 +03:00
job.yaml release: prepare v0.6.14 (#1446) 2023-05-18 10:32:39 +03:00
LICENSE
main.go
makefile chore: publish ubi based image (#1412) 2023-04-05 13:02:36 +03:00
mkdocs.yml Fixing typos (#899) 2021-06-09 15:11:05 +03:00
NOTICE
OWNERS
README.md Remove broken badges and add link for some badges (#1083) 2022-01-19 10:13:23 +02:00

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

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.