1
0
mirror of https://github.com/aquasecurity/kube-bench.git synced 2024-12-21 06:08:06 +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
dependabot[bot] cce6b9d24f
build(deps): bump github.com/magiconair/properties from 1.8.7 to 1.8.9 ()
Bumps [github.com/magiconair/properties](https://github.com/magiconair/properties) from 1.8.7 to 1.8.9.
- [Release notes](https://github.com/magiconair/properties/releases)
- [Commits](https://github.com/magiconair/properties/compare/v1.8.7...v1.8.9)

---
updated-dependencies:
- dependency-name: github.com/magiconair/properties
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-12-12 13:39:04 +06:00
.github build(deps): bump codecov/codecov-action from 4 to 5 () 2024-11-19 12:14:09 +06:00
cfg fix: change the folder name for certificate files in rke-cis-1.7 2024-12-09 11:16:04 +06:00
check Fix issue 1595: failed to output to ASFF () 2024-09-28 13:36:44 +06:00
cmd Add GKE 1.6 CIS benchmark for GCP environment () 2024-10-11 10:49:35 +06:00
docs Add GKE 1.6 CIS benchmark for GCP environment () 2024-10-11 10:49:35 +06:00
hack Adding eks-stig-kubernetes-v1r6 () 2022-09-14 17:40:48 +03:00
helper_scripts FIX| RKE-CIS-1.24- CHECK 1.1.19 () 2024-11-15 18:32:24 +06:00
hooks adds kube-bench version to docker build hook () 2019-11-27 20:06:42 +00:00
integration/testdata fix: correct TLSCipherSuites to tlsCipherSuites () 2024-10-16 11:50:10 +06:00
internal/findings Fix issue 1595: failed to output to ASFF () 2024-09-28 13:36:44 +06:00
.gitignore release: prepare v0.6.7-rc1 () 2022-04-03 12:00:08 +03:00
.golangci.yaml chore(lint): setup golangci-lint () 2022-04-05 16:25:45 +03:00
.goreleaser.yml Statically link binaries and remove debug information () 2024-05-22 08:37:36 +03:00
.yamllint.yaml Support Linting YAML as part of Travis CI build () 2020-01-06 09:18:25 +00:00
codecov.yml Improve Proxykubeconfig tests () 2020-10-07 21:53:34 +03:00
CONTRIBUTING.md Adding eks-stig-kubernetes-v1r6 () 2022-09-14 17:40:48 +03:00
Dockerfile build(deps): bump golang from 1.23.3 to 1.23.4 () 2024-12-12 13:23:48 +06:00
Dockerfile.fips.ubi build(deps): bump golang from 1.23.3 to 1.23.4 () 2024-12-12 13:23:48 +06:00
Dockerfile.ubi build(deps): bump golang from 1.23.3 to 1.23.4 () 2024-12-12 13:23:48 +06:00
entrypoint.sh Set -e to fail fast 2018-05-11 13:44:04 -04:00
fipsonly.go chore: add fips compliant images () 2023-07-24 10:02:19 +03:00
go.mod build(deps): bump github.com/magiconair/properties from 1.8.7 to 1.8.9 () 2024-12-12 13:39:04 +06:00
go.sum build(deps): bump github.com/magiconair/properties from 1.8.7 to 1.8.9 () 2024-12-12 13:39:04 +06:00
job-ack.yaml fix: fully qualified image names () 2022-06-17 18:01:32 +03:00
job-aks.yaml fix: fully qualified image names () 2022-06-17 18:01:32 +03:00
job-eks-asff.yaml support CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v1.2.0 () 2023-05-21 17:53:58 +03:00
job-eks-stig.yaml Adding eks-stig-kubernetes-v1r6 () 2022-09-14 17:40:48 +03:00
job-eks.yaml support CIS Amazon Elastic Kubernetes Service (EKS) Benchmark v1.2.0 () 2023-05-21 17:53:58 +03:00
job-gke.yaml fix: fully qualified image names () 2022-06-17 18:01:32 +03:00
job-iks.yaml fix: fully qualified image names () 2022-06-17 18:01:32 +03:00
job-master.yaml job.yaml: Adding /var/lib/cni mounts for proper CIS 1.1.9 and 1.1.0 checking () 2024-02-11 11:23:17 +02:00
job-node.yaml job.yaml: Adding /var/lib/cni mounts for proper CIS 1.1.9 and 1.1.0 checking () 2024-02-11 11:23:17 +02:00
job-tkgi.yaml add support VMware Tanzu(TKGI) Benchmarks v1.2.53 () 2023-06-01 16:37:50 +03:00
job.yaml release: prepare v0.9.3 () 2024-12-09 14:38:35 +06:00
LICENSE Initial commit 2017-06-19 17:01:57 +03:00
main.go Fix issue about supporting verbosity. 2017-07-07 17:01:30 +00:00
makefile Updated KUBECTL_VERSION to 1.31.0 for fixing vulnerabilities () 2024-10-03 22:43:01 +06:00
mkdocs.yml Fixing typos () 2021-06-09 15:11:05 +03:00
NOTICE Create NOTICE () 2019-01-16 10:53:07 +02:00
OWNERS Create OWNERS 2017-08-11 16:06:44 +01:00
README.md updates to the readme 2023-10-02 12:39:24 +03: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

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.