Skip to content
Snippets Groups Projects
Select Git revision
  • main
  • lihiz_preflight
  • release/prepare-v0.10.7
  • dependabot/github_actions/golangci/golangci-lint-action-7
  • release/prepare-v0.9.1
  • gh-pages
  • aquadev
  • v0.11.2
  • v0.11.1
  • v0.11.0
  • v0.10.7
  • v0.10.6
  • v0.10.5
  • v0.10.4
  • v0.10.3
  • v0.10.2
  • v0.10.1
  • v0.10.0
  • v0.9.4
  • v0.9.3
  • v0.9.2
  • v0.9.1
  • v0.9.0
  • v0.8.0
  • v0.7.3
  • v0.7.2
  • v0.7.1
27 results

kube-bench

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    mjshastha authored and GitHub committed
    a02030bd
    History

    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.