mirror of
https://github.com/aquasecurity/kube-bench.git
synced 2024-11-25 09:28:16 +00:00
f8fe5ee173
* add Support VMware Tanzu(TKGI) Benchmarks v1.2.53 with this change, we are adding 1. latest kubernetes cis benchmarks for VMware Tanzu1.2.53 2. logic to kube-bench so that kube-bench can auto detect vmware platform, will be able to execute the respective vmware tkgi compliance checks. 3. job-tkgi.yaml file to run the benchmark as a job in tkgi cluster Reference Document for checks: https://network.pivotal.io/products/p-compliance-scanner/#/releases/1248397 * add Support VMware Tanzu(TKGI) Benchmarks v1.2.53 with this change, we are adding 1. latest kubernetes cis benchmarks for VMware Tanzu1.2.53 2. logic to kube-bench so that kube-bench can auto detect vmware platform, will be able to execute the respective vmware tkgi compliance checks. 3. job-tkgi.yaml file to run the benchmark as a job in tkgi cluster Reference Document for checks: https://network.pivotal.io/products/p-compliance-scanner/#/releases/1248397 * release: prepare v0.6.15 (#1455) Signed-off-by: chenk <hen.keinan@gmail.com> * build(deps): bump golang from 1.19.4 to 1.20.4 (#1436) Bumps golang from 1.19.4 to 1.20.4. --- updated-dependencies: - dependency-name: golang dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * build(deps): bump actions/setup-go from 3 to 4 (#1402) Bumps [actions/setup-go](https://github.com/actions/setup-go) from 3 to 4. - [Release notes](https://github.com/actions/setup-go/releases) - [Commits](https://github.com/actions/setup-go/compare/v3...v4) --- updated-dependencies: - dependency-name: actions/setup-go dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: chenk <hen.keinan@gmail.com> * Fix test_items in cis-1.7 - node - 4.2.12 (#1469) Related issue: https://github.com/aquasecurity/kube-bench/issues/1468 * Fix node.yaml - 4.1.7 and 4.1.8 audit by adding uniq (#1472) * chore: add fips compliant images (#1473) For fips complaince we need to generate fips compliant images. As part of this change, we will create new kube-bench image which will be fips compliant. Image name follows this tag pattern <version>-ubi-fips * release: prepare v0.6.16-rc (#1476) * release: prepare v0.6.16-rc Signed-off-by: chenk <hen.keinan@gmail.com> * release: prepare v0.6.16-rc Signed-off-by: chenk <hen.keinan@gmail.com> --------- Signed-off-by: chenk <hen.keinan@gmail.com> * release: prepare v0.6.16 official (#1479) Signed-off-by: chenk <hen.keinan@gmail.com> * Update job.yaml (#1477) * Update job.yaml Fix on typo for image version * chore: sync with upstream Signed-off-by: chenk <hen.keinan@gmail.com> --------- Signed-off-by: chenk <hen.keinan@gmail.com> Co-authored-by: chenk <hen.keinan@gmail.com> * release: prepare v0.6.17 (#1480) Signed-off-by: chenk <hen.keinan@gmail.com> * Bump docker base images (#1465) During a recent CVE scan we found kube-bench to use `alpine:3.18` as the final image which has a known high CVE. ``` grype aquasec/kube-bench:v0.6.15 ✔ Vulnerability DB [no update available] ✔ Loaded image ✔ Parsed image ✔ Cataloged packages [73 packages] ✔ Scanning image... [4 vulnerabilities] ├── 0 critical, 4 high, 0 medium, 0 low, 0 negligible └── 4 fixed NAME INSTALLED FIXED-IN TYPE VULNERABILITY SEVERITY libcrypto3 3.1.0-r4 3.1.1-r0 apk CVE-2023-2650 High libssl3 3.1.0-r4 3.1.1-r0 apk CVE-2023-2650 High openssl 3.1.0-r4 3.1.1-r0 apk CVE-2023-2650 High ``` The CVE in question was addressed in the latest [alpine release](https://www.alpinelinux.org/posts/Alpine-3.15.9-3.16.6-3.17.4-3.18.2-released.html), hence updating the dockerfiles accordingly * build(deps): bump golang from 1.20.4 to 1.20.6 (#1475) Bumps golang from 1.20.4 to 1.20.6. --- updated-dependencies: - dependency-name: golang 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> * Add CIS Benchmarks support to Rancher Distributions RKE/RKE2/K3s Based on the information furnished in https://ranchermanager.docs.rancher.com/v2.7/pages-for-subheaders/rancher-hardening-guides kube-bench executes CIS-1.23 (Kubernetes v1.23) , CIS-1.24(Kubernetes v1.24),CIS-1.7 (Kubernetes v1.25,v1.26,v1.27) CIS Benchmarks of respective distributions. * RKE/RKE2 CIS Benchmarks Updated the order of checks for RKE and RKE2 Platforms. * fixed vulnerabilities|upgraded package golang.org/x/net to version v0.17.0 * Error handling for RKE Detection Pre-requisites * Based on the information furnished in https://ranchermanager.docs.rancher.com/v2.7/pages-for-subheaders/rancher-hardening-guides#hardening-guides-and-benchmark-versions, kube-bench executes CIS-1.23 (Kubernetes v1.23) , CIS-1.24(Kubernetes v1.24),CIS-1.7 (Kubernetes v1.25,v1.26,v1.27) CIS Benchmarks of respective distributions. updated documentation specific to added rancher platforms * addressed review comments 1.Implemented IsRKE functionality in kube-bench 2. Removed containerd from global level config and accommodated in individual config file 3. Corrected the control id from 1.2.25 to 1.2.23 in master.yaml(k3s-cis-1.23 and k3s-cis-1.24) * Removed unncessary dependency - kubernetes-provider-detector --------- Signed-off-by: chenk <hen.keinan@gmail.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: chenk <hen.keinan@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Andy Pitcher <andy.pitcher@suse.com> Co-authored-by: Devendra Turkar <devendra.turkar@gmail.com> Co-authored-by: Guille Vigil <contact@guillermotti.com> Co-authored-by: Jonas-Taha El Sesiy <jonas-taha.elsesiy@snowflake.com>
150 lines
5.2 KiB
YAML
150 lines
5.2 KiB
YAML
---
|
|
controls:
|
|
version: "rke-cis-1.24"
|
|
id: 2
|
|
text: "Etcd Node Configuration"
|
|
type: "etcd"
|
|
groups:
|
|
- id: 2
|
|
text: "Etcd Node Configuration"
|
|
checks:
|
|
- id: 2.1
|
|
text: "Ensure that the --cert-file and --key-file arguments are set as appropriate (Automated)"
|
|
audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
|
|
tests:
|
|
bin_op: and
|
|
test_items:
|
|
- flag: "--cert-file"
|
|
env: "ETCD_CERT_FILE"
|
|
set: true
|
|
- flag: "--key-file"
|
|
env: "ETCD_KEY_FILE"
|
|
set: true
|
|
remediation: |
|
|
Follow the etcd service documentation and configure TLS encryption.
|
|
Then, edit the etcd pod specification file /etc/kubernetes/manifests/etcd.yaml
|
|
on the master node and set the below parameters.
|
|
--cert-file=</path/to/ca-file>
|
|
--key-file=</path/to/key-file>
|
|
scored: true
|
|
|
|
- id: 2.2
|
|
text: "Ensure that the --client-cert-auth argument is set to true (Automated)"
|
|
audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
|
|
tests:
|
|
bin_op: or
|
|
test_items:
|
|
- flag: "--client-cert-auth"
|
|
set: true
|
|
- flag: "--client-cert-auth"
|
|
env: "ETCD_CLIENT_CERT_AUTH"
|
|
compare:
|
|
op: eq
|
|
value: true
|
|
set: true
|
|
remediation: |
|
|
Edit the etcd pod specification file $etcdconf on the master
|
|
node and set the below parameter.
|
|
--client-cert-auth="true"
|
|
scored: true
|
|
|
|
- id: 2.3
|
|
text: "Ensure that the --auto-tls argument is not set to true (Automated)"
|
|
audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
|
|
tests:
|
|
bin_op: or
|
|
test_items:
|
|
- flag: "--auto-tls"
|
|
env: "ETCD_AUTO_TLS"
|
|
set: false
|
|
- flag: "--auto-tls"
|
|
env: "ETCD_AUTO_TLS"
|
|
compare:
|
|
op: eq
|
|
value: false
|
|
remediation: |
|
|
Edit the etcd pod specification file $etcdconf on the master
|
|
node and either remove the --auto-tls parameter or set it to false.
|
|
--auto-tls=false
|
|
scored: true
|
|
|
|
- id: 2.4
|
|
text: "Ensure that the --peer-cert-file and --peer-key-file arguments are
|
|
set as appropriate (Automated)"
|
|
audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
|
|
tests:
|
|
bin_op: and
|
|
test_items:
|
|
- flag: "--peer-cert-file"
|
|
env: "ETCD_PEER_CERT_FILE"
|
|
set: true
|
|
- flag: "--peer-key-file"
|
|
env: "ETCD_PEER_KEY_FILE"
|
|
set: true
|
|
remediation: |
|
|
Follow the etcd service documentation and configure peer TLS encryption as appropriate
|
|
for your etcd cluster.
|
|
Then, edit the etcd pod specification file $etcdconf on the
|
|
master node and set the below parameters.
|
|
--peer-client-file=</path/to/peer-cert-file>
|
|
--peer-key-file=</path/to/peer-key-file>
|
|
scored: true
|
|
|
|
- id: 2.5
|
|
text: "Ensure that the --peer-client-cert-auth argument is set to true (Automated)"
|
|
audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
|
|
tests:
|
|
bin_op: or
|
|
test_items:
|
|
- flag: "--peer-client-cert-auth"
|
|
set: true
|
|
- flag: "--peer-client-cert-auth"
|
|
env: "ETCD_PEER_CLIENT_CERT_AUTH"
|
|
compare:
|
|
op: eq
|
|
value: true
|
|
set: true
|
|
remediation: |
|
|
Edit the etcd pod specification file $etcdconf on the master
|
|
node and set the below parameter.
|
|
--peer-client-cert-auth=true
|
|
scored: true
|
|
|
|
- id: 2.6
|
|
text: "Ensure that the --peer-auto-tls argument is not set to true (Automated)"
|
|
audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
|
|
tests:
|
|
bin_op: or
|
|
test_items:
|
|
- flag: "--peer-auto-tls"
|
|
env: "ETCD_PEER_AUTO_TLS"
|
|
set: false
|
|
- flag: "--peer-auto-tls"
|
|
env: "ETCD_PEER_AUTO_TLS"
|
|
compare:
|
|
op: eq
|
|
value: false
|
|
set: false
|
|
remediation: |
|
|
Edit the etcd pod specification file $etcdconf on the master
|
|
node and either remove the --peer-auto-tls parameter or set it to false.
|
|
--peer-auto-tls=false
|
|
scored: true
|
|
|
|
- id: 2.7
|
|
text: "Ensure that a unique Certificate Authority is used for etcd (Automated)"
|
|
audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
|
|
tests:
|
|
test_items:
|
|
- flag: "--trusted-ca-file"
|
|
env: "ETCD_TRUSTED_CA_FILE"
|
|
set: true
|
|
remediation: |
|
|
[Manual test]
|
|
Follow the etcd documentation and create a dedicated certificate authority setup for the
|
|
etcd service.
|
|
Then, edit the etcd pod specification file $etcdconf on the
|
|
master node and set the below parameter.
|
|
--trusted-ca-file=</path/to/ca-file>
|
|
scored: true
|