1
0
mirror of https://github.com/aquasecurity/kube-bench.git synced 2024-11-22 08:08:07 +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
2021-06-20 11:23:24 +03:00
.github Add git config user (#901) 2021-06-14 12:13:48 +03:00
cfg Fix values of version field in cfg/cis-1.20 were wrong (#913) 2021-06-20 11:23:24 +03:00
check Add detected kubernetes version (#869) 2021-05-09 14:48:34 +03:00
cmd New cis v1.20 (#912) 2021-06-16 20:55:04 +03:00
docs mkdocs support and update docs (#884) 2021-06-09 11:17:16 +03:00
hack retire cis 1.3 and 1.4 (#693) 2020-10-03 11:23:28 +01:00
hooks adds kube-bench version to docker build hook (#524) 2019-11-27 20:06:42 +00:00
integration New cis v1.20 (#912) 2021-06-16 20:55:04 +03:00
internal/findings Aws asff (#770) 2020-11-23 19:43:53 +00:00
.gitignore Added .DS_Store and thumbs.db to .gitignore (#463) 2019-10-24 09:04:13 +01:00
.goreleaser.yml Fix issue with missing 'Maintainer' field (#875) 2021-05-20 11:21:04 +03:00
.yamllint.yaml Support Linting YAML as part of Travis CI build (#554) 2020-01-06 09:18:25 +00:00
codecov.yml Improve Proxykubeconfig tests (#708) 2020-10-07 21:53:34 +03:00
CONTRIBUTING.md mkdocs support and update docs (#884) 2021-06-09 11:17:16 +03:00
Dockerfile Fix ocp job issues (#893) 2021-06-09 15:34:39 +03:00
entrypoint.sh Set -e to fail fast 2018-05-11 13:44:04 -04:00
go.mod Update go modules 1.16 (#910) 2021-06-16 17:26:51 +03:00
go.sum Update go modules 1.16 (#910) 2021-06-16 17:26:51 +03:00
job-ack.yaml Support CIS ACK 1.0.0 benchmark (#841) 2021-05-11 11:52:24 +03:00
job-aks.yaml cfg: add /etc/default/kubeletconfig.json for AKS (#865) 2021-05-11 12:37:25 +03:00
job-eks-asff.yaml Refactor of EKS and ASFF integration Job and instructions (#794) 2021-02-22 14:28:36 +00:00
job-eks.yaml Refactor of EKS and ASFF integration Job and instructions (#794) 2021-02-22 14:28:36 +00:00
job-gke.yaml CIS GKE 1.0.0 benchmark (#570) 2020-03-03 09:51:48 -05:00
job-iks.yaml Set all host-mounted volumes to be read-only. (#569) 2020-01-28 10:45:31 -05:00
job-master.yaml mount /etc/passwd and /etc/group for etcd ownership related checks (#868) 2021-05-09 14:25:14 +03:00
job-node.yaml Fix file permissions false positive (#800) 2021-04-08 17:02:27 +03:00
job.yaml Fix file permissions false positive (#800) 2021-04-08 17:02:27 +03:00
LICENSE Initial commit 2017-06-19 17:01:57 +03:00
main.go Fix issue #16 about supporting verbosity. 2017-07-07 17:01:30 +00:00
makefile Fix go vet issues (#720) 2020-10-09 15:56:22 +01:00
mkdocs.yml Fixing typos (#899) 2021-06-09 15:11:05 +03:00
NOTICE Create NOTICE (#199) 2019-01-16 10:53:07 +02:00
OWNERS Create OWNERS 2017-08-11 16:06:44 +01:00
README.md mkdocs support and update docs (#884) 2021-06-09 11:17:16 +03:00

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

kube-bench logo

kube-bench is 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.