release: prepare v0.6.12-rc

Signed-off-by: chenk <hen.keinan@gmail.com>

.github/workflows/build.yml

@@ -14,56 +14,56 @@ on:
       - "LICENSE"
       - "NOTICE"
 env:
-  GO_VERSION: "1.23.6"
+  GO_VERSION: "1.19"
   KIND_VERSION: "v0.11.1"
   KIND_IMAGE: "kindest/node:v1.21.1@sha256:69860bda5563ac81e3c0057d654b5253219618a22ec3a346306239bba8cfa1a6"
 
 jobs:
   lint:
     name: Lint
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     steps:
       - name: Setup Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v3
         with:
           go-version: ${{ env.GO_VERSION }}
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v3
       - name: yaml-lint
         uses: ibiqlik/action-yamllint@v3
       - name: Setup golangci-lint
-        uses: golangci/golangci-lint-action@v8
+        uses: golangci/golangci-lint-action@v3
         with:
-          version: v2.5.0
-          args: --verbose --timeout 2m
+          version: latest
+          args: --verbose
   unit:
     name: Unit tests
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     steps:
       - name: Setup Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v3
         with:
           go-version: ${{ env.GO_VERSION }}
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v3
       - name: Run unit tests
         run: make tests
       - name: Upload code coverage
-        uses: codecov/codecov-action@v5
+        uses: codecov/codecov-action@v3
         with:
           file: ./coverage.txt
   e2e:
     name: E2e tests
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     steps:
       - name: Setup Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v3
         with:
           go-version: ${{ env.GO_VERSION }}
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v3
       - name: Setup Kubernetes cluster (KIND)
-        uses: engineerd/setup-kind@v0.6.2
+        uses: engineerd/setup-kind@v0.5.0
         with:
           version: ${{ env.KIND_VERSION }}
           image: ${{ env.KIND_IMAGE }}
@@ -83,19 +83,19 @@ jobs:
           expected_result: PASSED
   release:
     name: Release snapshot
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     needs: [e2e, unit]
     steps:
       - name: Setup Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v3
         with:
           go-version: ${{ env.GO_VERSION }}
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v3
         with:
           fetch-depth: 0
       - name: Dry-run release snapshot
-        uses: goreleaser/goreleaser-action@v6
+        uses: goreleaser/goreleaser-action@v4
         with:
           distribution: goreleaser
           version: v1.7.0

.github/workflows/mkdocs-deploy.yaml

@@ -13,14 +13,14 @@ on:
 jobs:
   deploy:
     name: Deploy documentation
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     steps:
       - name: Checkout main
-        uses: actions/checkout@v5
+        uses: actions/checkout@v3
         with:
           fetch-depth: 0
           persist-credentials: true
-      - uses: actions/setup-python@v6
+      - uses: actions/setup-python@v4
         with:
           python-version: 3.x
       - run: |

.github/workflows/publish.yml

@@ -9,51 +9,47 @@ env:
   ALIAS: aquasecurity
   DOCKERHUB_ALIAS: aquasec
   REP: kube-bench
-
 jobs:
   publish:
     name: Publish
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     steps:
       - name: Check Out Repo
-        uses: actions/checkout@v5
+        uses: actions/checkout@v3
       - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3
+        uses: docker/setup-qemu-action@v2
       - name: Set up Docker Buildx
         id: buildx
-        uses: docker/setup-buildx-action@v3
+        uses: docker/setup-buildx-action@v2
       - name: Cache Docker layers
-        uses: actions/cache@v4
+        uses: actions/cache@v3
         with:
           path: /tmp/.buildx-cache
           key: ${{ runner.os }}-buildxarch-${{ github.sha }}
           restore-keys: |
             ${{ runner.os }}-buildxarch-
       - name: Login to Docker Hub
-        uses: docker/login-action@v3
+        uses: docker/login-action@v2
         with:
           username: ${{ secrets.DOCKERHUB_USER }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
       - name: Login to ECR
-        uses: docker/login-action@v3
+        uses: docker/login-action@v2
         with:
           registry: public.ecr.aws
           username: ${{ secrets.ECR_ACCESS_KEY_ID }}
           password: ${{ secrets.ECR_SECRET_ACCESS_KEY }}
       - name: Get version
         id: get_version
-        uses: crazy-max/ghaction-docker-meta@v5
+        uses: crazy-max/ghaction-docker-meta@v4
         with:
           images: ${{ env.REP }}
           tag-semver: |
             {{version}}
-      - name: Extract variables from makefile (kubectl)
-        id: extract_vars
-        run: |
-          echo "KUBECTL_VERSION=$(grep -oP '^KUBECTL_VERSION\s*\?=\s*\K.*' makefile)" >> $GITHUB_ENV
+
       - name: Build and push - Docker/ECR
         id: docker_build
-        uses: docker/build-push-action@v6
+        uses: docker/build-push-action@v3
         with:
           context: .
           platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x
@@ -61,7 +57,6 @@ jobs:
           push: true
           build-args: |
             KUBEBENCH_VERSION=${{ steps.get_version.outputs.version }}
-            KUBECTL_VERSION=${{ env.KUBECTL_VERSION }}
           tags: |
             ${{ env.DOCKERHUB_ALIAS }}/${{ env.REP }}:${{ steps.get_version.outputs.version }}
             public.ecr.aws/${{ env.ALIAS }}/${{ env.REP }}:${{ steps.get_version.outputs.version }}
@@ -69,43 +64,5 @@ jobs:
             public.ecr.aws/${{ env.ALIAS }}/${{ env.REP }}:latest
           cache-from: type=local,src=/tmp/.buildx-cache/release
           cache-to: type=local,mode=max,dest=/tmp/.buildx-cache/release
-
-      - name: Build and push ubi image - Docker/ECR
-        id: docker_build_ubi
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x
-          builder: ${{ steps.buildx.outputs.name }}
-          push: true
-          file: Dockerfile.ubi
-          build-args: |
-            KUBEBENCH_VERSION=${{ steps.get_version.outputs.version }}
-            KUBECTL_VERSION=${{ env.KUBECTL_VERSION }}
-          tags: |
-            ${{ env.DOCKERHUB_ALIAS }}/${{ env.REP }}:${{ steps.get_version.outputs.version }}-ubi
-            public.ecr.aws/${{ env.ALIAS }}/${{ env.REP }}:${{ steps.get_version.outputs.version }}-ubi
-          cache-from: type=local,src=/tmp/.buildx-cache/release
-          cache-to: type=local,mode=max,dest=/tmp/.buildx-cache/release
-      - name: Image digest
-        run: echo ${{ steps.docker_build.outputs.digest }}
-
-      - name: Build and push fips ubi image - Docker/ECR
-        id: docker_build_fips_ubi
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          platforms: linux/amd64,linux/arm64,linux/ppc64le,linux/s390x
-          builder: ${{ steps.buildx.outputs.name }}
-          push: true
-          file: Dockerfile.fips.ubi
-          build-args: |
-            KUBEBENCH_VERSION=${{ steps.get_version.outputs.version }}
-            KUBECTL_VERSION=${{ env.KUBECTL_VERSION }}
-          tags: |
-            ${{ env.DOCKERHUB_ALIAS }}/${{ env.REP }}:${{ steps.get_version.outputs.version }}-ubi-fips
-            public.ecr.aws/${{ env.ALIAS }}/${{ env.REP }}:${{ steps.get_version.outputs.version }}-ubi-fips
-          cache-from: type=local,src=/tmp/.buildx-cache/release
-          cache-to: type=local,mode=max,dest=/tmp/.buildx-cache/release
       - name: Image digest
         run: echo ${{ steps.docker_build.outputs.digest }}

.github/workflows/release.yml

@@ -5,27 +5,27 @@ on:
     tags:
       - "v*"
 env:
-  GO_VERSION: "1.23.6"
+  GO_VERSION: "1.19"
   KIND_VERSION: "v0.11.1"
   KIND_IMAGE: "kindest/node:v1.21.1@sha256:69860bda5563ac81e3c0057d654b5253219618a22ec3a346306239bba8cfa1a6"
 
 jobs:
   release:
     name: Release
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     steps:
       - name: Setup Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v3
         with:
           go-version: ${{ env.GO_VERSION }}
       - name: Checkout code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v3
         with:
           fetch-depth: 0
       - name: Run unit tests
         run: make tests
       - name: Setup Kubernetes cluster (KIND)
-        uses: engineerd/setup-kind@v0.6.2
+        uses: engineerd/setup-kind@v0.5.0
         with:
           version: ${{ env.KIND_VERSION }}
           image: ${{ env.KIND_IMAGE }}
@@ -44,7 +44,7 @@ jobs:
           second_file_path: integration/testdata/Expected_output.data
           expected_result: PASSED
       - name: Release
-        uses: goreleaser/goreleaser-action@v6
+        uses: goreleaser/goreleaser-action@v4
         with:
           distribution: goreleaser
           version: v1.7.0

.golangci.yaml

@@ -1,28 +1,12 @@
-version: "2"
+---
 linters:
-  default: none
+  disable-all: true
   enable:
+    - deadcode
     - gocyclo
-    - govet
-    - misspell
-  exclusions:
-    generated: lax
-    presets:
-      - comments
-      - common-false-positives
-      - legacy
-      - std-error-handling
-    paths:
-      - third_party$
-      - builtin$
-      - examples$
-formatters:
-  enable:
     - gofmt
     - goimports
-  exclusions:
-    generated: lax
-    paths:
-      - third_party$
-      - builtin$
-      - examples$
+    - govet
+    - misspell
+    - typecheck
+    - varcheck

.goreleaser.yml

@@ -2,18 +2,12 @@
 project_name: kube-bench
 env:
   - GO111MODULE=on
-  - CGO_ENABLED=0
   - KUBEBENCH_CFG=/etc/kube-bench/cfg
 builds:
-  - main: .
+  - main: main.go
     binary: kube-bench
-    tags:
-      - osusergo
-      - netgo
-      - static_build
     goos:
       - linux
-      - darwin
     goarch:
       - amd64
       - arm
@@ -24,9 +18,6 @@ builds:
       - 6
       - 7
     ldflags:
-      - "-s"
-      - "-w"
-      - "-extldflags '-static'"
       - "-X github.com/aquasecurity/kube-bench/cmd.KubeBenchVersion={{.Version}}"
       - "-X github.com/aquasecurity/kube-bench/cmd.cfgDir={{.Env.KUBEBENCH_CFG}}"
 # Archive customization

Dockerfile

@@ -1,4 +1,4 @@
-FROM golang:1.25.3 AS build
+FROM golang:1.19.4 AS build
 WORKDIR /go/src/github.com/aquasecurity/kube-bench/
 COPY makefile makefile
 COPY go.mod go.sum ./
@@ -9,22 +9,11 @@ COPY internal/ internal/
 ARG KUBEBENCH_VERSION
 RUN make build && cp kube-bench /go/bin/kube-bench
 
-# Add kubectl to run policies checks
-ARG KUBECTL_VERSION TARGETARCH
-RUN wget -O /usr/local/bin/kubectl "https://dl.k8s.io/release/v${KUBECTL_VERSION}/bin/linux/${TARGETARCH}/kubectl"
-RUN wget -O kubectl.sha256 "https://dl.k8s.io/release/v${KUBECTL_VERSION}/bin/linux/${TARGETARCH}/kubectl.sha256"
-
-# Verify kubectl sha256sum
-RUN /bin/bash -c 'echo "$(<kubectl.sha256)  /usr/local/bin/kubectl" | sha256sum -c -'
-
-RUN chmod +x /usr/local/bin/kubectl
-
-FROM alpine:3.22.2 AS run
+FROM alpine:3.17.0 AS run
 WORKDIR /opt/kube-bench/
-# add GNU ps for -C, -o cmd, --no-headers support and add findutils to get GNU xargs
+# add GNU ps for -C, -o cmd, and --no-headers support
 # https://github.com/aquasecurity/kube-bench/issues/109
-# https://github.com/aquasecurity/kube-bench/issues/1656
-RUN apk --no-cache add procps findutils
+RUN apk --no-cache add procps
 
 # Upgrading apk-tools to remediate CVE-2021-36159 - https://snyk.io/vuln/SNYK-ALPINE314-APKTOOLS-1533752
 # https://github.com/aquasecurity/kube-bench/issues/943
@@ -40,34 +29,21 @@ RUN wget -q -O /etc/apk/keys/sgerrand.rsa.pub https://alpine-pkgs.sgerrand.com/s
 RUN apk add gcompat
 RUN apk add jq
 
-# Add bash for running helper scripts
-RUN apk add bash
-
-ENV PATH=$PATH:/usr/local/mount-from-host/bin:/go/bin
+ENV PATH=$PATH:/usr/local/mount-from-host/bin
 
 COPY --from=build /go/bin/kube-bench /usr/local/bin/kube-bench
-COPY --from=build /usr/local/bin/kubectl /usr/local/bin/kubectl
 COPY entrypoint.sh .
 COPY cfg/ cfg/
-COPY helper_scripts/check_files_owner_in_dir.sh /go/bin/
-RUN chmod a+x /go/bin/check_files_owner_in_dir.sh
 ENTRYPOINT ["./entrypoint.sh"]
 CMD ["install"]
 
 # Build-time metadata as defined at http://label-schema.org
 ARG BUILD_DATE
 ARG VCS_REF
-ARG KUBEBENCH_VERSION
-
 LABEL org.label-schema.build-date=$BUILD_DATE \
-      org.label-schema.name="kube-bench" \
-      org.label-schema.vendor="Aqua Security Software Ltd." \
-      org.label-schema.version=$KUBEBENCH_VERSION \
-      org.label-schema.release=$KUBEBENCH_VERSION \
-      org.label-schema.summary="Aqua security server" \
-      org.label-schema.maintainer="admin@aquasec.com" \
-      org.label-schema.description="Run the CIS Kubernetes Benchmark tests" \
-      org.label-schema.url="https://github.com/aquasecurity/kube-bench" \
-      org.label-schema.vcs-ref=$VCS_REF \
-      org.label-schema.vcs-url="https://github.com/aquasecurity/kube-bench" \
-      org.label-schema.schema-version="1.0"
+    org.label-schema.name="kube-bench" \
+    org.label-schema.description="Run the CIS Kubernetes Benchmark tests" \
+    org.label-schema.url="https://github.com/aquasecurity/kube-bench" \
+    org.label-schema.vcs-ref=$VCS_REF \
+    org.label-schema.vcs-url="https://github.com/aquasecurity/kube-bench" \
+    org.label-schema.schema-version="1.0"

Dockerfile.fips.ubi

@@ -1,66 +0,0 @@
-FROM golang:1.25.3 AS build
-WORKDIR /go/src/github.com/aquasecurity/kube-bench/
-COPY makefile makefile
-COPY go.mod go.sum ./
-COPY main.go .
-COPY check/ check/
-COPY cmd/ cmd/
-COPY internal/ internal/
-ARG KUBEBENCH_VERSION
-RUN make build-fips && cp kube-bench /go/bin/kube-bench
-
-# Add kubectl to run policies checks
-ARG KUBECTL_VERSION TARGETARCH
-RUN wget -O /usr/local/bin/kubectl "https://dl.k8s.io/release/v${KUBECTL_VERSION}/bin/linux/${TARGETARCH}/kubectl"
-RUN wget -O kubectl.sha256 "https://dl.k8s.io/release/v${KUBECTL_VERSION}/bin/linux/${TARGETARCH}/kubectl.sha256"
-# Verify kubectl sha256sum
-RUN /bin/bash -c 'echo "$(<kubectl.sha256)  /usr/local/bin/kubectl" | sha256sum -c -'
-RUN chmod +x /usr/local/bin/kubectl
-
-
-# ubi8-minimal base image for build with ubi standards
-FROM registry.access.redhat.com/ubi9/ubi-minimal as run
-
-RUN microdnf install -y yum findutils openssl \
-  && yum -y update-minimal --security --sec-severity=Moderate --sec-severity=Important --sec-severity=Critical \
-  && yum update -y \
-  && yum install -y glibc \
-  && yum update -y glibc \
-  && yum install -y procps \
-  && yum update -y procps \
-  && yum install jq -y \
-  && yum clean all \
-  && microdnf remove yum || rpm -e -v yum \
-  && microdnf clean all
-
-WORKDIR /opt/kube-bench/
-
-ENV PATH=$PATH:/usr/local/mount-from-host/bin 
-
-COPY LICENSE /licenses/LICENSE
-COPY --from=build /go/bin/kube-bench /usr/local/bin/kube-bench
-COPY --from=build /usr/local/bin/kubectl /usr/local/bin/kubectl
-COPY entrypoint.sh .
-COPY cfg/ cfg/
-COPY helper_scripts/check_files_owner_in_dir.sh /go/bin
-ENTRYPOINT ["./entrypoint.sh"]
-CMD ["install"]
-
-
-# Build-time metadata as defined at http://label-schema.org
-ARG BUILD_DATE
-ARG VCS_REF
-ARG KUBEBENCH_VERSION
-
-LABEL org.label-schema.build-date=$BUILD_DATE \
-      org.label-schema.name="kube-bench" \
-      org.label-schema.vendor="Aqua Security Software Ltd." \
-      org.label-schema.version=$KUBEBENCH_VERSION \
-      org.label-schema.release=$KUBEBENCH_VERSION \
-      org.label-schema.summary="Aqua security server" \
-      org.label-schema.maintainer="admin@aquasec.com" \
-      org.label-schema.description="Run the CIS Kubernetes Benchmark tests" \
-      org.label-schema.url="https://github.com/aquasecurity/kube-bench" \
-      org.label-schema.vcs-ref=$VCS_REF \
-      org.label-schema.vcs-url="https://github.com/aquasecurity/kube-bench" \
-      org.label-schema.schema-version="1.0"

Dockerfile.ubi

@@ -1,66 +0,0 @@
-FROM golang:1.25.3 AS build
-WORKDIR /go/src/github.com/aquasecurity/kube-bench/
-COPY makefile makefile
-COPY go.mod go.sum ./
-COPY main.go .
-COPY check/ check/
-COPY cmd/ cmd/
-COPY internal/ internal/
-ARG KUBEBENCH_VERSION
-RUN make build && cp kube-bench /go/bin/kube-bench
-
-# Add kubectl to run policies checks
-ARG KUBECTL_VERSION TARGETARCH
-RUN wget -O /usr/local/bin/kubectl "https://dl.k8s.io/release/v${KUBECTL_VERSION}/bin/linux/${TARGETARCH}/kubectl"
-RUN wget -O kubectl.sha256 "https://dl.k8s.io/release/v${KUBECTL_VERSION}/bin/linux/${TARGETARCH}/kubectl.sha256"
-# Verify kubectl sha256sum
-RUN /bin/bash -c 'echo "$(<kubectl.sha256)  /usr/local/bin/kubectl" | sha256sum -c -'
-RUN chmod +x /usr/local/bin/kubectl
-
-
-# ubi8-minimal base image for build with ubi standards
-FROM registry.access.redhat.com/ubi9/ubi-minimal as run
-
-RUN microdnf install -y yum findutils openssl \
-  && yum -y update-minimal --security --sec-severity=Moderate --sec-severity=Important --sec-severity=Critical \
-  && yum update -y \
-  && yum install -y glibc \
-  && yum update -y glibc \
-  && yum install -y procps \
-  && yum update -y procps \
-  && yum install jq -y \
-  && yum clean all \
-  && microdnf remove yum || rpm -e -v yum \
-  && microdnf clean all
-
-WORKDIR /opt/kube-bench/
-
-ENV PATH=$PATH:/usr/local/mount-from-host/bin
-
-COPY LICENSE /licenses/LICENSE
-COPY --from=build /go/bin/kube-bench /usr/local/bin/kube-bench
-COPY --from=build /usr/local/bin/kubectl /usr/local/bin/kubectl
-COPY entrypoint.sh .
-COPY cfg/ cfg/
-COPY helper_scripts/check_files_owner_in_dir.sh /go/bin
-ENTRYPOINT ["./entrypoint.sh"]
-CMD ["install"]
-
-
-# Build-time metadata as defined at http://label-schema.org
-ARG BUILD_DATE
-ARG VCS_REF
-ARG KUBEBENCH_VERSION
-
-LABEL org.label-schema.build-date=$BUILD_DATE \
-      org.label-schema.description="Run the CIS Kubernetes Benchmark tests" \
-      org.label-schema.url="https://github.com/aquasecurity/kube-bench" \
-      org.label-schema.vcs-ref=$VCS_REF \
-      org.label-schema.vcs-url="https://github.com/aquasecurity/kube-bench" \
-      org.label-schema.schema-version="1.0" \
-      vendor="Aqua Security Software Ltd." \
-      maintainer="Aqua Security Software Ltd." \
-      version=$KUBEBENCH_VERSION \
-      release=$KUBEBENCH_VERSION \
-      summary="Aqua Security Kube-bench." \
-      description="Run the CIS Kubernetes Benchmark tests"

Dockerfile.ubi8

@@ -0,0 +1,48 @@
+FROM golang:1.19.4 AS build
+WORKDIR /go/src/github.com/aquasecurity/kube-bench/
+COPY makefile makefile
+COPY go.mod go.sum ./
+COPY main.go .
+COPY check/ check/
+COPY cmd/ cmd/
+COPY internal/ internal/
+ARG KUBEBENCH_VERSION
+RUN make build && cp kube-bench /go/bin/kube-bench
+
+
+# ubi8-minimal base image for build with ubi standards
+FROM registry.access.redhat.com/ubi8/ubi-minimal:8.7 as run
+
+RUN microdnf install yum findutils openssl\
+  && yum -y update-minimal --security --sec-severity=Moderate --sec-severity=Important --sec-severity=Critical \
+  && yum update -y \
+  && yum install -y glibc \
+  && yum update -y glibc \
+  && yum install -y procps \
+  && yum update -y procps \
+  && yum install jq -y \
+  && yum clean all \
+  && microdnf remove yum || rpm -e -v yum \
+  && microdnf clean all
+
+WORKDIR /opt/kube-bench/
+
+ENV PATH=$PATH:/usr/local/mount-from-host/bin 
+
+COPY --from=build /go/bin/kube-bench /usr/local/bin/kube-bench
+COPY entrypoint.sh .
+COPY cfg/ cfg/
+ENTRYPOINT ["./entrypoint.sh"]
+CMD ["install"]
+
+
+# Build-time metadata as defined at http://label-schema.org
+ARG BUILD_DATE
+ARG VCS_REF
+LABEL org.label-schema.build-date=$BUILD_DATE \
+    org.label-schema.name="kube-bench" \
+    org.label-schema.description="Run the CIS Kubernetes Benchmark tests" \
+    org.label-schema.url="https://github.com/aquasecurity/kube-bench" \
+    org.label-schema.vcs-ref=$VCS_REF \
+    org.label-schema.vcs-url="https://github.com/aquasecurity/kube-bench" \
+    org.label-schema.schema-version="1.0"

README.md

@@ -24,12 +24,7 @@ Tests are configured with YAML files, making this tool easy to update as test sp
 
 ![Kubernetes Bench for Security](/docs/images/output.png "Kubernetes Bench for Security")
 
-## CIS Scanning as part of Trivy and the Trivy Operator
-
-[Trivy](https://github.com/aquasecurity/trivy), the all in one cloud native security scanner, can be deployed as a [Kubernetes Operator](https://github.com/aquasecurity/trivy-operator) inside a cluster.
-Both, the [Trivy CLI](https://github.com/aquasecurity/trivy), and the [Trivy Operator](https://github.com/aquasecurity/trivy-operator) support CIS Kubernetes Benchmark scanning among several other features.
-
-## Quick start
+### 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.

cfg/ack-1.0/node.yaml

@@ -25,16 +25,14 @@ groups:
 
       - id: 4.1.2
         text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
+        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; fi'' '
         tests:
-          bin_op: or
           test_items:
             - flag: root:root
-            - flag: "File not found"
         remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
+          Run the below command (based on the file location on your system) on the each worker node.
+          For example,
+          chown root:root $kubeletsvc
         scored: true
 
       - id: 4.1.3
@@ -47,6 +45,8 @@ groups:
               compare:
                 op: bitmask
                 value: "644"
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example,
@@ -60,6 +60,8 @@ groups:
           bin_op: or
           test_items:
             - flag: root:root
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example, chown root:root $proxykubeconfig
@@ -95,7 +97,7 @@ groups:
       - id: 4.1.7
         text: "Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
         tests:
@@ -112,7 +114,7 @@ groups:
       - id: 4.1.8
         text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
         tests:
@@ -377,7 +379,7 @@ groups:
                 op: valid_elements
                 value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
         remediation: |
-          If using a Kubelet config file, edit the file to set tlsCipherSuites: to
+          If using a Kubelet config file, edit the file to set TLSCipherSuites: to
           TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
           or to a subset of these values.
           If using executable arguments, edit the kubelet service file

cfg/ack-1.0/policies.yaml

@@ -132,7 +132,7 @@ groups:
         type: "manual"
         remediation: |
           Review the use of capabilites in applications runnning on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
+          contains applicaions which do not require any Linux capabities to operate consider adding
           a PSP which forbids the admission of containers which do not drop all capabilities.
         scored: false
 

cfg/aks-1.7/config.yaml

@@ -1,2 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml

cfg/aks-1.7/controlplane.yaml

@@ -1,31 +0,0 @@
----
-controls:
-version: "aks-1.7"
-id: 2
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 2.1
-    text: "Logging"
-    checks:
-      - id: 2.1.1
-        text: "Enable audit Logs"
-        type: "manual"
-        remediation: |
-          Azure audit logs are enabled and managed in the Azure portal. To enable log collection for
-          the Kubernetes master components in your AKS cluster, open the Azure portal in a web
-          browser and complete the following steps:
-          1. Select the resource group for your AKS cluster, such as myResourceGroup. Don't
-             select the resource group that contains your individual AKS cluster resources, such
-             as MC_myResourceGroup_myAKSCluster_eastus.
-          2. On the left-hand side, choose Diagnostic settings.
-          3. Select your AKS cluster, such as myAKSCluster, then choose to Add diagnostic setting.
-          4. Enter a name, such as myAKSClusterLogs, then select the option to Send to Log Analytics.
-          5. Select an existing workspace or create a new one. If you create a workspace, provide
-             a workspace name, a resource group, and a location.
-          6. In the list of available logs, select the logs you wish to enable. For this example,
-             enable the kube-audit and kube-audit-admin logs. Common logs include the kube-
-             apiserver, kube-controller-manager, and kube-scheduler. You can return and change
-             the collected logs once Log Analytics workspaces are enabled.
-          7. When ready, select Save to enable collection of the selected logs.
-        scored: false

cfg/aks-1.7/managedservices.yaml

@@ -1,169 +0,0 @@
----
-controls:
-version: "aks-1.7"
-id: 5
-text: "Managed Services"
-type: "managedservices"
-groups:
-  - id: 5.1
-    text: "Image Registry and Image Scanning"
-    checks:
-      - id: 5.1.1
-        text: "Ensure Image Vulnerability Scanning using Microsoft Defender for Cloud (MDC) image scanning or a third party provider (Manual)"
-        type: "manual"
-        remediation: |
-          Enable MDC for Container Registries by running the following Azure CLI command:
-          az security pricing create --name ContainerRegistry --tier Standard
-          Alternatively, use the following command to enable image scanning for your container registry:
-          az resource update --ids /subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.ContainerRegistry/registries/{registry-name} --set properties.enabled=true
-          Replace `subscription-id`, `resource-group-name`, and `registry-name` with the correct values for your environment.
-          Please note that enabling MDC for Container Registries will incur additional costs, so be sure to review the pricing information provided in the Azure documentation before enabling it.
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize user access to Azure Container Registry (ACR) (Manual)"
-        type: "manual"
-        remediation: |
-          Azure Container Registry
-          If you use Azure Container Registry (ACR) as your container image store, you need to grant
-          permissions to the service principal for your AKS cluster to read and pull images. Currently,
-          the recommended configuration is to use the az aks create or az aks update command to
-          integrate with a registry and assign the appropriate role for the service principal. For
-          detailed steps, see Authenticate with Azure Container Registry from Azure Kubernetes
-          Service.
-          To avoid needing an Owner or Azure account administrator role, you can configure a
-          service principal manually or use an existing service principal to authenticate ACR from
-          AKS. For more information, see ACR authentication with service principals or Authenticate
-          from Kubernetes with a pull secret.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize cluster access to read-only for Azure Container Registry (ACR) (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize Container Registries to only those approved (Manual)"
-        type: "manual"
-        remediation: |
-          If you are using **Azure Container Registry**, you can restrict access using firewall rules as described in the official documentation:
-          https://docs.microsoft.com/en-us/azure/container-registry/container-registry-firewall-access-rules
-          For other non-AKS repositories, you can use **admission controllers** or **Azure Policy** to enforce registry access restrictions.
-          Limiting or locking down egress traffic to specific container registries is also recommended. For more information, refer to:
-          https://docs.microsoft.com/en-us/azure/aks/limit-egress-traffic
-        scored: false
-
-
-  - id: 5.2
-    text: "Access and identity options for Azure Kubernetes Service (AKS)"
-    checks:
-      - id: 5.2.1
-        text: "Prefer using dedicated AKS Service Accounts (Manual)"
-        type: "manual"
-        remediation: |
-          Azure Active Directory integration
-          The security of AKS clusters can be enhanced with the integration of Azure Active Directory
-          (AD). Built on decades of enterprise identity management, Azure AD is a multi-tenant,
-          cloud-based directory, and identity management service that combines core directory
-          services, application access management, and identity protection. With Azure AD, you can
-          integrate on-premises identities into AKS clusters to provide a single source for account
-          management and security.
-          Azure Active Directory integration with AKS clusters
-          With Azure AD-integrated AKS clusters, you can grant users or groups access to Kubernetes
-          resources within a namespace or across the cluster. To obtain a kubectl configuration
-          context, a user can run the az aks get-credentials command. When a user then interacts
-          with the AKS cluster with kubectl, they're prompted to sign in with their Azure AD
-          credentials. This approach provides a single source for user account management and
-          password credentials. The user can only access the resources as defined by the cluster
-          administrator.
-          Azure AD authentication is provided to AKS clusters with OpenID Connect. OpenID Connect
-          is an identity layer built on top of the OAuth 2.0 protocol. For more information on OpenID
-          Connect, see the Open ID connect documentation. From inside of the Kubernetes cluster,
-          Webhook Token Authentication is used to verify authentication tokens. Webhook token
-          authentication is configured and managed as part of the AKS cluster.
-        scored: false
-
-
-  - id: 5.3
-    text: "Key Management Service (KMS)"
-    checks:
-      - id: 5.3.1
-        text: "Ensure Kubernetes Secrets are encrypted (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-
-  - id: 5.4
-    text: "Cluster Networking"
-    checks:
-      - id: 5.4.1
-        text: "Restrict Access to the Control Plane Endpoint (Manual)"
-        type: "manual"
-        remediation: |
-          By enabling private endpoint access to the Kubernetes API server, all communication between your nodes and the API server stays within your VPC. You can also limit the IP addresses that can access your API server from the internet, or completely disable internet access to the API server.
-          With this in mind, you can update your cluster accordingly using the AKS CLI to ensure that Private Endpoint Access is enabled.
-          If you choose to also enable Public Endpoint Access then you should also configure a list of allowable CIDR blocks, resulting in restricted access from the internet. If you specify no CIDR blocks, then the public API server endpoint is able to receive and process requests from all IP addresses by defaulting to ['0.0.0.0/0'].
-          Example:
-          az aks update --name ${CLUSTER_NAME} --resource-group ${RESOURCE_GROUP} --api-server-access-profile enablePrivateCluster=true --api-server-access-profile authorizedIpRanges=192.168.1.0/24
-        scored: false
-
-      - id: 5.4.2
-        text: "Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Manual)"
-        type: "manual"
-        remediation: |
-          To use a private endpoint, create a new private endpoint in your virtual network, then create a link between your virtual network and a new private DNS zone.
-          You can also restrict access to the public endpoint by enabling only specific CIDR blocks to access it. For example:
-          az aks update --name ${CLUSTER_NAME} --resource-group ${RESOURCE_GROUP} --api-server-access-profile enablePublicFqdn=false
-          This command disables the public API endpoint for your AKS cluster.
-        scored: false
-
-      - id: 5.4.3
-        text: "Ensure clusters are created with Private Nodes (Manual)"
-        type: "manual"
-        remediation: |
-          To create a private cluster, use the following command:
-          az aks create \
-          --resource-group <private-cluster-resource-group> \
-          --name <private-cluster-name> \
-          --load-balancer-sku standard \
-          --enable-private-cluster \
-          --network-plugin azure \
-          --vnet-subnet-id <subnet-id> \
-          --docker-bridge-address <docker-bridge-address> \
-          --dns-service-ip <dns-service-ip> \
-          --service-cidr <service-cidr>
-          Ensure that --enable-private-cluster flag is set to enable private nodes in your cluster.
-        scored: false
-
-      - id: 5.4.4
-        text: "Ensure Network Policy is Enabled and set as appropriate (Manual)"
-        type: "manual"
-        remediation: |
-          Utilize Calico or another network policy engine to segment and isolate your traffic.
-          Enable network policies on your AKS cluster by following the Azure documentation or using the `az aks` CLI to enable the network policy add-on.
-        scored: false
-
-
-      - id: 5.4.5
-        text: "Encrypt traffic to HTTPS load balancers with TLS certificates (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-
-  - id: 5.5
-    text: "Authentication and Authorization"
-    checks:
-      - id: 5.5.1
-        text: "Manage Kubernetes RBAC users with Azure AD (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-      - id: 5.5.2
-        text: "Use Azure RBAC for Kubernetes Authorization (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false

cfg/aks-1.7/master.yaml

@@ -1,6 +0,0 @@
----
-controls:
-version: "aks-1.7"
-id: 1
-text: "Control Plane Components"
-type: "master"

cfg/aks-1.7/node.yaml

@@ -1,283 +0,0 @@
----
-controls:
-version: "aks-1.7"
-id: 3
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 3.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 3.1.1
-        text: "Ensure that the kubeconfig file permissions are set to 644 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 644 $kubeletkubeconfig
-        scored: true
-
-      - id: 3.1.2
-        text: "Ensure that the kubelet kubeconfig file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 3.1.3
-        text: "Ensure that the azure.json file has permissions set to 644 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e /etc/kubernetes/azure.json; then stat -c permissions=%a /etc/kubernetes/azure.json; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 644 $kubeletconf
-        scored: true
-
-      - id: 3.1.4
-        text: "Ensure that the azure.json file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: true
-
-
-  - id: 3.2
-    text: "Kubelet"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set authentication: anonymous: enabled to
-          false.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --anonymous-auth=false
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set authorization: mode to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.3
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-              set: true
-        remediation: |
-          If using a Kubelet config file, edit the file to set authentication: x509: clientCAFile to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.4
-        text: "Ensure that the --read-only-port is secured (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: true
-              compare:
-                op: eq
-                value: 0
-        remediation: |
-          If using a Kubelet config file, edit the file to set readOnlyPort to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: true
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set streamingConnectionIdleTimeout to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated) "
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: true
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set makeIPTablesUtilChains: true.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-
-      - id: 3.2.7
-        text: "Ensure that the --eventRecordQPS argument is set to 0 or a level which ensures appropriate event capture (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: true
-              compare:
-                op: eq
-                value: 0
-        remediation: |
-          If using a Kubelet config file, edit the file to set the 'eventRecordQPS' value to an appropriate level (e.g., 5).
-          If using executable arguments, check the Kubelet service file `$kubeletsvc` on each worker node, and add the following parameter to the `KUBELET_ARGS` variable:
-          --eventRecordQPS=5
-          Ensure that there is no conflicting `--eventRecordQPS` setting in the service file that overrides the config file.
-          After making the changes, restart the Kubelet service:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-
-      - id: 3.2.8
-        text: "Ensure that the --rotate-certificates argument is not set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: true
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          If modifying the Kubelet config file, edit the `kubelet-config.json` file located at `/etc/kubernetes/kubelet/kubelet-config.json` and set the following parameter to `true`:
-          "rotateCertificates": true
-          Ensure that the Kubelet service file located at `/etc/systemd/system/kubelet.service.d/10-kubelet-args.conf` does not define the `--rotate-certificates` argument as `false`, as this would override the config file.
-          If using executable arguments, add the following line to the `KUBELET_CERTIFICATE_ARGS` variable:
-          --rotate-certificates=true
-          After making the necessary changes, restart the Kubelet service:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.9
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: true
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true

cfg/aks-1.7/policies.yaml

@@ -1,417 +0,0 @@
----
-controls:
-version: "aks-1.7"
-id: 4
-text: "Policies"
-type: "policies"
-groups:
-  - id: 4.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Automated)"
-        audit: |
-          kubectl get clusterrolebindings -o json | jq -r '
-            .items[]
-            | select(.roleRef.name == "cluster-admin")
-            | .subjects[]?
-            | select(.kind != "Group" or (.name != "system:masters" and .name != "system:nodes"))
-            | "FOUND_CLUSTER_ADMIN_BINDING"
-          ' || echo "NO_CLUSTER_ADMIN_BINDINGS"
-        tests:
-          test_items:
-            - flag: "NO_CLUSTER_ADMIN_BINDINGS"
-              set: true
-              compare:
-                op: eq
-                value: "NO_CLUSTER_ADMIN_BINDINGS"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role using:
-
-            kubectl get clusterrolebindings --no-headers | grep cluster-admin
-
-          Review if each of them actually needs this role. If not, remove the binding:
-
-            kubectl delete clusterrolebinding <binding-name>
-
-          Where possible, assign a less privileged ClusterRole.
-        scored: true
-
-      - id: 4.1.2
-        text: "Minimize access to secrets (Automated)"
-        audit: |
-          count=$(kubectl get roles --all-namespaces -o json | jq '
-            .items[]
-            | select(.rules[]?
-              | (.resources[]? == "secrets")
-              and ((.verbs[]? == "get") or (.verbs[]? == "list") or (.verbs[]? == "watch"))
-            )' | wc -l)
-
-          if [ "$count" -gt 0 ]; then
-            echo "SECRETS_ACCESS_FOUND"
-          fi
-        tests:
-          test_items:
-            - flag: "SECRETS_ACCESS_FOUND"
-              set: false
-        remediation: |
-          Identify all roles that grant access to secrets via get/list/watch verbs.
-          Use `kubectl edit role -n <namespace> <name>` to remove these permissions.
-          Alternatively, create a new least-privileged role that excludes secret access.
-        scored: true
-
-      - id: 4.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Automated)"
-        audit: |
-          wildcards=$(kubectl get roles --all-namespaces -o json | jq '
-            .items[] | select(
-              .rules[]? | (.verbs[]? == "*" or .resources[]? == "*" or .apiGroups[]? == "*")
-            )' | wc -l)
-
-          wildcards_clusterroles=$(kubectl get clusterroles -o json | jq '
-            .items[] | select(
-              .rules[]? | (.verbs[]? == "*" or .resources[]? == "*" or .apiGroups[]? == "*")
-            )' | wc -l)
-
-          total=$((wildcards + wildcards_clusterroles))
-
-          if [ "$total" -gt 0 ]; then
-            echo "wildcards_present"
-          fi
-        tests:
-          test_items:
-            - flag: wildcards_present
-              set: false
-        remediation: |
-          Identify roles and clusterroles using wildcards (*) in 'verbs', 'resources', or 'apiGroups'.
-          Replace wildcards with specific values to enforce least privilege access.
-          Use `kubectl edit role -n <namespace> <name>` or `kubectl edit clusterrole <name>` to update.
-        scored: true
-
-
-      - id: 4.1.4
-        text: "Minimize access to create pods (Automated)"
-        audit: |
-          echo "🔹 Roles and ClusterRoles with 'create' access on 'pods':"
-          access=$(kubectl get roles,clusterroles -A -o json | jq '
-            [.items[] |
-              select(
-                .rules[]? |
-                (.resources[]? == "pods" and .verbs[]? == "create")
-              )
-            ] | length')
-
-          if [ "$access" -gt 0 ]; then
-            echo "pods_create_access"
-          fi
-        tests:
-          test_items:
-            - flag: pods_create_access
-              set: false
-        remediation: |
-          Review all roles and clusterroles that have "create" permission on "pods".
-
-          🔒 Where possible, remove or restrict this permission to only required service accounts.
-
-          🛠 Use:
-            - `kubectl edit role -n <namespace> <role>`
-            - `kubectl edit clusterrole <name>`
-
-          ✅ Apply least privilege principle across the cluster.
-        scored: true
-
-
-      - id: 4.1.5
-        text: "Ensure that default service accounts are not actively used (Automated)"
-        audit: |
-          echo "🔹 Default Service Accounts with automountServiceAccountToken enabled:"
-          default_sa_count=$(kubectl get serviceaccounts --all-namespaces -o json | jq '
-            [.items[] | select(.metadata.name == "default" and (.automountServiceAccountToken != false))] | length')
-          if [ "$default_sa_count" -gt 0 ]; then
-            echo "default_sa_not_auto_mounted"
-          fi
-
-          echo "\n🔹 Pods using default ServiceAccount:"
-          pods_using_default_sa=$(kubectl get pods --all-namespaces -o json | jq '
-            [.items[] | select(.spec.serviceAccountName == "default")] | length')
-          if [ "$pods_using_default_sa" -gt 0 ]; then
-            echo "default_sa_used_in_pods"
-          fi
-        tests:
-          test_items:
-            - flag: default_sa_not_auto_mounted
-              set: false
-            - flag: default_sa_used_in_pods
-              set: false
-        remediation: |
-          1. Avoid using default service accounts for workloads.
-          2. Set `automountServiceAccountToken: false` on all default SAs:
-             kubectl patch serviceaccount default -n <namespace> -p '{"automountServiceAccountToken": false}'
-          3. Use custom service accounts with only the necessary permissions.
-        scored: true
-
-
-      - id: 4.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Automated)"
-        audit: |
-          echo "🔹 Pods with automountServiceAccountToken enabled:"
-          pods_with_token_mount=$(kubectl get pods --all-namespaces -o json | jq '
-            [.items[] | select(.spec.automountServiceAccountToken != false)] | length')
-
-          if [ "$pods_with_token_mount" -gt 0 ]; then
-            echo "automountServiceAccountToken"
-          fi
-        tests:
-          test_items:
-            - flag: automountServiceAccountToken
-              set: false
-        remediation: |
-          Pods that do not need access to the Kubernetes API should not mount service account tokens.
-
-          ✅ To disable token mounting in a pod definition:
-          ```yaml
-          spec:
-            automountServiceAccountToken: false
-          ```
-
-          ✅ Or patch an existing pod's spec (recommended via workload template):
-          Patch not possible for running pods — update the deployment YAML or recreate pods with updated spec.
-        scored: true
-
-
-  - id: 4.2
-    text: "Pod Security Policies"
-    checks:
-      - id: 4.2.1
-        text: "Minimize the admission of privileged containers (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | \
-            jq -r 'if any(.items[]?.spec.containers[]?; .securityContext?.privileged == true) then "PRIVILEGED_FOUND" else "NO_PRIVILEGED" end'
-        tests:
-          test_items:
-            - flag: "NO_PRIVILEGED"
-              set: true
-              compare:
-                op: eq
-                value: "NO_PRIVILEGED"
-        remediation: |
-          Add a Pod Security Admission (PSA) policy to each namespace in the cluster to restrict the admission of privileged containers.
-          To enforce a restricted policy for a specific namespace, use the following command:
-          kubectl label --overwrite ns NAMESPACE pod-security.kubernetes.io/enforce=restricted
-          You can also enforce PSA for all namespaces:
-          kubectl label --overwrite ns --all pod-security.kubernetes.io/warn=baseline
-          Additionally, review the namespaces that should be excluded (e.g., `kube-system`, `gatekeeper-system`, `azure-arc`, `azure-extensions-usage-system`) and adjust your filtering if necessary.
-          To enable Pod Security Policies, refer to the detailed documentation for Kubernetes and Azure integration at:
-          https://learn.microsoft.com/en-us/azure/governance/policy/concepts/policy-for-kubernetes
-        scored: true
-
-      - id: 4.2.2
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | \
-            jq -r 'if any(.items[]?; .spec.hostPID == true) then "HOSTPID_FOUND" else "NO_HOSTPID" end'
-        tests:
-          test_items:
-            - flag: "NO_HOSTPID"
-              set: true
-              compare:
-                op: eq
-                value: "NO_HOSTPID"
-
-        remediation: |
-          Add a policy to each namespace in the cluster that restricts the admission of containers with hostPID. For namespaces that need it, ensure RBAC controls limit access to a specific service account.
-          You can label your namespaces as follows to restrict or enforce the policy:
-          kubectl label --overwrite ns NAMESPACE pod-security.kubernetes.io/enforce=restricted
-          You can also use the following to warn about policies:
-          kubectl label --overwrite ns --all pod-security.kubernetes.io/warn=baseline
-          For more information, refer to the official Kubernetes and Azure documentation on policies:
-          https://learn.microsoft.com/en-us/azure/governance/policy/concepts/policy-for-kubernetes
-        scored: true
-
-      - id: 4.2.3
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | jq -r 'if any(.items[]?; .spec.hostIPC == true) then "HOSTIPC_FOUND" else "NO_HOSTIPC" end'
-        tests:
-          test_items:
-            - flag: "NO_HOSTIPC"
-              set: true
-              compare:
-                op: eq
-                value: "NO_HOSTIPC"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the admission of hostIPC containers.
-          You can label your namespaces as follows to restrict or enforce the policy:
-          kubectl label --overwrite ns NAMESPACE pod-security.kubernetes.io/enforce=restricted
-          You can also use the following to warn about policies:
-          kubectl label --overwrite ns --all pod-security.kubernetes.io/warn=baseline
-          For more information, refer to the official Kubernetes and Azure documentation on policies:
-          https://learn.microsoft.com/en-us/azure/governance/policy/concepts/policy-for-kubernetes
-        scored: true
-
-      - id: 4.2.4
-        text: "Minimize the admission of containers wishing to share the host network namespace (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | jq -r 'if any(.items[]?; .spec.hostNetwork == true) then "HOSTNETWORK_FOUND" else "NO_HOSTNETWORK" end'
-        tests:
-          test_items:
-            - flag: "NO_HOSTNETWORK"
-              set: true
-              compare:
-                op: eq
-                value: "NO_HOSTNETWORK"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the admission of hostNetwork containers.
-          You can label your namespaces as follows to restrict or enforce the policy:
-          kubectl label --overwrite ns NAMESPACE pod-security.kubernetes.io/enforce=restricted
-          You can also use the following to warn about policies:
-          kubectl label --overwrite ns --all pod-security.kubernetes.io/warn=baseline
-          For more information, refer to the official Kubernetes and Azure documentation on policies:
-          https://learn.microsoft.com/en-us/azure/governance/policy/concepts/policy-for-kubernetes
-        scored: true
-
-      - id: 4.2.5
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | \
-            jq -r 'if any(.items[]?.spec.containers[]?; .securityContext?.allowPrivilegeEscalation == true) then "ALLOWPRIVILEGEESCALTION_FOUND" else "NO_ALLOWPRIVILEGEESCALTION" end'
-        tests:
-          test_items:
-            - flag: "NO_ALLOWPRIVILEGEESCALTION"
-              set: true
-              compare:
-                op: eq
-                value: "NO_ALLOWPRIVILEGEESCALTION"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the admission of containers with .spec.allowPrivilegeEscalation set to true.
-          You can label your namespaces as follows to restrict or enforce the policy:
-          kubectl label --overwrite ns NAMESPACE pod-security.kubernetes.io/enforce=restricted
-          You can also use the following to warn about policies:
-          kubectl label --overwrite ns --all pod-security.kubernetes.io/warn=baseline
-          For more information, refer to the official Kubernetes and Azure documentation on policies:
-          https://learn.microsoft.com/en-us/azure/governance/policy/concepts/policy-for-kubernetes
-        scored: true
-
-
-  - id: 4.3
-    text: "Azure Policy / OPA"
-    checks: []
-
-
-  - id: 4.4
-    text: "CNI Plugin"
-    checks:
-      - id: 4.4.1
-        text: "Ensure latest CNI version is used (Manual)"
-        type: "manual"
-        remediation: |
-          Review the documentation of AWS CNI plugin, and ensure latest CNI version is used.
-        scored: false
-
-      - id: 4.4.2
-        text: "Ensure that all Namespaces have Network Policies defined (Automated)"
-        audit: |
-          ns_without_np=$(comm -23 \
-            <(kubectl get ns -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | sort) \
-            <(kubectl get networkpolicy --all-namespaces -o jsonpath='{.items[*].metadata.namespace}' | tr ' ' '\n' | sort))
-          if [ -z "$ns_without_np" ]; then echo "ALL_NAMESPACES_HAVE_NETWORKPOLICIES"; else echo "MISSING_NETWORKPOLICIES"; fi
-        tests:
-          test_items:
-            - flag: "ALL_NAMESPACES_HAVE_NETWORKPOLICIES"
-              set: true
-              compare:
-                op: eq
-                value: "ALL_NAMESPACES_HAVE_NETWORKPOLICIES"
-        remediation: |
-          Define at least one NetworkPolicy in each namespace to control pod-level traffic. Example:
-
-          kubectl apply -n <namespace> -f - <<EOF
-          apiVersion: networking.k8s.io/v1
-          kind: NetworkPolicy
-          metadata:
-            name: default-deny-all
-          spec:
-            podSelector: {}
-            policyTypes:
-              - Ingress
-              - Egress
-          EOF
-
-          This denies all traffic unless explicitly allowed. Review and adjust policies per namespace as needed.
-        scored: true
-
-
-  - id: 4.5
-    text: "Secrets Management"
-    checks:
-      - id: 4.5.1
-        text: "Prefer using secrets as files over secrets as environment variables (Automated)"
-        audit: |
-          output=$(kubectl get all --all-namespaces -o jsonpath='{range .items[?(@..secretKeyRef)]} {.kind} {.metadata.name} {"\n"}{end}')
-          if [ -z "$output" ]; then echo "NO_ENV_SECRET_REFERENCES"; else echo "ENV_SECRET_REFERENCES_FOUND"; fi
-        tests:
-          test_items:
-            - flag: "NO_ENV_SECRET_REFERENCES"
-              set: true
-              compare:
-                op: eq
-                value: "NO_ENV_SECRET_REFERENCES"
-        remediation: |
-          Refactor application deployments to mount secrets as files instead of passing them as environment variables.
-          Avoid using `envFrom` or `env` with `secretKeyRef` in container specs.
-        scored: true
-
-
-      - id: 4.5.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-
-  - id: 4.6
-    text: "General Policies"
-    checks:
-      - id: 4.6.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 4.6.2
-        text: "Apply Security Context to Your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply security contexts to your pods. For a
-          suggested list of security contexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 4.6.3
-        text: "The default namespace should not be used (Automated)"
-        audit: |
-          output=$(kubectl get all -n default --no-headers 2>/dev/null | grep -v '^service\s\+kubernetes\s' || true)
-          if [ -z "$output" ]; then echo "DEFAULT_NAMESPACE_UNUSED"; else echo "DEFAULT_NAMESPACE_IN_USE"; fi
-        tests:
-          test_items:
-            - flag: "DEFAULT_NAMESPACE_UNUSED"
-              set: true
-              compare:
-                op: eq
-                value: "DEFAULT_NAMESPACE_UNUSED"
-        remediation: |
-          Avoid using the default namespace for user workloads.
-          - Create separate namespaces for your applications and infrastructure components.
-          - Move any user-defined resources out of the default namespace.
-
-          Example to create a namespace:
-          kubectl create namespace my-namespace
-
-          Example to move resources:
-          kubectl get deployment my-app -n default -o yaml | sed 's/namespace: default/namespace: my-namespace/' | kubectl apply -f -
-          kubectl delete deployment my-app -n default
-        scored: true

cfg/cis-1.10/config.yaml

@@ -1,2 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml

cfg/cis-1.10/controlplane.yaml

@@ -1,62 +0,0 @@
----
-controls:
-version: "cis-1.10"
-id: 3
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 3.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 3.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-        scored: false
-
-      - id: 3.1.2
-        text: "Service account token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of service account tokens.
-        scored: false
-
-      - id: 3.1.3
-        text: "Bootstrap token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of bootstrap tokens.
-        scored: false
-
-  - id: 3.2
-    text: "Logging"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that a minimal audit policy is created (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-policy-file"
-              set: true
-        remediation: |
-          Create an audit policy file for your cluster.
-        scored: false
-
-      - id: 3.2.2
-        text: "Ensure that the audit policy covers key security concerns (Manual)"
-        type: "manual"
-        remediation: |
-          Review the audit policy provided for the cluster and ensure that it covers
-          at least the following areas,
-          - Access to Secrets managed by the cluster. Care should be taken to only
-            log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in
-            order to avoid risk of logging sensitive data.
-          - Modification of Pod and Deployment objects.
-          - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.
-          For most requests, minimally logging at the Metadata level is recommended
-          (the most basic level of logging).
-        scored: false

cfg/cis-1.10/etcd.yaml

@@ -1,135 +0,0 @@
----
-controls:
-version: "cis-1.10"
-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"
-            - flag: "--key-file"
-              env: "ETCD_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--client-cert-auth"
-              env: "ETCD_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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"
-            - flag: "--peer-key-file"
-              env: "ETCD_PEER_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--peer-client-cert-auth"
-              env: "ETCD_PEER_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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
-        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 (Manual)"
-        audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
-        tests:
-          test_items:
-            - flag: "--trusted-ca-file"
-              env: "ETCD_TRUSTED_CA_FILE"
-        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: false

cfg/cis-1.10/master.yaml

@@ -1,917 +0,0 @@
----
-controls:
-version: "cis-1.10"
-id: 1
-text: "Control Plane Security Configuration"
-type: "master"
-groups:
-  - id: 1.1
-    text: "Control Plane Node Configuration Files"
-    checks:
-      - id: 1.1.1
-        text: "Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c permissions=%a $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the
-          control plane node.
-          For example, chmod 600 $apiserverconf
-        scored: true
-
-      - id: 1.1.2
-        text: "Ensure that the API server pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c %U:%G $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $apiserverconf
-        scored: true
-
-      - id: 1.1.3
-        text: "Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c permissions=%a $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $controllermanagerconf
-        scored: true
-
-      - id: 1.1.4
-        text: "Ensure that the controller manager pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c %U:%G $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $controllermanagerconf
-        scored: true
-
-      - id: 1.1.5
-        text: "Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c permissions=%a $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $schedulerconf
-        scored: true
-
-      - id: 1.1.6
-        text: "Ensure that the scheduler pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c %U:%G $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $schedulerconf
-        scored: true
-
-      - id: 1.1.7
-        text: "Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c permissions=%a; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $etcdconf
-        scored: true
-
-      - id: 1.1.8
-        text: "Ensure that the etcd pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c %U:%G; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $etcdconf
-        scored: true
-
-      - id: 1.1.9
-        text: "Ensure that the Container Network Interface file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c permissions=%a
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c permissions=%a
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.10
-        text: "Ensure that the Container Network Interface file ownership is set to root:root (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c %U:%G
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c %U:%G
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.11
-        text: "Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c permissions=%a "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "700"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above). For example,
-          chmod 700 /var/lib/etcd
-        scored: true
-
-      - id: 1.1.12
-        text: "Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c %U:%G "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "etcd:etcd"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above).
-          For example, chown etcd:etcd /var/lib/etcd
-        scored: true
-
-      - id: 1.1.13
-        text: "Ensure that the default administrative credential file permissions are set to 600 (Automated)"
-        audit: |
-         for adminconf in /etc/kubernetes/admin.conf /etc/kubernetes/super-admin.conf; do if test -e $adminconf; then stat -c "permissions=%a %n" $adminconf; fi; done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 /etc/kubernetes/admin.conf
-          On Kubernetes 1.29+ the super-admin.conf file should also be modified, if present.
-          For example, chmod 600 /etc/kubernetes/super-admin.conf
-        scored: true
-
-      - id: 1.1.14
-        text: "Ensure that the default administrative credential file ownership is set to root:root (Automated)"
-        audit: |
-         for adminconf in /etc/kubernetes/admin.conf /etc/kubernetes/super-admin.conf; do if test -e $adminconf; then stat -c "ownership=%U:%G %n" $adminconf; fi; done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "ownership"
-              compare:
-                op: eq
-                value: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root /etc/kubernetes/admin.conf
-          On Kubernetes 1.29+ the super-admin.conf file should also be modified, if present.
-          For example, chown root:root /etc/kubernetes/super-admin.conf
-        scored: true
-
-      - id: 1.1.15
-        text: "Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c permissions=%a $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.16
-        text: "Ensure that the scheduler.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c %U:%G $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.17
-        text: "Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c permissions=%a $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.18
-        text: "Ensure that the controller-manager.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c %U:%G $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.19
-        text: "Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)"
-        audit: "find /etc/kubernetes/pki/ | xargs stat -c %U:%G"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown -R root:root /etc/kubernetes/pki/
-        scored: true
-
-      - id: 1.1.20
-        text: "Ensure that the Kubernetes PKI certificate file permissions are set to 600 or more restrictive (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.crt' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.crt
-        scored: false
-
-      - id: 1.1.21
-        text: "Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.key' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.key
-        scored: false
-
-  - id: 1.2
-    text: "API Server"
-    checks:
-      - id: 1.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --anonymous-auth=false
-        scored: false
-
-      - id: 1.2.2
-        text: "Ensure that the --token-auth-file parameter is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--token-auth-file"
-              set: false
-        remediation: |
-          Follow the documentation and configure alternate mechanisms for authentication. Then,
-          edit the API server pod specification file $apiserverconf
-          on the control plane node and remove the --token-auth-file=<filename> parameter.
-        scored: true
-
-      - id: 1.2.3
-        text: "Ensure that the --DenyServiceExternalIPs is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "DenyServiceExternalIPs"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and add the `DenyServiceExternalIPs` plugin
-          to the enabled admission plugins, as such --enable-admission-plugin=DenyServiceExternalIPs.
-        scored: false
-
-      - id: 1.2.4
-        text: "Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--kubelet-client-certificate"
-            - flag: "--kubelet-client-key"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the
-          apiserver and kubelets. Then, edit API server pod specification file
-          $apiserverconf on the control plane node and set the
-          kubelet client certificate and key parameters as below.
-          --kubelet-client-certificate=<path/to/client-certificate-file>
-          --kubelet-client-key=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.5
-        text: "Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--kubelet-certificate-authority"
-        remediation: |
-          Follow the Kubernetes documentation and setup the TLS connection between
-          the apiserver and kubelets. Then, edit the API server pod specification file
-          $apiserverconf on the control plane node and set the
-          --kubelet-certificate-authority parameter to the path to the cert file for the certificate authority.
-          --kubelet-certificate-authority=<ca-string>
-        scored: true
-
-      - id: 1.2.6
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: nothave
-                value: "AlwaysAllow"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to values other than AlwaysAllow.
-          One such example could be as below.
-          --authorization-mode=RBAC
-        scored: true
-
-      - id: 1.2.7
-        text: "Ensure that the --authorization-mode argument includes Node (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "Node"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes Node.
-          --authorization-mode=Node,RBAC
-        scored: true
-
-      - id: 1.2.8
-        text: "Ensure that the --authorization-mode argument includes RBAC (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "RBAC"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes RBAC,
-          for example `--authorization-mode=Node,RBAC`.
-        scored: true
-
-      - id: 1.2.9
-        text: "Ensure that the admission control plugin EventRateLimit is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "EventRateLimit"
-        remediation: |
-          Follow the Kubernetes documentation and set the desired limits in a configuration file.
-          Then, edit the API server pod specification file $apiserverconf
-          and set the below parameters.
-          --enable-admission-plugins=...,EventRateLimit,...
-          --admission-control-config-file=<path/to/configuration/file>
-        scored: false
-
-      - id: 1.2.10
-        text: "Ensure that the admission control plugin AlwaysAdmit is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: nothave
-                value: AlwaysAdmit
-            - flag: "--enable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --enable-admission-plugins parameter, or set it to a
-          value that does not include AlwaysAdmit.
-        scored: true
-
-      - id: 1.2.11
-        text: "Ensure that the admission control plugin AlwaysPullImages is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "AlwaysPullImages"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          AlwaysPullImages.
-          --enable-admission-plugins=...,AlwaysPullImages,...
-        scored: false
-
-      - id: 1.2.12
-        text: "Ensure that the admission control plugin ServiceAccount is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "ServiceAccount"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Follow the documentation and create ServiceAccount objects as per your environment.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and ensure that the --disable-admission-plugins parameter is set to a
-          value that does not include ServiceAccount.
-        scored: true
-
-      - id: 1.2.13
-        text: "Ensure that the admission control plugin NamespaceLifecycle is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "NamespaceLifecycle"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --disable-admission-plugins parameter to
-          ensure it does not include NamespaceLifecycle.
-        scored: true
-
-      - id: 1.2.14
-        text: "Ensure that the admission control plugin NodeRestriction is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "NodeRestriction"
-        remediation: |
-          Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to a
-          value that includes NodeRestriction.
-          --enable-admission-plugins=...,NodeRestriction,...
-        scored: true
-
-      - id: 1.2.15
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.2.16
-        text: "Ensure that the --audit-log-path argument is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-path"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-path parameter to a suitable path and
-          file where you would like audit logs to be written, for example,
-          --audit-log-path=/var/log/apiserver/audit.log
-        scored: true
-
-      - id: 1.2.17
-        text: "Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxage"
-              compare:
-                op: gte
-                value: 30
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxage parameter to 30
-          or as an appropriate number of days, for example,
-          --audit-log-maxage=30
-        scored: true
-
-      - id: 1.2.18
-        text: "Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxbackup"
-              compare:
-                op: gte
-                value: 10
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxbackup parameter to 10 or to an appropriate
-          value. For example,
-          --audit-log-maxbackup=10
-        scored: true
-
-      - id: 1.2.19
-        text: "Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxsize"
-              compare:
-                op: gte
-                value: 100
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxsize parameter to an appropriate size in MB.
-          For example, to set it as 100 MB, --audit-log-maxsize=100
-        scored: true
-
-      - id: 1.2.20
-        text: "Ensure that the --request-timeout argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        type: manual
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          and set the below parameter as appropriate and if needed.
-          For example, --request-timeout=300s
-        scored: false
-
-      - id: 1.2.21
-        text: "Ensure that the --service-account-lookup argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--service-account-lookup"
-              set: false
-            - flag: "--service-account-lookup"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --service-account-lookup=true
-          Alternatively, you can delete the --service-account-lookup parameter from this file so
-          that the default takes effect.
-        scored: true
-
-      - id: 1.2.22
-        text: "Ensure that the --service-account-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-key-file"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --service-account-key-file parameter
-          to the public key file for service accounts. For example,
-          --service-account-key-file=<filename>
-        scored: true
-
-      - id: 1.2.23
-        text: "Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--etcd-certfile"
-            - flag: "--etcd-keyfile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate and key file parameters.
-          --etcd-certfile=<path/to/client-certificate-file>
-          --etcd-keyfile=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.24
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--tls-cert-file"
-            - flag: "--tls-private-key-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the TLS certificate and private key file parameters.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-        scored: true
-
-      - id: 1.2.25
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--client-ca-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the client certificate authority file.
-          --client-ca-file=<path/to/client-ca-file>
-        scored: true
-
-      - id: 1.2.26
-        text: "Ensure that the --etcd-cafile argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--etcd-cafile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate authority file parameter.
-          --etcd-cafile=<path/to/ca-file>
-        scored: true
-
-      - id: 1.2.27
-        text: "Ensure that the --encryption-provider-config argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--encryption-provider-config"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --encryption-provider-config parameter to the path of that file.
-          For example, --encryption-provider-config=</path/to/EncryptionConfig/File>
-        scored: false
-
-      - id: 1.2.28
-        text: "Ensure that encryption providers are appropriately configured (Manual)"
-        audit: |
-          ENCRYPTION_PROVIDER_CONFIG=$(ps -ef | grep $apiserverbin | grep -- --encryption-provider-config | sed 's%.*encryption-provider-config[= ]\([^ ]*\).*%\1%')
-          if test -e $ENCRYPTION_PROVIDER_CONFIG; then grep -A1 'providers:' $ENCRYPTION_PROVIDER_CONFIG | tail -n1 | grep -o "[A-Za-z]*" | sed 's/^/provider=/'; fi
-        tests:
-          test_items:
-            - flag: "provider"
-              compare:
-                op: valid_elements
-                value: "aescbc,kms,secretbox"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          In this file, choose aescbc, kms or secretbox as the encryption provider.
-        scored: false
-
-      - id: 1.2.29
-        text: "Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--tls-cipher-suites"
-              compare:
-                op: valid_elements
-                value: "TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256"
-        remediation: |
-          Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
-          on the control plane node and set the below parameter.
-          --tls-cipher-suites=TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
-          TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
-          TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
-        scored: false
-
-  - id: 1.3
-    text: "Controller Manager"
-    checks:
-      - id: 1.3.1
-        text: "Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--terminated-pod-gc-threshold"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --terminated-pod-gc-threshold to an appropriate threshold,
-          for example, --terminated-pod-gc-threshold=10
-        scored: false
-
-      - id: 1.3.2
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.3.3
-        text: "Ensure that the --use-service-account-credentials argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--use-service-account-credentials"
-              compare:
-                op: noteq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node to set the below parameter.
-          --use-service-account-credentials=true
-        scored: true
-
-      - id: 1.3.4
-        text: "Ensure that the --service-account-private-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-private-key-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --service-account-private-key-file parameter
-          to the private key file for service accounts.
-          --service-account-private-key-file=<filename>
-        scored: true
-
-      - id: 1.3.5
-        text: "Ensure that the --root-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--root-ca-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --root-ca-file parameter to the certificate bundle file`.
-          --root-ca-file=<path/to/file>
-        scored: true
-
-      - id: 1.3.6
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--feature-gates"
-              compare:
-                op: nothave
-                value: "RotateKubeletServerCertificate=false"
-              set: true
-            - flag: "--feature-gates"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.
-          --feature-gates=RotateKubeletServerCertificate=true
-        scored: true
-
-      - id: 1.3.7
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true
-
-  - id: 1.4
-    text: "Scheduler"
-    checks:
-      - id: 1.4.1
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf file
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.4.2
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true

cfg/cis-1.10/node.yaml

@@ -1,478 +0,0 @@
----
-controls:
-version: "cis-1.10"
-id: 4
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 4.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c permissions=%a $kubeletsvc; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chmod 600 $kubeletsvc
-        scored: true
-
-      - id: 4.1.2
-        text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-            - flag: "File not found"
-        remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
-        scored: true
-
-      - id: 4.1.3
-        text: "If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "permissions"
-              set: true
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $proxykubeconfig
-        scored: false
-
-      - id: 4.1.4
-        text: "If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chown root:root $proxykubeconfig
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.6
-        text: "Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.7
-        text: "Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command to modify the file permissions of the
-          --client-ca-file chmod 600 <filename>
-        scored: false
-
-      - id: 4.1.8
-        text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
-        tests:
-          test_items:
-            - flag: root:root
-              compare:
-                op: eq
-                value: root:root
-        remediation: |
-          Run the following command to modify the ownership of the --client-ca-file.
-          chown root:root <filename>
-        scored: false
-
-      - id: 4.1.9
-        text: "If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 600 $kubeletconf
-        scored: true
-
-      - id: 4.1.10
-        text: "If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: true
-
-  - id: 4.2
-    text: "Kubelet"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to
-          `false`.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          `--anonymous-auth=false`
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authorization.mode` to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.3
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication.x509.clientCAFile` to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.4
-        text: "Verify that the --read-only-port argument is set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              compare:
-                op: eq
-                value: 0
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `readOnlyPort` to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `streamingConnectionIdleTimeout` to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `makeIPTablesUtilChains` to `true`.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.7
-        text: "Ensure that the --hostname-override argument is not set (Manual)"
-        # This is one of those properties that can only be set as a command line argument.
-        # To check if the property is set as expected, we need to parse the kubelet command
-        # instead reading the Kubelet Configuration file.
-        audit: "/bin/ps -fC $kubeletbin"
-        tests:
-          test_items:
-            - flag: --hostname-override
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and remove the --hostname-override argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.8
-        text: "Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              compare:
-                op: gte
-                value: 0
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `eventRecordQPS` to an appropriate level.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.9
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cert-file
-              path: '{.tlsCertFile}'
-            - flag: --tls-private-key-file
-              path: '{.tlsPrivateKeyFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCertFile` to the location
-          of the certificate file to use to identify this Kubelet, and `tlsPrivateKeyFile`
-          to the location of the corresponding private key file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameters in KUBELET_CERTIFICATE_ARGS variable.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.10
-        text: "Ensure that the --rotate-certificates argument is not set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to add the line `rotateCertificates` to `true` or
-          remove it altogether to use the default value.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS
-          variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.11
-        text: "Verify that the RotateKubeletServerCertificate argument is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              compare:
-                op: nothave
-                value: false
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.12
-        text: "Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cipher-suites
-              path: '{range .tlsCipherSuites[:]}{}{'',''}{end}'
-              compare:
-                op: valid_elements
-                value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
-          TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          or to a subset of these values.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the --tls-cipher-suites parameter as follows, or to a subset of these values.
-          --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.13
-        text: "Ensure that a limit is set on pod PIDs (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --pod-max-pids
-              path: '{.podPidsLimit}'
-        remediation: |
-          Decide on an appropriate level for this parameter and set it,
-          either via the --pod-max-pids command line parameter or the PodPidsLimit configuration file setting.
-        scored: false
-
-  - id: 4.3
-    text: "kube-proxy"
-    checks:
-      - id: 4.3.1
-        text: "Ensure that the kube-proxy metrics service is bound to localhost (Automated)"
-        audit: "/bin/ps -fC $proxybin"
-        audit_config: "/bin/sh -c 'if test -e $proxykubeconfig; then cat $proxykubeconfig; fi'"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--metrics-bind-address"
-              path: '{.metricsBindAddress}'
-              compare:
-                op: has
-                value: "127.0.0.1"
-            - flag: "--metrics-bind-address"
-              path: '{.metricsBindAddress}'
-              set: false
-        remediation: |
-           Modify or remove any values which bind the metrics service to a non-localhost address.
-           The default value is 127.0.0.1:10249.
-        scored: true

cfg/cis-1.10/policies.yaml

@@ -1,559 +0,0 @@
----
-controls:
-version: "cis-1.10"
-id: 5
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 5.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 5.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Automated)"
-        audit: |
-          kubectl get clusterrolebindings -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECT:.subjects[*].name --no-headers | while read -r role_name role_binding subject
-          do
-            if [[ "${role_name}" != "cluster-admin" && "${role_binding}" == "cluster-admin" ]]; then
-              is_compliant="false"
-            else
-              is_compliant="true"
-            fi;
-            echo "**role_name: ${role_name} role_binding: ${role_binding} subject: ${subject} is_compliant: ${is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role : kubectl delete clusterrolebinding [name]
-          Condition: is_compliant is false if rolename is not cluster-admin and rolebinding is cluster-admin.
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize access to secrets (Automated)"
-        audit: "echo \"canGetListWatchSecretsAsSystemAuthenticated: $(kubectl auth can-i get,list,watch secrets --all-namespaces --as=system:authenticated)\""
-        tests:
-          test_items:
-            - flag: "canGetListWatchSecretsAsSystemAuthenticated"
-              compare:
-                op: eq
-                value: no
-        remediation: |
-          Where possible, remove get, list and watch access to Secret objects in the cluster.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Automated)"
-        audit: |
-          # Check Roles
-          kubectl get roles --all-namespaces -o custom-columns=ROLE_NAMESPACE:.metadata.namespace,ROLE_NAME:.metadata.name --no-headers | while read -r role_namespace role_name
-          do
-            role_rules=$(kubectl get role -n "${role_namespace}" "${role_name}" -o=json | jq -c '.rules')
-            if echo "${role_rules}" | grep -q "\[\"\*\"\]"; then
-              role_is_compliant="false"
-            else
-              role_is_compliant="true"
-            fi;
-            echo "**role_name: ${role_name} role_namespace: ${role_namespace} role_rules: ${role_rules} role_is_compliant: ${role_is_compliant}"
-          done
-
-          # Check ClusterRoles
-          kubectl get clusterroles -o custom-columns=CLUSTERROLE_NAME:.metadata.name --no-headers | while read -r clusterrole_name
-          do
-            clusterrole_rules=$(kubectl get clusterrole "${clusterrole_name}" -o=json | jq -c '.rules')
-            if echo "${clusterrole_rules}" | grep -q "\[\"\*\"\]"; then
-              clusterrole_is_compliant="false"
-            else
-              clusterrole_is_compliant="true"
-            fi;
-          echo "**clusterrole_name: ${clusterrole_name} clusterrole_rules: ${clusterrole_rules} clusterrole_is_compliant: ${clusterrole_is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "role_is_compliant"
-              compare:
-                op: eq
-                value: true
-              set: true
-            - flag: "clusterrole_is_compliant"
-              compare:
-                op: eq
-                value: true
-              set: true
-        remediation: |
-          Where possible replace any use of wildcards ["*"] in roles and clusterroles with specific
-          objects or actions.
-          Condition: role_is_compliant is false if ["*"] is found in rules.
-          Condition: clusterrole_is_compliant is false if ["*"] is found in rules.
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize access to create pods (Automated)"
-        audit: |
-          echo "canCreatePodsAsSystemAuthenticated: $(kubectl auth can-i create pods --all-namespaces --as=system:authenticated)"
-        tests:
-          test_items:
-            - flag: "canCreatePodsAsSystemAuthenticated"
-              compare:
-                op: eq
-                value: no
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-      - id: 5.1.5
-        text: "Ensure that default service accounts are not actively used (Automated)"
-        audit: |
-          kubectl get serviceaccount --all-namespaces --field-selector metadata.name=default -o=json | jq -r '.items[] | " namespace: \(.metadata.namespace), kind: \(.kind), name: \(.metadata.name), automountServiceAccountToken: \(.automountServiceAccountToken | if . == null then "notset" else . end )"' | xargs -L 1
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "automountServiceAccountToken"
-              compare:
-                op: eq
-                value: false
-              set: true
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific access
-          to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          `automountServiceAccountToken: false`.
-        scored: false
-
-      - id: 5.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAMESPACE:.metadata.namespace,POD_NAME:.metadata.name,POD_SERVICE_ACCOUNT:.spec.serviceAccount,POD_IS_AUTOMOUNTSERVICEACCOUNTTOKEN:.spec.automountServiceAccountToken --no-headers | while read -r pod_namespace pod_name pod_service_account pod_is_automountserviceaccounttoken
-          do
-            # Retrieve automountServiceAccountToken's value for ServiceAccount and Pod, set to notset if null or <none>.
-            svacc_is_automountserviceaccounttoken=$(kubectl get serviceaccount -n "${pod_namespace}" "${pod_service_account}" -o json | jq -r '.automountServiceAccountToken' | sed -e 's/<none>/notset/g' -e 's/null/notset/g')
-            pod_is_automountserviceaccounttoken=$(echo "${pod_is_automountserviceaccounttoken}" | sed -e 's/<none>/notset/g' -e 's/null/notset/g')
-            if [ "${svacc_is_automountserviceaccounttoken}" = "false" ] && ( [ "${pod_is_automountserviceaccounttoken}" = "false" ] || [ "${pod_is_automountserviceaccounttoken}" = "notset" ] ); then
-              is_compliant="true"
-            elif [ "${svacc_is_automountserviceaccounttoken}" = "true" ] && [ "${pod_is_automountserviceaccounttoken}" = "false" ]; then
-              is_compliant="true"
-            else
-              is_compliant="false"
-            fi
-            echo "**namespace: ${pod_namespace} pod_name: ${pod_name} service_account: ${pod_service_account} pod_is_automountserviceaccounttoken: ${pod_is_automountserviceaccounttoken} svacc_is_automountServiceAccountToken: ${svacc_is_automountserviceaccounttoken} is_compliant: ${is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Modify the definition of ServiceAccounts and Pods which do not need to mount service
-          account tokens to disable it, with `automountServiceAccountToken: false`.
-          If both the ServiceAccount and the Pod's .spec specify a value for automountServiceAccountToken, the Pod spec takes precedence.
-          Condition: Pod is_compliant to true when
-            - ServiceAccount is automountServiceAccountToken: false and Pod is automountServiceAccountToken: false or notset
-            - ServiceAccount is automountServiceAccountToken: true notset and Pod is automountServiceAccountToken: false
-        scored: false
-
-      - id: 5.1.7
-        text: "Avoid use of system:masters group (Manual)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 5.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-      - id: 5.1.9
-        text: "Minimize access to create persistent volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to PersistentVolume objects in the cluster.
-        scored: false
-
-      - id: 5.1.10
-        text: "Minimize access to the proxy sub-resource of nodes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the proxy sub-resource of node objects.
-        scored: false
-
-      - id: 5.1.11
-        text: "Minimize access to the approval sub-resource of certificatesigningrequests objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the approval sub-resource of certificatesigningrequests objects.
-        scored: false
-
-      - id: 5.1.12
-        text: "Minimize access to webhook configuration objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the validatingwebhookconfigurations or mutatingwebhookconfigurations objects
-        scored: false
-
-      - id: 5.1.13
-        text: "Minimize access to the service account token creation (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the token sub-resource of serviceaccount objects.
-        scored: false
-
-  - id: 5.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 5.2.1
-        text: "Ensure that the cluster has at least one active policy control mechanism in place (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that either Pod Security Admission or an external policy control system is in place
-          for every namespace which contains user workloads.
-        scored: false
-
-      - id: 5.2.2
-        text: "Minimize the admission of privileged containers (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve container(s) for each Pod.
-            kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o json | jq -c '.spec.containers[]' | while read -r container
-            do
-              # Retrieve container's name.
-              container_name=$(echo ${container} | jq -r '.name')
-              # Retrieve container's .securityContext.privileged value.
-              container_privileged=$(echo ${container} | jq -r '.securityContext.privileged' | sed -e 's/null/notset/g')
-              if [ "${container_privileged}" = "false" ] || [ "${container_privileged}" = "notset" ] ; then
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_privileged: ${container_privileged} is_compliant: true"
-              else
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_privileged: ${container_privileged} is_compliant: false"
-              fi
-            done
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of privileged containers.
-          Audit: the audit list all pods' containers to retrieve their .securityContext.privileged value.
-          Condition: is_compliant is false if container's `.securityContext.privileged` is set to `true`.
-          Default: by default, there are no restrictions on the creation of privileged containers.
-        scored: false
-
-      - id: 5.2.3
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve spec.hostPID for each pod.
-            pod_hostpid=$(kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o jsonpath='{.spec.hostPID}' 2>/dev/null)
-            if [ -z "${pod_hostpid}" ]; then
-              pod_hostpid="false"
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostpid: ${pod_hostpid} is_compliant: true"
-            else
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostpid: ${pod_hostpid} is_compliant: false"
-            fi
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostPID` containers.
-          Audit: the audit retrieves each Pod' spec.hostPID.
-          Condition: is_compliant is false if Pod's spec.hostPID is set to `true`.
-          Default: by default, there are no restrictions on the creation of hostPID containers.
-        scored: false
-
-      - id: 5.2.4
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve spec.hostIPC for each pod.
-            pod_hostipc=$(kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o jsonpath='{.spec.hostIPC}' 2>/dev/null)
-            if [ -z "${pod_hostipc}" ]; then
-              pod_hostipc="false"
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostipc: ${pod_hostipc} is_compliant: true"
-            else
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostipc: ${pod_hostipc} is_compliant: false"
-            fi
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostIPC` containers.
-          Audit: the audit retrieves each Pod' spec.IPC.
-          Condition: is_compliant is false if Pod's spec.hostIPC is set to `true`.
-          Default: by default, there are no restrictions on the creation of hostIPC containers.
-        scored: false
-
-      - id: 5.2.5
-        text: "Minimize the admission of containers wishing to share the host network namespace (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve spec.hostNetwork for each pod.
-            pod_hostnetwork=$(kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o jsonpath='{.spec.hostNetwork}' 2>/dev/null)
-            if [ -z "${pod_hostnetwork}" ]; then
-              pod_hostnetwork="false"
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostnetwork: ${pod_hostnetwork} is_compliant: true"
-            else
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostnetwork: ${pod_hostnetwork} is_compliant: false"
-            fi
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostNetwork` containers.
-          Audit: the audit retrieves each Pod' spec.hostNetwork.
-          Condition: is_compliant is false if Pod's spec.hostNetwork is set to `true`.
-          Default: by default, there are no restrictions on the creation of hostNetwork containers.
-        scored: false
-
-      - id: 5.2.6
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve container(s) for each Pod.
-            kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o json | jq -c '.spec.containers[]' | while read -r container
-            do
-              # Retrieve container's name
-              container_name=$(echo ${container} | jq -r '.name')
-              # Retrieve container's .securityContext.allowPrivilegeEscalation
-              container_allowprivesc=$(echo ${container} | jq -r '.securityContext.allowPrivilegeEscalation' | sed -e 's/null/notset/g')
-              if [ "${container_allowprivesc}" = "false" ] || [ "${container_allowprivesc}" = "notset" ]; then
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_allowprivesc: ${container_allowprivesc} is_compliant: true"
-              else
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_allowprivesc: ${container_allowprivesc} is_compliant: false"
-              fi
-            done
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `.securityContext.allowPrivilegeEscalation` set to `true`.
-          Audit: the audit retrieves each Pod's container(s) `.securityContext.allowPrivilegeEscalation`.
-          Condition: is_compliant is false if container's `.securityContext.allowPrivilegeEscalation` is set to `true`.
-          Default: If notset, privilege escalation is allowed (default to true). However if PSP/PSA is used with a `restricted` profile,
-          privilege escalation is explicitly disallowed unless configured otherwise.
-        scored: false
-
-      - id: 5.2.7
-        text: "Minimize the admission of root containers (Manual)"
-        type: "manual"
-        remediation: |
-          Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot`
-          or `MustRunAs` with the range of UIDs not including 0, is set.
-        scored: false
-
-      - id: 5.2.8
-        text: "Minimize the admission of containers with the NET_RAW capability (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with the `NET_RAW` capability.
-        scored: false
-
-      - id: 5.2.9
-        text: "Minimize the admission of containers with added capabilities (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve container(s) for each Pod.
-            kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o json | jq -c '.spec.containers[]' | while read -r container
-            do
-              # Retrieve container's name
-              container_name=$(echo ${container} | jq -r '.name')
-              # Retrieve container's added capabilities
-              container_caps_add=$(echo ${container} | jq -r '.securityContext.capabilities.add' | sed -e 's/null/notset/g')
-              # Set is_compliant to true by default.
-              is_compliant=true
-              caps_list=""
-              if [ "${container_caps_add}" != "notset" ]; then
-                # Loop through all caps and append caps_list, then set is_compliant to false.
-                for cap in $(echo "${container_caps_add}" | jq -r '.[]'); do
-                caps_list+="${cap},"
-                is_compliant=false
-                done
-                # Remove trailing comma for the last list member.
-                caps_list=${caps_list%,}
-              fi
-              if [ "${is_compliant}" = true ]; then
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} container_caps_add: ${container_caps_add} is_compliant: true"
-              else
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} container_caps_add: ${caps_list} is_compliant: false"
-              fi
-            done
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Ensure that `allowedCapabilities` is not present in policies for the cluster unless
-          it is set to an empty array.
-          Audit: the audit retrieves each Pod's container(s) added capabilities.
-          Condition: is_compliant is false if added capabilities are added for a given container.
-          Default: Containers run with a default set of capabilities as assigned by the Container Runtime.
-        scored: false
-
-      - id: 5.2.10
-        text: "Minimize the admission of containers with capabilities assigned (Manual)"
-        type: "manual"
-        remediation: |
-          Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
-          a PSP which forbids the admission of containers which do not drop all capabilities.
-        scored: false
-
-      - id: 5.2.11
-        text: "Minimize the admission of Windows HostProcess containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers that have `.securityContext.windowsOptions.hostProcess` set to `true`.
-        scored: false
-
-      - id: 5.2.12
-        text: "Minimize the admission of HostPath volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `hostPath` volumes.
-        scored: false
-
-      - id: 5.2.13
-        text: "Minimize the admission of containers which use HostPorts (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers which use `hostPort` sections.
-        scored: false
-
-  - id: 5.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 5.3.1
-        text: "Ensure that the CNI in use supports NetworkPolicies (Manual)"
-        type: "manual"
-        remediation: |
-          If the CNI plugin in use does not support network policies, consideration should be given to
-          making use of a different plugin, or finding an alternate mechanism for restricting traffic
-          in the Kubernetes cluster.
-        scored: false
-
-      - id: 5.3.2
-        text: "Ensure that all Namespaces have NetworkPolicies defined (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 5.4
-    text: "Secrets Management"
-    checks:
-      - id: 5.4.1
-        text: "Prefer using Secrets as files over Secrets as environment variables (Manual)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read Secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 5.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the Secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 5.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 5.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-        scored: false
-
-  - id: 5.7
-    text: "General Policies"
-    checks:
-      - id: 5.7.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 5.7.2
-        text: "Ensure that the seccomp profile is set to docker/default in your Pod definitions (Manual)"
-        type: "manual"
-        remediation: |
-          Use `securityContext` to enable the docker/default seccomp profile in your pod definitions.
-          An example is as below:
-            securityContext:
-              seccompProfile:
-                type: RuntimeDefault
-        scored: false
-
-      - id: 5.7.3
-        text: "Apply SecurityContext to your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply SecurityContexts to your Pods. For a
-          suggested list of SecurityContexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 5.7.4
-        text: "The default namespace should not be used (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/cis-1.11/config.yaml

@@ -1,2 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml

cfg/cis-1.11/controlplane.yaml

@@ -1,62 +0,0 @@
----
-controls:
-version: "cis-1.11"
-id: 3
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 3.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 3.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-        scored: false
-
-      - id: 3.1.2
-        text: "Service account token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of service account tokens.
-        scored: false
-
-      - id: 3.1.3
-        text: "Bootstrap token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of bootstrap tokens.
-        scored: false
-
-  - id: 3.2
-    text: "Logging"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that a minimal audit policy is created (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-policy-file"
-              set: true
-        remediation: |
-          Create an audit policy file for your cluster.
-        scored: false
-
-      - id: 3.2.2
-        text: "Ensure that the audit policy covers key security concerns (Manual)"
-        type: "manual"
-        remediation: |
-          Review the audit policy provided for the cluster and ensure that it covers
-          at least the following areas,
-          - Access to Secrets managed by the cluster. Care should be taken to only
-            log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in
-            order to avoid risk of logging sensitive data.
-          - Modification of Pod and Deployment objects.
-          - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.
-          For most requests, minimally logging at the Metadata level is recommended
-          (the most basic level of logging).
-        scored: false

cfg/cis-1.11/etcd.yaml

@@ -1,135 +0,0 @@
----
-controls:
-version: "cis-1.11"
-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"
-            - flag: "--key-file"
-              env: "ETCD_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--client-cert-auth"
-              env: "ETCD_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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"
-            - flag: "--peer-key-file"
-              env: "ETCD_PEER_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--peer-client-cert-auth"
-              env: "ETCD_PEER_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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
-        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 (Manual)"
-        audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
-        tests:
-          test_items:
-            - flag: "--trusted-ca-file"
-              env: "ETCD_TRUSTED_CA_FILE"
-        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: false

cfg/cis-1.11/master.yaml

@@ -1,932 +0,0 @@
----
-controls:
-version: "cis-1.11"
-id: 1
-text: "Control Plane Security Configuration"
-type: "master"
-groups:
-  - id: 1.1
-    text: "Control Plane Node Configuration Files"
-    checks:
-      - id: 1.1.1
-        text: "Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c permissions=%a $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the
-          control plane node.
-          For example, chmod 600 $apiserverconf
-        scored: true
-
-      - id: 1.1.2
-        text: "Ensure that the API server pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c %U:%G $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $apiserverconf
-        scored: true
-
-      - id: 1.1.3
-        text: "Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c permissions=%a $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $controllermanagerconf
-        scored: true
-
-      - id: 1.1.4
-        text: "Ensure that the controller manager pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c %U:%G $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $controllermanagerconf
-        scored: true
-
-      - id: 1.1.5
-        text: "Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c permissions=%a $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $schedulerconf
-        scored: true
-
-      - id: 1.1.6
-        text: "Ensure that the scheduler pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c %U:%G $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $schedulerconf
-        scored: true
-
-      - id: 1.1.7
-        text: "Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c permissions=%a; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $etcdconf
-        scored: true
-
-      - id: 1.1.8
-        text: "Ensure that the etcd pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c %U:%G; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $etcdconf
-        scored: true
-
-      - id: 1.1.9
-        text: "Ensure that the Container Network Interface file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c permissions=%a
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c permissions=%a
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.10
-        text: "Ensure that the Container Network Interface file ownership is set to root:root (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c %U:%G
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c %U:%G
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.11
-        text: "Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c permissions=%a "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "700"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above). For example,
-          chmod 700 /var/lib/etcd
-        scored: true
-
-      - id: 1.1.12
-        text: "Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c %U:%G "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "etcd:etcd"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above).
-          For example, chown etcd:etcd /var/lib/etcd
-        scored: true
-
-      - id: 1.1.13
-        text: "Ensure that the default administrative credential file permissions are set to 600 (Automated)"
-        audit: |
-         for adminconf in /etc/kubernetes/admin.conf /etc/kubernetes/super-admin.conf; do if test -e $adminconf; then stat -c "permissions=%a %n" $adminconf; fi; done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 /etc/kubernetes/admin.conf
-          On Kubernetes 1.29+ the super-admin.conf file should also be modified, if present.
-          For example, chmod 600 /etc/kubernetes/super-admin.conf
-        scored: true
-
-      - id: 1.1.14
-        text: "Ensure that the default administrative credential file ownership is set to root:root (Automated)"
-        audit: |
-         for adminconf in /etc/kubernetes/admin.conf /etc/kubernetes/super-admin.conf; do if test -e $adminconf; then stat -c "ownership=%U:%G %n" $adminconf; fi; done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "ownership"
-              compare:
-                op: eq
-                value: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root /etc/kubernetes/admin.conf
-          On Kubernetes 1.29+ the super-admin.conf file should also be modified, if present.
-          For example, chown root:root /etc/kubernetes/super-admin.conf
-        scored: true
-
-      - id: 1.1.15
-        text: "Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c permissions=%a $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.16
-        text: "Ensure that the scheduler.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c %U:%G $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.17
-        text: "Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c permissions=%a $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.18
-        text: "Ensure that the controller-manager.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c %U:%G $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.19
-        text: "Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)"
-        audit: "find /etc/kubernetes/pki/ | xargs stat -c %U:%G"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown -R root:root /etc/kubernetes/pki/
-        scored: true
-
-      - id: 1.1.20
-        text: "Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.crt' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 644 /etc/kubernetes/pki/*.crt
-        scored: false
-
-      - id: 1.1.21
-        text: "Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.key' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.key
-        scored: false
-
-  - id: 1.2
-    text: "API Server"
-    checks:
-      - id: 1.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --anonymous-auth=false
-        scored: false
-
-      - id: 1.2.2
-        text: "Ensure that the --token-auth-file parameter is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--token-auth-file"
-              set: false
-        remediation: |
-          Follow the documentation and configure alternate mechanisms for authentication. Then,
-          edit the API server pod specification file $apiserverconf
-          on the control plane node and remove the --token-auth-file=<filename> parameter.
-        scored: true
-
-      - id: 1.2.3
-        text: "Ensure that the --DenyServiceExternalIPs is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "DenyServiceExternalIPs"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and add the `DenyServiceExternalIPs` plugin
-          to the enabled admission plugins, as such --enable-admission-plugin=DenyServiceExternalIPs.
-        scored: false
-
-      - id: 1.2.4
-        text: "Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--kubelet-client-certificate"
-            - flag: "--kubelet-client-key"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the
-          apiserver and kubelets. Then, edit API server pod specification file
-          $apiserverconf on the control plane node and set the
-          kubelet client certificate and key parameters as below.
-          --kubelet-client-certificate=<path/to/client-certificate-file>
-          --kubelet-client-key=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.5
-        text: "Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--kubelet-certificate-authority"
-        remediation: |
-          Follow the Kubernetes documentation and setup the TLS connection between
-          the apiserver and kubelets. Then, edit the API server pod specification file
-          $apiserverconf on the control plane node and set the
-          --kubelet-certificate-authority parameter to the path to the cert file for the certificate authority.
-          --kubelet-certificate-authority=<ca-string>
-        scored: true
-
-      - id: 1.2.6
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: nothave
-                value: "AlwaysAllow"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to values other than AlwaysAllow.
-          One such example could be as below.
-          --authorization-mode=RBAC
-        scored: true
-
-      - id: 1.2.7
-        text: "Ensure that the --authorization-mode argument includes Node (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "Node"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes Node.
-          --authorization-mode=Node,RBAC
-        scored: true
-
-      - id: 1.2.8
-        text: "Ensure that the --authorization-mode argument includes RBAC (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "RBAC"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes RBAC,
-          for example `--authorization-mode=Node,RBAC`.
-        scored: true
-
-      - id: 1.2.9
-        text: "Ensure that the admission control plugin EventRateLimit is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "EventRateLimit"
-        remediation: |
-          Follow the Kubernetes documentation and set the desired limits in a configuration file.
-          Then, edit the API server pod specification file $apiserverconf
-          and set the below parameters.
-          --enable-admission-plugins=...,EventRateLimit,...
-          --admission-control-config-file=<path/to/configuration/file>
-        scored: false
-
-      - id: 1.2.10
-        text: "Ensure that the admission control plugin AlwaysAdmit is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: nothave
-                value: AlwaysAdmit
-            - flag: "--enable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --enable-admission-plugins parameter, or set it to a
-          value that does not include AlwaysAdmit.
-        scored: true
-
-      - id: 1.2.11
-        text: "Ensure that the admission control plugin AlwaysPullImages is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "AlwaysPullImages"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          AlwaysPullImages.
-          --enable-admission-plugins=...,AlwaysPullImages,...
-        scored: false
-
-      - id: 1.2.12
-        text: "Ensure that the admission control plugin ServiceAccount is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "ServiceAccount"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Follow the documentation and create ServiceAccount objects as per your environment.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and ensure that the --disable-admission-plugins parameter is set to a
-          value that does not include ServiceAccount.
-        scored: true
-
-      - id: 1.2.13
-        text: "Ensure that the admission control plugin NamespaceLifecycle is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "NamespaceLifecycle"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --disable-admission-plugins parameter to
-          ensure it does not include NamespaceLifecycle.
-        scored: true
-
-      - id: 1.2.14
-        text: "Ensure that the admission control plugin NodeRestriction is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "NodeRestriction"
-        remediation: |
-          Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to a
-          value that includes NodeRestriction.
-          --enable-admission-plugins=...,NodeRestriction,...
-        scored: true
-
-      - id: 1.2.15
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.2.16
-        text: "Ensure that the --audit-log-path argument is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-path"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-path parameter to a suitable path and
-          file where you would like audit logs to be written, for example,
-          --audit-log-path=/var/log/apiserver/audit.log
-        scored: true
-
-      - id: 1.2.17
-        text: "Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxage"
-              compare:
-                op: gte
-                value: 30
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxage parameter to 30
-          or as an appropriate number of days, for example,
-          --audit-log-maxage=30
-        scored: true
-
-      - id: 1.2.18
-        text: "Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxbackup"
-              compare:
-                op: gte
-                value: 10
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxbackup parameter to 10 or to an appropriate
-          value. For example,
-          --audit-log-maxbackup=10
-        scored: true
-
-      - id: 1.2.19
-        text: "Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxsize"
-              compare:
-                op: gte
-                value: 100
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxsize parameter to an appropriate size in MB.
-          For example, to set it as 100 MB, --audit-log-maxsize=100
-        scored: true
-
-      - id: 1.2.20
-        text: "Ensure that the --request-timeout argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        type: manual
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          and set the below parameter as appropriate and if needed.
-          For example, --request-timeout=300s
-        scored: false
-
-      - id: 1.2.21
-        text: "Ensure that the --service-account-lookup argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--service-account-lookup"
-              set: false
-            - flag: "--service-account-lookup"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --service-account-lookup=true
-          Alternatively, you can delete the --service-account-lookup parameter from this file so
-          that the default takes effect.
-        scored: true
-
-      - id: 1.2.22
-        text: "Ensure that the --service-account-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-key-file"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --service-account-key-file parameter
-          to the public key file for service accounts. For example,
-          --service-account-key-file=<filename>
-        scored: true
-
-      - id: 1.2.23
-        text: "Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--etcd-certfile"
-            - flag: "--etcd-keyfile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate and key file parameters.
-          --etcd-certfile=<path/to/client-certificate-file>
-          --etcd-keyfile=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.24
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--tls-cert-file"
-            - flag: "--tls-private-key-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the TLS certificate and private key file parameters.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-        scored: true
-
-      - id: 1.2.25
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--client-ca-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the client certificate authority file.
-          --client-ca-file=<path/to/client-ca-file>
-        scored: true
-
-      - id: 1.2.26
-        text: "Ensure that the --etcd-cafile argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--etcd-cafile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate authority file parameter.
-          --etcd-cafile=<path/to/ca-file>
-        scored: true
-
-      - id: 1.2.27
-        text: "Ensure that the --encryption-provider-config argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--encryption-provider-config"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --encryption-provider-config parameter to the path of that file.
-          For example, --encryption-provider-config=</path/to/EncryptionConfig/File>
-        scored: false
-
-      - id: 1.2.28
-        text: "Ensure that encryption providers are appropriately configured (Manual)"
-        audit: |
-          ENCRYPTION_PROVIDER_CONFIG=$(ps -ef | grep $apiserverbin | grep -- --encryption-provider-config | sed 's%.*encryption-provider-config[= ]\([^ ]*\).*%\1%')
-          if test -e $ENCRYPTION_PROVIDER_CONFIG; then grep -A1 'providers:' $ENCRYPTION_PROVIDER_CONFIG | tail -n1 | grep -o "[A-Za-z]*" | sed 's/^/provider=/'; fi
-        tests:
-          test_items:
-            - flag: "provider"
-              compare:
-                op: valid_elements
-                value: "aescbc,kms,secretbox"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          In this file, choose aescbc, kms or secretbox as the encryption provider.
-        scored: false
-
-      - id: 1.2.29
-        text: "Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--tls-cipher-suites"
-              compare:
-                op: valid_elements
-                value: "TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256"
-        remediation: |
-          Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
-          on the control plane node and set the below parameter.
-          --tls-cipher-suites=TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
-          TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
-          TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
-        scored: false
-
-      - id: 1.2.30
-        text: "Ensure that the --service-account-extend-token-expiration parameter is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-extend-token-expiration"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the Control Plane node and set the --service-account-extend-token-expiration parameter to false.
-          `--service-account-extend-token-expiration=false`
-          By default, this parameter is set to true.
-        scored: true
-
-  - id: 1.3
-    text: "Controller Manager"
-    checks:
-      - id: 1.3.1
-        text: "Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--terminated-pod-gc-threshold"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --terminated-pod-gc-threshold to an appropriate threshold,
-          for example, --terminated-pod-gc-threshold=10
-        scored: false
-
-      - id: 1.3.2
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.3.3
-        text: "Ensure that the --use-service-account-credentials argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--use-service-account-credentials"
-              compare:
-                op: noteq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node to set the below parameter.
-          --use-service-account-credentials=true
-        scored: true
-
-      - id: 1.3.4
-        text: "Ensure that the --service-account-private-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-private-key-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --service-account-private-key-file parameter
-          to the private key file for service accounts.
-          --service-account-private-key-file=<filename>
-        scored: true
-
-      - id: 1.3.5
-        text: "Ensure that the --root-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--root-ca-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --root-ca-file parameter to the certificate bundle file`.
-          --root-ca-file=<path/to/file>
-        scored: true
-
-      - id: 1.3.6
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--feature-gates"
-              compare:
-                op: nothave
-                value: "RotateKubeletServerCertificate=false"
-              set: true
-            - flag: "--feature-gates"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.
-          --feature-gates=RotateKubeletServerCertificate=true
-        scored: true
-
-      - id: 1.3.7
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true
-
-  - id: 1.4
-    text: "Scheduler"
-    checks:
-      - id: 1.4.1
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf file
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.4.2
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true

cfg/cis-1.11/node.yaml

@@ -1,509 +0,0 @@
----
-controls:
-version: "cis-1.11"
-id: 4
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 4.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c permissions=%a $kubeletsvc; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chmod 600 $kubeletsvc
-        scored: true
-
-      - id: 4.1.2
-        text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-            - flag: "File not found"
-        remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
-        scored: true
-
-      - id: 4.1.3
-        text: "If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "permissions"
-              set: true
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $proxykubeconfig
-        scored: false
-
-      - id: 4.1.4
-        text: "If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chown root:root $proxykubeconfig
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.6
-        text: "Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.7
-        text: "Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the following command to modify the file permissions of the
-          --client-ca-file chmod 644 <filename>
-        scored: false
-
-      - id: 4.1.8
-        text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
-        tests:
-          test_items:
-            - flag: root:root
-              compare:
-                op: eq
-                value: root:root
-        remediation: |
-          Run the following command to modify the ownership of the --client-ca-file.
-          chown root:root <filename>
-        scored: false
-
-      - id: 4.1.9
-        text: "If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 600 $kubeletconf
-        scored: true
-
-      - id: 4.1.10
-        text: "If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: true
-
-  - id: 4.2
-    text: "Kubelet"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to
-          `false`.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          `--anonymous-auth=false`
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authorization.mode` to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.3
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication.x509.clientCAFile` to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.4
-        text: "Verify that if defined, the --read-only-port argument is set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              compare:
-                op: eq
-                value: 0
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `readOnlyPort` to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `streamingConnectionIdleTimeout` to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `makeIPTablesUtilChains` to `true`.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.7
-        text: "Ensure that the --hostname-override argument is not set (Manual)"
-        # This is one of those properties that can only be set as a command line argument.
-        # To check if the property is set as expected, we need to parse the kubelet command
-        # instead reading the Kubelet Configuration file.
-        audit: "/bin/ps -fC $kubeletbin"
-        tests:
-          test_items:
-            - flag: --hostname-override
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and remove the --hostname-override argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.8
-        text: "Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              compare:
-                op: gte
-                value: 0
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `eventRecordQPS` to an appropriate level.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.9
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cert-file
-              path: '{.tlsCertFile}'
-            - flag: --tls-private-key-file
-              path: '{.tlsPrivateKeyFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCertFile` to the location
-          of the certificate file to use to identify this Kubelet, and `tlsPrivateKeyFile`
-          to the location of the corresponding private key file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameters in KUBELET_CERTIFICATE_ARGS variable.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.10
-        text: "Ensure that the --rotate-certificates argument is not set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to add the line `rotateCertificates` to `true` or
-          remove it altogether to use the default value.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS
-          variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.11
-        text: "Verify that the RotateKubeletServerCertificate argument is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              compare:
-                op: nothave
-                value: false
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.12
-        text: "Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cipher-suites
-              path: '{range .tlsCipherSuites[:]}{}{'',''}{end}'
-              compare:
-                op: valid_elements
-                value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
-          TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          or to a subset of these values.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the --tls-cipher-suites parameter as follows, or to a subset of these values.
-          --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.13
-        text: "Ensure that a limit is set on pod PIDs (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --pod-max-pids
-              path: '{.podPidsLimit}'
-        remediation: |
-          Decide on an appropriate level for this parameter and set it,
-          either via the --pod-max-pids command line parameter or the PodPidsLimit configuration file setting.
-        scored: false
-
-      - id: 4.2.14
-        text: "Ensure that the --seccomp-default parameter is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --seccomp-default
-              path: '{.seccompDefault}'
-        remediation: |
-          Set the parameter, either via the --seccomp-default command line parameter or the
-          seccompDefault configuration file setting.
-          By default the seccomp profile is not enabled.
-        scored: false
-
-      - id: 4.2.15
-        text: "Ensure that the --IPAddressDeny is set to any (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --IPAddressDeny
-              path: '{.IPAddressDeny}'
-        remediation: |
-         Configuring the setting IPAddressDeny=any will deny service to any IP address not specified in the complimentary setting IPAddressAllow configuration parameter (
-         IPAddressDeny=any
-         IPAddressAllow={{ kubelet_secure_addresses }}
-         *Note
-           kubelet_secure_addresses: "localhost link-local {{ kube_pods_subnets |regex_replace(',', ' ') }} {{ kube_node_addresses }} {{ loadbalancer_apiserver.address | default('')"
-         By default IPAddressDeny is not enabled.
-        scored: false
-
-  - id: 4.3
-    text: "kube-proxy"
-    checks:
-      - id: 4.3.1
-        text: "Ensure that the kube-proxy metrics service is bound to localhost (Automated)"
-        audit: "/bin/ps -fC $proxybin"
-        audit_config: "/bin/sh -c 'if test -e $proxykubeconfig; then cat $proxykubeconfig; fi'"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--metrics-bind-address"
-              path: '{.metricsBindAddress}'
-              compare:
-                op: has
-                value: "127.0.0.1"
-            - flag: "--metrics-bind-address"
-              path: '{.metricsBindAddress}'
-              set: false
-        remediation: |
-           Modify or remove any values which bind the metrics service to a non-localhost address.
-           The default value is 127.0.0.1:10249.
-        scored: true

cfg/cis-1.11/policies.yaml

@@ -1,560 +0,0 @@
----
-controls:
-version: "cis-1.11"
-id: 5
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 5.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 5.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Manual)"
-        audit: |
-          kubectl get clusterrolebindings -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECT:.subjects[*].name --no-headers | while read -r role_name role_binding subject
-          do
-            if [[ "${role_name}" != "cluster-admin" && "${role_binding}" == "cluster-admin" ]]; then
-              is_compliant="false"
-            else
-              is_compliant="true"
-            fi;
-            echo "**role_name: ${role_name} role_binding: ${role_binding} subject: ${subject} is_compliant: ${is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role : kubectl delete clusterrolebinding [name]
-          Condition: is_compliant is false if rolename is not cluster-admin and rolebinding is cluster-admin.
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize access to secrets (Manual)"
-        audit: "echo \"canGetListWatchSecretsAsSystemAuthenticated: $(kubectl auth can-i get,list,watch secrets --all-namespaces --as=system:authenticated)\""
-        tests:
-          test_items:
-            - flag: "canGetListWatchSecretsAsSystemAuthenticated"
-              compare:
-                op: eq
-                value: no
-        remediation: |
-          Where possible, remove get, list and watch access to Secret objects in the cluster.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Manual)"
-        audit: |
-          # Check Roles
-          kubectl get roles --all-namespaces -o custom-columns=ROLE_NAMESPACE:.metadata.namespace,ROLE_NAME:.metadata.name --no-headers | while read -r role_namespace role_name
-          do
-            role_rules=$(kubectl get role -n "${role_namespace}" "${role_name}" -o=json | jq -c '.rules')
-            if echo "${role_rules}" | grep -q "\[\"\*\"\]"; then
-              role_is_compliant="false"
-            else
-              role_is_compliant="true"
-            fi;
-            echo "**role_name: ${role_name} role_namespace: ${role_namespace} role_rules: ${role_rules} role_is_compliant: ${role_is_compliant}"
-          done
-
-          # Check ClusterRoles
-          kubectl get clusterroles -o custom-columns=CLUSTERROLE_NAME:.metadata.name --no-headers | while read -r clusterrole_name
-          do
-            clusterrole_rules=$(kubectl get clusterrole "${clusterrole_name}" -o=json | jq -c '.rules')
-            if echo "${clusterrole_rules}" | grep -q "\[\"\*\"\]"; then
-              clusterrole_is_compliant="false"
-            else
-              clusterrole_is_compliant="true"
-            fi;
-          echo "**clusterrole_name: ${clusterrole_name} clusterrole_rules: ${clusterrole_rules} clusterrole_is_compliant: ${clusterrole_is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "role_is_compliant"
-              compare:
-                op: eq
-                value: true
-              set: true
-            - flag: "clusterrole_is_compliant"
-              compare:
-                op: eq
-                value: true
-              set: true
-        remediation: |
-          Where possible replace any use of wildcards ["*"] in roles and clusterroles with specific
-          objects or actions.
-          Condition: role_is_compliant is false if ["*"] is found in rules.
-          Condition: clusterrole_is_compliant is false if ["*"] is found in rules.
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize access to create pods (Manual)"
-        audit: |
-          echo "canCreatePodsAsSystemAuthenticated: $(kubectl auth can-i create pods --all-namespaces --as=system:authenticated)"
-        tests:
-          test_items:
-            - flag: "canCreatePodsAsSystemAuthenticated"
-              compare:
-                op: eq
-                value: no
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-
-      - id: 5.1.5
-        text: "Ensure that default service accounts are not actively used (Manual)"
-        audit: |
-          kubectl get serviceaccount --all-namespaces --field-selector metadata.name=default -o=json | jq -r '.items[] | " namespace: \(.metadata.namespace), kind: \(.kind), name: \(.metadata.name), automountServiceAccountToken: \(.automountServiceAccountToken | if . == null then "notset" else . end )"' | xargs -L 1
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "automountServiceAccountToken"
-              compare:
-                op: eq
-                value: false
-              set: true
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific access
-          to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          `automountServiceAccountToken: false`.
-        scored: false
-
-      - id: 5.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAMESPACE:.metadata.namespace,POD_NAME:.metadata.name,POD_SERVICE_ACCOUNT:.spec.serviceAccount,POD_IS_AUTOMOUNTSERVICEACCOUNTTOKEN:.spec.automountServiceAccountToken --no-headers | while read -r pod_namespace pod_name pod_service_account pod_is_automountserviceaccounttoken
-          do
-            # Retrieve automountServiceAccountToken's value for ServiceAccount and Pod, set to notset if null or <none>.
-            svacc_is_automountserviceaccounttoken=$(kubectl get serviceaccount -n "${pod_namespace}" "${pod_service_account}" -o json | jq -r '.automountServiceAccountToken' | sed -e 's/<none>/notset/g' -e 's/null/notset/g')
-            pod_is_automountserviceaccounttoken=$(echo "${pod_is_automountserviceaccounttoken}" | sed -e 's/<none>/notset/g' -e 's/null/notset/g')
-            if [ "${svacc_is_automountserviceaccounttoken}" = "false" ] && ( [ "${pod_is_automountserviceaccounttoken}" = "false" ] || [ "${pod_is_automountserviceaccounttoken}" = "notset" ] ); then
-              is_compliant="true"
-            elif [ "${svacc_is_automountserviceaccounttoken}" = "true" ] && [ "${pod_is_automountserviceaccounttoken}" = "false" ]; then
-              is_compliant="true"
-            else
-              is_compliant="false"
-            fi
-            echo "**namespace: ${pod_namespace} pod_name: ${pod_name} service_account: ${pod_service_account} pod_is_automountserviceaccounttoken: ${pod_is_automountserviceaccounttoken} svacc_is_automountServiceAccountToken: ${svacc_is_automountserviceaccounttoken} is_compliant: ${is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Modify the definition of ServiceAccounts and Pods which do not need to mount service
-          account tokens to disable it, with `automountServiceAccountToken: false`.
-          If both the ServiceAccount and the Pod's .spec specify a value for automountServiceAccountToken, the Pod spec takes precedence.
-          Condition: Pod is_compliant to true when
-            - ServiceAccount is automountServiceAccountToken: false and Pod is automountServiceAccountToken: false or notset
-            - ServiceAccount is automountServiceAccountToken: true notset and Pod is automountServiceAccountToken: false
-        scored: false
-
-      - id: 5.1.7
-        text: "Avoid use of system:masters group (Manual)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 5.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-      - id: 5.1.9
-        text: "Minimize access to create persistent volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to PersistentVolume objects in the cluster.
-        scored: false
-
-      - id: 5.1.10
-        text: "Minimize access to the proxy sub-resource of nodes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the proxy sub-resource of node objects.
-        scored: false
-
-      - id: 5.1.11
-        text: "Minimize access to the approval sub-resource of certificatesigningrequests objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the approval sub-resource of certificatesigningrequests objects.
-        scored: false
-
-      - id: 5.1.12
-        text: "Minimize access to webhook configuration objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the validatingwebhookconfigurations or mutatingwebhookconfigurations objects
-        scored: false
-
-      - id: 5.1.13
-        text: "Minimize access to the service account token creation (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the token sub-resource of serviceaccount objects.
-        scored: false
-
-  - id: 5.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 5.2.1
-        text: "Ensure that the cluster has at least one active policy control mechanism in place (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that either Pod Security Admission or an external policy control system is in place
-          for every namespace which contains user workloads.
-        scored: false
-
-      - id: 5.2.2
-        text: "Minimize the admission of privileged containers (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve container(s) for each Pod.
-            kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o json | jq -c '.spec.containers[]' | while read -r container
-            do
-              # Retrieve container's name.
-              container_name=$(echo ${container} | jq -r '.name')
-              # Retrieve container's .securityContext.privileged value.
-              container_privileged=$(echo ${container} | jq -r '.securityContext.privileged' | sed -e 's/null/notset/g')
-              if [ "${container_privileged}" = "false" ] || [ "${container_privileged}" = "notset" ] ; then
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_privileged: ${container_privileged} is_compliant: true"
-              else
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_privileged: ${container_privileged} is_compliant: false"
-              fi
-            done
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of privileged containers.
-          Audit: the audit list all pods' containers to retrieve their .securityContext.privileged value.
-          Condition: is_compliant is false if container's `.securityContext.privileged` is set to `true`.
-          Default: by default, there are no restrictions on the creation of privileged containers.
-        scored: false
-
-      - id: 5.2.3
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve spec.hostPID for each pod.
-            pod_hostpid=$(kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o jsonpath='{.spec.hostPID}' 2>/dev/null)
-            if [ -z "${pod_hostpid}" ]; then
-              pod_hostpid="false"
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostpid: ${pod_hostpid} is_compliant: true"
-            else
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostpid: ${pod_hostpid} is_compliant: false"
-            fi
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostPID` containers.
-          Audit: the audit retrieves each Pod' spec.hostPID.
-          Condition: is_compliant is false if Pod's spec.hostPID is set to `true`.
-          Default: by default, there are no restrictions on the creation of hostPID containers.
-        scored: false
-
-      - id: 5.2.4
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve spec.hostIPC for each pod.
-            pod_hostipc=$(kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o jsonpath='{.spec.hostIPC}' 2>/dev/null)
-            if [ -z "${pod_hostipc}" ]; then
-              pod_hostipc="false"
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostipc: ${pod_hostipc} is_compliant: true"
-            else
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostipc: ${pod_hostipc} is_compliant: false"
-            fi
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostIPC` containers.
-          Audit: the audit retrieves each Pod' spec.IPC.
-          Condition: is_compliant is false if Pod's spec.hostIPC is set to `true`.
-          Default: by default, there are no restrictions on the creation of hostIPC containers.
-        scored: false
-
-      - id: 5.2.5
-        text: "Minimize the admission of containers wishing to share the host network namespace (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve spec.hostNetwork for each pod.
-            pod_hostnetwork=$(kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o jsonpath='{.spec.hostNetwork}' 2>/dev/null)
-            if [ -z "${pod_hostnetwork}" ]; then
-              pod_hostnetwork="false"
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostnetwork: ${pod_hostnetwork} is_compliant: true"
-            else
-              echo "***pod_name: ${pod_name} pod_namespace: ${pod_namespace} is_pod_hostnetwork: ${pod_hostnetwork} is_compliant: false"
-            fi
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostNetwork` containers.
-          Audit: the audit retrieves each Pod' spec.hostNetwork.
-          Condition: is_compliant is false if Pod's spec.hostNetwork is set to `true`.
-          Default: by default, there are no restrictions on the creation of hostNetwork containers.
-        scored: false
-
-      - id: 5.2.6
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve container(s) for each Pod.
-            kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o json | jq -c '.spec.containers[]' | while read -r container
-            do
-              # Retrieve container's name
-              container_name=$(echo ${container} | jq -r '.name')
-              # Retrieve container's .securityContext.allowPrivilegeEscalation
-              container_allowprivesc=$(echo ${container} | jq -r '.securityContext.allowPrivilegeEscalation' | sed -e 's/null/notset/g')
-              if [ "${container_allowprivesc}" = "false" ] || [ "${container_allowprivesc}" = "notset" ]; then
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_allowprivesc: ${container_allowprivesc} is_compliant: true"
-              else
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} is_container_allowprivesc: ${container_allowprivesc} is_compliant: false"
-              fi
-            done
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `.securityContext.allowPrivilegeEscalation` set to `true`.
-          Audit: the audit retrieves each Pod's container(s) `.securityContext.allowPrivilegeEscalation`.
-          Condition: is_compliant is false if container's `.securityContext.allowPrivilegeEscalation` is set to `true`.
-          Default: If notset, privilege escalation is allowed (default to true). However if PSP/PSA is used with a `restricted` profile,
-          privilege escalation is explicitly disallowed unless configured otherwise.
-        scored: false
-
-      - id: 5.2.7
-        text: "Minimize the admission of root containers (Manual)"
-        type: "manual"
-        remediation: |
-          Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot`
-          or `MustRunAs` with the range of UIDs not including 0, is set.
-        scored: false
-
-      - id: 5.2.8
-        text: "Minimize the admission of containers with the NET_RAW capability (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with the `NET_RAW` capability.
-        scored: false
-
-      - id: 5.2.9
-        text: "Minimize the admission of containers with added capabilities (Manual)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAME:.metadata.name,POD_NAMESPACE:.metadata.namespace --no-headers | while read -r pod_name pod_namespace
-          do
-            # Retrieve container(s) for each Pod.
-            kubectl get pod "${pod_name}" --namespace "${pod_namespace}" -o json | jq -c '.spec.containers[]' | while read -r container
-            do
-              # Retrieve container's name
-              container_name=$(echo ${container} | jq -r '.name')
-              # Retrieve container's added capabilities
-              container_caps_add=$(echo ${container} | jq -r '.securityContext.capabilities.add' | sed -e 's/null/notset/g')
-              # Set is_compliant to true by default.
-              is_compliant=true
-              caps_list=""
-              if [ "${container_caps_add}" != "notset" ]; then
-                # Loop through all caps and append caps_list, then set is_compliant to false.
-                for cap in $(echo "${container_caps_add}" | jq -r '.[]'); do
-                caps_list+="${cap},"
-                is_compliant=false
-                done
-                # Remove trailing comma for the last list member.
-                caps_list=${caps_list%,}
-              fi
-              if [ "${is_compliant}" = true ]; then
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} container_caps_add: ${container_caps_add} is_compliant: true"
-              else
-                echo "***pod_name: ${pod_name} container_name: ${container_name} pod_namespace: ${pod_namespace} container_caps_add: ${caps_list} is_compliant: false"
-              fi
-            done
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Ensure that `allowedCapabilities` is not present in policies for the cluster unless
-          it is set to an empty array.
-          Audit: the audit retrieves each Pod's container(s) added capabilities.
-          Condition: is_compliant is false if added capabilities are added for a given container.
-          Default: Containers run with a default set of capabilities as assigned by the Container Runtime.
-        scored: false
-
-      - id: 5.2.10
-        text: "Minimize the admission of containers with capabilities assigned (Manual)"
-        type: "manual"
-        remediation: |
-          Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
-          a PSP which forbids the admission of containers which do not drop all capabilities.
-        scored: false
-
-      - id: 5.2.11
-        text: "Minimize the admission of Windows HostProcess containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers that have `.securityContext.windowsOptions.hostProcess` set to `true`.
-        scored: false
-
-      - id: 5.2.12
-        text: "Minimize the admission of HostPath volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `hostPath` volumes.
-        scored: false
-
-      - id: 5.2.13
-        text: "Minimize the admission of containers which use HostPorts (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers which use `hostPort` sections.
-        scored: false
-
-  - id: 5.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 5.3.1
-        text: "Ensure that the CNI in use supports NetworkPolicies (Manual)"
-        type: "manual"
-        remediation: |
-          If the CNI plugin in use does not support network policies, consideration should be given to
-          making use of a different plugin, or finding an alternate mechanism for restricting traffic
-          in the Kubernetes cluster.
-        scored: false
-
-      - id: 5.3.2
-        text: "Ensure that all Namespaces have NetworkPolicies defined (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 5.4
-    text: "Secrets Management"
-    checks:
-      - id: 5.4.1
-        text: "Prefer using Secrets as files over Secrets as environment variables (Manual)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read Secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 5.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the Secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 5.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 5.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-        scored: false
-
-  - id: 5.6
-    text: "General Policies"
-    checks:
-      - id: 5.6.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 5.6.2
-        text: "Ensure that the seccomp profile is set to docker/default in your Pod definitions (Manual)"
-        type: "manual"
-        remediation: |
-          Use `securityContext` to enable the docker/default seccomp profile in your pod definitions.
-          An example is as below:
-            securityContext:
-              seccompProfile:
-                type: RuntimeDefault
-        scored: false
-
-      - id: 5.6.3
-        text: "Apply SecurityContext to your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply SecurityContexts to your Pods. For a
-          suggested list of SecurityContexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 5.6.4
-        text: "The default namespace should not be used (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/cis-1.20/node.yaml

@@ -25,16 +25,14 @@ groups:
 
       - id: 4.1.2
         text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
+        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; fi'' '
         tests:
-          bin_op: or
           test_items:
             - flag: root:root
-            - flag: "File not found"
         remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
+          Run the below command (based on the file location on your system) on the each worker node.
+          For example,
+          chown root:root $kubeletsvc
         scored: true
 
       - id: 4.1.3
@@ -48,6 +46,8 @@ groups:
               compare:
                 op: bitmask
                 value: "644"
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example,
@@ -61,6 +61,8 @@ groups:
           bin_op: or
           test_items:
             - flag: root:root
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example, chown root:root $proxykubeconfig
@@ -96,7 +98,7 @@ groups:
       - id: 4.1.7
         text: "Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
         tests:
@@ -113,7 +115,7 @@ groups:
       - id: 4.1.8
         text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
         tests:
@@ -448,7 +450,7 @@ groups:
                 op: valid_elements
                 value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
         remediation: |
-          If using a Kubelet config file, edit the file to set tlsCipherSuites: to
+          If using a Kubelet config file, edit the file to set TLSCipherSuites: to
           TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
           or to a subset of these values.
           If using executable arguments, edit the kubelet service file

cfg/cis-1.20/policies.yaml

@@ -146,7 +146,7 @@ groups:
         type: "manual"
         remediation: |
           Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
+          contains applicaions which do not require any Linux capabities to operate consider adding
           a PSP which forbids the admission of containers which do not drop all capabilities.
         scored: false
 

cfg/cis-1.23/node.yaml

@@ -24,16 +24,14 @@ groups:
 
       - id: 4.1.2
         text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
+        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; fi'' '
         tests:
-          bin_op: or
           test_items:
             - flag: root:root
-            - flag: "File not found"
         remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
+          Run the below command (based on the file location on your system) on the each worker node.
+          For example,
+          chown root:root $kubeletsvc
         scored: true
 
       - id: 4.1.3
@@ -47,6 +45,8 @@ groups:
               compare:
                 op: bitmask
                 value: "644"
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example,
@@ -60,6 +60,8 @@ groups:
           bin_op: or
           test_items:
             - flag: root:root
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example, chown root:root $proxykubeconfig
@@ -95,7 +97,7 @@ groups:
       - id: 4.1.7
         text: "Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
         tests:
@@ -112,7 +114,7 @@ groups:
       - id: 4.1.8
         text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
         tests:
@@ -447,7 +449,7 @@ groups:
                 op: valid_elements
                 value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
         remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
+          If using a Kubelet config file, edit the file to set `TLSCipherSuites` to
           TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
           or to a subset of these values.
           If using executable arguments, edit the kubelet service file

cfg/cis-1.23/policies.yaml

@@ -153,7 +153,7 @@ groups:
         type: "manual"
         remediation: |
           Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
+          contains applicaions which do not require any Linux capabities to operate consider adding
           a PSP which forbids the admission of containers which do not drop all capabilities.
         scored: false
 

cfg/cis-1.24-microk8s/config.yaml

@@ -1,2 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml

cfg/cis-1.24-microk8s/controlplane.yaml

@@ -1,46 +0,0 @@
----
-controls:
-version: "cis-1.24"
-id: 3
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 3.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 3.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-        scored: false
-
-  - id: 3.2
-    text: "Logging"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that a minimal audit policy is created (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-policy-file"
-              set: true
-        remediation: |
-          Create an audit policy file for your cluster.
-        scored: false
-
-      - id: 3.2.2
-        text: "Ensure that the audit policy covers key security concerns (Manual)"
-        type: "manual"
-        remediation: |
-          Review the audit policy provided for the cluster and ensure that it covers
-          at least the following areas,
-          - Access to Secrets managed by the cluster. Care should be taken to only
-            log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in
-            order to avoid risk of logging sensitive data.
-          - Modification of Pod and Deployment objects.
-          - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.
-          For most requests, minimally logging at the Metadata level is recommended
-          (the most basic level of logging).
-        scored: false

cfg/cis-1.24-microk8s/etcd.yaml

@@ -1,121 +0,0 @@
----
-controls:
-version: "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"
-            - flag: "--key-file"
-              env: "ETCD_KEY_FILE"
-        remediation: |
-          Not applicable. MicroK8s used dqlite and the communication to this service is done through a
-          local socket (/var/snap/microk8s/current/var/kubernetes/backend/kine.sock:12379) accessible
-          to users with root permissions.
-        scored: false
-
-      - 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:
-          test_items:
-            - flag: "--client-cert-auth"
-              env: "ETCD_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Not applicable. MicroK8s used dqlite and the communication to this service is done through a
-          local socket (/var/snap/microk8s/current/var/kubernetes/backend/kine.sock:12379) accessible
-          to users with root permissions.
-        scored: false
-
-      - 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: |
-          Not applicable. MicroK8s used dqlite and the communication to this service is done through a
-          local socket (/var/snap/microk8s/current/var/kubernetes/backend/kine.sock:12379) accessible
-          to users with root permissions.
-        scored: false
-
-      - id: 2.4
-        text: "Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate (Automated)"
-        audit: "if test -e /var/snap/microk8s/current/var/kubernetes/backend/cluster.crt && test -e /var/snap/microk8s/current/var/kubernetes/backend/cluster.key; then echo 'certs-found'; fi"
-        tests:
-          test_items:
-            - flag: "certs-found"
-        remediation: |
-          The certificate pair for dqlite and tls peer communication is
-          /var/snap/microk8s/current/var/kubernetes/backend/cluster.crt and
-          /var/snap/microk8s/current/var/kubernetes/backend/cluster.key.
-        scored: true
-
-      - id: 2.5
-        text: "Ensure that the --peer-client-cert-auth argument is set to true (Automated)"
-        audit: "/bin/cat $etcdconf | /bin/grep enable-tls || true"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-tls"
-              compare:
-                op: eq
-                value: true
-            - flag: "--enable-tls"
-              set: false
-        remediation: |
-          MicroK8s used dqlite and tls peer communication uses is TLS if the --enable-tls is set in
-          /var/snap/microk8s/current/args/k8s-dqlite, set to true by default.
-        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
-        remediation: |
-          Not applicable. MicroK8s used dqlite and tls peer communication uses the certificates
-          created upon the snap creation.
-        scored: false
-
-      - id: 2.7
-        text: "Ensure that a unique Certificate Authority is used for etcd (Manual)"
-        audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
-        tests:
-          test_items:
-            - flag: "--trusted-ca-file"
-              env: "ETCD_TRUSTED_CA_FILE"
-        remediation: |
-          Not applicable. MicroK8s used dqlite and tls peer communication uses the certificates
-          created upon the snap creation.
-        scored: false

cfg/cis-1.24-microk8s/master.yaml

@@ -1,948 +0,0 @@
----
-controls:
-version: "cis-1.24"
-id: 1
-text: "Control Plane Security Configuration"
-type: "master"
-groups:
-  - id: 1.1
-    text: "Control Plane Node Configuration Files"
-    checks:
-      - id: 1.1.1
-        text: "Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c permissions=%a $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on the
-          control plane node.
-          For example, chmod 644 $apiserverconf
-        scored: true
-
-      - id: 1.1.2
-        text: "Ensure that the API server pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c %U:%G $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $apiserverconf
-        scored: true
-
-      - id: 1.1.3
-        text: "Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c permissions=%a $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $controllermanagerconf
-        scored: true
-
-      - id: 1.1.4
-        text: "Ensure that the controller manager pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c %U:%G $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $controllermanagerconf
-        scored: true
-
-      - id: 1.1.5
-        text: "Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c permissions=%a $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $schedulerconf
-        scored: true
-
-      - id: 1.1.6
-        text: "Ensure that the scheduler pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c %U:%G $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $schedulerconf
-        scored: true
-
-      - id: 1.1.7
-        text: "Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then stat -c permissions=%a $etcdconf; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $etcdconf
-        scored: true
-
-      - id: 1.1.8
-        text: "Ensure that the etcd pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then stat -c %U:%G $etcdconf; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $etcdconf
-        scored: true
-
-      - id: 1.1.9
-        text: "Ensure that the Container Network Interface file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          find /var/snap/microk8s/current/args/cni-network/10-calico.conflist -type f 2> /dev/null | xargs --no-run-if-empty stat -c permissions=%a
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.10
-        text: "Ensure that the Container Network Interface file ownership is set to root:root (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c %U:%G
-          find /var/snap/microk8s/current/args/cni-network/10-calico.conflist -type f 2> /dev/null | xargs --no-run-if-empty stat -c %U:%G
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root <path/to/cni/files>
-        scored: false
-
-      # Etcd is not running on MicroK8s master nodes
-      - id: 1.1.11
-        text: "Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)"
-        audit: |
-          DATA_DIR='/var/snap/microk8s/current/var/kubernetes/backend/'
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c permissions=%a "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "700"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above). For example,
-          chmod 700 /var/snap/microk8s/current/var/kubernetes/backend/
-        scored: true
-
-      # Etcd is not running on MicroK8s master nodes
-      - id: 1.1.12
-        text: "Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)"
-        audit: |
-          DATA_DIR='/var/snap/microk8s/current/var/kubernetes/backend/'
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c %U:%G "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above).
-          For example, chown root:root /var/snap/microk8s/current/var/kubernetes/backend/
-        scored: true
-
-      - id: 1.1.13
-        text: "Ensure that the admin.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e /var/snap/microk8s/current/credentials/client.config; then stat -c permissions=%a /var/snap/microk8s/current/credentials/client.config; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 /var/snap/microk8s/current/credentials/client.config
-        scored: true
-
-      - id: 1.1.14
-        text: "Ensure that the admin.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e /var/snap/microk8s/current/credentials/client.config; then stat -c %U:%G /var/snap/microk8s/current/credentials/client.config; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root /var/snap/microk8s/current/credentials/client.config
-        scored: true
-
-      - id: 1.1.15
-        text: "Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c permissions=%a $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.16
-        text: "Ensure that the scheduler.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c %U:%G $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.17
-        text: "Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c permissions=%a $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.18
-        text: "Ensure that the controller-manager.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c %U:%G $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.19
-        text: "Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)"
-        audit: "find /var/snap/microk8s/current/certs/ | xargs stat -c %U:%G"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown -R root:root /var/snap/microk8s/current/certs/
-        scored: true
-
-      - id: 1.1.20
-        text: "Ensure that the Kubernetes PKI certificate file permissions are set to 600 or more restrictive (Manual)"
-        audit: "find /var/snap/microk8s/current/certs/ -name '*.crt' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /var/snap/microk8s/current/certs/*.crt
-        scored: false
-
-      - id: 1.1.21
-        text: "Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)"
-        audit: "find /var/snap/microk8s/current/certs/ -name '*.key' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /var/snap/microk8s/current/certs/*.key
-        scored: false
-
-  - id: 1.2
-    text: "API Server"
-    checks:
-      - id: 1.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--anonymous-auth"
-              compare:
-                op: eq
-                value: false
-            - flag: "--anonymous-auth"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --anonymous-auth=false
-        scored: false
-
-      - id: 1.2.2
-        text: "Ensure that the --token-auth-file parameter is not set (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--token-auth-file"
-              set: false
-        remediation: |
-          Follow the documentation and configure alternate mechanisms for authentication. Then,
-          edit the API server pod specification file $apiserverconf
-          on the control plane node and remove the --token-auth-file=<filename> parameter.
-        scored: true
-
-      - id: 1.2.3
-        text: "Ensure that the --DenyServiceExternalIPs is not set (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: nothave
-                value: "DenyServiceExternalIPs"
-            - flag: "--enable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and remove the `DenyServiceExternalIPs`
-          from enabled admission plugins.
-        scored: true
-
-      - id: 1.2.4
-        text: "Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--kubelet-client-certificate"
-            - flag: "--kubelet-client-key"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the
-          apiserver and kubelets. Then, edit API server pod specification file
-          $apiserverconf on the control plane node and set the
-          kubelet client certificate and key parameters as below.
-          --kubelet-client-certificate=<path/to/client-certificate-file>
-          --kubelet-client-key=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.5
-        text: "Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--kubelet-certificate-authority"
-        remediation: |
-          Follow the Kubernetes documentation and setup the TLS connection between
-          the apiserver and kubelets. Then, edit the API server pod specification file
-          $apiserverconf on the control plane node and set the
-          --kubelet-certificate-authority parameter to the path to the cert file for the certificate authority.
-          --kubelet-certificate-authority=<ca-string>
-        scored: true
-
-      - id: 1.2.6
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: nothave
-                value: "AlwaysAllow"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to values other than AlwaysAllow.
-          One such example could be as below.
-          --authorization-mode=RBAC
-        scored: true
-
-      - id: 1.2.7
-        text: "Ensure that the --authorization-mode argument includes Node (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "Node"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes Node.
-          --authorization-mode=Node,RBAC
-        scored: true
-
-      - id: 1.2.8
-        text: "Ensure that the --authorization-mode argument includes RBAC (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "RBAC"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes RBAC,
-          for example `--authorization-mode=Node,RBAC`.
-        scored: true
-
-      - id: 1.2.9
-        text: "Ensure that the admission control plugin EventRateLimit is set (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "EventRateLimit"
-        remediation: |
-          Follow the Kubernetes documentation and set the desired limits in a configuration file.
-          Then, edit the API server pod specification file $apiserverconf
-          and set the below parameters.
-          --enable-admission-plugins=...,EventRateLimit,...
-          --admission-control-config-file=<path/to/configuration/file>
-        scored: false
-
-      - id: 1.2.10
-        text: "Ensure that the admission control plugin AlwaysAdmit is not set (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: nothave
-                value: AlwaysAdmit
-            - flag: "--enable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --enable-admission-plugins parameter, or set it to a
-          value that does not include AlwaysAdmit.
-        scored: true
-
-      - id: 1.2.11
-        text: "Ensure that the admission control plugin AlwaysPullImages is set (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "AlwaysPullImages"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          AlwaysPullImages.
-          --enable-admission-plugins=...,AlwaysPullImages,...
-        scored: false
-
-      - id: 1.2.12
-        text: "Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "SecurityContextDeny"
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "PodSecurityPolicy"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          SecurityContextDeny, unless PodSecurityPolicy is already in place.
-          --enable-admission-plugins=...,SecurityContextDeny,...
-        scored: false
-
-      - id: 1.2.13
-        text: "Ensure that the admission control plugin ServiceAccount is set (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "ServiceAccount"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Follow the documentation and create ServiceAccount objects as per your environment.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and ensure that the --disable-admission-plugins parameter is set to a
-          value that does not include ServiceAccount.
-        scored: true
-
-      - id: 1.2.14
-        text: "Ensure that the admission control plugin NamespaceLifecycle is set (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "NamespaceLifecycle"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --disable-admission-plugins parameter to
-          ensure it does not include NamespaceLifecycle.
-        scored: true
-
-      - id: 1.2.15
-        text: "Ensure that the admission control plugin NodeRestriction is set (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "NodeRestriction"
-        remediation: |
-          Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to a
-          value that includes NodeRestriction.
-          --enable-admission-plugins=...,NodeRestriction,...
-        scored: true
-
-      - id: 1.2.16
-        text: "Ensure that the --secure-port argument is not set to 0 (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--secure-port"
-              compare:
-                op: gt
-                value: 0
-            - flag: "--secure-port"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --secure-port parameter or
-          set it to a different (non-zero) desired port.
-        scored: true
-
-      - id: 1.2.17
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.2.18
-        text: "Ensure that the --audit-log-path argument is set (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-path"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-path parameter to a suitable path and
-          file where you would like audit logs to be written, for example,
-          --audit-log-path=/var/log/apiserver/audit.log
-        scored: true
-
-      - id: 1.2.19
-        text: "Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxage"
-              compare:
-                op: gte
-                value: 30
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxage parameter to 30
-          or as an appropriate number of days, for example,
-          --audit-log-maxage=30
-        scored: true
-
-      - id: 1.2.20
-        text: "Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxbackup"
-              compare:
-                op: gte
-                value: 10
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxbackup parameter to 10 or to an appropriate
-          value. For example,
-          --audit-log-maxbackup=10
-        scored: true
-
-      - id: 1.2.21
-        text: "Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxsize"
-              compare:
-                op: gte
-                value: 100
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxsize parameter to an appropriate size in MB.
-          For example, to set it as 100 MB, --audit-log-maxsize=100
-        scored: true
-
-      - id: 1.2.22
-        text: "Ensure that the --request-timeout argument is set as appropriate (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        type: manual
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          and set the below parameter as appropriate and if needed.
-          For example, --request-timeout=300s
-        scored: false
-
-      - id: 1.2.23
-        text: "Ensure that the --service-account-lookup argument is set to true (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--service-account-lookup"
-              set: false
-            - flag: "--service-account-lookup"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --service-account-lookup=true
-          Alternatively, you can delete the --service-account-lookup parameter from this file so
-          that the default takes effect.
-        scored: true
-
-      - id: 1.2.24
-        text: "Ensure that the --service-account-key-file argument is set as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-key-file"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --service-account-key-file parameter
-          to the public key file for service accounts. For example,
-          --service-account-key-file=<filename>
-        scored: true
-
-      # MicroK8s does not use etcd. The API server talk to a local dqlite instance
-      - id: 1.2.25
-        text: "Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--etcd-certfile"
-            - flag: "--etcd-keyfile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate and key file parameters.
-          --etcd-certfile=<path/to/client-certificate-file>
-          --etcd-keyfile=<path/to/client-key-file>
-        scored: false
-
-      - id: 1.2.26
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--tls-cert-file"
-            - flag: "--tls-private-key-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the TLS certificate and private key file parameters.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-        scored: true
-
-      - id: 1.2.27
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--client-ca-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the client certificate authority file.
-          --client-ca-file=<path/to/client-ca-file>
-        scored: true
-
-      - id: 1.2.28
-        text: "Ensure that the --etcd-cafile argument is set as appropriate (Automated)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--etcd-cafile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate authority file parameter.
-          --etcd-cafile=<path/to/ca-file>
-        scored: false
-
-      - id: 1.2.29
-        text: "Ensure that the --encryption-provider-config argument is set as appropriate (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--encryption-provider-config"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --encryption-provider-config parameter to the path of that file.
-          For example, --encryption-provider-config=</path/to/EncryptionConfig/File>
-        scored: false
-
-      - id: 1.2.30
-        text: "Ensure that encryption providers are appropriately configured (Manual)"
-        audit: |
-          ENCRYPTION_PROVIDER_CONFIG=$(cat $apiserverconf | grep -- --encryption-provider-config | sed 's%.*encryption-provider-config[= ]\([^ ]*\).*%\1%')
-          if test -e $ENCRYPTION_PROVIDER_CONFIG; then grep -A1 'providers:' $ENCRYPTION_PROVIDER_CONFIG | tail -n1 | grep -o "[A-Za-z]*" | sed 's/^/provider=/'; fi
-        tests:
-          test_items:
-            - flag: "provider"
-              compare:
-                op: valid_elements
-                value: "aescbc,kms,secretbox"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          In this file, choose aescbc, kms or secretbox as the encryption provider.
-        scored: false
-
-      - id: 1.2.31
-        text: "Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "cat $apiserverconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--tls-cipher-suites"
-              compare:
-                op: valid_elements
-                value: "TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384"
-        remediation: |
-          Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
-          on the control plane node and set the below parameter.
-          --tls-cipher-suites=TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
-          TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
-          TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,
-          TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384
-        scored: false
-
-  - id: 1.3
-    text: "Controller Manager"
-    checks:
-      - id: 1.3.1
-        text: "Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Manual)"
-        audit: "cat $controllermanagerconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--terminated-pod-gc-threshold"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --terminated-pod-gc-threshold to an appropriate threshold,
-          for example, --terminated-pod-gc-threshold=10
-        scored: false
-
-      - id: 1.3.2
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "cat $controllermanagerconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.3.3
-        text: "Ensure that the --use-service-account-credentials argument is set to true (Automated)"
-        audit: "cat $controllermanagerconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--use-service-account-credentials"
-              compare:
-                op: noteq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node to set the below parameter.
-          --use-service-account-credentials=true
-        scored: true
-
-      - id: 1.3.4
-        text: "Ensure that the --service-account-private-key-file argument is set as appropriate (Automated)"
-        audit: "cat $controllermanagerconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-private-key-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --service-account-private-key-file parameter
-          to the private key file for service accounts.
-          --service-account-private-key-file=<filename>
-        scored: true
-
-      - id: 1.3.5
-        text: "Ensure that the --root-ca-file argument is set as appropriate (Automated)"
-        audit: "cat $controllermanagerconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--root-ca-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --root-ca-file parameter to the certificate bundle file`.
-          --root-ca-file=<path/to/file>
-        scored: true
-
-      - id: 1.3.6
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "cat $controllermanagerconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--feature-gates"
-              compare:
-                op: nothave
-                value: "RotateKubeletServerCertificate=false"
-              set: true
-            - flag: "--feature-gates"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.
-          --feature-gates=RotateKubeletServerCertificate=true
-        scored: true
-
-      - id: 1.3.7
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "cat $controllermanagerconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true
-
-  - id: 1.4
-    text: "Scheduler"
-    checks:
-      - id: 1.4.1
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "cat $schedulerconf | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf file
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.4.2
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "cat $schedulerconf | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true

cfg/cis-1.24-microk8s/node.yaml

@@ -1,458 +0,0 @@
----
-controls:
-version: "cis-1.24"
-id: 4
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 4.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $kubeletsvc; then stat -c permissions=%a $kubeletsvc; fi' "
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chmod 600 $kubeletsvc
-        scored: true
-
-      - id: 4.1.2
-        text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; fi' "
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletsvc
-        scored: true
-
-      - id: 4.1.3
-        text: "If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual)"
-        audit: "/bin/sh -c 'if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi' "
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "permissions"
-              set: true
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $proxykubeconfig
-        scored: false
-
-      - id: 4.1.4
-        text: "If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)"
-        audit: "/bin/sh -c 'if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi' "
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chown root:root $proxykubeconfig
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi' "
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.6
-        text: "Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi' "
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.7
-        text: "Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command to modify the file permissions of the
-          --client-ca-file chmod 600 <filename>
-        scored: false
-
-      - id: 4.1.8
-        text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
-        tests:
-          test_items:
-            - flag: root:root
-              compare:
-                op: eq
-                value: root:root
-        remediation: |
-          Run the following command to modify the ownership of the --client-ca-file.
-          chown root:root <filename>
-        scored: false
-
-      - id: 4.1.9
-        text: "If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Manual)"
-        audit: "/bin/sh -c 'if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi' "
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 600 $kubeletconf
-        scored: false
-
-      - id: 4.1.10
-        text: "If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Manual)"
-        audit: "/bin/sh -c 'if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi' "
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: false
-
-  - id: 4.2
-    text: "Kubelet"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Automated)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: "{.authentication.anonymous.enabled}"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to
-          `false`.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          `--anonymous-auth=false`
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: "{.authorization.mode}"
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authorization.mode` to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.3
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: "{.authentication.x509.clientCAFile}"
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication.x509.clientCAFile` to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.4
-        text: "Verify that the --read-only-port argument is set to 0 (Manual)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--read-only-port"
-              path: "{.readOnlyPort}"
-              compare:
-                op: eq
-                value: 0
-            - flag: "--read-only-port"
-              path: "{.readOnlyPort}"
-              set: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `readOnlyPort` to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Manual)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: "{.streamingConnectionIdleTimeout}"
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: "{.streamingConnectionIdleTimeout}"
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `streamingConnectionIdleTimeout` to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.6
-        text: "Ensure that the --protect-kernel-defaults argument is set to true (Automated)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --protect-kernel-defaults
-              path: "{.protectKernelDefaults}"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          If using a Kubelet config file, edit the file to set `protectKernelDefaults` to `true`.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --protect-kernel-defaults=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.7
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: "{.makeIPTablesUtilChains}"
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: "{.makeIPTablesUtilChains}"
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `makeIPTablesUtilChains` to `true`.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.8
-        text: "Ensure that the --hostname-override argument is not set (Manual)"
-        # This is one of those properties that can only be set as a command line argument.
-        # To check if the property is set as expected, we need to parse the kubelet command
-        # instead reading the Kubelet Configuration file.
-        audit: "cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --hostname-override
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and remove the --hostname-override argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.9
-        text: "Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture (Manual)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: "{.eventRecordQPS}"
-              compare:
-                op: eq
-                value: 0
-        remediation: |
-          If using a Kubelet config file, edit the file to set `eventRecordQPS` to an appropriate level.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.10
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Manual)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cert-file
-              path: "{.tlsCertFile}"
-            - flag: --tls-private-key-file
-              path: "{.tlsPrivateKeyFile}"
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCertFile` to the location
-          of the certificate file to use to identify this Kubelet, and `tlsPrivateKeyFile`
-          to the location of the corresponding private key file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameters in KUBELET_CERTIFICATE_ARGS variable.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.11
-        text: "Ensure that the --rotate-certificates argument is not set to false (Automated)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: "{.rotateCertificates}"
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: "{.rotateCertificates}"
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to add the line `rotateCertificates` to `true` or
-          remove it altogether to use the default value.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS
-          variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.12
-        text: "Verify that the RotateKubeletServerCertificate argument is set to true (Manual)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: "{.featureGates.RotateKubeletServerCertificate}"
-              compare:
-                op: nothave
-                value: false
-            - flag: RotateKubeletServerCertificate
-              path: "{.featureGates.RotateKubeletServerCertificate}"
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.13
-        text: "Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "cat $kubeletconf"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cipher-suites
-              path: "{range .tlsCipherSuites[:]}{}{','}{end}"
-              compare:
-                op: valid_elements
-                value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
-          TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          or to a subset of these values.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the --tls-cipher-suites parameter as follows, or to a subset of these values.
-          --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false

cfg/cis-1.24-microk8s/policies.yaml

@@ -1,269 +0,0 @@
----
-controls:
-version: "cis-1.24"
-id: 5
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 5.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 5.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Manual)"
-        type: "manual"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role :
-          kubectl delete clusterrolebinding [name]
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize access to secrets (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove get, list and watch access to Secret objects in the cluster.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize access to create pods (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-
-      - id: 5.1.5
-        text: "Ensure that default service accounts are not actively used. (Manual)"
-        type: "manual"
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific access
-          to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          automountServiceAccountToken: false
-        scored: false
-
-      - id: 5.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Manual)"
-        type: "manual"
-        remediation: |
-          Modify the definition of pods and service accounts which do not need to mount service
-          account tokens to disable it.
-        scored: false
-
-      - id: 5.1.7
-        text: "Avoid use of system:masters group (Manual)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 5.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-  - id: 5.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 5.2.1
-        text: "Ensure that the cluster has at least one active policy control mechanism in place (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that either Pod Security Admission or an external policy control system is in place
-          for every namespace which contains user workloads.
-        scored: false
-
-      - id: 5.2.2
-        text: "Minimize the admission of privileged containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of privileged containers.
-        scored: false
-
-      - id: 5.2.3
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostPID` containers.
-        scored: false
-
-      - id: 5.2.4
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostIPC` containers.
-        scored: false
-
-      - id: 5.2.5
-        text: "Minimize the admission of containers wishing to share the host network namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostNetwork` containers.
-        scored: false
-
-      - id: 5.2.6
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `.spec.allowPrivilegeEscalation` set to `true`.
-        scored: false
-
-      - id: 5.2.7
-        text: "Minimize the admission of root containers (Automated)"
-        type: "manual"
-        remediation: |
-          Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot`
-          or `MustRunAs` with the range of UIDs not including 0, is set.
-        scored: false
-
-      - id: 5.2.8
-        text: "Minimize the admission of containers with the NET_RAW capability (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with the `NET_RAW` capability.
-        scored: false
-
-      - id: 5.2.9
-        text: "Minimize the admission of containers with added capabilities (Automated)"
-        type: "manual"
-        remediation: |
-          Ensure that `allowedCapabilities` is not present in policies for the cluster unless
-          it is set to an empty array.
-        scored: false
-
-      - id: 5.2.10
-        text: "Minimize the admission of containers with capabilities assigned (Manual)"
-        type: "manual"
-        remediation: |
-          Review the use of capabilities in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
-          a PSP which forbids the admission of containers which do not drop all capabilities.
-        scored: false
-
-      - id: 5.2.11
-        text: "Minimize the admission of Windows HostProcess containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers that have `.securityContext.windowsOptions.hostProcess` set to `true`.
-        scored: false
-
-      - id: 5.2.12
-        text: "Minimize the admission of HostPath volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `hostPath` volumes.
-        scored: false
-
-      - id: 5.2.13
-        text: "Minimize the admission of containers which use HostPorts (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers which use `hostPort` sections.
-        scored: false
-
-  - id: 5.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 5.3.1
-        text: "Ensure that the CNI in use supports NetworkPolicies (Manual)"
-        type: "manual"
-        remediation: |
-          If the CNI plugin in use does not support network policies, consideration should be given to
-          making use of a different plugin, or finding an alternate mechanism for restricting traffic
-          in the Kubernetes cluster.
-        scored: false
-
-      - id: 5.3.2
-        text: "Ensure that all Namespaces have NetworkPolicies defined (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 5.4
-    text: "Secrets Management"
-    checks:
-      - id: 5.4.1
-        text: "Prefer using Secrets as files over Secrets as environment variables (Manual)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read Secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 5.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the Secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 5.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 5.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-        scored: false
-
-  - id: 5.7
-    text: "General Policies"
-    checks:
-      - id: 5.7.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 5.7.2
-        text: "Ensure that the seccomp profile is set to docker/default in your Pod definitions (Manual)"
-        type: "manual"
-        remediation: |
-          Use `securityContext` to enable the docker/default seccomp profile in your pod definitions.
-          An example is as below:
-            securityContext:
-              seccompProfile:
-                type: RuntimeDefault
-        scored: false
-
-      - id: 5.7.3
-        text: "Apply SecurityContext to your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply SecurityContexts to your Pods. For a
-          suggested list of SecurityContexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 5.7.4
-        text: "The default namespace should not be used (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/cis-1.24/master.yaml

@@ -9,18 +9,18 @@ groups:
     text: "Control Plane Node Configuration Files"
     checks:
       - id: 1.1.1
-        text: "Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)"
+        text: "Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Automated)"
         audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c permissions=%a $apiserverconf; fi'"
         tests:
           test_items:
             - flag: "permissions"
               compare:
                 op: bitmask
-                value: "600"
+                value: "644"
         remediation: |
           Run the below command (based on the file location on your system) on the
           control plane node.
-          For example, chmod 600 $apiserverconf
+          For example, chmod 644 $apiserverconf
         scored: true
 
       - id: 1.1.2
@@ -900,11 +900,14 @@ groups:
         text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
         audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
         tests:
+          bin_op: or
           test_items:
             - flag: "--bind-address"
               compare:
                 op: eq
                 value: "127.0.0.1"
+            - flag: "--bind-address"
+              set: false
         remediation: |
           Edit the Controller Manager pod specification file $controllermanagerconf
           on the control plane node and ensure the correct value for the --bind-address parameter
@@ -932,11 +935,14 @@ groups:
         text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
         audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
         tests:
+          bin_op: or
           test_items:
             - flag: "--bind-address"
               compare:
                 op: eq
                 value: "127.0.0.1"
+            - flag: "--bind-address"
+              set: false
         remediation: |
           Edit the Scheduler pod specification file $schedulerconf
           on the control plane node and ensure the correct value for the --bind-address parameter

cfg/cis-1.24/node.yaml

@@ -24,16 +24,14 @@ groups:
 
       - id: 4.1.2
         text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
+        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; fi'' '
         tests:
-          bin_op: or
           test_items:
             - flag: root:root
-            - flag: "File not found"
         remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
+          Run the below command (based on the file location on your system) on the each worker node.
+          For example,
+          chown root:root $kubeletsvc
         scored: true
 
       - id: 4.1.3
@@ -47,6 +45,8 @@ groups:
               compare:
                 op: bitmask
                 value: "600"
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example,
@@ -60,6 +60,8 @@ groups:
           bin_op: or
           test_items:
             - flag: root:root
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example, chown root:root $proxykubeconfig
@@ -95,7 +97,7 @@ groups:
       - id: 4.1.7
         text: "Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
         tests:
@@ -112,7 +114,7 @@ groups:
       - id: 4.1.8
         text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
         tests:
@@ -348,12 +350,8 @@ groups:
             - flag: --event-qps
               path: '{.eventRecordQPS}'
               compare:
-                op: gte
+                op: eq
                 value: 0
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: false
-          bin_op: or
         remediation: |
           If using a Kubelet config file, edit the file to set `eventRecordQPS` to an appropriate level.
           If using command line arguments, edit the kubelet service file
@@ -451,7 +449,7 @@ groups:
                 op: valid_elements
                 value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
         remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
+          If using a Kubelet config file, edit the file to set `TLSCipherSuites` to
           TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
           or to a subset of these values.
           If using executable arguments, edit the kubelet service file

cfg/cis-1.24/policies.yaml

@@ -1,6 +1,6 @@
 ---
 controls:
-version: "cis-1.24"
+version: "cis-1.25"
 id: 5
 text: "Kubernetes Policies"
 type: "policies"
@@ -153,7 +153,7 @@ groups:
         type: "manual"
         remediation: |
           Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
+          contains applicaions which do not require any Linux capabities to operate consider adding
           a PSP which forbids the admission of containers which do not drop all capabilities.
         scored: false
 

cfg/cis-1.5/node.yaml

@@ -25,17 +25,16 @@ groups:
         scored: true
 
       - id: 4.1.2
-        text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
+        text: "Ensure that the kubelet service file ownership is set to root:root (Scored)"
+        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; fi'' '
         tests:
-          bin_op: or
           test_items:
             - flag: root:root
-            - flag: "File not found"
+              set: true
         remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
+          Run the below command (based on the file location on your system) on the each worker node.
+          For example,
+          chown root:root $kubeletsvc
         scored: true
 
       - id: 4.1.3
@@ -49,6 +48,8 @@ groups:
               compare:
                 op: bitmask
                 value: "644"
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example,
@@ -63,6 +64,8 @@ groups:
           test_items:
             - flag: root:root
               set: true
+            - flag: "$proxykubeconfig"
+              set: false
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example, chown root:root $proxykubeconfig
@@ -103,7 +106,7 @@ groups:
       - id: 4.1.7
         text: "Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Scored)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
         tests:
@@ -121,7 +124,7 @@ groups:
       - id: 4.1.8
         text: "Ensure that the client certificate authorities file ownership is set to root:root (Scored)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
         tests:
@@ -472,7 +475,7 @@ groups:
                 op: valid_elements
                 value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
         remediation: |
-          If using a Kubelet config file, edit the file to set tlsCipherSuites: to
+          If using a Kubelet config file, edit the file to set TLSCipherSuites: to
           TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
           or to a subset of these values.
           If using executable arguments, edit the kubelet service file

cfg/cis-1.5/policies.yaml

@@ -132,7 +132,7 @@ groups:
         type: "manual"
         remediation: |
           Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
+          contains applicaions which do not require any Linux capabities to operate consider adding
           a PSP which forbids the admission of containers which do not drop all capabilities.
         scored: false
 

cfg/cis-1.6/node.yaml

@@ -25,12 +25,10 @@ groups:
 
       - id: 4.1.2
         text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
+        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; fi'' '
         tests:
-          bin_op: or
           test_items:
             - flag: root:root
-            - flag: "File not found"
         remediation: |
           Run the below command (based on the file location on your system) on the each worker node.
           For example,
@@ -100,7 +98,7 @@ groups:
       - id: 4.1.7
         text: "Ensure that the certificate authorities file permissions are set to 644 or more restrictive (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
         tests:
@@ -117,7 +115,7 @@ groups:
       - id: 4.1.8
         text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
         audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
+          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}')
           if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
           if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
         tests:
@@ -452,7 +450,7 @@ groups:
                 op: valid_elements
                 value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
         remediation: |
-          If using a Kubelet config file, edit the file to set tlsCipherSuites: to
+          If using a Kubelet config file, edit the file to set TLSCipherSuites: to
           TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
           or to a subset of these values.
           If using executable arguments, edit the kubelet service file

cfg/cis-1.6/policies.yaml

@@ -132,7 +132,7 @@ groups:
         type: "manual"
         remediation: |
           Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
+          contains applicaions which do not require any Linux capabities to operate consider adding
           a PSP which forbids the admission of containers which do not drop all capabilities.
         scored: false
 

cfg/cis-1.7/config.yaml

@@ -1,2 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml

cfg/cis-1.7/controlplane.yaml

@@ -1,60 +0,0 @@
----
-controls:
-version: "cis-1.7"
-id: 3
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 3.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 3.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-        scored: false
-      - id: 3.1.2
-        text: "Service account token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of service account tokens.
-        scored: false
-      - id: 3.1.3
-        text: "Bootstrap token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of bootstrap tokens.
-        scored: false
-
-  - id: 3.2
-    text: "Logging"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that a minimal audit policy is created (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-policy-file"
-              set: true
-        remediation: |
-          Create an audit policy file for your cluster.
-        scored: false
-
-      - id: 3.2.2
-        text: "Ensure that the audit policy covers key security concerns (Manual)"
-        type: "manual"
-        remediation: |
-          Review the audit policy provided for the cluster and ensure that it covers
-          at least the following areas,
-          - Access to Secrets managed by the cluster. Care should be taken to only
-            log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in
-            order to avoid risk of logging sensitive data.
-          - Modification of Pod and Deployment objects.
-          - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.
-          For most requests, minimally logging at the Metadata level is recommended
-          (the most basic level of logging).
-        scored: false

cfg/cis-1.7/etcd.yaml

@@ -1,135 +0,0 @@
----
-controls:
-version: "cis-1.7"
-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"
-            - flag: "--key-file"
-              env: "ETCD_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--client-cert-auth"
-              env: "ETCD_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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"
-            - flag: "--peer-key-file"
-              env: "ETCD_PEER_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--peer-client-cert-auth"
-              env: "ETCD_PEER_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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
-        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 (Manual)"
-        audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
-        tests:
-          test_items:
-            - flag: "--trusted-ca-file"
-              env: "ETCD_TRUSTED_CA_FILE"
-        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: false

cfg/cis-1.7/master.yaml

@@ -1,946 +0,0 @@
----
-controls:
-version: "cis-1.7"
-id: 1
-text: "Control Plane Security Configuration"
-type: "master"
-groups:
-  - id: 1.1
-    text: "Control Plane Node Configuration Files"
-    checks:
-      - id: 1.1.1
-        text: "Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c permissions=%a $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the
-          control plane node.
-          For example, chmod 600 $apiserverconf
-        scored: true
-
-      - id: 1.1.2
-        text: "Ensure that the API server pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c %U:%G $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $apiserverconf
-        scored: true
-
-      - id: 1.1.3
-        text: "Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c permissions=%a $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $controllermanagerconf
-        scored: true
-
-      - id: 1.1.4
-        text: "Ensure that the controller manager pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c %U:%G $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $controllermanagerconf
-        scored: true
-
-      - id: 1.1.5
-        text: "Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c permissions=%a $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $schedulerconf
-        scored: true
-
-      - id: 1.1.6
-        text: "Ensure that the scheduler pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c %U:%G $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $schedulerconf
-        scored: true
-
-      - id: 1.1.7
-        text: "Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c permissions=%a; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $etcdconf
-        scored: true
-
-      - id: 1.1.8
-        text: "Ensure that the etcd pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c %U:%G; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $etcdconf
-        scored: true
-
-      - id: 1.1.9
-        text: "Ensure that the Container Network Interface file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c permissions=%a
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c permissions=%a
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.10
-        text: "Ensure that the Container Network Interface file ownership is set to root:root (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c %U:%G
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c %U:%G
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.11
-        text: "Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c permissions=%a "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "700"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above). For example,
-          chmod 700 /var/lib/etcd
-        scored: true
-
-      - id: 1.1.12
-        text: "Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c %U:%G "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "etcd:etcd"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above).
-          For example, chown etcd:etcd /var/lib/etcd
-        scored: true
-
-      - id: 1.1.13
-        text: "Ensure that the admin.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e /etc/kubernetes/admin.conf; then stat -c permissions=%a /etc/kubernetes/admin.conf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 /etc/kubernetes/admin.conf
-        scored: true
-
-      - id: 1.1.14
-        text: "Ensure that the admin.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e /etc/kubernetes/admin.conf; then stat -c %U:%G /etc/kubernetes/admin.conf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root /etc/kubernetes/admin.conf
-        scored: true
-
-      - id: 1.1.15
-        text: "Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c permissions=%a $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.16
-        text: "Ensure that the scheduler.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c %U:%G $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.17
-        text: "Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c permissions=%a $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.18
-        text: "Ensure that the controller-manager.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c %U:%G $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.19
-        text: "Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)"
-        audit: "find /etc/kubernetes/pki/ | xargs stat -c %U:%G"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown -R root:root /etc/kubernetes/pki/
-        scored: true
-
-      - id: 1.1.20
-        text: "Ensure that the Kubernetes PKI certificate file permissions are set to 600 or more restrictive (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.crt' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.crt
-        scored: false
-
-      - id: 1.1.21
-        text: "Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.key' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.key
-        scored: false
-
-  - id: 1.2
-    text: "API Server"
-    checks:
-      - id: 1.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --anonymous-auth=false
-        scored: false
-
-      - id: 1.2.2
-        text: "Ensure that the --token-auth-file parameter is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--token-auth-file"
-              set: false
-        remediation: |
-          Follow the documentation and configure alternate mechanisms for authentication. Then,
-          edit the API server pod specification file $apiserverconf
-          on the control plane node and remove the --token-auth-file=<filename> parameter.
-        scored: true
-
-      - id: 1.2.3
-        text: "Ensure that the --DenyServiceExternalIPs is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "DenyServiceExternalIPs"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and add the `DenyServiceExternalIPs` plugin
-          to the enabled admission plugins, as such --enable-admission-plugin=DenyServiceExternalIPs.
-        scored: false
-
-      - id: 1.2.4
-        text: "Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--kubelet-client-certificate"
-            - flag: "--kubelet-client-key"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the
-          apiserver and kubelets. Then, edit API server pod specification file
-          $apiserverconf on the control plane node and set the
-          kubelet client certificate and key parameters as below.
-          --kubelet-client-certificate=<path/to/client-certificate-file>
-          --kubelet-client-key=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.5
-        text: "Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--kubelet-certificate-authority"
-        remediation: |
-          Follow the Kubernetes documentation and setup the TLS connection between
-          the apiserver and kubelets. Then, edit the API server pod specification file
-          $apiserverconf on the control plane node and set the
-          --kubelet-certificate-authority parameter to the path to the cert file for the certificate authority.
-          --kubelet-certificate-authority=<ca-string>
-        scored: true
-
-      - id: 1.2.6
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: nothave
-                value: "AlwaysAllow"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to values other than AlwaysAllow.
-          One such example could be as below.
-          --authorization-mode=RBAC
-        scored: true
-
-      - id: 1.2.7
-        text: "Ensure that the --authorization-mode argument includes Node (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "Node"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes Node.
-          --authorization-mode=Node,RBAC
-        scored: true
-
-      - id: 1.2.8
-        text: "Ensure that the --authorization-mode argument includes RBAC (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "RBAC"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes RBAC,
-          for example `--authorization-mode=Node,RBAC`.
-        scored: true
-
-      - id: 1.2.9
-        text: "Ensure that the admission control plugin EventRateLimit is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "EventRateLimit"
-        remediation: |
-          Follow the Kubernetes documentation and set the desired limits in a configuration file.
-          Then, edit the API server pod specification file $apiserverconf
-          and set the below parameters.
-          --enable-admission-plugins=...,EventRateLimit,...
-          --admission-control-config-file=<path/to/configuration/file>
-        scored: false
-
-      - id: 1.2.10
-        text: "Ensure that the admission control plugin AlwaysAdmit is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: nothave
-                value: AlwaysAdmit
-            - flag: "--enable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --enable-admission-plugins parameter, or set it to a
-          value that does not include AlwaysAdmit.
-        scored: true
-
-      - id: 1.2.11
-        text: "Ensure that the admission control plugin AlwaysPullImages is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "AlwaysPullImages"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          AlwaysPullImages.
-          --enable-admission-plugins=...,AlwaysPullImages,...
-        scored: false
-
-      - id: 1.2.12
-        text: "Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "SecurityContextDeny"
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "PodSecurityPolicy"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          SecurityContextDeny, unless PodSecurityPolicy is already in place.
-          --enable-admission-plugins=...,SecurityContextDeny,...
-        scored: false
-
-      - id: 1.2.13
-        text: "Ensure that the admission control plugin ServiceAccount is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "ServiceAccount"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Follow the documentation and create ServiceAccount objects as per your environment.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and ensure that the --disable-admission-plugins parameter is set to a
-          value that does not include ServiceAccount.
-        scored: true
-
-      - id: 1.2.14
-        text: "Ensure that the admission control plugin NamespaceLifecycle is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "NamespaceLifecycle"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --disable-admission-plugins parameter to
-          ensure it does not include NamespaceLifecycle.
-        scored: true
-
-      - id: 1.2.15
-        text: "Ensure that the admission control plugin NodeRestriction is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "NodeRestriction"
-        remediation: |
-          Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to a
-          value that includes NodeRestriction.
-          --enable-admission-plugins=...,NodeRestriction,...
-        scored: true
-
-      - id: 1.2.16
-        text: "Ensure that the --secure-port argument is not set to 0 - NoteThis recommendation is obsolete and will be deleted per the consensus process (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--secure-port"
-              compare:
-                op: gt
-                value: 0
-            - flag: "--secure-port"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --secure-port parameter or
-          set it to a different (non-zero) desired port.
-        scored: false
-
-      - id: 1.2.17
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.2.18
-        text: "Ensure that the --audit-log-path argument is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-path"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-path parameter to a suitable path and
-          file where you would like audit logs to be written, for example,
-          --audit-log-path=/var/log/apiserver/audit.log
-        scored: true
-
-      - id: 1.2.19
-        text: "Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxage"
-              compare:
-                op: gte
-                value: 30
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxage parameter to 30
-          or as an appropriate number of days, for example,
-          --audit-log-maxage=30
-        scored: true
-
-      - id: 1.2.20
-        text: "Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxbackup"
-              compare:
-                op: gte
-                value: 10
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxbackup parameter to 10 or to an appropriate
-          value. For example,
-          --audit-log-maxbackup=10
-        scored: true
-
-      - id: 1.2.21
-        text: "Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxsize"
-              compare:
-                op: gte
-                value: 100
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxsize parameter to an appropriate size in MB.
-          For example, to set it as 100 MB, --audit-log-maxsize=100
-        scored: true
-
-      - id: 1.2.22
-        text: "Ensure that the --request-timeout argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        type: manual
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          and set the below parameter as appropriate and if needed.
-          For example, --request-timeout=300s
-        scored: false
-
-      - id: 1.2.23
-        text: "Ensure that the --service-account-lookup argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--service-account-lookup"
-              set: false
-            - flag: "--service-account-lookup"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --service-account-lookup=true
-          Alternatively, you can delete the --service-account-lookup parameter from this file so
-          that the default takes effect.
-        scored: true
-
-      - id: 1.2.24
-        text: "Ensure that the --service-account-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-key-file"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --service-account-key-file parameter
-          to the public key file for service accounts. For example,
-          --service-account-key-file=<filename>
-        scored: true
-
-      - id: 1.2.25
-        text: "Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--etcd-certfile"
-            - flag: "--etcd-keyfile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate and key file parameters.
-          --etcd-certfile=<path/to/client-certificate-file>
-          --etcd-keyfile=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.26
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--tls-cert-file"
-            - flag: "--tls-private-key-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the TLS certificate and private key file parameters.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-        scored: true
-
-      - id: 1.2.27
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--client-ca-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the client certificate authority file.
-          --client-ca-file=<path/to/client-ca-file>
-        scored: true
-
-      - id: 1.2.28
-        text: "Ensure that the --etcd-cafile argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--etcd-cafile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate authority file parameter.
-          --etcd-cafile=<path/to/ca-file>
-        scored: true
-
-      - id: 1.2.29
-        text: "Ensure that the --encryption-provider-config argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--encryption-provider-config"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --encryption-provider-config parameter to the path of that file.
-          For example, --encryption-provider-config=</path/to/EncryptionConfig/File>
-        scored: false
-
-      - id: 1.2.30
-        text: "Ensure that encryption providers are appropriately configured (Manual)"
-        audit: |
-          ENCRYPTION_PROVIDER_CONFIG=$(ps -ef | grep $apiserverbin | grep -- --encryption-provider-config | sed 's%.*encryption-provider-config[= ]\([^ ]*\).*%\1%')
-          if test -e $ENCRYPTION_PROVIDER_CONFIG; then grep -A1 'providers:' $ENCRYPTION_PROVIDER_CONFIG | tail -n1 | grep -o "[A-Za-z]*" | sed 's/^/provider=/'; fi
-        tests:
-          test_items:
-            - flag: "provider"
-              compare:
-                op: valid_elements
-                value: "aescbc,kms,secretbox"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          In this file, choose aescbc, kms or secretbox as the encryption provider.
-        scored: false
-
-      - id: 1.2.31
-        text: "Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--tls-cipher-suites"
-              compare:
-                op: valid_elements
-                value: "TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384"
-        remediation: |
-          Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
-          on the control plane node and set the below parameter.
-          --tls-cipher-suites=TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
-          TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
-          TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,
-          TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384
-        scored: false
-
-  - id: 1.3
-    text: "Controller Manager"
-    checks:
-      - id: 1.3.1
-        text: "Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--terminated-pod-gc-threshold"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --terminated-pod-gc-threshold to an appropriate threshold,
-          for example, --terminated-pod-gc-threshold=10
-        scored: false
-
-      - id: 1.3.2
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.3.3
-        text: "Ensure that the --use-service-account-credentials argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--use-service-account-credentials"
-              compare:
-                op: noteq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node to set the below parameter.
-          --use-service-account-credentials=true
-        scored: true
-
-      - id: 1.3.4
-        text: "Ensure that the --service-account-private-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-private-key-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --service-account-private-key-file parameter
-          to the private key file for service accounts.
-          --service-account-private-key-file=<filename>
-        scored: true
-
-      - id: 1.3.5
-        text: "Ensure that the --root-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--root-ca-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --root-ca-file parameter to the certificate bundle file`.
-          --root-ca-file=<path/to/file>
-        scored: true
-
-      - id: 1.3.6
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--feature-gates"
-              compare:
-                op: nothave
-                value: "RotateKubeletServerCertificate=false"
-              set: true
-            - flag: "--feature-gates"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.
-          --feature-gates=RotateKubeletServerCertificate=true
-        scored: true
-
-      - id: 1.3.7
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true
-
-  - id: 1.4
-    text: "Scheduler"
-    checks:
-      - id: 1.4.1
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf file
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.4.2
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true

cfg/cis-1.7/node.yaml

@@ -1,455 +0,0 @@
----
-controls:
-version: "cis-1.7"
-id: 4
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 4.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c permissions=%a $kubeletsvc; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chmod 600 $kubeletsvc
-        scored: true
-
-      - id: 4.1.2
-        text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-            - flag: "File not found"
-        remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
-        scored: true
-
-      - id: 4.1.3
-        text: "If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "permissions"
-              set: true
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $proxykubeconfig
-        scored: false
-
-      - id: 4.1.4
-        text: "If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chown root:root $proxykubeconfig
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.6
-        text: "Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.7
-        text: "Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command to modify the file permissions of the
-          --client-ca-file chmod 600 <filename>
-        scored: false
-
-      - id: 4.1.8
-        text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
-        tests:
-          test_items:
-            - flag: root:root
-              compare:
-                op: eq
-                value: root:root
-        remediation: |
-          Run the following command to modify the ownership of the --client-ca-file.
-          chown root:root <filename>
-        scored: false
-
-      - id: 4.1.9
-        text: "If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 600 $kubeletconf
-        scored: false
-
-      - id: 4.1.10
-        text: "If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: false
-
-  - id: 4.2
-    text: "Kubelet"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to
-          `false`.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          `--anonymous-auth=false`
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authorization.mode` to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.3
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication.x509.clientCAFile` to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.4
-        text: "Verify that the --read-only-port argument is set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              compare:
-                op: eq
-                value: 0
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `readOnlyPort` to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `streamingConnectionIdleTimeout` to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `makeIPTablesUtilChains` to `true`.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.7
-        text: "Ensure that the --hostname-override argument is not set (Manual)"
-        # This is one of those properties that can only be set as a command line argument.
-        # To check if the property is set as expected, we need to parse the kubelet command
-        # instead reading the Kubelet Configuration file.
-        audit: "/bin/ps -fC $kubeletbin "
-        tests:
-          test_items:
-            - flag: --hostname-override
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and remove the --hostname-override argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.8
-        text: "Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              compare:
-                op: gte
-                value: 0
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `eventRecordQPS` to an appropriate level.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.9
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cert-file
-              path: '{.tlsCertFile}'
-            - flag: --tls-private-key-file
-              path: '{.tlsPrivateKeyFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCertFile` to the location
-          of the certificate file to use to identify this Kubelet, and `tlsPrivateKeyFile`
-          to the location of the corresponding private key file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameters in KUBELET_CERTIFICATE_ARGS variable.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.10
-        text: "Ensure that the --rotate-certificates argument is not set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to add the line `rotateCertificates` to `true` or
-          remove it altogether to use the default value.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS
-          variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.11
-        text: "Verify that the RotateKubeletServerCertificate argument is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              compare:
-                op: nothave
-                value: false
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.12
-        text: "Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cipher-suites
-              path: '{range .tlsCipherSuites[:]}{}{'',''}{end}'
-              compare:
-                op: valid_elements
-                value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
-          TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          or to a subset of these values.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the --tls-cipher-suites parameter as follows, or to a subset of these values.
-          --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.13
-        text: "Ensure that a limit is set on pod PIDs (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --pod-max-pids
-              path: '{.podPidsLimit}'
-        remediation: |
-          Decide on an appropriate level for this parameter and set it,
-          either via the --pod-max-pids command line parameter or the PodPidsLimit configuration file setting.
-        scored: false

cfg/cis-1.7/policies.yaml

@@ -1,304 +0,0 @@
----
-controls:
-version: "cis-1.7"
-id: 5
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 5.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 5.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Manual)"
-        type: "manual"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role :
-          kubectl delete clusterrolebinding [name]
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize access to secrets (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove get, list and watch access to Secret objects in the cluster.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize access to create pods (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-
-      - id: 5.1.5
-        text: "Ensure that default service accounts are not actively used. (Manual)"
-        type: "manual"
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific access
-          to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          automountServiceAccountToken: false
-        scored: false
-
-      - id: 5.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Manual)"
-        type: "manual"
-        remediation: |
-          Modify the definition of pods and service accounts which do not need to mount service
-          account tokens to disable it.
-        scored: false
-
-      - id: 5.1.7
-        text: "Avoid use of system:masters group (Manual)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 5.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-      - id: 5.1.9
-        text: "Minimize access to create persistent volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to PersistentVolume objects in the cluster.
-        scored: false
-
-      - id: 5.1.10
-        text: "Minimize access to the proxy sub-resource of nodes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the proxy sub-resource of node objects.
-        scored: false
-
-      - id: 5.1.11
-        text: "Minimize access to the approval sub-resource of certificatesigningrequests objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the approval sub-resource of certificatesigningrequest objects.
-        scored: false
-
-      - id: 5.1.12
-        text: "Minimize access to webhook configuration objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the validatingwebhookconfigurations or mutatingwebhookconfigurations objects
-        scored: false
-
-      - id: 5.1.13
-        text: "Minimize access to the service account token creation (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the token sub-resource of serviceaccount objects.
-        scored: false
-
-  - id: 5.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 5.2.1
-        text: "Ensure that the cluster has at least one active policy control mechanism in place (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that either Pod Security Admission or an external policy control system is in place
-          for every namespace which contains user workloads.
-        scored: false
-
-      - id: 5.2.2
-        text: "Minimize the admission of privileged containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of privileged containers.
-        scored: false
-
-      - id: 5.2.3
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostPID` containers.
-        scored: false
-
-      - id: 5.2.4
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostIPC` containers.
-        scored: false
-
-      - id: 5.2.5
-        text: "Minimize the admission of containers wishing to share the host network namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostNetwork` containers.
-        scored: false
-
-      - id: 5.2.6
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `.spec.allowPrivilegeEscalation` set to `true`.
-        scored: false
-
-      - id: 5.2.7
-        text: "Minimize the admission of root containers (Automated)"
-        type: "manual"
-        remediation: |
-          Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot`
-          or `MustRunAs` with the range of UIDs not including 0, is set.
-        scored: false
-
-      - id: 5.2.8
-        text: "Minimize the admission of containers with the NET_RAW capability (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with the `NET_RAW` capability.
-        scored: false
-
-      - id: 5.2.9
-        text: "Minimize the admission of containers with added capabilities (Automated)"
-        type: "manual"
-        remediation: |
-          Ensure that `allowedCapabilities` is not present in policies for the cluster unless
-          it is set to an empty array.
-        scored: false
-
-      - id: 5.2.10
-        text: "Minimize the admission of containers with capabilities assigned (Manual)"
-        type: "manual"
-        remediation: |
-          Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
-          a PSP which forbids the admission of containers which do not drop all capabilities.
-        scored: false
-
-      - id: 5.2.11
-        text: "Minimize the admission of Windows HostProcess containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers that have `.securityContext.windowsOptions.hostProcess` set to `true`.
-        scored: false
-
-      - id: 5.2.12
-        text: "Minimize the admission of HostPath volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `hostPath` volumes.
-        scored: false
-
-      - id: 5.2.13
-        text: "Minimize the admission of containers which use HostPorts (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers which use `hostPort` sections.
-        scored: false
-
-  - id: 5.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 5.3.1
-        text: "Ensure that the CNI in use supports NetworkPolicies (Manual)"
-        type: "manual"
-        remediation: |
-          If the CNI plugin in use does not support network policies, consideration should be given to
-          making use of a different plugin, or finding an alternate mechanism for restricting traffic
-          in the Kubernetes cluster.
-        scored: false
-
-      - id: 5.3.2
-        text: "Ensure that all Namespaces have NetworkPolicies defined (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 5.4
-    text: "Secrets Management"
-    checks:
-      - id: 5.4.1
-        text: "Prefer using Secrets as files over Secrets as environment variables (Manual)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read Secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 5.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the Secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 5.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 5.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-        scored: false
-
-  - id: 5.7
-    text: "General Policies"
-    checks:
-      - id: 5.7.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 5.7.2
-        text: "Ensure that the seccomp profile is set to docker/default in your Pod definitions (Manual)"
-        type: "manual"
-        remediation: |
-          Use `securityContext` to enable the docker/default seccomp profile in your pod definitions.
-          An example is as below:
-            securityContext:
-              seccompProfile:
-                type: RuntimeDefault
-        scored: false
-
-      - id: 5.7.3
-        text: "Apply SecurityContext to your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply SecurityContexts to your Pods. For a
-          suggested list of SecurityContexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 5.7.4
-        text: "The default namespace should not be used (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/cis-1.8/config.yaml

@@ -1,2 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml

cfg/cis-1.8/controlplane.yaml

@@ -1,60 +0,0 @@
----
-controls:
-version: "cis-1.8"
-id: 3
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 3.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 3.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-        scored: false
-      - id: 3.1.2
-        text: "Service account token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of service account tokens.
-        scored: false
-      - id: 3.1.3
-        text: "Bootstrap token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of bootstrap tokens.
-        scored: false
-
-  - id: 3.2
-    text: "Logging"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that a minimal audit policy is created (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-policy-file"
-              set: true
-        remediation: |
-          Create an audit policy file for your cluster.
-        scored: false
-
-      - id: 3.2.2
-        text: "Ensure that the audit policy covers key security concerns (Manual)"
-        type: "manual"
-        remediation: |
-          Review the audit policy provided for the cluster and ensure that it covers
-          at least the following areas,
-          - Access to Secrets managed by the cluster. Care should be taken to only
-            log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in
-            order to avoid risk of logging sensitive data.
-          - Modification of Pod and Deployment objects.
-          - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.
-          For most requests, minimally logging at the Metadata level is recommended
-          (the most basic level of logging).
-        scored: false

cfg/cis-1.8/etcd.yaml

@@ -1,135 +0,0 @@
----
-controls:
-version: "cis-1.8"
-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"
-            - flag: "--key-file"
-              env: "ETCD_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--client-cert-auth"
-              env: "ETCD_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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"
-            - flag: "--peer-key-file"
-              env: "ETCD_PEER_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--peer-client-cert-auth"
-              env: "ETCD_PEER_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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
-        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 (Manual)"
-        audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
-        tests:
-          test_items:
-            - flag: "--trusted-ca-file"
-              env: "ETCD_TRUSTED_CA_FILE"
-        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: false

cfg/cis-1.8/master.yaml

@@ -1,928 +0,0 @@
----
-controls:
-version: "cis-1.8"
-id: 1
-text: "Control Plane Security Configuration"
-type: "master"
-groups:
-  - id: 1.1
-    text: "Control Plane Node Configuration Files"
-    checks:
-      - id: 1.1.1
-        text: "Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c permissions=%a $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the
-          control plane node.
-          For example, chmod 600 $apiserverconf
-        scored: true
-
-      - id: 1.1.2
-        text: "Ensure that the API server pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c %U:%G $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $apiserverconf
-        scored: true
-
-      - id: 1.1.3
-        text: "Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c permissions=%a $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $controllermanagerconf
-        scored: true
-
-      - id: 1.1.4
-        text: "Ensure that the controller manager pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c %U:%G $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $controllermanagerconf
-        scored: true
-
-      - id: 1.1.5
-        text: "Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c permissions=%a $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $schedulerconf
-        scored: true
-
-      - id: 1.1.6
-        text: "Ensure that the scheduler pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c %U:%G $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $schedulerconf
-        scored: true
-
-      - id: 1.1.7
-        text: "Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c permissions=%a; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $etcdconf
-        scored: true
-
-      - id: 1.1.8
-        text: "Ensure that the etcd pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c %U:%G; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $etcdconf
-        scored: true
-
-      - id: 1.1.9
-        text: "Ensure that the Container Network Interface file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c permissions=%a
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c permissions=%a
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.10
-        text: "Ensure that the Container Network Interface file ownership is set to root:root (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c %U:%G
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c %U:%G
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.11
-        text: "Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c permissions=%a "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "700"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above). For example,
-          chmod 700 /var/lib/etcd
-        scored: true
-
-      - id: 1.1.12
-        text: "Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c %U:%G "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "etcd:etcd"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above).
-          For example, chown etcd:etcd /var/lib/etcd
-        scored: true
-
-      - id: 1.1.13
-        text: "Ensure that the admin.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e /etc/kubernetes/admin.conf; then stat -c permissions=%a /etc/kubernetes/admin.conf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 /etc/kubernetes/admin.conf
-        scored: true
-
-      - id: 1.1.14
-        text: "Ensure that the admin.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e /etc/kubernetes/admin.conf; then stat -c %U:%G /etc/kubernetes/admin.conf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root /etc/kubernetes/admin.conf
-        scored: true
-
-      - id: 1.1.15
-        text: "Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c permissions=%a $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.16
-        text: "Ensure that the scheduler.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c %U:%G $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.17
-        text: "Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c permissions=%a $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.18
-        text: "Ensure that the controller-manager.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c %U:%G $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.19
-        text: "Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)"
-        audit: "find /etc/kubernetes/pki/ | xargs stat -c %U:%G"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown -R root:root /etc/kubernetes/pki/
-        scored: true
-
-      - id: 1.1.20
-        text: "Ensure that the Kubernetes PKI certificate file permissions are set to 600 or more restrictive (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.crt' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.crt
-        scored: false
-
-      - id: 1.1.21
-        text: "Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.key' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.key
-        scored: false
-
-  - id: 1.2
-    text: "API Server"
-    checks:
-      - id: 1.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --anonymous-auth=false
-        scored: false
-
-      - id: 1.2.2
-        text: "Ensure that the --token-auth-file parameter is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--token-auth-file"
-              set: false
-        remediation: |
-          Follow the documentation and configure alternate mechanisms for authentication. Then,
-          edit the API server pod specification file $apiserverconf
-          on the control plane node and remove the --token-auth-file=<filename> parameter.
-        scored: true
-
-      - id: 1.2.3
-        text: "Ensure that the --DenyServiceExternalIPs is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "DenyServiceExternalIPs"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and add the `DenyServiceExternalIPs` plugin
-          to the enabled admission plugins, as such --enable-admission-plugin=DenyServiceExternalIPs.
-        scored: false
-
-      - id: 1.2.4
-        text: "Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--kubelet-client-certificate"
-            - flag: "--kubelet-client-key"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the
-          apiserver and kubelets. Then, edit API server pod specification file
-          $apiserverconf on the control plane node and set the
-          kubelet client certificate and key parameters as below.
-          --kubelet-client-certificate=<path/to/client-certificate-file>
-          --kubelet-client-key=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.5
-        text: "Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--kubelet-certificate-authority"
-        remediation: |
-          Follow the Kubernetes documentation and setup the TLS connection between
-          the apiserver and kubelets. Then, edit the API server pod specification file
-          $apiserverconf on the control plane node and set the
-          --kubelet-certificate-authority parameter to the path to the cert file for the certificate authority.
-          --kubelet-certificate-authority=<ca-string>
-        scored: true
-
-      - id: 1.2.6
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: nothave
-                value: "AlwaysAllow"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to values other than AlwaysAllow.
-          One such example could be as below.
-          --authorization-mode=RBAC
-        scored: true
-
-      - id: 1.2.7
-        text: "Ensure that the --authorization-mode argument includes Node (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "Node"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes Node.
-          --authorization-mode=Node,RBAC
-        scored: true
-
-      - id: 1.2.8
-        text: "Ensure that the --authorization-mode argument includes RBAC (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "RBAC"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes RBAC,
-          for example `--authorization-mode=Node,RBAC`.
-        scored: true
-
-      - id: 1.2.9
-        text: "Ensure that the admission control plugin EventRateLimit is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "EventRateLimit"
-        remediation: |
-          Follow the Kubernetes documentation and set the desired limits in a configuration file.
-          Then, edit the API server pod specification file $apiserverconf
-          and set the below parameters.
-          --enable-admission-plugins=...,EventRateLimit,...
-          --admission-control-config-file=<path/to/configuration/file>
-        scored: false
-
-      - id: 1.2.10
-        text: "Ensure that the admission control plugin AlwaysAdmit is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: nothave
-                value: AlwaysAdmit
-            - flag: "--enable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --enable-admission-plugins parameter, or set it to a
-          value that does not include AlwaysAdmit.
-        scored: true
-
-      - id: 1.2.11
-        text: "Ensure that the admission control plugin AlwaysPullImages is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "AlwaysPullImages"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          AlwaysPullImages.
-          --enable-admission-plugins=...,AlwaysPullImages,...
-        scored: false
-
-      - id: 1.2.12
-        text: "Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "SecurityContextDeny"
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "PodSecurityPolicy"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          SecurityContextDeny, unless PodSecurityPolicy is already in place.
-          --enable-admission-plugins=...,SecurityContextDeny,...
-        scored: false
-
-      - id: 1.2.13
-        text: "Ensure that the admission control plugin ServiceAccount is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "ServiceAccount"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Follow the documentation and create ServiceAccount objects as per your environment.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and ensure that the --disable-admission-plugins parameter is set to a
-          value that does not include ServiceAccount.
-        scored: true
-
-      - id: 1.2.14
-        text: "Ensure that the admission control plugin NamespaceLifecycle is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "NamespaceLifecycle"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --disable-admission-plugins parameter to
-          ensure it does not include NamespaceLifecycle.
-        scored: true
-
-      - id: 1.2.15
-        text: "Ensure that the admission control plugin NodeRestriction is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "NodeRestriction"
-        remediation: |
-          Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to a
-          value that includes NodeRestriction.
-          --enable-admission-plugins=...,NodeRestriction,...
-        scored: true
-
-      - id: 1.2.16
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.2.17
-        text: "Ensure that the --audit-log-path argument is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-path"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-path parameter to a suitable path and
-          file where you would like audit logs to be written, for example,
-          --audit-log-path=/var/log/apiserver/audit.log
-        scored: true
-
-      - id: 1.2.18
-        text: "Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxage"
-              compare:
-                op: gte
-                value: 30
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxage parameter to 30
-          or as an appropriate number of days, for example,
-          --audit-log-maxage=30
-        scored: true
-
-      - id: 1.2.19
-        text: "Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxbackup"
-              compare:
-                op: gte
-                value: 10
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxbackup parameter to 10 or to an appropriate
-          value. For example,
-          --audit-log-maxbackup=10
-        scored: true
-
-      - id: 1.2.20
-        text: "Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxsize"
-              compare:
-                op: gte
-                value: 100
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxsize parameter to an appropriate size in MB.
-          For example, to set it as 100 MB, --audit-log-maxsize=100
-        scored: true
-
-      - id: 1.2.21
-        text: "Ensure that the --request-timeout argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        type: manual
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          and set the below parameter as appropriate and if needed.
-          For example, --request-timeout=300s
-        scored: false
-
-      - id: 1.2.22
-        text: "Ensure that the --service-account-lookup argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--service-account-lookup"
-              set: false
-            - flag: "--service-account-lookup"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --service-account-lookup=true
-          Alternatively, you can delete the --service-account-lookup parameter from this file so
-          that the default takes effect.
-        scored: true
-
-      - id: 1.2.23
-        text: "Ensure that the --service-account-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-key-file"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --service-account-key-file parameter
-          to the public key file for service accounts. For example,
-          --service-account-key-file=<filename>
-        scored: true
-
-      - id: 1.2.24
-        text: "Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--etcd-certfile"
-            - flag: "--etcd-keyfile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate and key file parameters.
-          --etcd-certfile=<path/to/client-certificate-file>
-          --etcd-keyfile=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.25
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--tls-cert-file"
-            - flag: "--tls-private-key-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the TLS certificate and private key file parameters.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-        scored: true
-
-      - id: 1.2.26
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--client-ca-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the client certificate authority file.
-          --client-ca-file=<path/to/client-ca-file>
-        scored: true
-
-      - id: 1.2.27
-        text: "Ensure that the --etcd-cafile argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--etcd-cafile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate authority file parameter.
-          --etcd-cafile=<path/to/ca-file>
-        scored: true
-
-      - id: 1.2.28
-        text: "Ensure that the --encryption-provider-config argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--encryption-provider-config"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --encryption-provider-config parameter to the path of that file.
-          For example, --encryption-provider-config=</path/to/EncryptionConfig/File>
-        scored: false
-
-      - id: 1.2.29
-        text: "Ensure that encryption providers are appropriately configured (Manual)"
-        audit: |
-          ENCRYPTION_PROVIDER_CONFIG=$(ps -ef | grep $apiserverbin | grep -- --encryption-provider-config | sed 's%.*encryption-provider-config[= ]\([^ ]*\).*%\1%')
-          if test -e $ENCRYPTION_PROVIDER_CONFIG; then grep -A1 'providers:' $ENCRYPTION_PROVIDER_CONFIG | tail -n1 | grep -o "[A-Za-z]*" | sed 's/^/provider=/'; fi
-        tests:
-          test_items:
-            - flag: "provider"
-              compare:
-                op: valid_elements
-                value: "aescbc,kms,secretbox"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          In this file, choose aescbc, kms or secretbox as the encryption provider.
-        scored: false
-
-      - id: 1.2.30
-        text: "Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--tls-cipher-suites"
-              compare:
-                op: valid_elements
-                value: "TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384"
-        remediation: |
-          Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
-          on the control plane node and set the below parameter.
-          --tls-cipher-suites=TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
-          TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
-          TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,
-          TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384
-        scored: false
-
-  - id: 1.3
-    text: "Controller Manager"
-    checks:
-      - id: 1.3.1
-        text: "Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--terminated-pod-gc-threshold"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --terminated-pod-gc-threshold to an appropriate threshold,
-          for example, --terminated-pod-gc-threshold=10
-        scored: false
-
-      - id: 1.3.2
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.3.3
-        text: "Ensure that the --use-service-account-credentials argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--use-service-account-credentials"
-              compare:
-                op: noteq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node to set the below parameter.
-          --use-service-account-credentials=true
-        scored: true
-
-      - id: 1.3.4
-        text: "Ensure that the --service-account-private-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-private-key-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --service-account-private-key-file parameter
-          to the private key file for service accounts.
-          --service-account-private-key-file=<filename>
-        scored: true
-
-      - id: 1.3.5
-        text: "Ensure that the --root-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--root-ca-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --root-ca-file parameter to the certificate bundle file`.
-          --root-ca-file=<path/to/file>
-        scored: true
-
-      - id: 1.3.6
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--feature-gates"
-              compare:
-                op: nothave
-                value: "RotateKubeletServerCertificate=false"
-              set: true
-            - flag: "--feature-gates"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.
-          --feature-gates=RotateKubeletServerCertificate=true
-        scored: true
-
-      - id: 1.3.7
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true
-
-  - id: 1.4
-    text: "Scheduler"
-    checks:
-      - id: 1.4.1
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf file
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.4.2
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true

cfg/cis-1.8/node.yaml

@@ -1,455 +0,0 @@
----
-controls:
-version: "cis-1.8"
-id: 4
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 4.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c permissions=%a $kubeletsvc; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chmod 600 $kubeletsvc
-        scored: true
-
-      - id: 4.1.2
-        text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-            - flag: "File not found"
-        remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
-        scored: true
-
-      - id: 4.1.3
-        text: "If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "permissions"
-              set: true
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $proxykubeconfig
-        scored: false
-
-      - id: 4.1.4
-        text: "If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chown root:root $proxykubeconfig
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.6
-        text: "Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.7
-        text: "Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command to modify the file permissions of the
-          --client-ca-file chmod 600 <filename>
-        scored: false
-
-      - id: 4.1.8
-        text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
-        tests:
-          test_items:
-            - flag: root:root
-              compare:
-                op: eq
-                value: root:root
-        remediation: |
-          Run the following command to modify the ownership of the --client-ca-file.
-          chown root:root <filename>
-        scored: false
-
-      - id: 4.1.9
-        text: "If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 600 $kubeletconf
-        scored: true
-
-      - id: 4.1.10
-        text: "If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: true
-
-  - id: 4.2
-    text: "Kubelet"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to
-          `false`.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          `--anonymous-auth=false`
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authorization.mode` to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.3
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication.x509.clientCAFile` to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.4
-        text: "Verify that the --read-only-port argument is set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              compare:
-                op: eq
-                value: 0
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `readOnlyPort` to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `streamingConnectionIdleTimeout` to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `makeIPTablesUtilChains` to `true`.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.7
-        text: "Ensure that the --hostname-override argument is not set (Manual)"
-        # This is one of those properties that can only be set as a command line argument.
-        # To check if the property is set as expected, we need to parse the kubelet command
-        # instead reading the Kubelet Configuration file.
-        audit: "/bin/ps -fC $kubeletbin "
-        tests:
-          test_items:
-            - flag: --hostname-override
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and remove the --hostname-override argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.8
-        text: "Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              compare:
-                op: gte
-                value: 0
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `eventRecordQPS` to an appropriate level.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.9
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cert-file
-              path: '{.tlsCertFile}'
-            - flag: --tls-private-key-file
-              path: '{.tlsPrivateKeyFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCertFile` to the location
-          of the certificate file to use to identify this Kubelet, and `tlsPrivateKeyFile`
-          to the location of the corresponding private key file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameters in KUBELET_CERTIFICATE_ARGS variable.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.10
-        text: "Ensure that the --rotate-certificates argument is not set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to add the line `rotateCertificates` to `true` or
-          remove it altogether to use the default value.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS
-          variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.11
-        text: "Verify that the RotateKubeletServerCertificate argument is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              compare:
-                op: nothave
-                value: false
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.12
-        text: "Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cipher-suites
-              path: '{range .tlsCipherSuites[:]}{}{'',''}{end}'
-              compare:
-                op: valid_elements
-                value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
-          TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          or to a subset of these values.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the --tls-cipher-suites parameter as follows, or to a subset of these values.
-          --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.13
-        text: "Ensure that a limit is set on pod PIDs (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --pod-max-pids
-              path: '{.podPidsLimit}'
-        remediation: |
-          Decide on an appropriate level for this parameter and set it,
-          either via the --pod-max-pids command line parameter or the PodPidsLimit configuration file setting.
-        scored: false

cfg/cis-1.8/policies.yaml

@@ -1,304 +0,0 @@
----
-controls:
-version: "cis-1.8"
-id: 5
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 5.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 5.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Manual)"
-        type: "manual"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role :
-          kubectl delete clusterrolebinding [name]
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize access to secrets (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove get, list and watch access to Secret objects in the cluster.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize access to create pods (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-
-      - id: 5.1.5
-        text: "Ensure that default service accounts are not actively used. (Manual)"
-        type: "manual"
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific access
-          to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          automountServiceAccountToken: false
-        scored: false
-
-      - id: 5.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Manual)"
-        type: "manual"
-        remediation: |
-          Modify the definition of pods and service accounts which do not need to mount service
-          account tokens to disable it.
-        scored: false
-
-      - id: 5.1.7
-        text: "Avoid use of system:masters group (Manual)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 5.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-      - id: 5.1.9
-        text: "Minimize access to create persistent volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to PersistentVolume objects in the cluster.
-        scored: false
-
-      - id: 5.1.10
-        text: "Minimize access to the proxy sub-resource of nodes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the proxy sub-resource of node objects.
-        scored: false
-
-      - id: 5.1.11
-        text: "Minimize access to the approval sub-resource of certificatesigningrequests objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the approval sub-resource of certificatesigningrequest objects.
-        scored: false
-
-      - id: 5.1.12
-        text: "Minimize access to webhook configuration objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the validatingwebhookconfigurations or mutatingwebhookconfigurations objects
-        scored: false
-
-      - id: 5.1.13
-        text: "Minimize access to the service account token creation (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the token sub-resource of serviceaccount objects.
-        scored: false
-
-  - id: 5.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 5.2.1
-        text: "Ensure that the cluster has at least one active policy control mechanism in place (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that either Pod Security Admission or an external policy control system is in place
-          for every namespace which contains user workloads.
-        scored: false
-
-      - id: 5.2.2
-        text: "Minimize the admission of privileged containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of privileged containers.
-        scored: false
-
-      - id: 5.2.3
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostPID` containers.
-        scored: false
-
-      - id: 5.2.4
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostIPC` containers.
-        scored: false
-
-      - id: 5.2.5
-        text: "Minimize the admission of containers wishing to share the host network namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostNetwork` containers.
-        scored: false
-
-      - id: 5.2.6
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `.spec.allowPrivilegeEscalation` set to `true`.
-        scored: false
-
-      - id: 5.2.7
-        text: "Minimize the admission of root containers (Automated)"
-        type: "manual"
-        remediation: |
-          Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot`
-          or `MustRunAs` with the range of UIDs not including 0, is set.
-        scored: false
-
-      - id: 5.2.8
-        text: "Minimize the admission of containers with the NET_RAW capability (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with the `NET_RAW` capability.
-        scored: false
-
-      - id: 5.2.9
-        text: "Minimize the admission of containers with added capabilities (Automated)"
-        type: "manual"
-        remediation: |
-          Ensure that `allowedCapabilities` is not present in policies for the cluster unless
-          it is set to an empty array.
-        scored: false
-
-      - id: 5.2.10
-        text: "Minimize the admission of containers with capabilities assigned (Manual)"
-        type: "manual"
-        remediation: |
-          Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
-          a PSP which forbids the admission of containers which do not drop all capabilities.
-        scored: false
-
-      - id: 5.2.11
-        text: "Minimize the admission of Windows HostProcess containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers that have `.securityContext.windowsOptions.hostProcess` set to `true`.
-        scored: false
-
-      - id: 5.2.12
-        text: "Minimize the admission of HostPath volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `hostPath` volumes.
-        scored: false
-
-      - id: 5.2.13
-        text: "Minimize the admission of containers which use HostPorts (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers which use `hostPort` sections.
-        scored: false
-
-  - id: 5.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 5.3.1
-        text: "Ensure that the CNI in use supports NetworkPolicies (Manual)"
-        type: "manual"
-        remediation: |
-          If the CNI plugin in use does not support network policies, consideration should be given to
-          making use of a different plugin, or finding an alternate mechanism for restricting traffic
-          in the Kubernetes cluster.
-        scored: false
-
-      - id: 5.3.2
-        text: "Ensure that all Namespaces have NetworkPolicies defined (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 5.4
-    text: "Secrets Management"
-    checks:
-      - id: 5.4.1
-        text: "Prefer using Secrets as files over Secrets as environment variables (Manual)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read Secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 5.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the Secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 5.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 5.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-        scored: false
-
-  - id: 5.7
-    text: "General Policies"
-    checks:
-      - id: 5.7.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 5.7.2
-        text: "Ensure that the seccomp profile is set to docker/default in your Pod definitions (Manual)"
-        type: "manual"
-        remediation: |
-          Use `securityContext` to enable the docker/default seccomp profile in your pod definitions.
-          An example is as below:
-            securityContext:
-              seccompProfile:
-                type: RuntimeDefault
-        scored: false
-
-      - id: 5.7.3
-        text: "Apply SecurityContext to your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply SecurityContexts to your Pods. For a
-          suggested list of SecurityContexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 5.7.4
-        text: "The default namespace should not be used (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/cis-1.9/config.yaml

@@ -1,2 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml

cfg/cis-1.9/controlplane.yaml

@@ -1,62 +0,0 @@
----
-controls:
-version: "cis-1.9"
-id: 3
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 3.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 3.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-        scored: false
-
-      - id: 3.1.2
-        text: "Service account token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of service account tokens.
-        scored: false
-
-      - id: 3.1.3
-        text: "Bootstrap token authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be implemented
-          in place of bootstrap tokens.
-        scored: false
-
-  - id: 3.2
-    text: "Logging"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that a minimal audit policy is created (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-policy-file"
-              set: true
-        remediation: |
-          Create an audit policy file for your cluster.
-        scored: false
-
-      - id: 3.2.2
-        text: "Ensure that the audit policy covers key security concerns (Manual)"
-        type: "manual"
-        remediation: |
-          Review the audit policy provided for the cluster and ensure that it covers
-          at least the following areas,
-          - Access to Secrets managed by the cluster. Care should be taken to only
-            log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in
-            order to avoid risk of logging sensitive data.
-          - Modification of Pod and Deployment objects.
-          - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.
-          For most requests, minimally logging at the Metadata level is recommended
-          (the most basic level of logging).
-        scored: false

cfg/cis-1.9/etcd.yaml

@@ -1,135 +0,0 @@
----
-controls:
-version: "cis-1.9"
-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"
-            - flag: "--key-file"
-              env: "ETCD_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--client-cert-auth"
-              env: "ETCD_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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"
-            - flag: "--peer-key-file"
-              env: "ETCD_PEER_KEY_FILE"
-        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:
-          test_items:
-            - flag: "--peer-client-cert-auth"
-              env: "ETCD_PEER_CLIENT_CERT_AUTH"
-              compare:
-                op: eq
-                value: 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
-        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 (Manual)"
-        audit: "/bin/ps -ef | /bin/grep $etcdbin | /bin/grep -v grep"
-        tests:
-          test_items:
-            - flag: "--trusted-ca-file"
-              env: "ETCD_TRUSTED_CA_FILE"
-        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: false

cfg/cis-1.9/master.yaml

@@ -1,919 +0,0 @@
----
-controls:
-version: "cis-1.9"
-id: 1
-text: "Control Plane Security Configuration"
-type: "master"
-groups:
-  - id: 1.1
-    text: "Control Plane Node Configuration Files"
-    checks:
-      - id: 1.1.1
-        text: "Ensure that the API server pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c permissions=%a $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the
-          control plane node.
-          For example, chmod 600 $apiserverconf
-        scored: true
-
-      - id: 1.1.2
-        text: "Ensure that the API server pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $apiserverconf; then stat -c %U:%G $apiserverconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $apiserverconf
-        scored: true
-
-      - id: 1.1.3
-        text: "Ensure that the controller manager pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c permissions=%a $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $controllermanagerconf
-        scored: true
-
-      - id: 1.1.4
-        text: "Ensure that the controller manager pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerconf; then stat -c %U:%G $controllermanagerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $controllermanagerconf
-        scored: true
-
-      - id: 1.1.5
-        text: "Ensure that the scheduler pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c permissions=%a $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 $schedulerconf
-        scored: true
-
-      - id: 1.1.6
-        text: "Ensure that the scheduler pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerconf; then stat -c %U:%G $schedulerconf; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root $schedulerconf
-        scored: true
-
-      - id: 1.1.7
-        text: "Ensure that the etcd pod specification file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c permissions=%a; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $etcdconf
-        scored: true
-
-      - id: 1.1.8
-        text: "Ensure that the etcd pod specification file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $etcdconf; then find $etcdconf -name '*etcd*' | xargs stat -c %U:%G; fi'"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $etcdconf
-        scored: true
-
-      - id: 1.1.9
-        text: "Ensure that the Container Network Interface file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c permissions=%a
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c permissions=%a
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.10
-        text: "Ensure that the Container Network Interface file ownership is set to root:root (Manual)"
-        audit: |
-          ps -ef | grep $kubeletbin | grep -- --cni-conf-dir | sed 's%.*cni-conf-dir[= ]\([^ ]*\).*%\1%' | xargs -I{} find {} -mindepth 1 | xargs --no-run-if-empty stat -c %U:%G
-          find /var/lib/cni/networks -type f 2> /dev/null | xargs --no-run-if-empty stat -c %U:%G
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root <path/to/cni/files>
-        scored: false
-
-      - id: 1.1.11
-        text: "Ensure that the etcd data directory permissions are set to 700 or more restrictive (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c permissions=%a "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "700"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above). For example,
-          chmod 700 /var/lib/etcd
-        scored: true
-
-      - id: 1.1.12
-        text: "Ensure that the etcd data directory ownership is set to etcd:etcd (Automated)"
-        audit: |
-          DATA_DIR=''
-          for d in $(ps -ef | grep $etcdbin | grep -- --data-dir | sed 's%.*data-dir[= ]\([^ ]*\).*%\1%'); do
-            if test -d "$d"; then DATA_DIR="$d"; fi
-          done
-          if ! test -d "$DATA_DIR"; then DATA_DIR=$etcddatadir; fi
-          stat -c %U:%G "$DATA_DIR"
-        tests:
-          test_items:
-            - flag: "etcd:etcd"
-        remediation: |
-          On the etcd server node, get the etcd data directory, passed as an argument --data-dir,
-          from the command 'ps -ef | grep etcd'.
-          Run the below command (based on the etcd data directory found above).
-          For example, chown etcd:etcd /var/lib/etcd
-        scored: true
-
-      - id: 1.1.13
-        text: "Ensure that the default administrative credential file permissions are set to 600 (Automated)"
-        audit: |
-         for adminconf in /etc/kubernetes/admin.conf /etc/kubernetes/super-admin.conf; do if test -e $adminconf; then stat -c "permissions=%a %n" $adminconf; fi; done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chmod 600 /etc/kubernetes/admin.conf
-          On Kubernetes 1.29+ the super-admin.conf file should also be modified, if present.
-          For example, chmod 600 /etc/kubernetes/super-admin.conf
-        scored: true
-
-      - id: 1.1.14
-        text: "Ensure that the default administrative credential file ownership is set to root:root (Automated)"
-        audit: |
-         for adminconf in /etc/kubernetes/admin.conf /etc/kubernetes/super-admin.conf; do if test -e $adminconf; then stat -c "ownership=%U:%G %n" $adminconf; fi; done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "ownership"
-              compare:
-                op: eq
-                value: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example, chown root:root /etc/kubernetes/admin.conf
-          On Kubernetes 1.29+ the super-admin.conf file should also be modified, if present.
-          For example, chown root:root /etc/kubernetes/super-admin.conf
-        scored: true
-
-      - id: 1.1.15
-        text: "Ensure that the scheduler.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c permissions=%a $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.16
-        text: "Ensure that the scheduler.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $schedulerkubeconfig; then stat -c %U:%G $schedulerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $schedulerkubeconfig
-        scored: true
-
-      - id: 1.1.17
-        text: "Ensure that the controller-manager.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c permissions=%a $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod 600 $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.18
-        text: "Ensure that the controller-manager.conf file ownership is set to root:root (Automated)"
-        audit: "/bin/sh -c 'if test -e $controllermanagerkubeconfig; then stat -c %U:%G $controllermanagerkubeconfig; fi'"
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown root:root $controllermanagerkubeconfig
-        scored: true
-
-      - id: 1.1.19
-        text: "Ensure that the Kubernetes PKI directory and file ownership is set to root:root (Automated)"
-        audit: "find /etc/kubernetes/pki/ | xargs stat -c %U:%G"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "root:root"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chown -R root:root /etc/kubernetes/pki/
-        scored: true
-
-      - id: 1.1.20
-        text: "Ensure that the Kubernetes PKI certificate file permissions are set to 600 or more restrictive (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.crt' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.crt
-        scored: false
-
-      - id: 1.1.21
-        text: "Ensure that the Kubernetes PKI key file permissions are set to 600 (Manual)"
-        audit: "find /etc/kubernetes/pki/ -name '*.key' | xargs stat -c permissions=%a"
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the control plane node.
-          For example,
-          chmod -R 600 /etc/kubernetes/pki/*.key
-        scored: false
-
-  - id: 1.2
-    text: "API Server"
-    checks:
-      - id: 1.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --anonymous-auth=false
-        scored: false
-
-      - id: 1.2.2
-        text: "Ensure that the --token-auth-file parameter is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--token-auth-file"
-              set: false
-        remediation: |
-          Follow the documentation and configure alternate mechanisms for authentication. Then,
-          edit the API server pod specification file $apiserverconf
-          on the control plane node and remove the --token-auth-file=<filename> parameter.
-        scored: true
-
-      - id: 1.2.3
-        text: "Ensure that the --DenyServiceExternalIPs is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "DenyServiceExternalIPs"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and add the `DenyServiceExternalIPs` plugin
-          to the enabled admission plugins, as such --enable-admission-plugin=DenyServiceExternalIPs.
-        scored: false
-
-      - id: 1.2.4
-        text: "Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--kubelet-client-certificate"
-            - flag: "--kubelet-client-key"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the
-          apiserver and kubelets. Then, edit API server pod specification file
-          $apiserverconf on the control plane node and set the
-          kubelet client certificate and key parameters as below.
-          --kubelet-client-certificate=<path/to/client-certificate-file>
-          --kubelet-client-key=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.5
-        text: "Ensure that the --kubelet-certificate-authority argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--kubelet-certificate-authority"
-        remediation: |
-          Follow the Kubernetes documentation and setup the TLS connection between
-          the apiserver and kubelets. Then, edit the API server pod specification file
-          $apiserverconf on the control plane node and set the
-          --kubelet-certificate-authority parameter to the path to the cert file for the certificate authority.
-          --kubelet-certificate-authority=<ca-string>
-        scored: true
-
-      - id: 1.2.6
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: nothave
-                value: "AlwaysAllow"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to values other than AlwaysAllow.
-          One such example could be as below.
-          --authorization-mode=RBAC
-        scored: true
-
-      - id: 1.2.7
-        text: "Ensure that the --authorization-mode argument includes Node (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "Node"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes Node.
-          --authorization-mode=Node,RBAC
-        scored: true
-
-      - id: 1.2.8
-        text: "Ensure that the --authorization-mode argument includes RBAC (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--authorization-mode"
-              compare:
-                op: has
-                value: "RBAC"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --authorization-mode parameter to a value that includes RBAC,
-          for example `--authorization-mode=Node,RBAC`.
-        scored: true
-
-      - id: 1.2.9
-        text: "Ensure that the admission control plugin EventRateLimit is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "EventRateLimit"
-        remediation: |
-          Follow the Kubernetes documentation and set the desired limits in a configuration file.
-          Then, edit the API server pod specification file $apiserverconf
-          and set the below parameters.
-          --enable-admission-plugins=...,EventRateLimit,...
-          --admission-control-config-file=<path/to/configuration/file>
-        scored: false
-
-      - id: 1.2.10
-        text: "Ensure that the admission control plugin AlwaysAdmit is not set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: nothave
-                value: AlwaysAdmit
-            - flag: "--enable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and either remove the --enable-admission-plugins parameter, or set it to a
-          value that does not include AlwaysAdmit.
-        scored: true
-
-      - id: 1.2.11
-        text: "Ensure that the admission control plugin AlwaysPullImages is set (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "AlwaysPullImages"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to include
-          AlwaysPullImages.
-          --enable-admission-plugins=...,AlwaysPullImages,...
-        scored: false
-
-      - id: 1.2.12
-        text: "Ensure that the admission control plugin ServiceAccount is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "ServiceAccount"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Follow the documentation and create ServiceAccount objects as per your environment.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and ensure that the --disable-admission-plugins parameter is set to a
-          value that does not include ServiceAccount.
-        scored: true
-
-      - id: 1.2.13
-        text: "Ensure that the admission control plugin NamespaceLifecycle is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--disable-admission-plugins"
-              compare:
-                op: nothave
-                value: "NamespaceLifecycle"
-            - flag: "--disable-admission-plugins"
-              set: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --disable-admission-plugins parameter to
-          ensure it does not include NamespaceLifecycle.
-        scored: true
-
-      - id: 1.2.14
-        text: "Ensure that the admission control plugin NodeRestriction is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--enable-admission-plugins"
-              compare:
-                op: has
-                value: "NodeRestriction"
-        remediation: |
-          Follow the Kubernetes documentation and configure NodeRestriction plug-in on kubelets.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --enable-admission-plugins parameter to a
-          value that includes NodeRestriction.
-          --enable-admission-plugins=...,NodeRestriction,...
-        scored: true
-
-      - id: 1.2.15
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.2.16
-        text: "Ensure that the --audit-log-path argument is set (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-path"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-path parameter to a suitable path and
-          file where you would like audit logs to be written, for example,
-          --audit-log-path=/var/log/apiserver/audit.log
-        scored: true
-
-      - id: 1.2.17
-        text: "Ensure that the --audit-log-maxage argument is set to 30 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxage"
-              compare:
-                op: gte
-                value: 30
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxage parameter to 30
-          or as an appropriate number of days, for example,
-          --audit-log-maxage=30
-        scored: true
-
-      - id: 1.2.18
-        text: "Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxbackup"
-              compare:
-                op: gte
-                value: 10
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxbackup parameter to 10 or to an appropriate
-          value. For example,
-          --audit-log-maxbackup=10
-        scored: true
-
-      - id: 1.2.19
-        text: "Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--audit-log-maxsize"
-              compare:
-                op: gte
-                value: 100
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --audit-log-maxsize parameter to an appropriate size in MB.
-          For example, to set it as 100 MB, --audit-log-maxsize=100
-        scored: true
-
-      - id: 1.2.20
-        text: "Ensure that the --request-timeout argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        type: manual
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          and set the below parameter as appropriate and if needed.
-          For example, --request-timeout=300s
-        scored: false
-
-      - id: 1.2.21
-        text: "Ensure that the --service-account-lookup argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--service-account-lookup"
-              set: false
-            - flag: "--service-account-lookup"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the below parameter.
-          --service-account-lookup=true
-          Alternatively, you can delete the --service-account-lookup parameter from this file so
-          that the default takes effect.
-        scored: true
-
-      - id: 1.2.22
-        text: "Ensure that the --service-account-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-key-file"
-        remediation: |
-          Edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --service-account-key-file parameter
-          to the public key file for service accounts. For example,
-          --service-account-key-file=<filename>
-        scored: true
-
-      - id: 1.2.23
-        text: "Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--etcd-certfile"
-            - flag: "--etcd-keyfile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate and key file parameters.
-          --etcd-certfile=<path/to/client-certificate-file>
-          --etcd-keyfile=<path/to/client-key-file>
-        scored: true
-
-      - id: 1.2.24
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "--tls-cert-file"
-            - flag: "--tls-private-key-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the TLS certificate and private key file parameters.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-        scored: true
-
-      - id: 1.2.25
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--client-ca-file"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection on the apiserver.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the client certificate authority file.
-          --client-ca-file=<path/to/client-ca-file>
-        scored: true
-
-      - id: 1.2.26
-        text: "Ensure that the --etcd-cafile argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--etcd-cafile"
-        remediation: |
-          Follow the Kubernetes documentation and set up the TLS connection between the apiserver and etcd.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the etcd certificate authority file parameter.
-          --etcd-cafile=<path/to/ca-file>
-        scored: true
-
-      - id: 1.2.27
-        text: "Ensure that the --encryption-provider-config argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--encryption-provider-config"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          Then, edit the API server pod specification file $apiserverconf
-          on the control plane node and set the --encryption-provider-config parameter to the path of that file.
-          For example, --encryption-provider-config=</path/to/EncryptionConfig/File>
-        scored: false
-
-      - id: 1.2.28
-        text: "Ensure that encryption providers are appropriately configured (Manual)"
-        audit: |
-          ENCRYPTION_PROVIDER_CONFIG=$(ps -ef | grep $apiserverbin | grep -- --encryption-provider-config | sed 's%.*encryption-provider-config[= ]\([^ ]*\).*%\1%')
-          if test -e $ENCRYPTION_PROVIDER_CONFIG; then grep -A1 'providers:' $ENCRYPTION_PROVIDER_CONFIG | tail -n1 | grep -o "[A-Za-z]*" | sed 's/^/provider=/'; fi
-        tests:
-          test_items:
-            - flag: "provider"
-              compare:
-                op: valid_elements
-                value: "aescbc,kms,secretbox"
-        remediation: |
-          Follow the Kubernetes documentation and configure a EncryptionConfig file.
-          In this file, choose aescbc, kms or secretbox as the encryption provider.
-        scored: false
-
-      - id: 1.2.29
-        text: "Ensure that the API Server only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -ef | grep $apiserverbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--tls-cipher-suites"
-              compare:
-                op: valid_elements
-                value: "TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384"
-        remediation: |
-          Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml
-          on the control plane node and set the below parameter.
-          --tls-cipher-suites=TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
-          TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
-          TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
-          TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,
-          TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,
-          TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384
-        scored: false
-
-  - id: 1.3
-    text: "Controller Manager"
-    checks:
-      - id: 1.3.1
-        text: "Ensure that the --terminated-pod-gc-threshold argument is set as appropriate (Manual)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--terminated-pod-gc-threshold"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --terminated-pod-gc-threshold to an appropriate threshold,
-          for example, --terminated-pod-gc-threshold=10
-        scored: false
-
-      - id: 1.3.2
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.3.3
-        text: "Ensure that the --use-service-account-credentials argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--use-service-account-credentials"
-              compare:
-                op: noteq
-                value: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node to set the below parameter.
-          --use-service-account-credentials=true
-        scored: true
-
-      - id: 1.3.4
-        text: "Ensure that the --service-account-private-key-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--service-account-private-key-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --service-account-private-key-file parameter
-          to the private key file for service accounts.
-          --service-account-private-key-file=<filename>
-        scored: true
-
-      - id: 1.3.5
-        text: "Ensure that the --root-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--root-ca-file"
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --root-ca-file parameter to the certificate bundle file`.
-          --root-ca-file=<path/to/file>
-        scored: true
-
-      - id: 1.3.6
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--feature-gates"
-              compare:
-                op: nothave
-                value: "RotateKubeletServerCertificate=false"
-              set: true
-            - flag: "--feature-gates"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and set the --feature-gates parameter to include RotateKubeletServerCertificate=true.
-          --feature-gates=RotateKubeletServerCertificate=true
-        scored: true
-
-      - id: 1.3.7
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $controllermanagerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Controller Manager pod specification file $controllermanagerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true
-
-  - id: 1.4
-    text: "Scheduler"
-    checks:
-      - id: 1.4.1
-        text: "Ensure that the --profiling argument is set to false (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          test_items:
-            - flag: "--profiling"
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf file
-          on the control plane node and set the below parameter.
-          --profiling=false
-        scored: true
-
-      - id: 1.4.2
-        text: "Ensure that the --bind-address argument is set to 127.0.0.1 (Automated)"
-        audit: "/bin/ps -ef | grep $schedulerbin | grep -v grep"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--bind-address"
-              compare:
-                op: eq
-                value: "127.0.0.1"
-            - flag: "--bind-address"
-              set: false
-        remediation: |
-          Edit the Scheduler pod specification file $schedulerconf
-          on the control plane node and ensure the correct value for the --bind-address parameter
-        scored: true

cfg/cis-1.9/node.yaml

@@ -1,478 +0,0 @@
----
-controls:
-version: "cis-1.9"
-id: 4
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 4.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the kubelet service file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletsvc; then stat -c permissions=%a $kubeletsvc; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chmod 600 $kubeletsvc
-        scored: true
-
-      - id: 4.1.2
-        text: "Ensure that the kubelet service file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c "if test -e $kubeletsvc; then stat -c %U:%G $kubeletsvc; else echo \"File not found\"; fi"'
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-            - flag: "File not found"
-        remediation: |
-            Run the below command (based on the file location on your system) on the each worker node.
-            For example,
-            chown root:root $kubeletsvc
-        scored: true
-
-      - id: 4.1.3
-        text: "If proxy kubeconfig file exists ensure permissions are set to 600 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "permissions"
-              set: true
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $proxykubeconfig
-        scored: false
-
-      - id: 4.1.4
-        text: "If proxy kubeconfig file exists ensure ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi'' '
-        tests:
-          bin_op: or
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example, chown root:root $proxykubeconfig
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that the --kubeconfig kubelet.conf file permissions are set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 600 $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.6
-        text: "Ensure that the --kubeconfig kubelet.conf file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 4.1.7
-        text: "Ensure that the certificate authorities file permissions are set to 600 or more restrictive (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c permissions=%a $CAFILE; fi
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command to modify the file permissions of the
-          --client-ca-file chmod 600 <filename>
-        scored: false
-
-      - id: 4.1.8
-        text: "Ensure that the client certificate authorities file ownership is set to root:root (Manual)"
-        audit: |
-          CAFILE=$(ps -ef | grep kubelet | grep -v apiserver | grep -- --client-ca-file= | awk -F '--client-ca-file=' '{print $2}' | awk '{print $1}' | uniq)
-          if test -z $CAFILE; then CAFILE=$kubeletcafile; fi
-          if test -e $CAFILE; then stat -c %U:%G $CAFILE; fi
-        tests:
-          test_items:
-            - flag: root:root
-              compare:
-                op: eq
-                value: root:root
-        remediation: |
-          Run the following command to modify the ownership of the --client-ca-file.
-          chown root:root <filename>
-        scored: false
-
-      - id: 4.1.9
-        text: "If the kubelet config.yaml configuration file is being used validate permissions set to 600 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 600 $kubeletconf
-        scored: true
-
-      - id: 4.1.10
-        text: "If the kubelet config.yaml configuration file is being used validate file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: true
-
-  - id: 4.2
-    text: "Kubelet"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the --anonymous-auth argument is set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication: anonymous: enabled` to
-          `false`.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          `--anonymous-auth=false`
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authorization.mode` to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.3
-        text: "Ensure that the --client-ca-file argument is set as appropriate (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `authentication.x509.clientCAFile` to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.4
-        text: "Verify that the --read-only-port argument is set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              compare:
-                op: eq
-                value: 0
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set `readOnlyPort` to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `streamingConnectionIdleTimeout` to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `makeIPTablesUtilChains` to `true`.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.7
-        text: "Ensure that the --hostname-override argument is not set (Manual)"
-        # This is one of those properties that can only be set as a command line argument.
-        # To check if the property is set as expected, we need to parse the kubelet command
-        # instead reading the Kubelet Configuration file.
-        audit: "/bin/ps -fC $kubeletbin"
-        tests:
-          test_items:
-            - flag: --hostname-override
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and remove the --hostname-override argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.8
-        text: "Ensure that the eventRecordQPS argument is set to a level which ensures appropriate event capture (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              compare:
-                op: gte
-                value: 0
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set `eventRecordQPS` to an appropriate level.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.9
-        text: "Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cert-file
-              path: '{.tlsCertFile}'
-            - flag: --tls-private-key-file
-              path: '{.tlsPrivateKeyFile}'
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCertFile` to the location
-          of the certificate file to use to identify this Kubelet, and `tlsPrivateKeyFile`
-          to the location of the corresponding private key file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameters in KUBELET_CERTIFICATE_ARGS variable.
-          --tls-cert-file=<path/to/tls-certificate-file>
-          --tls-private-key-file=<path/to/tls-key-file>
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.10
-        text: "Ensure that the --rotate-certificates argument is not set to false (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to add the line `rotateCertificates` to `true` or
-          remove it altogether to use the default value.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS
-          variable.
-          Based on your system, restart the kubelet service. For example,
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 4.2.11
-        text: "Verify that the RotateKubeletServerCertificate argument is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              compare:
-                op: nothave
-                value: false
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.12
-        text: "Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --tls-cipher-suites
-              path: '{range .tlsCipherSuites[:]}{}{'',''}{end}'
-              compare:
-                op: valid_elements
-                value: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-        remediation: |
-          If using a Kubelet config file, edit the file to set `tlsCipherSuites` to
-          TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          or to a subset of these values.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the --tls-cipher-suites parameter as follows, or to a subset of these values.
-          --tls-cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 4.2.13
-        text: "Ensure that a limit is set on pod PIDs (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --pod-max-pids
-              path: '{.podPidsLimit}'
-        remediation: |
-          Decide on an appropriate level for this parameter and set it,
-          either via the --pod-max-pids command line parameter or the PodPidsLimit configuration file setting.
-        scored: false
-
-  - id: 4.3
-    text: "kube-proxy"
-    checks:
-      - id: 4.3.1
-        text: "Ensure that the kube-proxy metrics service is bound to localhost (Automated)"
-        audit: "/bin/ps -fC $proxybin"
-        audit_config: "/bin/sh -c 'if test -e $proxykubeconfig; then cat $proxykubeconfig; fi'"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--metrics-bind-address"
-              path: '{.metricsBindAddress}'
-              compare:
-                op: has
-                value: "127.0.0.1"
-            - flag: "--metrics-bind-address"
-              path: '{.metricsBindAddress}'
-              set: false
-        remediation: |
-           Modify or remove any values which bind the metrics service to a non-localhost address.
-           The default value is 127.0.0.1:10249.
-        scored: true

cfg/cis-1.9/policies.yaml

@@ -1,405 +0,0 @@
----
-controls:
-version: "cis-1.9"
-id: 5
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 5.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 5.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Automated)"
-        audit: |
-          kubectl get clusterrolebindings -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECT:.subjects[*].name --no-headers | while read -r role_name role_binding subject
-          do
-            if [[ "${role_name}" != "cluster-admin" && "${role_binding}" == "cluster-admin" ]]; then
-              is_compliant="false"
-            else
-              is_compliant="true"
-            fi;
-            echo "**role_name: ${role_name} role_binding: ${role_binding} subject: ${subject} is_compliant: ${is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role : kubectl delete clusterrolebinding [name]
-          Condition: is_compliant is false if rolename is not cluster-admin and rolebinding is cluster-admin.
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize access to secrets (Automated)"
-        audit: "echo \"canGetListWatchSecretsAsSystemAuthenticated: $(kubectl auth can-i get,list,watch secrets --all-namespaces --as=system:authenticated)\""
-        tests:
-          test_items:
-            - flag: "canGetListWatchSecretsAsSystemAuthenticated"
-              compare:
-                op: eq
-                value: no
-        remediation: |
-          Where possible, remove get, list and watch access to Secret objects in the cluster.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Automated)"
-        audit: |
-          # Check Roles
-          kubectl get roles --all-namespaces -o custom-columns=ROLE_NAMESPACE:.metadata.namespace,ROLE_NAME:.metadata.name --no-headers | while read -r role_namespace role_name
-          do
-            role_rules=$(kubectl get role -n "${role_namespace}" "${role_name}" -o=json | jq -c '.rules')
-            if echo "${role_rules}" | grep -q "\[\"\*\"\]"; then
-              role_is_compliant="false"
-            else
-              role_is_compliant="true"
-            fi;
-            echo "**role_name: ${role_name} role_namespace: ${role_namespace} role_rules: ${role_rules} role_is_compliant: ${role_is_compliant}"
-          done
-
-          # Check ClusterRoles
-          kubectl get clusterroles -o custom-columns=CLUSTERROLE_NAME:.metadata.name --no-headers | while read -r clusterrole_name
-          do
-            clusterrole_rules=$(kubectl get clusterrole "${clusterrole_name}" -o=json | jq -c '.rules')
-            if echo "${clusterrole_rules}" | grep -q "\[\"\*\"\]"; then
-              clusterrole_is_compliant="false"
-            else
-              clusterrole_is_compliant="true"
-            fi;
-          echo "**clusterrole_name: ${clusterrole_name} clusterrole_rules: ${clusterrole_rules} clusterrole_is_compliant: ${clusterrole_is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "role_is_compliant"
-              compare:
-                op: eq
-                value: true
-              set: true
-            - flag: "clusterrole_is_compliant"
-              compare:
-                op: eq
-                value: true
-              set: true
-        remediation: |
-          Where possible replace any use of wildcards ["*"] in roles and clusterroles with specific
-          objects or actions.
-          Condition: role_is_compliant is false if ["*"] is found in rules.
-          Condition: clusterrole_is_compliant is false if ["*"] is found in rules.
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize access to create pods (Automated)"
-        audit: |
-          echo "canCreatePodsAsSystemAuthenticated: $(kubectl auth can-i create pods --all-namespaces --as=system:authenticated)"
-        tests:
-          test_items:
-            - flag: "canCreatePodsAsSystemAuthenticated"
-              compare:
-                op: eq
-                value: no
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-      - id: 5.1.5
-        text: "Ensure that default service accounts are not actively used (Automated)"
-        audit: |
-          kubectl get serviceaccount --all-namespaces --field-selector metadata.name=default -o=json | jq -r '.items[] | " namespace: \(.metadata.namespace), kind: \(.kind), name: \(.metadata.name), automountServiceAccountToken: \(.automountServiceAccountToken | if . == null then "notset" else . end )"' | xargs -L 1
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "automountServiceAccountToken"
-              compare:
-                op: eq
-                value: false
-              set: true
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific access
-          to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          `automountServiceAccountToken: false`.
-        scored: false
-
-      - id: 5.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o custom-columns=POD_NAMESPACE:.metadata.namespace,POD_NAME:.metadata.name,POD_SERVICE_ACCOUNT:.spec.serviceAccount,POD_IS_AUTOMOUNTSERVICEACCOUNTTOKEN:.spec.automountServiceAccountToken --no-headers | while read -r pod_namespace pod_name pod_service_account pod_is_automountserviceaccounttoken
-          do
-            # Retrieve automountServiceAccountToken's value for ServiceAccount and Pod, set to notset if null or <none>.
-            svacc_is_automountserviceaccounttoken=$(kubectl get serviceaccount -n "${pod_namespace}" "${pod_service_account}" -o json | jq -r '.automountServiceAccountToken' | sed -e 's/<none>/notset/g' -e 's/null/notset/g')
-            pod_is_automountserviceaccounttoken=$(echo "${pod_is_automountserviceaccounttoken}" | sed -e 's/<none>/notset/g' -e 's/null/notset/g')
-            if [ "${svacc_is_automountserviceaccounttoken}" = "false" ] && ( [ "${pod_is_automountserviceaccounttoken}" = "false" ] || [ "${pod_is_automountserviceaccounttoken}" = "notset" ] ); then
-              is_compliant="true"
-            elif [ "${svacc_is_automountserviceaccounttoken}" = "true" ] && [ "${pod_is_automountserviceaccounttoken}" = "false" ]; then
-              is_compliant="true"
-            else
-              is_compliant="false"
-            fi
-            echo "**namespace: ${pod_namespace} pod_name: ${pod_name} service_account: ${pod_service_account} pod_is_automountserviceaccounttoken: ${pod_is_automountserviceaccounttoken} svacc_is_automountServiceAccountToken: ${svacc_is_automountserviceaccounttoken} is_compliant: ${is_compliant}"
-          done
-        use_multiple_values: true
-        tests:
-          test_items:
-            - flag: "is_compliant"
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Modify the definition of ServiceAccounts and Pods which do not need to mount service
-          account tokens to disable it, with `automountServiceAccountToken: false`.
-          If both the ServiceAccount and the Pod's .spec specify a value for automountServiceAccountToken, the Pod spec takes precedence.
-          Condition: Pod is_compliant to true when
-            - ServiceAccount is automountServiceAccountToken: false and Pod is automountServiceAccountToken: false or notset
-            - ServiceAccount is automountServiceAccountToken: true notset and Pod is automountServiceAccountToken: false
-        scored: false
-
-      - id: 5.1.7
-        text: "Avoid use of system:masters group (Manual)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 5.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-      - id: 5.1.9
-        text: "Minimize access to create persistent volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to PersistentVolume objects in the cluster.
-        scored: false
-
-      - id: 5.1.10
-        text: "Minimize access to the proxy sub-resource of nodes (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the proxy sub-resource of node objects.
-        scored: false
-
-      - id: 5.1.11
-        text: "Minimize access to the approval sub-resource of certificatesigningrequests objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the approval sub-resource of certificatesigningrequest objects.
-        scored: false
-
-      - id: 5.1.12
-        text: "Minimize access to webhook configuration objects (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the validatingwebhookconfigurations or mutatingwebhookconfigurations objects
-        scored: false
-
-      - id: 5.1.13
-        text: "Minimize access to the service account token creation (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove access to the token sub-resource of serviceaccount objects.
-        scored: false
-
-  - id: 5.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 5.2.1
-        text: "Ensure that the cluster has at least one active policy control mechanism in place (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that either Pod Security Admission or an external policy control system is in place
-          for every namespace which contains user workloads.
-        scored: false
-
-      - id: 5.2.2
-        text: "Minimize the admission of privileged containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of privileged containers.
-        scored: false
-
-      - id: 5.2.3
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostPID` containers.
-        scored: false
-
-      - id: 5.2.4
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostIPC` containers.
-        scored: false
-
-      - id: 5.2.5
-        text: "Minimize the admission of containers wishing to share the host network namespace (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of `hostNetwork` containers.
-        scored: false
-
-      - id: 5.2.6
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `.spec.allowPrivilegeEscalation` set to `true`.
-        scored: false
-
-      - id: 5.2.7
-        text: "Minimize the admission of root containers (Manual)"
-        type: "manual"
-        remediation: |
-          Create a policy for each namespace in the cluster, ensuring that either `MustRunAsNonRoot`
-          or `MustRunAs` with the range of UIDs not including 0, is set.
-        scored: false
-
-      - id: 5.2.8
-        text: "Minimize the admission of containers with the NET_RAW capability (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with the `NET_RAW` capability.
-        scored: false
-
-      - id: 5.2.9
-        text: "Minimize the admission of containers with added capabilities (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that `allowedCapabilities` is not present in policies for the cluster unless
-          it is set to an empty array.
-        scored: false
-
-      - id: 5.2.10
-        text: "Minimize the admission of containers with capabilities assigned (Manual)"
-        type: "manual"
-        remediation: |
-          Review the use of capabilites in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
-          a PSP which forbids the admission of containers which do not drop all capabilities.
-        scored: false
-
-      - id: 5.2.11
-        text: "Minimize the admission of Windows HostProcess containers (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers that have `.securityContext.windowsOptions.hostProcess` set to `true`.
-        scored: false
-
-      - id: 5.2.12
-        text: "Minimize the admission of HostPath volumes (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with `hostPath` volumes.
-        scored: false
-
-      - id: 5.2.13
-        text: "Minimize the admission of containers which use HostPorts (Manual)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers which use `hostPort` sections.
-        scored: false
-
-  - id: 5.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 5.3.1
-        text: "Ensure that the CNI in use supports NetworkPolicies (Manual)"
-        type: "manual"
-        remediation: |
-          If the CNI plugin in use does not support network policies, consideration should be given to
-          making use of a different plugin, or finding an alternate mechanism for restricting traffic
-          in the Kubernetes cluster.
-        scored: false
-
-      - id: 5.3.2
-        text: "Ensure that all Namespaces have NetworkPolicies defined (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 5.4
-    text: "Secrets Management"
-    checks:
-      - id: 5.4.1
-        text: "Prefer using Secrets as files over Secrets as environment variables (Manual)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read Secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 5.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the Secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 5.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 5.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-        scored: false
-
-  - id: 5.7
-    text: "General Policies"
-    checks:
-      - id: 5.7.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 5.7.2
-        text: "Ensure that the seccomp profile is set to docker/default in your Pod definitions (Manual)"
-        type: "manual"
-        remediation: |
-          Use `securityContext` to enable the docker/default seccomp profile in your pod definitions.
-          An example is as below:
-            securityContext:
-              seccompProfile:
-                type: RuntimeDefault
-        scored: false
-
-      - id: 5.7.3
-        text: "Apply SecurityContext to your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply SecurityContexts to your Pods. For a
-          suggested list of SecurityContexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 5.7.4
-        text: "The default namespace should not be used (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/config.yaml

@@ -36,7 +36,6 @@ master:
       - /var/snap/microk8s/current/args/kube-apiserver
       - /etc/origin/master/master-config.yaml
       - /etc/kubernetes/manifests/talos-kube-apiserver.yaml
-      - /var/lib/rancher/rke2/agent/pod-manifests/kube-apiserver.yaml
     defaultconf: /etc/kubernetes/manifests/kube-apiserver.yaml
 
   scheduler:
@@ -54,13 +53,11 @@ master:
       - /var/snap/microk8s/current/args/kube-scheduler
       - /etc/origin/master/scheduler.json
       - /etc/kubernetes/manifests/talos-kube-scheduler.yaml
-      - /var/lib/rancher/rke2/agent/pod-manifests/kube-scheduler.yaml
     defaultconf: /etc/kubernetes/manifests/kube-scheduler.yaml
     kubeconfig:
       - /etc/kubernetes/scheduler.conf
       - /var/lib/kube-scheduler/kubeconfig
       - /var/lib/kube-scheduler/config.yaml
-      - /var/lib/rancher/rke2/server/cred/scheduler.kubeconfig
       - /system/secrets/kubernetes/kube-scheduler/kubeconfig
     defaultkubeconfig: /etc/kubernetes/scheduler.conf
 
@@ -80,12 +77,10 @@ master:
       - /var/snap/kube-controller-manager/current/args
       - /var/snap/microk8s/current/args/kube-controller-manager
       - /etc/kubernetes/manifests/talos-kube-controller-manager.yaml
-      - /var/lib/rancher/rke2/agent/pod-manifests/kube-controller-manager.yaml
     defaultconf: /etc/kubernetes/manifests/kube-controller-manager.yaml
     kubeconfig:
       - /etc/kubernetes/controller-manager.conf
       - /var/lib/kube-controller-manager/kubeconfig
-      - /var/lib/rancher/rke2/server/cred/controller.kubeconfig
       - /system/secrets/kubernetes/kube-controller-manager/kubeconfig
     defaultkubeconfig: /etc/kubernetes/controller-manager.conf
 
@@ -97,7 +92,6 @@ master:
     datadirs:
       - /var/lib/etcd/default.etcd
       - /var/lib/etcd/data.etcd
-      - /var/lib/rancher/k3s/server/db/etcd
     confs:
       - /etc/kubernetes/manifests/etcd.yaml
       - /etc/kubernetes/manifests/etcd.yml
@@ -107,8 +101,6 @@ master:
       - /var/snap/etcd/common/etcd.conf.yaml
       - /var/snap/microk8s/current/args/etcd
       - /usr/lib/systemd/system/etcd.service
-      - /var/lib/rancher/rke2/server/db/etcd/config
-      - /var/lib/rancher/k3s/server/db/etcd/config
     defaultconf: /etc/kubernetes/manifests/etcd.yaml
     defaultdatadir: /var/lib/etcd/default.etcd
 
@@ -140,9 +132,6 @@ node:
       - "/etc/kubernetes/certs/ca.crt"
       - "/etc/kubernetes/cert/ca.pem"
       - "/var/snap/microk8s/current/certs/ca.crt"
-      - "/var/lib/rancher/rke2/agent/server.crt"
-      - "/var/lib/rancher/rke2/agent/client-ca.crt"
-      - "/var/lib/rancher/k3s/agent/client-ca.crt"
     svc:
       # These paths must also be included
       #  in the 'confs' property below
@@ -162,17 +151,13 @@ node:
       - "/var/lib/kubelet/kubeconfig"
       - "/etc/kubernetes/kubelet-kubeconfig"
       - "/etc/kubernetes/kubelet/kubeconfig"
-      - "/etc/kubernetes/ssl/kubecfg-kube-node.yaml"
       - "/var/snap/microk8s/current/credentials/kubelet.config"
       - "/etc/kubernetes/kubeconfig-kubelet"
-      - "/var/lib/rancher/rke2/agent/kubelet.kubeconfig"
-      - "/var/lib/rancher/k3s/agent/kubelet.kubeconfig"
     confs:
       - "/etc/kubernetes/kubelet-config.yaml"
       - "/var/lib/kubelet/config.yaml"
       - "/var/lib/kubelet/config.yml"
       - "/etc/kubernetes/kubelet/kubelet-config.json"
-      - "/etc/kubernetes/kubelet/config.json"
       - "/etc/kubernetes/kubelet/config"
       - "/home/kubernetes/kubelet-config.yaml"
       - "/home/kubernetes/kubelet-config.yml"
@@ -192,7 +177,6 @@ node:
       - "/etc/systemd/system/snap.kubelet.daemon.service"
       - "/etc/systemd/system/snap.microk8s.daemon-kubelet.service"
       - "/etc/kubernetes/kubelet.yaml"
-
     defaultconf: "/var/lib/kubelet/config.yaml"
     defaultsvc: "/etc/systemd/system/kubelet.service.d/10-kubeadm.conf"
     defaultkubeconfig: "/etc/kubernetes/kubelet.conf"
@@ -216,11 +200,8 @@ node:
       - "/etc/kubernetes/kubelet-kubeconfig"
       - "/etc/kubernetes/kubelet-kubeconfig.conf"
       - "/etc/kubernetes/kubelet/config"
-      - "/etc/kubernetes/ssl/kubecfg-kube-proxy.yaml"
       - "/var/lib/kubelet/kubeconfig"
       - "/var/snap/microk8s/current/credentials/proxy.config"
-      - "/var/lib/rancher/rke2/agent/kubeproxy.kubeconfig"
-      - "/var/lib/rancher/k3s/agent/kubeproxy.kubeconfig"
     svc:
       - "/lib/systemd/system/kube-proxy.service"
       - "/etc/systemd/system/snap.microk8s.daemon-proxy.service"
@@ -237,7 +218,6 @@ etcd:
     datadirs:
       - /var/lib/etcd/default.etcd
       - /var/lib/etcd/data.etcd
-      - /var/lib/rancher/k3s/server/db/etcd
     confs:
       - /etc/kubernetes/manifests/etcd.yaml
       - /etc/kubernetes/manifests/etcd.yml
@@ -247,8 +227,6 @@ etcd:
       - /var/snap/etcd/common/etcd.conf.yaml
       - /var/snap/microk8s/current/args/etcd
       - /usr/lib/systemd/system/etcd.service
-      - /var/lib/rancher/rke2/agent/pod-manifests/etcd.yaml
-      - /var/lib/rancher/k3s/server/db/etcd/config
     defaultconf: /etc/kubernetes/manifests/etcd.yaml
     defaultdatadir: /var/lib/etcd/default.etcd
 
@@ -280,43 +258,16 @@ version_mapping:
   "1.22": "cis-1.23"
   "1.23": "cis-1.23"
   "1.24": "cis-1.24"
-  "1.25": "cis-1.7"
-  "1.26": "cis-1.8"
-  "1.27": "cis-1.9"
-  "1.28": "cis-1.10"
-  "1.29": "cis-1.11"
-  "1.30": "cis-1.11"
-  "1.31": "cis-1.11"
-  "1.32": "cis-1.11"
   "eks-1.0.1": "eks-1.0.1"
   "eks-1.1.0": "eks-1.1.0"
-  "eks-1.2.0": "eks-1.2.0"
-  "eks-1.5.0": "eks-1.5.0"
   "gke-1.0": "gke-1.0"
   "gke-1.2.0": "gke-1.2.0"
-  "gke-1.6.0": "gke-1.6.0"
-  "gke-1.8.0": "gke-1.8.0"
   "ocp-3.10": "rh-0.7"
   "ocp-3.11": "rh-0.7"
   "ocp-4.0": "rh-1.0"
-  "ocp-4.11": "rh-1.4"
-  "ocp-4.13": "rh-1.8"
   "aks-1.0": "aks-1.0"
-  "aks-1.7": "aks-1.7"
   "ack-1.0": "ack-1.0"
   "cis-1.6-k3s": "cis-1.6-k3s"
-  "cis-1.24-microk8s": "cis-1.24-microk8s"
-  "tkgi-1.2.53": "tkgi-1.2.53"
-  "k3s-cis-1.7": "k3s-cis-1.7"
-  "k3s-cis-1.23": "k3s-cis-1.23"
-  "k3s-cis-1.24": "k3s-cis-1.24"
-  "rke-cis-1.7": "rke-cis-1.7"
-  "rke-cis-1.23": "rke-cis-1.23"
-  "rke-cis-1.24": "rke-cis-1.24"
-  "rke2-cis-1.7": "rke2-cis-1.7"
-  "rke2-cis-1.8": "rke2-cis-1.8"
-  "rke2-cis-1.23": "rke2-cis-1.23"
-  "rke2-cis-1.24": "rke2-cis-1.24"
 
 target_mapping:
   "cis-1.5":
@@ -355,42 +306,6 @@ target_mapping:
     - "controlplane"
     - "etcd"
     - "policies"
-  "cis-1.24-microk8s":
-    - "master"
-    - "etcd"
-    - "node"
-    - "controlplane"
-    - "policies"
-  "cis-1.7":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "etcd"
-    - "policies"
-  "cis-1.8":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "etcd"
-    - "policies"
-  "cis-1.9":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "etcd"
-    - "policies"
-  "cis-1.10":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "etcd"
-    - "policies"
-  "cis-1.11":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "etcd"
-    - "policies"
   "gke-1.0":
     - "master"
     - "node"
@@ -404,18 +319,6 @@ target_mapping:
     - "controlplane"
     - "policies"
     - "managedservices"
-  "gke-1.6.0":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "managedservices"
-  "gke-1.8.0":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "managedservices"
   "eks-1.0.1":
     - "master"
     - "node"
@@ -428,24 +331,6 @@ target_mapping:
     - "controlplane"
     - "policies"
     - "managedservices"
-  "eks-1.2.0":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "managedservices"
-  "eks-1.5.0":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "managedservices"
-  "eks-1.7.0":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "managedservices"
   "rh-0.7":
     - "master"
     - "node"
@@ -455,12 +340,6 @@ target_mapping:
     - "controlplane"
     - "policies"
     - "managedservices"
-  "aks-1.7":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "managedservices"
   "ack-1.0":
     - "master"
     - "node"
@@ -474,92 +353,8 @@ target_mapping:
     - "controlplane"
     - "policies"
     - "etcd"
-  "rh-1.4":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "etcd"
-  "rh-1.8":
-    - "master"
-    - "node"
-    - "controlplane"
-    - "policies"
-    - "etcd"
   "eks-stig-kubernetes-v1r6":
     - "node"
     - "controlplane"
     - "policies"
     - "managedservices"
-  "tkgi-1.2.53":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "k3s-cis-1.7":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "k3s-cis-1.8":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "k3s-cis-1.23":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "k3s-cis-1.24":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "rke-cis-1.7":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "rke-cis-1.23":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "rke-cis-1.24":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "rke2-cis-1.7":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "rke2-cis-1.8":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "rke2-cis-1.23":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"
-  "rke2-cis-1.24":
-    - "master"
-    - "etcd"
-    - "controlplane"
-    - "node"
-    - "policies"

cfg/eks-1.2.0/config.yaml

@@ -1,9 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml
-## These settings are required if you are using the --asff option to report findings to AWS Security Hub
-## AWS account number is required.
-AWS_ACCOUNT: "<AWS_ACCT_NUMBER>"
-## AWS region is required.
-AWS_REGION: "<AWS_REGION>"
-## EKS Cluster ARN is required.
-CLUSTER_ARN: "<AWS_CLUSTER_ARN>"

cfg/eks-1.2.0/controlplane.yaml

@@ -1,14 +0,0 @@
----
-controls:
-version: "eks-1.2.0"
-id: 2
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 2.1
-    text: "Logging"
-    checks:
-      - id: 2.1.1
-        text: "Enable audit logs (Manual)"
-        remediation: "Enable control plane logging for API Server, Audit, Authenticator, Controller Manager, and Scheduler."
-        scored: false

cfg/eks-1.2.0/managedservices.yaml

@@ -1,154 +0,0 @@
----
-controls:
-version: "eks-1.2.0"
-id: 5
-text: "Managed Services"
-type: "managedservices"
-groups:
-  - id: 5.1
-    text: "Image Registry and Image Scanning"
-    checks:
-      - id: 5.1.1
-        text: "Ensure Image Vulnerability Scanning using Amazon ECR image scanning or a third-party provider (Manual)"
-        type: "manual"
-        remediation: |
-          To utilize AWS ECR for Image scanning please follow the steps below:
-
-          To create a repository configured for scan on push (AWS CLI):
-          aws ecr create-repository --repository-name $REPO_NAME --image-scanning-configuration scanOnPush=true --region $REGION_CODE
-
-          To edit the settings of an existing repository (AWS CLI):
-          aws ecr put-image-scanning-configuration --repository-name $REPO_NAME --image-scanning-configuration scanOnPush=true --region $REGION_CODE
-
-          Use the following steps to start a manual image scan using the AWS Management Console.
-              Open the Amazon ECR console at https://console.aws.amazon.com/ecr/repositories.
-              From the navigation bar, choose the Region to create your repository in.
-              In the navigation pane, choose Repositories.
-              On the Repositories page, choose the repository that contains the image to scan.
-              On the Images page, select the image to scan and then choose Scan.
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize user access to Amazon ECR (Manual)"
-        type: "manual"
-        remediation: |
-          Before you use IAM to manage access to Amazon ECR, you should understand what IAM features
-          are available to use with Amazon ECR. To get a high-level view of how Amazon ECR and other
-          AWS services work with IAM, see AWS Services That Work with IAM in the IAM User Guide.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize cluster access to read-only for Amazon ECR (Manual)"
-        type: "manual"
-        remediation: |
-          You can use your Amazon ECR images with Amazon EKS, but you need to satisfy the following prerequisites.
-
-          The Amazon EKS worker node IAM role (NodeInstanceRole) that you use with your worker nodes must possess
-          the following IAM policy permissions for Amazon ECR.
-
-          {
-              "Version": "2012-10-17",
-              "Statement": [
-                  {
-                      "Effect": "Allow",
-                      "Action": [
-                          "ecr:BatchCheckLayerAvailability",
-                          "ecr:BatchGetImage",
-                          "ecr:GetDownloadUrlForLayer",
-                          "ecr:GetAuthorizationToken"
-                      ],
-                      "Resource": "*"
-                  }
-              ]
-          }
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize Container Registries to only those approved (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-  - id: 5.2
-    text: "Identity and Access Management (IAM)"
-    checks:
-      - id: 5.2.1
-        text: "Prefer using dedicated Amazon EKS Service Accounts (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-  - id: 5.3
-    text: "AWS Key Management Service (KMS)"
-    checks:
-      - id: 5.3.1
-        text: "Ensure Kubernetes Secrets are encrypted using Customer Master Keys (CMKs) managed in AWS KMS (Manual)"
-        type: "manual"
-        remediation: |
-          This process can only be performed during Cluster Creation.
-
-          Enable 'Secrets Encryption' during Amazon EKS cluster creation as described
-          in the links within the 'References' section.
-        scored: false
-
-  - id: 5.4
-    text: "Cluster Networking"
-    checks:
-      - id: 5.4.1
-        text: "Restrict Access to the Control Plane Endpoint (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-      - id: 5.4.2
-        text: "Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-      - id: 5.4.3
-        text: "Ensure clusters are created with Private Nodes (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-      - id: 5.4.4
-        text: "Ensure Network Policy is Enabled and set as appropriate (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-      - id: 5.4.5
-        text: "Encrypt traffic to HTTPS load balancers with TLS certificates (Manual)"
-        type: "manual"
-        remediation: "No remediation"
-        scored: false
-
-
-  - id: 5.5
-    text: "Authentication and Authorization"
-    checks:
-      - id: 5.5.1
-        text: "Manage Kubernetes RBAC users with AWS IAM Authenticator for Kubernetes (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the 'Managing users or IAM roles for your cluster' in Amazon EKS documentation.
-        scored: false
-
-
-  - id: 5.6
-    text: "Other Cluster Configurations"
-    checks:
-      - id: 5.6.1
-        text: "Consider Fargate for running untrusted workloads (Manual)"
-        type: "manual"
-        remediation: |
-          Create a Fargate profile for your cluster Before you can schedule pods running on Fargate
-          in your cluster, you must define a Fargate profile that specifies which pods should use
-          Fargate when they are launched. For more information, see AWS Fargate profile.
-
-          Note: If you created your cluster with eksctl using the --fargate option, then a Fargate profile has
-          already been created for your cluster with selectors for all pods in the kube-system
-          and default namespaces. Use the following procedure to create Fargate profiles for
-          any other namespaces you would like to use with Fargate.
-        scored: false

cfg/eks-1.2.0/master.yaml

@@ -1,6 +0,0 @@
----
-controls:
-version: "eks-1.2.0"
-id: 1
-text: "Control Plane Components"
-type: "master"

cfg/eks-1.2.0/node.yaml

@@ -1,330 +0,0 @@
----
-controls:
-version: "eks-1.2.0"
-id: 3
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 3.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 3.1.1
-        text: "Ensure that the kubeconfig file permissions are set to 644 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 644 $kubeletkubeconfig
-        scored: false
-
-      - id: 3.1.2
-        text: "Ensure that the kubelet kubeconfig file ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: false
-
-      - id: 3.1.3
-        text: "Ensure that the kubelet configuration file has permissions set to 644 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 644 $kubeletconf
-        scored: false
-
-      - id: 3.1.4
-        text: "Ensure that the kubelet configuration file ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: false
-
-  - id: 3.2
-    text: "Kubelet"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that the Anonymous Auth is Not Enabled (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              set: true
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          If using a Kubelet config file, edit the file to set authentication: anonymous: enabled to
-          false.
-          If using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --anonymous-auth=false
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              set: true
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          If using a Kubelet config file, edit the file to set authorization: mode to Webhook. If
-          using executable arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --authorization-mode=Webhook
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.3
-        text: "Ensure that a Client CA File is Configured (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-              set: true
-        remediation: |
-          If using a Kubelet config file, edit the file to set authentication: x509: clientCAFile to
-          the location of the client CA file.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_AUTHZ_ARGS variable.
-          --client-ca-file=<path/to/client-ca-file>
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 3.2.4
-        text: "Ensure that the --read-only-port is disabled (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: true
-              compare:
-                op: eq
-                value: 0
-        remediation: |
-          If using a Kubelet config file, edit the file to set readOnlyPort to 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --read-only-port=0
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 3.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: true
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set streamingConnectionIdleTimeout to a
-          value other than 0.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --streaming-connection-idle-timeout=5m
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.6
-        text: "Ensure that the --protect-kernel-defaults argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --protect-kernel-defaults
-              path: '{.protectKernelDefaults}'
-              set: true
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          If using a Kubelet config file, edit the file to set protectKernelDefaults: true.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          --protect-kernel-defaults=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.7
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated) "
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: true
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set makeIPTablesUtilChains: true.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove the --make-iptables-util-chains argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.8
-        text: "Ensure that the --hostname-override argument is not set (Manual)"
-        # This is one of those properties that can only be set as a command line argument.
-        # To check if the property is set as expected, we need to parse the kubelet command
-        # instead reading the Kubelet Configuration file.
-        audit: "/bin/ps -fC $kubeletbin "
-        tests:
-          test_items:
-            - flag: --hostname-override
-              set: false
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and remove the --hostname-override argument from the
-          KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 3.2.9
-        text: "Ensure that the --eventRecordQPS argument is set to 0 or a level which ensures appropriate event capture (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: true
-              compare:
-                op: gte
-                value: 0
-        remediation: |
-          If using a Kubelet config file, edit the file to set eventRecordQPS: to an appropriate level.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 3.2.10
-        text: "Ensure that the --rotate-certificates argument is not present or is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: true
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to add the line rotateCertificates: true or
-          remove it altogether to use the default value.
-          If using command line arguments, edit the kubelet service file
-          $kubeletsvc on each worker node and
-          remove --rotate-certificates=false argument from the KUBELET_CERTIFICATE_ARGS
-          variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-
-      - id: 3.2.11
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Manual)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: true
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Edit the kubelet service file $kubeletsvc
-          on each worker node and set the below parameter in KUBELET_CERTIFICATE_ARGS variable.
-          --feature-gates=RotateKubeletServerCertificate=true
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: false
-  - id: 3.3
-    text: "Container Optimized OS"
-    checks:
-      - id: 3.3.1
-        text: "Prefer using a container-optimized OS when possible (Manual)"
-        remediation: "No remediation"
-        scored: false

cfg/eks-1.2.0/policies.yaml

@@ -1,213 +0,0 @@
----
-controls:
-version: "eks-1.2.0"
-id: 4
-text: "Policies"
-type: "policies"
-groups:
-  - id: 4.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Manual)"
-        type: "manual"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role :
-          kubectl delete clusterrolebinding [name]
-        scored: false
-
-      - id: 4.1.2
-        text: "Minimize access to secrets (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove get, list and watch access to secret objects in the cluster.
-        scored: false
-
-      - id: 4.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: false
-
-      - id: 4.1.4
-        text: "Minimize access to create pods (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that default service accounts are not actively used. (Manual)"
-        type: "manual"
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific access
-          to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          automountServiceAccountToken: false
-        scored: false
-
-      - id: 4.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Manual)"
-        type: "manual"
-        remediation: |
-          Modify the definition of pods and service accounts which do not need to mount service
-          account tokens to disable it.
-        scored: false
-
-      - id: 4.1.7
-        text: "Avoid use of system:masters group (Manual)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 4.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-  - id: 4.2
-    text: "Pod Security Policies"
-    checks:
-      - id: 4.2.1
-        text: "Minimize the admission of privileged containers (Automated)"
-        type: "manual"
-        remediation: |
-          Create a PSP as described in the Kubernetes documentation, ensuring that
-          the .spec.privileged field is omitted or set to false.
-        scored: false
-
-      - id: 4.2.2
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Create a PSP as described in the Kubernetes documentation, ensuring that the
-          .spec.hostPID field is omitted or set to false.
-        scored: false
-
-      - id: 4.2.3
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Create a PSP as described in the Kubernetes documentation, ensuring that the
-          .spec.hostIPC field is omitted or set to false.
-        scored: false
-
-      - id: 4.2.4
-        text: "Minimize the admission of containers wishing to share the host network namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Create a PSP as described in the Kubernetes documentation, ensuring that the
-          .spec.hostNetwork field is omitted or set to false.
-        scored: false
-
-      - id: 4.2.5
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Automated)"
-        type: "manual"
-        remediation: |
-          Create a PSP as described in the Kubernetes documentation, ensuring that the
-          .spec.allowPrivilegeEscalation field is omitted or set to false.
-        scored: false
-
-      - id: 4.2.6
-        text: "Minimize the admission of root containers (Automated)"
-        type: "manual"
-        remediation: |
-          Create a PSP as described in the Kubernetes documentation, ensuring that the
-          .spec.runAsUser.rule is set to either MustRunAsNonRoot or MustRunAs with the range of
-          UIDs not including 0.
-        scored: false
-
-      - id: 4.2.7
-        text: "Minimize the admission of containers with added capabilities (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that allowedCapabilities is not present in PSPs for the cluster unless
-          it is set to an empty array.
-        scored: false
-
-      - id: 4.2.8
-        text: "Minimize the admission of containers with capabilities assigned (Manual)"
-        type: "manual"
-        remediation: |
-          Review the use of capabilities in applications running on your cluster. Where a namespace
-          contains applications which do not require any Linux capabities to operate consider adding
-          a PSP which forbids the admission of containers which do not drop all capabilities.
-        scored: false
-
-  - id: 4.3
-    text: "CNI Plugin"
-    checks:
-      - id: 4.3.1
-        text: "Ensure CNI plugin supports network policies (Manual)"
-        type: "manual"
-        remediation: |
-          As with RBAC policies, network policies should adhere to the policy of least privileged
-          access. Start by creating a deny all policy that restricts all inbound and outbound traffic
-          from a namespace or create a global policy using Calico.
-        scored: false
-
-      - id: 4.3.2
-        text: "Ensure that all Namespaces have Network Policies defined (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 4.4
-    text: "Secrets Management"
-    checks:
-      - id: 4.4.1
-        text: "Prefer using secrets as files over secrets as environment variables (Manual)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 4.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 4.5
-    text: "Extensible Admission Control"
-    checks: []
-
-  - id: 4.6
-    text: "General Policies"
-    checks:
-      - id: 4.6.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 4.6.2
-        text: "Apply Security Context to Your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply security contexts to your pods. For a
-          suggested list of security contexts, you may refer to the CIS Security Benchmark for Docker
-          Containers.
-        scored: false
-
-      - id: 4.6.3
-        text: "The default namespace should not be used (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/eks-1.5.0/config.yaml

@@ -1,9 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml
-## These settings are required if you are using the --asff option to report findings to AWS Security Hub
-## AWS account number is required.
-AWS_ACCOUNT: "<AWS_ACCT_NUMBER>"
-## AWS region is required.
-AWS_REGION: "<AWS_REGION>"
-## EKS Cluster ARN is required.
-CLUSTER_ARN: "<AWS_CLUSTER_ARN>"

cfg/eks-1.5.0/controlplane.yaml

@@ -1,32 +0,0 @@
----
-controls:
-version: "eks-1.5.0"
-id: 2
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 2.1
-    text: "Logging"
-    checks:
-      - id: 2.1.1
-        text: "Enable audit Logs (Automated)"
-        remediation: |
-          From Console:
-          1.  For each EKS Cluster in each region;
-          2.  Go to 'Amazon EKS' > 'Clusters' > '' > 'Configuration' > 'Logging'.
-          3.  Click 'Manage logging'.
-          4.  Ensure that all options are toggled to 'Enabled'.
-                API server: Enabled
-                Audit: Enabled
-                Authenticator: Enabled
-                Controller manager: Enabled
-                Scheduler: Enabled
-          5.  Click 'Save Changes'.
-
-          From CLI:
-          # For each EKS Cluster in each region;
-          aws eks update-cluster-config \
-            --region '${REGION_CODE}' \
-            --name '${CLUSTER_NAME}' \
-            --logging '{"clusterLogging":[{"types":["api","audit","authenticator","controllerManager","scheduler"],"enabled":true}]}'
-        scored: false

cfg/eks-1.5.0/managedservices.yaml

@@ -1,227 +0,0 @@
----
-controls:
-version: "eks-1.5.0"
-id: 5
-text: "Managed Services"
-type: "managedservices"
-groups:
-  - id: 5.1
-    text: "Image Registry and Image Scanning"
-    checks:
-      - id: 5.1.1
-        text: "Ensure Image Vulnerability Scanning using Amazon ECR image scanning or a third party provider (Automated)"
-        type: "manual"
-        remediation: |
-          To utilize AWS ECR for Image scanning please follow the steps below:
-
-          To create a repository configured for scan on push (AWS CLI):
-          aws ecr create-repository --repository-name $REPO_NAME --image-scanning-configuration scanOnPush=true --region $REGION_CODE
-
-          To edit the settings of an existing repository (AWS CLI):
-          aws ecr put-image-scanning-configuration --repository-name $REPO_NAME --image-scanning-configuration scanOnPush=true --region $REGION_CODE
-
-          Use the following steps to start a manual image scan using the AWS Management Console.
-
-          1.  Open the Amazon ECR console at https://console.aws.amazon.com/ecr/repositories.
-          2.  From the navigation bar, choose the Region to create your repository in.
-          3.  In the navigation pane, choose Repositories.
-          4.  On the Repositories page, choose the repository that contains the image to scan.
-          5.  On the Images page, select the image to scan and then choose Scan.
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize user access to Amazon ECR (Manual)"
-        type: "manual"
-        remediation: |
-          Before you use IAM to manage access to Amazon ECR, you should understand what IAM features
-          are available to use with Amazon ECR. To get a high-level view of how Amazon ECR and other
-          AWS services work with IAM, see AWS Services That Work with IAM in the IAM User Guide.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize cluster access to read-only for Amazon ECR (Manual)"
-        type: "manual"
-        remediation: |
-          You can use your Amazon ECR images with Amazon EKS, but you need to satisfy the following prerequisites.
-
-          The Amazon EKS worker node IAM role (NodeInstanceRole) that you use with your worker nodes must possess
-          the following IAM policy permissions for Amazon ECR.
-
-          {
-              "Version": "2012-10-17",
-              "Statement": [
-                  {
-                      "Effect": "Allow",
-                      "Action": [
-                          "ecr:BatchCheckLayerAvailability",
-                          "ecr:BatchGetImage",
-                          "ecr:GetDownloadUrlForLayer",
-                          "ecr:GetAuthorizationToken"
-                      ],
-                      "Resource": "*"
-                  }
-              ]
-          }
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize Container Registries to only those approved (Manual)"
-        type: "manual"
-        remediation: |
-          To minimize AWS ECR container registries to only those approved, you can follow these steps:
-
-          1.  Define your approval criteria: Determine the criteria that containers must meet to
-              be considered approved. This can include factors such as security, compliance,
-              compatibility, and other requirements.
-          2.  Identify all existing ECR registries: Identify all ECR registries that are currently
-              being used in your organization.
-          3.  Evaluate ECR registries against approval criteria: Evaluate each ECR registry
-              against your approval criteria to determine whether it should be approved or not.
-              This can be done by reviewing the registry settings and configuration, as well as
-              conducting security assessments and vulnerability scans.
-          4.  Establish policies and procedures: Establish policies and procedures that outline
-              how ECR registries will be approved, maintained, and monitored. This should
-              include guidelines for developers to follow when selecting a registry for their
-              container images.
-          5.  Implement access controls: Implement access controls to ensure that only
-              approved ECR registries are used to store and distribute container images. This
-              can be done by setting up IAM policies and roles that restrict access to
-              unapproved registries or create a whitelist of approved registries.
-          6.  Monitor and review: Continuously monitor and review the use of ECR registries
-              to ensure that they continue to meet your approval criteria. This can include
-        scored: false
-
-  - id: 5.2
-    text: "Identity and Access Management (IAM)"
-    checks:
-      - id: 5.2.1
-        text: "Prefer using dedicated Amazon EKS Service Accounts (Automated)"
-        type: "manual"
-        remediation: |
-          With IAM roles for service accounts on Amazon EKS clusters, you can associate an
-          IAM role with a Kubernetes service account. This service account can then provide
-          AWS permissions to the containers in any pod that uses that service account. With this
-          feature, you no longer need to provide extended permissions to the worker node IAM
-          role so that pods on that node can call AWS APIs.
-          Applications must sign their AWS API requests with AWS credentials. This feature
-          provides a strategy for managing credentials for your applications, similar to the way
-          that Amazon EC2 instance profiles provide credentials to Amazon EC2 instances.
-          Instead of creating and distributing your AWS credentials to the containers or using the
-          Amazon EC2 instance’s role, you can associate an IAM role with a Kubernetes service
-          account. The applications in the pod’s containers can then use an AWS SDK or the
-          AWS CLI to make API requests to authorized AWS services.
-
-          The IAM roles for service accounts feature provides the following benefits:
-
-          - Least privilege - By using the IAM roles for service accounts feature, you no
-            longer need to provide extended permissions to the worker node IAM role so that
-            pods on that node can call AWS APIs. You can scope IAM permissions to a
-            service account, and only pods that use that service account have access to
-            those permissions. This feature also eliminates the need for third-party solutions
-            such as kiam or kube2iam.
-          - Credential isolation - A container can only retrieve credentials for the IAM role
-            that is associated with the service account to which it belongs. A container never
-            has access to credentials that are intended for another container that belongs to
-            another pod.
-          - Audit-ability - Access and event logging is available through CloudTrail to help
-            ensure retrospective auditing.
-        scored: false
-
-  - id: 5.3
-    text: "AWS EKS Key Management Service"
-    checks:
-      - id: 5.3.1
-        text: "Ensure Kubernetes Secrets are encrypted using Customer Master Keys (CMKs) managed in AWS KMS (Manual)"
-        type: "manual"
-        remediation: |
-          This process can only be performed during Cluster Creation.
-
-          Enable 'Secrets Encryption' during Amazon EKS cluster creation as described
-          in the links within the 'References' section.
-        scored: false
-
-  - id: 5.4
-    text: "Cluster Networking"
-    checks:
-      - id: 5.4.1
-        text: "Restrict Access to the Control Plane Endpoint (Automated)"
-        type: "manual"
-        remediation: |
-          By enabling private endpoint access to the Kubernetes API server, all communication
-          between your nodes and the API server stays within your VPC. You can also limit the IP
-          addresses that can access your API server from the internet, or completely disable
-          internet access to the API server.
-          With this in mind, you can update your cluster accordingly using the AWS CLI to ensure
-          that Private Endpoint Access is enabled.
-          If you choose to also enable Public Endpoint Access then you should also configure a
-          list of allowable CIDR blocks, resulting in restricted access from the internet. If you
-          specify no CIDR blocks, then the public API server endpoint is able to receive and
-          process requests from all IP addresses by defaulting to ['0.0.0.0/0'].
-          For example, the following command would enable private access to the Kubernetes
-          API as well as limited public access over the internet from a single IP address (noting
-          the /32 CIDR suffix):
-          aws eks update-cluster-config --region $AWS_REGION --name $CLUSTER_NAME --resources-vpc-config endpointPrivateAccess=true,endpointPrivateAccess=true,publicAccessCidrs="203.0.113.5/32"
-
-          Note: The CIDR blocks specified cannot include reserved addresses.
-          There is a maximum number of CIDR blocks that you can specify. For more information,
-          see the EKS Service Quotas link in the references section.
-          For more detailed information, see the EKS Cluster Endpoint documentation link in the
-          references section.
-        scored: false
-
-      - id: 5.4.2
-        text: "Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Automated)"
-        type: "manual"
-        remediation: |
-          By enabling private endpoint access to the Kubernetes API server, all communication
-          between your nodes and the API server stays within your VPC.
-          With this in mind, you can update your cluster accordingly using the AWS CLI to ensure
-          that Private Endpoint Access is enabled.
-          For example, the following command would enable private access to the Kubernetes
-          API and ensure that no public access is permitted:
-          aws eks update-cluster-config --region $AWS_REGION --name $CLUSTER_NAME --resources-vpc-config endpointPrivateAccess=true,endpointPublicAccess=false
-
-          Note: For more detailed information, see the EKS Cluster Endpoint documentation link
-          in the references section.
-        scored: false
-
-      - id: 5.4.3
-        text: "Ensure clusters are created with Private Nodes (Automated)"
-        type: "manual"
-        remediation: |
-          aws eks update-cluster-config \
-            --region region-code \
-            --name my-cluster \
-            --resources-vpc-config endpointPublicAccess=true,publicAccessCidrs="203.0.113.5/32",endpointPrivateAccess=true
-        scored: false
-
-      - id: 5.4.4
-        text: "Ensure Network Policy is Enabled and set as appropriate (Automated)"
-        type: "manual"
-        remediation: |
-          Utilize Calico or other network policy engine to segment and isolate your traffic.
-        scored: false
-
-      - id: 5.4.5
-        text: "Encrypt traffic to HTTPS load balancers with TLS certificates (Manual)"
-        type: "manual"
-        remediation: |
-          Your load balancer vendor can provide details on configuring HTTPS with TLS.
-        scored: false
-
-
-  - id: 5.5
-    text: "Authentication and Authorization"
-    checks:
-      - id: 5.5.1
-        text: "Manage Kubernetes RBAC users with AWS IAM Authenticator for Kubernetes or Upgrade to AWS CLI v1.16.156 or greater (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the 'Managing users or IAM roles for your cluster' in Amazon EKS documentation.
-
-          Note: If using AWS CLI version 1.16.156 or later there is no need to install the AWS
-          IAM Authenticator anymore.
-          The relevant AWS CLI commands, depending on the use case, are:
-          aws eks update-kubeconfig
-          aws eks get-token
-        scored: false

cfg/eks-1.5.0/master.yaml

@@ -1,6 +0,0 @@
----
-controls:
-version: "eks-1.5.0"
-id: 1
-text: "Control Plane Components"
-type: "master"

cfg/eks-1.5.0/node.yaml

@@ -1,453 +0,0 @@
----
-controls:
-version: "eks-1.5.0"
-id: 3
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 3.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 3.1.1
-        text: "Ensure that the kubeconfig file permissions are set to 644 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 644 $kubeletkubeconfig
-        scored: true
-
-      - id: 3.1.2
-        text: "Ensure that the kubelet kubeconfig file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 3.1.3
-        text: "Ensure that the kubelet configuration file has permissions set to 644 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 644 $kubeletconf
-        scored: true
-
-      - id: 3.1.4
-        text: "Ensure that the kubelet configuration file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: true
-
-  - id: 3.2
-    text: "Kubelet"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that the Anonymous Auth is Not Enabled (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              set: true
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-          ps -ef | grep kubelet
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-          sudo less /path/to/kubelet-config.json
-          Disable Anonymous Authentication by setting the following parameter:
-          "authentication": { "anonymous": { "enabled": false } }
-
-          Remediation Method 2.
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-          --anonymous-auth=false
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              set: true
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-          ps -ef | grep kubelet
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-          sudo less /path/to/kubelet-config.json
-          Enable Webhook Authentication by setting the following parameter:
-          "authentication": { "webhook": { "enabled": true } }
-          Next, set the Authorization Mode to Webhook by setting the following parameter:
-          "authorization": { "mode": "Webhook }
-          Finer detail of the authentication and authorization fields can be found in the
-          Kubelet Configuration documentation.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-          --authentication-token-webhook
-          --authorization-mode=Webhook
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.3
-        text: "Ensure that a Client CA File is Configured (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-              set: true
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-          ps -ef | grep kubelet
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-          sudo less /path/to/kubelet-config.json
-          Configure the client certificate authority file by setting the following parameter
-          appropriately:
-          "authentication": { "x509": {"clientCAFile": <path/to/client-ca-file> } }"
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-          --client-ca-file=<path/to/client-ca-file>
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.4
-        text: "Ensure that the --read-only-port is disabled (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: true
-              compare:
-                op: eq
-                value: 0
-        remediation: |
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to 0
-          "readOnlyPort": 0
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --read-only-port=0
-
-          Based on your system, restart the kubelet service and check status
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: true
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to a
-          non-zero value in the format of #h#m#s
-          "streamingConnectionIdleTimeout": "4h0m0s"
-          You should ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not
-          specify a --streaming-connection-idle-timeout argument because it would
-          override the Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --streaming-connection-idle-timeout=4h0m0s
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "streamingConnectionIdleTimeout": by extracting the live configuration from the
-          nodes running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster, and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-          kubectl proxy --port=8001 &
-          export HOSTNAME_PORT=localhost:8001 (example host and port number)
-          export NODE_NAME=ip-192.168.31.226.ec2.internal (example node name from "kubectl get nodes")
-          curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediations:
-          Based on your system, restart the kubelet service and check status
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: true
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to
-          true
-          "makeIPTablesUtilChains": true
-          Ensure that /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf
-          does not set the --make-iptables-util-chains argument because that would
-          override your Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --make-iptables-util-chains:true
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "makeIPTablesUtilChains.: true by extracting the live configuration from the nodes
-          running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster, and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-          kubectl proxy --port=8001 &
-          export HOSTNAME_PORT=localhost:8001 (example host and port number)
-          export NODE_NAME=ip-192.168.31.226.ec2.internal (example node name from "kubectl get nodes")
-          curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediations:
-          Based on your system, restart the kubelet service and check status
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.7
-        text: "Ensure that the --eventRecordQPS argument is set to 0 or a level which ensures appropriate event capture (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: true
-              compare:
-                op: gte
-                value: 0
-        remediation: |
-          If using a Kubelet config file, edit the file to set eventRecordQPS: to an appropriate
-          level.
-          If using command line arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node
-          and set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.8
-        text: "Ensure that the --rotate-certificates argument is not present or is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: true
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to
-          true
-          "RotateCertificate":true
-          Additionally, ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not set the --RotateCertificate
-          executable argument to false because this would override the Kubelet
-          config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --RotateCertificate=true
-        scored: true
-
-      - id: 3.2.9
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: true
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to
-          true
-
-          "featureGates": {
-            "RotateKubeletServerCertificate":true
-          },
-
-          Additionally, ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not set
-          the --rotate-kubelet-server-certificate executable argument to false because
-          this would override the Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --rotate-kubelet-server-certificate=true
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "RotateKubeletServerCertificate": by extracting the live configuration from the
-          nodes running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster, and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-          kubectl proxy --port=8001 &
-          export HOSTNAME_PORT=localhost:8001 (example host and port number)
-          export NODE_NAME=ip-192.168.31.226.ec2.internal (example node name from "kubectl get nodes")
-          curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediation methods:
-          Restart the kubelet service and check status. The example below is for when using
-          systemctl to manage services:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true

cfg/eks-1.5.0/policies.yaml

@@ -1,250 +0,0 @@
----
-controls:
-version: "eks-1.5.0"
-id: 4
-text: "Policies"
-type: "policies"
-groups:
-  - id: 4.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Automated)"
-        type: "manual"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and if
-          they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role :
-          kubectl delete clusterrolebinding [name]
-        scored: false
-
-      - id: 4.1.2
-        text: "Minimize access to secrets (Automated)"
-        type: "manual"
-        remediation: |
-          Where possible, remove get, list and watch access to secret objects in the cluster.
-        scored: false
-
-      - id: 4.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Automated)"
-        type: "manual"
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: false
-
-      - id: 4.1.4
-        text: "Minimize access to create pods (Automated)"
-        type: "manual"
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that default service accounts are not actively used. ((Automated)"
-        type: "manual"
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific
-          access to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          automountServiceAccountToken: false
-
-          Automatic remediation for the default account:
-          kubectl patch serviceaccount default -p
-          $'automountServiceAccountToken: false'
-        scored: false
-
-      - id: 4.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Automated)"
-        type: "manual"
-        remediation: |
-          Modify the definition of pods and service accounts which do not need to mount service
-          account tokens to disable it.
-        scored: false
-
-      - id: 4.1.7
-        text: "Avoid use of system:masters group (Automated)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 4.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-  - id: 4.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 4.2.1
-        text: "Minimize the admission of privileged containers (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of privileged containers.
-          To enable PSA for a namespace in your cluster, set the pod-security.kubernetes.io/enforce
-          label with the policy value you want to enforce.
-          kubectl label --overwrite ns NAMESPACE pod-security.kubernetes.io/enforce=restricted
-          The above command enforces the restricted policy for the NAMESPACE namespace.
-          You can also enable Pod Security Admission for all your namespaces. For example:
-          kubectl label --overwrite ns --all pod-security.kubernetes.io/warn=baseline
-        scored: false
-
-      - id: 4.2.2
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of hostPID containers.
-        scored: false
-
-      - id: 4.2.3
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of hostIPC containers.
-        scored: false
-
-      - id: 4.2.4
-        text: "Minimize the admission of containers wishing to share the host network namespace (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of hostNetwork containers.
-        scored: false
-
-      - id: 4.2.5
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Automated)"
-        type: "manual"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with .spec.allowPrivilegeEscalation set to true.
-        scored: false
-
-  - id: 4.3
-    text: "CNI Plugin"
-    checks:
-      - id: 4.3.1
-        text: "Ensure CNI plugin supports network policies (Manual)"
-        type: "manual"
-        remediation: |
-          As with RBAC policies, network policies should adhere to the policy of least privileged
-          access. Start by creating a deny all policy that restricts all inbound and outbound traffic
-          from a namespace or create a global policy using Calico.
-        scored: false
-
-      - id: 4.3.2
-        text: "Ensure that all Namespaces have Network Policies defined (Automated)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as you need them.
-        scored: false
-
-  - id: 4.4
-    text: "Secrets Management"
-    checks:
-      - id: 4.4.1
-        text: "Prefer using secrets as files over secrets as environment variables (Automated)"
-        type: "manual"
-        remediation: |
-          If possible, rewrite application code to read secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 4.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 4.5
-    text: "General Policies"
-    checks:
-      - id: 4.5.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 4.5.2
-        text: "Apply Security Context to Your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          As a best practice we recommend that you scope the binding for privileged pods to
-          service accounts within a particular namespace, e.g. kube-system, and limiting access
-          to that namespace. For all other serviceaccounts/namespaces, we recommend
-          implementing a more restrictive policy such as this:
-
-          apiVersion: policy/v1beta1
-          kind: PodSecurityPolicy
-          metadata:
-            name: restricted
-            annotations:
-              seccomp.security.alpha.kubernetes.io/allowedProfileNames: 'docker/default,runtime/default'
-              apparmor.security.beta.kubernetes.io/allowedProfileNames: 'runtime/default'
-              seccomp.security.alpha.kubernetes.io/defaultProfileName: 'runtime/default'
-              apparmor.security.beta.kubernetes.io/defaultProfileName: 'runtime/default'
-          spec:
-            privileged: false
-            # Required to prevent escalations to root.
-            allowPrivilegeEscalation: false
-            # This is redundant with non-root + disallow privilege escalation,
-            # but we can provide it for defense in depth.
-            requiredDropCapabilities:
-            - ALL
-            # Allow core volume types.
-            volumes:
-            - 'configMap'
-            - 'emptyDir'
-            - 'projected'
-            - 'secret'
-            - 'downwardAPI'
-            # Assume that persistentVolumes set up by the cluster admin are safe to use.
-            - 'persistentVolumeClaim'
-            hostNetwork: false
-            hostIPC: false
-            hostPID: false
-            runAsUser:
-            # Require the container to run without root privileges.
-            rule: 'MustRunAsNonRoot'
-            seLinux:
-            # This policy assumes the nodes are using AppArmor rather than SELinux.
-            rule: 'RunAsAny'
-            supplementalGroups:
-            rule: 'MustRunAs'
-            ranges:
-              # Forbid adding the root group.
-              - min: 1
-                max: 65535
-            fsGroup:
-            rule: 'MustRunAs'
-            ranges:
-              # Forbid adding the root group.
-              - min: 1
-                max: 65535
-            readOnlyRootFilesystem: false
-
-          This policy prevents pods from running as privileged or escalating privileges. It also
-          restricts the types of volumes that can be mounted and the root supplemental groups
-          that can be added.
-          Another, albeit similar, approach is to start with policy that locks everything down and
-          incrementally add exceptions for applications that need looser restrictions such as
-          logging agents which need the ability to mount a host path.
-        scored: false
-
-      - id: 4.5.3
-        text: "The default namespace should not be used (Automated)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/eks-1.7.0/config.yaml

@@ -1,9 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml
-## These settings are required if you are using the --asff option to report findings to AWS Security Hub
-## AWS account number is required.
-AWS_ACCOUNT: "<AWS_ACCT_NUMBER>"
-## AWS region is required.
-AWS_REGION: "<AWS_REGION>"
-## EKS Cluster ARN is required.
-CLUSTER_ARN: "<AWS_CLUSTER_ARN>"

cfg/eks-1.7.0/controlplane.yaml

@@ -1,69 +0,0 @@
----
-controls:
-version: "eks-1.7.0"
-id: 2
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 2.1
-    text: "Logging"
-    checks:
-      - id: 2.1.1
-        text: "Enable audit Logs (Manual)"
-        type: manual
-        remediation: |
-          From Console:
-          1.  For each EKS Cluster in each region;
-          2.  Go to 'Amazon EKS' > 'Clusters' > '' > 'Configuration' > 'Logging'.
-          3.  Click 'Manage logging'.
-          4.  Ensure that all options are toggled to 'Enabled'.
-                API server: Enabled
-                Audit: Enabled
-                Authenticator: Enabled
-                Controller manager: Enabled
-                Scheduler: Enabled
-          5.  Click 'Save Changes'.
-
-          From CLI:
-          # For each EKS Cluster in each region;
-          aws eks update-cluster-config \
-            --region '${REGION_CODE}' \
-            --name '${CLUSTER_NAME}' \
-            --logging '{"clusterLogging":[{"types":["api","audit","authenticator","controllerManager","scheduler"],"enabled":true}]}'
-        scored: false
-
-      - id: 2.1.2
-        text: "Ensure audit logs are collected and managed (Manual)"
-        type: manual
-        remediation: |
-          Create or update the audit-policy.yaml to specify the audit logging configuration:
-          apiVersion: audit.k8s.io/v1
-          kind: Policy
-          rules:
-            - level: Metadata
-              resources:
-                - group: ""
-                  resources: ["pods"]
-          Apply the audit policy configuration to the cluster:
-            kubectl apply -f <path-to-audit-policy>.yaml
-          Ensure audit logs are forwarded to a centralized logging system like CloudWatch, Elasticsearch, or another log management solution:
-            kubectl create configmap cluster-audit-policy --from-file=audit-policy.yaml -n kube-system
-            kubectl apply -f - <<EOF
-          apiVersion: v1
-          kind: Pod
-          metadata:
-            name: audit-logging
-            namespace: kube-system
-          spec:
-            containers:
-              - name: audit-log-forwarder
-                image: my-log-forwarder-image
-                volumeMounts:
-                  - mountPath: /etc/kubernetes/audit
-                    name: audit-config
-            volumes:
-              - name: audit-config
-                configMap:
-                  name: cluster-audit-policy
-            EOF
-        scored: false

cfg/eks-1.7.0/managedservices.yaml

@@ -1,227 +0,0 @@
----
-controls:
-version: "eks-1.7.0"
-id: 5
-text: "Managed Services"
-type: "managedservices"
-groups:
-  - id: 5.1
-    text: "Image Registry and Image Scanning"
-    checks:
-      - id: 5.1.1
-        text: "Ensure Image Vulnerability Scanning using Amazon ECR image scanning or a third party provider (Manual)"
-        type: "manual"
-        remediation: |
-          To utilize AWS ECR for Image scanning please follow the steps below:
-
-          To create a repository configured for scan on push (AWS CLI):
-          aws ecr create-repository --repository-name $REPO_NAME --image-scanning-configuration scanOnPush=true --region $REGION_CODE
-
-          To edit the settings of an existing repository (AWS CLI):
-          aws ecr put-image-scanning-configuration --repository-name $REPO_NAME --image-scanning-configuration scanOnPush=true --region $REGION_CODE
-
-          Use the following steps to start a manual image scan using the AWS Management Console.
-
-          1.  Open the Amazon ECR console at https://console.aws.amazon.com/ecr/repositories.
-          2.  From the navigation bar, choose the Region to create your repository in.
-          3.  In the navigation pane, choose Repositories.
-          4.  On the Repositories page, choose the repository that contains the image to scan.
-          5.  On the Images page, select the image to scan and then choose Scan.
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize user access to Amazon ECR (Manual)"
-        type: "manual"
-        remediation: |
-          Before you use IAM to manage access to Amazon ECR, you should understand what IAM features
-          are available to use with Amazon ECR. To get a high-level view of how Amazon ECR and other
-          AWS services work with IAM, see AWS Services That Work with IAM in the IAM User Guide.
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize cluster access to read-only for Amazon ECR (Manual)"
-        type: "manual"
-        remediation: |
-          You can use your Amazon ECR images with Amazon EKS, but you need to satisfy the following prerequisites.
-
-          The Amazon EKS worker node IAM role (NodeInstanceRole) that you use with your worker nodes must possess
-          the following IAM policy permissions for Amazon ECR.
-
-          {
-              "Version": "2012-10-17",
-              "Statement": [
-                  {
-                      "Effect": "Allow",
-                      "Action": [
-                          "ecr:BatchCheckLayerAvailability",
-                          "ecr:BatchGetImage",
-                          "ecr:GetDownloadUrlForLayer",
-                          "ecr:GetAuthorizationToken"
-                      ],
-                      "Resource": "*"
-                  }
-              ]
-          }
-        scored: false
-
-      - id: 5.1.4
-        text: "Minimize Container Registries to only those approved (Manual)"
-        type: "manual"
-        remediation: |
-          To minimize AWS ECR container registries to only those approved, you can follow these steps:
-
-          1.  Define your approval criteria: Determine the criteria that containers must meet to
-              be considered approved. This can include factors such as security, compliance,
-              compatibility, and other requirements.
-          2.  Identify all existing ECR registries: Identify all ECR registries that are currently
-              being used in your organization.
-          3.  Evaluate ECR registries against approval criteria: Evaluate each ECR registry
-              against your approval criteria to determine whether it should be approved or not.
-              This can be done by reviewing the registry settings and configuration, as well as
-              conducting security assessments and vulnerability scans.
-          4.  Establish policies and procedures: Establish policies and procedures that outline
-              how ECR registries will be approved, maintained, and monitored. This should
-              include guidelines for developers to follow when selecting a registry for their
-              container images.
-          5.  Implement access controls: Implement access controls to ensure that only
-              approved ECR registries are used to store and distribute container images. This
-              can be done by setting up IAM policies and roles that restrict access to
-              unapproved registries or create a whitelist of approved registries.
-          6.  Monitor and review: Continuously monitor and review the use of ECR registries
-              to ensure that they continue to meet your approval criteria. This can include
-        scored: false
-
-  - id: 5.2
-    text: "Identity and Access Management (IAM)"
-    checks:
-      - id: 5.2.1
-        text: "Prefer using dedicated Amazon EKS Service Accounts (Manual)"
-        type: "manual"
-        remediation: |
-          With IAM roles for service accounts on Amazon EKS clusters, you can associate an
-          IAM role with a Kubernetes service account. This service account can then provide
-          AWS permissions to the containers in any pod that uses that service account. With this
-          feature, you no longer need to provide extended permissions to the worker node IAM
-          role so that pods on that node can call AWS APIs.
-          Applications must sign their AWS API requests with AWS credentials. This feature
-          provides a strategy for managing credentials for your applications, similar to the way
-          that Amazon EC2 instance profiles provide credentials to Amazon EC2 instances.
-          Instead of creating and distributing your AWS credentials to the containers or using the
-          Amazon EC2 instance’s role, you can associate an IAM role with a Kubernetes service
-          account. The applications in the pod’s containers can then use an AWS SDK or the
-          AWS CLI to make API requests to authorized AWS services.
-
-          The IAM roles for service accounts feature provides the following benefits:
-
-          - Least privilege - By using the IAM roles for service accounts feature, you no
-            longer need to provide extended permissions to the worker node IAM role so that
-            pods on that node can call AWS APIs. You can scope IAM permissions to a
-            service account, and only pods that use that service account have access to
-            those permissions. This feature also eliminates the need for third-party solutions
-            such as kiam or kube2iam.
-          - Credential isolation - A container can only retrieve credentials for the IAM role
-            that is associated with the service account to which it belongs. A container never
-            has access to credentials that are intended for another container that belongs to
-            another pod.
-          - Audit-ability - Access and event logging is available through CloudTrail to help
-            ensure retrospective auditing.
-        scored: false
-
-  - id: 5.3
-    text: "AWS EKS Key Management Service"
-    checks:
-      - id: 5.3.1
-        text: "Ensure Kubernetes Secrets are encrypted using Customer Master Keys (CMKs) managed in AWS KMS (Manual)"
-        type: "manual"
-        remediation: |
-          This process can only be performed during Cluster Creation.
-
-          Enable 'Secrets Encryption' during Amazon EKS cluster creation as described
-          in the links within the 'References' section.
-        scored: false
-
-  - id: 5.4
-    text: "Cluster Networking"
-    checks:
-      - id: 5.4.1
-        text: "Restrict Access to the Control Plane Endpoint (Manual)"
-        type: "manual"
-        remediation: |
-          By enabling private endpoint access to the Kubernetes API server, all communication
-          between your nodes and the API server stays within your VPC. You can also limit the IP
-          addresses that can access your API server from the internet, or completely disable
-          internet access to the API server.
-          With this in mind, you can update your cluster accordingly using the AWS CLI to ensure
-          that Private Endpoint Access is enabled.
-          If you choose to also enable Public Endpoint Access then you should also configure a
-          list of allowable CIDR blocks, resulting in restricted access from the internet. If you
-          specify no CIDR blocks, then the public API server endpoint is able to receive and
-          process requests from all IP addresses by defaulting to ['0.0.0.0/0'].
-          For example, the following command would enable private access to the Kubernetes
-          API as well as limited public access over the internet from a single IP address (noting
-          the /32 CIDR suffix):
-          aws eks update-cluster-config --region $AWS_REGION --name $CLUSTER_NAME --resources-vpc-config endpointPrivateAccess=true,endpointPrivateAccess=true,publicAccessCidrs="203.0.113.5/32"
-
-          Note: The CIDR blocks specified cannot include reserved addresses.
-          There is a maximum number of CIDR blocks that you can specify. For more information,
-          see the EKS Service Quotas link in the references section.
-          For more detailed information, see the EKS Cluster Endpoint documentation link in the
-          references section.
-        scored: false
-
-      - id: 5.4.2
-        text: "Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Manual)"
-        type: "manual"
-        remediation: |
-          By enabling private endpoint access to the Kubernetes API server, all communication
-          between your nodes and the API server stays within your VPC.
-          With this in mind, you can update your cluster accordingly using the AWS CLI to ensure
-          that Private Endpoint Access is enabled.
-          For example, the following command would enable private access to the Kubernetes
-          API and ensure that no public access is permitted:
-          aws eks update-cluster-config --region $AWS_REGION --name $CLUSTER_NAME --resources-vpc-config endpointPrivateAccess=true,endpointPublicAccess=false
-
-          Note: For more detailed information, see the EKS Cluster Endpoint documentation link
-          in the references section.
-        scored: false
-
-      - id: 5.4.3
-        text: "Ensure clusters are created with Private Nodes (Manual)"
-        type: "manual"
-        remediation: |
-          aws eks update-cluster-config \
-            --region region-code \
-            --name my-cluster \
-            --resources-vpc-config endpointPublicAccess=true,publicAccessCidrs="203.0.113.5/32",endpointPrivateAccess=true
-        scored: false
-
-      - id: 5.4.4
-        text: "Ensure Network Policy is Enabled and set as appropriate (Manual)"
-        type: "manual"
-        remediation: |
-          Utilize Calico or other network policy engine to segment and isolate your traffic.
-        scored: false
-
-      - id: 5.4.5
-        text: "Encrypt traffic to HTTPS load balancers with TLS certificates (Manual)"
-        type: "manual"
-        remediation: |
-          Your load balancer vendor can provide details on configuring HTTPS with TLS.
-        scored: false
-
-
-  - id: 5.5
-    text: "Authentication and Authorization"
-    checks:
-      - id: 5.5.1
-        text: "Manage Kubernetes RBAC users with AWS IAM Authenticator for Kubernetes or Upgrade to AWS CLI v1.16.156 or greater (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the 'Managing users or IAM roles for your cluster' in Amazon EKS documentation.
-
-          Note: If using AWS CLI version 1.16.156 or later there is no need to install the AWS
-          IAM Authenticator anymore.
-          The relevant AWS CLI commands, depending on the use case, are:
-          aws eks update-kubeconfig
-          aws eks get-token
-        scored: false

cfg/eks-1.7.0/master.yaml

@@ -1,6 +0,0 @@
----
-controls:
-version: "eks-1.7.0"
-id: 1
-text: "Control Plane Components"
-type: "master"

cfg/eks-1.7.0/node.yaml

@@ -1,456 +0,0 @@
----
-controls:
-version: "eks-1.7.0"
-id: 3
-text: "Worker Nodes"
-type: "node"
-groups:
-  - id: 3.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 3.1.1
-        text: "Ensure that the kubeconfig file permissions are set to 644 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c permissions=%a $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chmod 644 $kubeletkubeconfig
-        scored: true
-
-      - id: 3.1.2
-        text: "Ensure that the kubelet kubeconfig file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletkubeconfig; then stat -c %U:%G $kubeletkubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on the each worker node.
-          For example,
-          chown root:root $kubeletkubeconfig
-        scored: true
-
-      - id: 3.1.3
-        text: "Ensure that the kubelet configuration file has permissions set to 644 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chmod 644 $kubeletconf
-        scored: true
-
-      - id: 3.1.4
-        text: "Ensure that the kubelet configuration file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identified in the Audit step)
-          chown root:root $kubeletconf
-        scored: true
-
-  - id: 3.2
-    text: "Kubelet"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that the Anonymous Auth is Not Enabled (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              set: true
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-          ps -ef | grep kubelet
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-          sudo less /path/to/kubelet-config.json
-          Disable Anonymous Authentication by setting the following parameter:
-          "authentication": { "anonymous": { "enabled": false } }
-
-          Remediation Method 2.
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-          --anonymous-auth=false
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              set: true
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-          ps -ef | grep kubelet
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-          sudo less /path/to/kubelet-config.json
-          Enable Webhook Authentication by setting the following parameter:
-          "authentication": { "webhook": { "enabled": true } }
-          Next, set the Authorization Mode to Webhook by setting the following parameter:
-          "authorization": { "mode": "Webhook }
-          Finer detail of the authentication and authorization fields can be found in the
-          Kubelet Configuration documentation.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-          --authentication-token-webhook
-          --authorization-mode=Webhook
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.3
-        text: "Ensure that a Client CA File is Configured (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-              set: true
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-          ps -ef | grep kubelet
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-          sudo less /path/to/kubelet-config.json
-          Configure the client certificate authority file by setting the following parameter
-          appropriately:
-          "authentication": { "x509": {"clientCAFile": <path/to/client-ca-file> } }"
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-          --client-ca-file=<path/to/client-ca-file>
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.4
-        text: "Ensure that the --read-only-port is disabled (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: true
-              compare:
-                op: eq
-                value: 0
-        remediation: |
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to 0
-          "readOnlyPort": 0
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --read-only-port=0
-
-          Based on your system, restart the kubelet service and check status
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: true
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to a
-          non-zero value in the format of #h#m#s
-          "streamingConnectionIdleTimeout": "4h0m0s"
-          You should ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not
-          specify a --streaming-connection-idle-timeout argument because it would
-          override the Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --streaming-connection-idle-timeout=4h0m0s
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "streamingConnectionIdleTimeout": by extracting the live configuration from the
-          nodes running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster, and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-          kubectl proxy --port=8001 &
-          export HOSTNAME_PORT=localhost:8001 (example host and port number)
-          export NODE_NAME=ip-192.168.31.226.ec2.internal (example node name from "kubectl get nodes")
-          curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediations:
-          Based on your system, restart the kubelet service and check status
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: true
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to
-          true
-          "makeIPTablesUtilChains": true
-          Ensure that /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf
-          does not set the --make-iptables-util-chains argument because that would
-          override your Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --make-iptables-util-chains:true
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "makeIPTablesUtilChains.: true by extracting the live configuration from the nodes
-          running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster, and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-          kubectl proxy --port=8001 &
-          export HOSTNAME_PORT=localhost:8001 (example host and port number)
-          export NODE_NAME=ip-192.168.31.226.ec2.internal (example node name from "kubectl get nodes")
-          curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediations:
-          Based on your system, restart the kubelet service and check status
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.7
-        text: "Ensure that the --eventRecordQPS argument is set to 0 or a level which ensures appropriate event capture (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: true
-              compare:
-                op: gte
-                value: 0
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: false
-          bin_op: or
-        remediation: |
-          If using a Kubelet config file, edit the file to set eventRecordQPS: to an appropriate
-          level.
-          If using command line arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubeadm.conf on each worker node
-          and set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-          Based on your system, restart the kubelet service. For example:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.8
-        text: "Ensure that the --rotate-certificates argument is not present or is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to
-          true
-          "RotateCertificate":true
-          Additionally, ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not set the --RotateCertificate
-          executable argument to false because this would override the Kubelet
-          config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --RotateCertificate=true
-        scored: true
-
-      - id: 3.2.9
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat $kubeletconf"
-        tests:
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              set: true
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to
-          true
-
-          "featureGates": {
-            "RotateKubeletServerCertificate":true
-          },
-
-          Additionally, ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not set
-          the --rotate-kubelet-server-certificate executable argument to false because
-          this would override the Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-          --rotate-kubelet-server-certificate=true
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "RotateKubeletServerCertificate": by extracting the live configuration from the
-          nodes running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster, and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-          kubectl proxy --port=8001 &
-          export HOSTNAME_PORT=localhost:8001 (example host and port number)
-          export NODE_NAME=ip-192.168.31.226.ec2.internal (example node name from "kubectl get nodes")
-          curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediation methods:
-          Restart the kubelet service and check status. The example below is for when using
-          systemctl to manage services:
-          systemctl daemon-reload
-          systemctl restart kubelet.service
-          systemctl status kubelet -l
-        scored: true

cfg/eks-1.7.0/policies.yaml

@@ -1,358 +0,0 @@
----
-controls:
-version: "eks-1.7.0"
-id: 4
-text: "Policies"
-type: "policies"
-groups:
-  - id: 4.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Automated)"
-        audit: |
-          kubectl get clusterrolebindings -o json | jq -r '
-            .items[]
-            | select(.roleRef.name == "cluster-admin")
-            | .subjects[]?
-            | select(.kind != "Group" or (.name != "system:masters" and .name != "system:nodes"))
-            | "FOUND_CLUSTER_ADMIN_BINDING"
-          ' || echo "NO_CLUSTER_ADMIN_BINDINGS"
-        tests:
-          test_items:
-            - flag: "NO_CLUSTER_ADMIN_BINDINGS"
-              set: true
-              compare:
-                op: eq
-                value: "NO_CLUSTER_ADMIN_BINDINGS"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and if
-          they need this role or if they could use a role with fewer privileges.
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role :
-          kubectl delete clusterrolebinding [name]
-        scored: true
-
-      - id: 4.1.2
-        text: "Minimize access to secrets (Automated)"
-        audit: |
-          count=$(kubectl get roles --all-namespaces -o json | jq '
-            .items[]
-            | select(.rules[]?
-              | (.resources[]? == "secrets")
-              and ((.verbs[]? == "get") or (.verbs[]? == "list") or (.verbs[]? == "watch"))
-            )' | wc -l)
-
-          if [ "$count" -gt 0 ]; then
-            echo "SECRETS_ACCESS_FOUND"
-          fi
-        tests:
-          test_items:
-            - flag: "SECRETS_ACCESS_FOUND"
-              set: false
-        remediation: |
-          Where possible, remove get, list and watch access to secret objects in the cluster.
-        scored: true
-
-      - id: 4.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Automated)"
-        audit: |
-          wildcards=$(kubectl get roles --all-namespaces -o json | jq '
-            .items[] | select(
-              .rules[]? | (.verbs[]? == "*" or .resources[]? == "*" or .apiGroups[]? == "*")
-            )' | wc -l)
-
-          wildcards_clusterroles=$(kubectl get clusterroles -o json | jq '
-            .items[] | select(
-              .rules[]? | (.verbs[]? == "*" or .resources[]? == "*" or .apiGroups[]? == "*")
-            )' | wc -l)
-
-          total=$((wildcards + wildcards_clusterroles))
-
-          if [ "$total" -gt 0 ]; then
-            echo "wildcards_present"
-          fi
-        tests:
-          test_items:
-            - flag: wildcards_present
-              set: false
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: true
-
-      - id: 4.1.4
-        text: "Minimize access to create pods (Automated)"
-        audit: |
-          access=$(kubectl get roles,clusterroles -A -o json | jq '
-            [.items[] |
-              select(
-                .rules[]? |
-                (.resources[]? == "pods" and .verbs[]? == "create")
-              )
-            ] | length')
-
-          if [ "$access" -gt 0 ]; then
-            echo "pods_create_access"
-          fi
-        tests:
-          test_items:
-            - flag: pods_create_access
-              set: false
-        remediation: |
-          Where possible, remove create access to pod objects in the cluster.
-        scored: true
-
-      - id: 4.1.5
-        text: "Ensure that default service accounts are not actively used. (Automated)"
-        audit: |
-          default_sa_count=$(kubectl get serviceaccounts --all-namespaces -o json | jq '
-            [.items[] | select(.metadata.name == "default" and (.automountServiceAccountToken != false))] | length')
-          if [ "$default_sa_count" -gt 0 ]; then
-            echo "default_sa_not_auto_mounted"
-          fi
-
-          pods_using_default_sa=$(kubectl get pods --all-namespaces -o json | jq '
-            [.items[] | select(.spec.serviceAccountName == "default")] | length')
-          if [ "$pods_using_default_sa" -gt 0 ]; then
-            echo "default_sa_used_in_pods"
-          fi
-        tests:
-          test_items:
-            - flag: default_sa_not_auto_mounted
-              set: false
-            - flag: default_sa_used_in_pods
-              set: false
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific
-          access to the Kubernetes API server.
-          Modify the configuration of each default service account to include this value
-          automountServiceAccountToken: false
-
-          Automatic remediation for the default account:
-          kubectl patch serviceaccount default -p
-          $'automountServiceAccountToken: false'
-        scored: true
-
-      - id: 4.1.6
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Automated)"
-        audit: |
-          pods_with_token_mount=$(kubectl get pods --all-namespaces -o json | jq '
-            [.items[] | select(.spec.automountServiceAccountToken != false)] | length')
-
-          if [ "$pods_with_token_mount" -gt 0 ]; then
-            echo "automountServiceAccountToken"
-          fi
-        tests:
-          test_items:
-            - flag: automountServiceAccountToken
-              set: false
-        remediation: |
-          Regularly review pod and service account objects in the cluster to ensure that the automountServiceAccountToken setting is false for pods and accounts that do not explicitly require API server access.
-        scored: true
-
-      - id: 4.1.7
-        text: "Cluster Access Manager API to streamline and enhance the management of access controls within EKS clusters (Manual)"
-        type: "manual"
-        remediation: |
-          Log in to the AWS Management Console.
-            Navigate to Amazon EKS and select your EKS cluster.
-
-            Go to the Access tab and click on "Manage Access" in the "Access Configuration section".
-            Under Cluster Authentication Mode for Cluster Access settings.
-            Click EKS API to change cluster will source authenticated IAM principals only from EKS access entry APIs.
-            Click ConfigMap to change cluster will source authenticated IAM principals only from the aws-auth ConfigMap.
-          Note: EKS API and ConfigMap must be selected during Cluster creation and cannot be changed once the Cluster is provisioned.
-        scored: false
-
-      - id: 4.1.8
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-  - id: 4.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 4.2.1
-        text: "Minimize the admission of privileged containers (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | \
-            jq -r 'if any(.items[]?.spec.containers[]?; .securityContext?.privileged == true) then "PRIVILEGED_FOUND" else "NO_PRIVILEGED" end'
-        tests:
-          test_items:
-            - flag: "NO_PRIVILEGED"
-              set: true
-              compare:
-                op: eq
-                value: "NO_PRIVILEGED"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the admission of privileged containers.
-            To enable PSA for a namespace in your cluster, set the pod-security.kubernetes.io/enforce label with the policy value you want to enforce.
-            kubectl label --overwrite ns NAMESPACE pod-security.kubernetes.io/enforce=restricted
-            The above command enforces the restricted policy for the NAMESPACE namespace.
-          You can also enable Pod Security Admission for all your namespaces. For example:
-            kubectl label --overwrite ns --all pod-security.kubernetes.io/warn=baseline
-        scored: true
-
-      - id: 4.2.2
-        text: "Minimize the admission of containers wishing to share the host process ID namespace (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | \
-            jq -r 'if any(.items[]?; .spec.hostPID == true) then "HOSTPID_FOUND" else "NO_HOSTPID" end'
-        tests:
-          test_items:
-            - flag: "NO_HOSTPID"
-              set: true
-              compare:
-                op: eq
-                value: "NO_HOSTPID"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of hostPID containers.
-        scored: true
-
-      - id: 4.2.3
-        text: "Minimize the admission of containers wishing to share the host IPC namespace (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | jq -r 'if any(.items[]?; .spec.hostIPC == true) then "HOSTIPC_FOUND" else "NO_HOSTIPC" end'
-        tests:
-          test_items:
-            - flag: "NO_HOSTIPC"
-              set: true
-              compare:
-                op: eq
-                value: "NO_HOSTIPC"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of hostIPC containers.
-        scored: true
-
-      - id: 4.2.4
-        text: "Minimize the admission of containers wishing to share the host network namespace (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | jq -r 'if any(.items[]?; .spec.hostNetwork == true) then "HOSTNETWORK_FOUND" else "NO_HOSTNETWORK" end'
-        tests:
-          test_items:
-            - flag: "NO_HOSTNETWORK"
-              set: true
-              compare:
-                op: eq
-                value: "NO_HOSTNETWORK"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of hostNetwork containers.
-        scored: true
-
-      - id: 4.2.5
-        text: "Minimize the admission of containers with allowPrivilegeEscalation (Automated)"
-        audit: |
-          kubectl get pods --all-namespaces -o json | \
-            jq -r 'if any(.items[]?.spec.containers[]?; .securityContext?.allowPrivilegeEscalation == true) then "ALLOWPRIVILEGEESCALTION_FOUND" else "NO_ALLOWPRIVILEGEESCALTION" end'
-        tests:
-          test_items:
-            - flag: "NO_ALLOWPRIVILEGEESCALTION"
-              set: true
-              compare:
-                op: eq
-                value: "NO_ALLOWPRIVILEGEESCALTION"
-        remediation: |
-          Add policies to each namespace in the cluster which has user workloads to restrict the
-          admission of containers with .spec.allowPrivilegeEscalation set to true.
-        scored: true
-
-  - id: 4.3
-    text: "CNI Plugin"
-    checks:
-      - id: 4.3.1
-        text: "Ensure CNI plugin supports network policies (Manual)"
-        type: "manual"
-        remediation: |
-          As with RBAC policies, network policies should adhere to the policy of least privileged
-          access. Start by creating a deny all policy that restricts all inbound and outbound traffic
-          from a namespace or create a global policy using Calico.
-        scored: false
-
-      - id: 4.3.2
-        text: "Ensure that all Namespaces have Network Policies defined (Automated)"
-        audit: |
-          ns_without_np=$(kubectl get namespaces -o json | jq -r '.items[].metadata.name' | while read ns; do
-            count=$(kubectl get networkpolicy -n $ns --no-headers 2>/dev/null | wc -l)
-            if [ "$count" -eq 0 ]; then echo $ns; fi
-          done)
-          if [ -z "$ns_without_np" ]; then
-            echo "ALL_NAMESPACES_HAVE_NETWORK_POLICIES"
-          else
-            echo "NAMESPACES_WITHOUT_NETWORK_POLICIES: $ns_without_np"
-          fi
-        tests:
-          test_items:
-            - flag: "ALL_NAMESPACES_HAVE_NETWORK_POLICIES"
-              set: true
-              compare:
-                op: eq
-                value: "ALL_NAMESPACES_HAVE_NETWORK_POLICIES"
-        remediation: |
-          Create at least one NetworkPolicy in each namespace to control and restrict traffic between pods as needed.
-        scored: true
-
-  - id: 4.4
-    text: "Secrets Management"
-    checks:
-      - id: 4.4.1
-        text: "Prefer using secrets as files over secrets as environment variables (Automated)"
-        audit: |
-          result=$(kubectl get all --all-namespaces -o jsonpath='{range .items[?(@..secretKeyRef)]}{.metadata.namespace} {.kind} {.metadata.name}{"\n"}{end}')
-          if [ -z "$result" ]; then
-            echo "NO_SECRETS_AS_ENV_VARS"
-          else
-            echo "SECRETS_AS_ENV_VARS_FOUND: $result"
-          fi
-        tests:
-          test_items:
-            - flag: "NO_SECRETS_AS_ENV_VARS"
-              set: true
-              compare:
-                op: eq
-                value: "NO_SECRETS_AS_ENV_VARS"
-        remediation: |
-          If possible, rewrite application code to read secrets from mounted secret files, rather than
-          from environment variables.
-        scored: true
-
-      - id: 4.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 4.5
-    text: "General Policies"
-    checks:
-      - id: 4.5.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 4.5.2
-        text: "The default namespace should not be used (Automated)"
-        audit: |
-          output=$(kubectl get $(kubectl api-resources --verbs=list --namespaced=true -o name | paste -sd, -) --ignore-not-found -n default 2>/dev/null | grep -v "^kubernetes ")
-          if [ -z "$output" ]; then
-            echo "NO_USER_RESOURCES_IN_DEFAULT"
-          else
-            echo "USER_RESOURCES_IN_DEFAULT_FOUND: $output"
-          fi
-        tests:
-          test_items:
-            - flag: "NO_USER_RESOURCES_IN_DEFAULT"
-              set: true
-        remediation: |
-          Create and use dedicated namespaces for resources instead of the default namespace. Move any user-defined objects out of the default namespace to improve resource segregation and RBAC control.
-        scored: true

cfg/gke-1.6.0/config.yaml

@@ -1,9 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml
-
-node:
-  proxy:
-    defaultkubeconfig: "/var/lib/kubelet/kubeconfig"
-
-  kubelet:
-    defaultconf: "/etc/kubernetes/kubelet/kubelet-config.yaml"

cfg/gke-1.6.0/controlplane.yaml

@@ -1,20 +0,0 @@
----
-controls:
-version: "gke-1.6.0"
-id: 2
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 2.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 2.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-
-          You can remediate the availability of client certificates in your GKE cluster. See
-          Recommendation 5.8.1.
-        scored: false

cfg/gke-1.6.0/managedservices.yaml

@@ -1,617 +0,0 @@
----
-controls:
-version: "gke-1.6.0"
-id: 5
-text: "Managed Services"
-type: "managedservices"
-groups:
-  - id: 5.1
-    text: "Image Registry and Image Scanning"
-    checks:
-      - id: 5.1.1
-        text: "Ensure Image Vulnerability Scanning is enabled (Automated)"
-        type: "manual"
-        remediation: |
-          For Images Hosted in GCR:
-          Using Command Line:
-
-            gcloud services enable containeranalysis.googleapis.com
-
-          For Images Hosted in AR:
-          Using Command Line:
-
-            gcloud services enable containerscanning.googleapis.com
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize user access to Container Image repositories (Manual)"
-        type: "manual"
-        remediation: |
-          For Images Hosted in AR:
-          Using Command Line:
-
-            gcloud artifacts repositories set-iam-policy <repository-name> <path-to-policy-file> \
-              --location <repository-location>
-
-          To learn how to configure policy files see: https://cloud.google.com/artifact-registry/docs/access-control#grant
-
-          For Images Hosted in GCR:
-          Using Command Line:
-          To change roles at the GCR bucket level:
-          Firstly, run the following if read permissions are required:
-
-            gsutil iam ch <type>:<email_address>:objectViewer gs://artifacts.<project_id>.appspot.com
-
-          Then remove the excessively privileged role (Storage Admin / Storage Object
-          Admin / Storage Object Creator) using:
-
-            gsutil iam ch -d <type>:<email_address>:<role> gs://artifacts.<project_id>.appspot.com
-
-          where:
-          <type> can be one of the following:
-            user, if the <email_address> is a Google account.
-            serviceAccount, if <email_address> specifies a Service account.
-            <email_address> can be one of the following:
-              a Google account (for example, someone@example.com).
-              a Cloud IAM service account.
-
-          To modify roles defined at the project level and subsequently inherited within the GCR
-          bucket, or the Service Account User role, extract the IAM policy file, modify it
-          accordingly and apply it using:
-
-            gcloud projects set-iam-policy <project_id> <policy_file>
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize cluster access to read-only for Container Image repositories (Manual)"
-        type: "manual"
-        remediation: |
-          For Images Hosted in AR:
-          Using Command Line:
-          Add artifactregistry.reader role
-
-            gcloud artifacts repositories add-iam-policy-binding <repository> \
-            --location=<repository-location> \
-            --member='serviceAccount:<email-address>' \
-            --role='roles/artifactregistry.reader'
-
-          Remove any roles other than artifactregistry.reader
-
-            gcloud artifacts repositories remove-iam-policy-binding <repository> \
-            --location <repository-location> \
-            --member='serviceAccount:<email-address>' \
-            --role='<role-name>'
-
-          For Images Hosted in GCR:
-          For an account explicitly granted to the bucket:
-          Firstly add read access to the Kubernetes Service Account:
-
-            gsutil iam ch <type>:<email_address>:objectViewer gs://artifacts.<project_id>.appspot.com
-
-            where:
-              <type> can be one of the following:
-                user, if the <email_address> is a Google account.
-                serviceAccount, if <email_address> specifies a Service account.
-                <email_address> can be one of the following:
-                  a Google account (for example, someone@example.com).
-                  a Cloud IAM service account.
-
-          Then remove the excessively privileged role (Storage Admin / Storage Object
-          Admin / Storage Object Creator) using:
-
-            gsutil iam ch -d <type>:<email_address>:<role> gs://artifacts.<project_id>.appspot.com
-
-          For an account that inherits access to the GCR Bucket through Project level
-          permissions, modify the Projects IAM policy file accordingly, then upload it using:
-
-            gcloud projects set-iam-policy <project_id> <policy_file>
-        scored: false
-
-      - id: 5.1.4
-        text: "Ensure only trusted container images are used (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Update the cluster to enable Binary Authorization:
-
-            gcloud container cluster update <cluster_name> --enable-binauthz
-
-          Create a Binary Authorization Policy using the Binary Authorization Policy Reference:
-          https://cloud.google.com/binary-authorization/docs/policy-yaml-reference for guidance.
-
-          Import the policy file into Binary Authorization:
-
-            gcloud container binauthz policy import <yaml_policy>
-        scored: false
-
-  - id: 5.2
-    text: "Identity and Access Management (IAM)"
-    checks:
-      - id: 5.2.1
-        text: "Ensure GKE clusters are not running using the Compute Engine default service account (Automated))"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a minimally privileged service account:
-
-            gcloud iam service-accounts create <node_sa_name> \
-              --display-name "GKE Node Service Account"
-            export NODE_SA_EMAIL=gcloud iam service-accounts list \
-              --format='value(email)' --filter='displayName:GKE Node Service Account'
-
-          Grant the following roles to the service account:
-
-            export PROJECT_ID=gcloud config get-value project
-            gcloud projects add-iam-policy-binding <project_id> --member \
-              serviceAccount:<node_sa_email> --role roles/monitoring.metricWriter
-            gcloud projects add-iam-policy-binding <project_id> --member \
-              serviceAccount:<node_sa_email> --role roles/monitoring.viewer
-            gcloud projects add-iam-policy-binding <project_id> --member \
-              serviceAccount:<node_sa_email> --role roles/logging.logWriter
-
-          To create a new Node pool using the Service account, run the following command:
-
-            gcloud container node-pools create <node_pool> \
-              --service-account=<sa_name>@<project_id>.iam.gserviceaccount.com \
-              --cluster=<cluster_name> --zone <compute_zone>
-
-          Note: The workloads will need to be migrated to the new Node pool, and the old node
-          pools that use the default service account should be deleted to complete the
-          remediation.
-        scored: false
-
-      - id: 5.2.2
-        text: "Prefer using dedicated GCP Service Accounts and Workload Identity (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-
-            gcloud container clusters update <cluster_name> --zone <cluster_zone> \
-            --workload-pool <project_id>.svc.id.goog
-
-          Note that existing Node pools are unaffected. New Node pools default to --workload-
-          metadata-from-node=GKE_METADATA_SERVER.
-
-          Then, modify existing Node pools to enable GKE_METADATA_SERVER:
-
-            gcloud container node-pools update <node_pool_name> --cluster <cluster_name> \
-              --zone <cluster_zone> --workload-metadata=GKE_METADATA
-
-          Workloads may need to be modified in order for them to use Workload Identity as
-          described within: https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity.
-          Also consider the effects on the availability of hosted workloads as Node pools
-          are updated. It may be more appropriate to create new Node Pools.
-        scored: false
-
-  - id: 5.3
-    text: "Cloud Key Management Service (Cloud KMS)"
-    checks:
-      - id: 5.3.1
-        text: "Ensure Kubernetes Secrets are encrypted using keys managed in Cloud KMS (Automated)"
-        type: "manual"
-        remediation: |
-          To create a key:
-          Create a key ring:
-
-            gcloud kms keyrings create <ring_name> --location <location> --project \
-              <key_project_id>
-
-          Create a key:
-
-            gcloud kms keys create <key_name> --location <location> --keyring <ring_name> \
-              --purpose encryption --project <key_project_id>
-
-          Grant the Kubernetes Engine Service Agent service account the Cloud KMS
-          CryptoKey Encrypter/Decrypter role:
-
-            gcloud kms keys add-iam-policy-binding <key_name> --location <location> \
-            --keyring <ring_name> --member serviceAccount:<service_account_name> \
-            --role roles/cloudkms.cryptoKeyEncrypterDecrypter --project <key_project_id>
-
-          To create a new cluster with Application-layer Secrets Encryption:
-
-            gcloud container clusters create <cluster_name> --cluster-version=latest \
-            --zone <zone> \
-            --database-encryption-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name> \
-            --project <cluster_project_id>
-
-          To enable on an existing cluster:
-
-            gcloud container clusters update <cluster_name> --zone <zone> \
-            --database-encryption-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name> \
-            --project <cluster_project_id>
-        scored: false
-
-  - id: 5.4
-    text: "Node Metadata"
-    checks:
-      - id: 5.4.1
-        text: "Ensure the GKE Metadata Server is Enabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-
-            gcloud container clusters update <cluster_name> --identity-namespace=<project_id>.svc.id.goog
-
-          Note that existing Node pools are unaffected. New Node pools default to --workload-
-          metadata-from-node=GKE_METADATA_SERVER.
-
-          To modify an existing Node pool to enable GKE Metadata Server:
-
-            gcloud container node-pools update <node_pool_name> --cluster=<cluster_name> \
-              --workload-metadata-from-node=GKE_METADATA_SERVER
-
-          Workloads may need modification in order for them to use Workload Identity as
-          described within: https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity.
-        scored: false
-
-  - id: 5.5
-    text: "Node Configuration and Maintenance"
-    checks:
-      - id: 5.5.1
-        text: "Ensure Container-Optimized OS (cos_containerd) is used for GKE node images (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To set the node image to cos for an existing cluster's Node pool:
-
-            gcloud container clusters upgrade <cluster_name> --image-type cos_containerd \
-              --zone <compute_zone> --node-pool <node_pool_name>
-        scored: false
-
-      - id: 5.5.2
-        text: "Ensure Node Auto-Repair is enabled for GKE nodes (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable node auto-repair for an existing cluster's Node pool:
-
-            gcloud container node-pools update <node_pool_name> --cluster <cluster_name> \
-              --zone <compute_zone> --enable-autorepair
-        scored: false
-
-      - id: 5.5.3
-        text: "Ensure Node Auto-Upgrade is enabled for GKE nodes (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable node auto-upgrade for an existing cluster's Node pool, run the following
-          command:
-
-            gcloud container node-pools update <node_pool_name> --cluster <cluster_name> \
-              --zone <cluster_zone> --enable-autoupgrade
-        scored: false
-
-      - id: 5.5.4
-        text: "When creating New Clusters - Automate GKE version management using Release Channels (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a new cluster by running the following command:
-
-            gcloud container clusters create <cluster_name> --zone <cluster_zone> \
-              --release-channel <release_channel>
-
-          where <release_channel> is stable or regular, according to requirements.
-        scored: false
-
-      - id: 5.5.5
-        text: "Ensure Shielded GKE Nodes are Enabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To migrate an existing cluster, the flag --enable-shielded-nodes needs to be
-          specified in the cluster update command:
-
-            gcloud container clusters update <cluster_name> --zone <cluster_zone> \
-              --enable-shielded-nodes
-        scored: false
-
-      - id: 5.5.6
-        text: "Ensure Integrity Monitoring for Shielded GKE Nodes is Enabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a Node pool within the cluster with Integrity Monitoring enabled, run the
-          following command:
-
-            gcloud container node-pools create <node_pool_name> --cluster <cluster_name> \
-              --zone <compute_zone> --shielded-integrity-monitoring
-
-          Workloads from existing non-conforming Node pools will need to be migrated to the
-          newly created Node pool, then delete non-conforming Node pools to complete the
-          remediation
-        scored: false
-
-      - id: 5.5.7
-        text: "Ensure Secure Boot for Shielded GKE Nodes is Enabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a Node pool within the cluster with Secure Boot enabled, run the following
-          command:
-
-            gcloud container node-pools create <node_pool_name> --cluster <cluster_name> \
-              --zone <compute_zone> --shielded-secure-boot
-
-          Workloads will need to be migrated from existing non-conforming Node pools to the
-          newly created Node pool, then delete the non-conforming pools.
-        scored: false
-
-  - id: 5.6
-    text: "Cluster Networking"
-    checks:
-      - id: 5.6.1
-        text: "Enable VPC Flow Logs and Intranode Visibility (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          1. Find the subnetwork name associated with the cluster.
-
-            gcloud container clusters describe <cluster_name> \
-              --region <cluster_region> - -format json | jq '.subnetwork'
-
-          2. Update the subnetwork to enable VPC Flow Logs.
-            gcloud compute networks subnets update <subnet_name> --enable-flow-logs
-        scored: false
-
-      - id: 5.6.2
-        text: "Ensure use of VPC-native clusters (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable Alias IP on a new cluster, run the following command:
-
-            gcloud container clusters create <cluster_name> --zone <compute_zone> \
-              --enable-ip-alias
-
-          If using Autopilot configuration mode:
-
-            gcloud container clusters create-auto <cluster_name> \
-              --zone <compute_zone>
-        scored: false
-
-      - id: 5.6.3
-        text: "Ensure Control Plane Authorized Networks is Enabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable Control Plane Authorized Networks for an existing cluster, run the following
-          command:
-
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-              --enable-master-authorized-networks
-
-          Along with this, you can list authorized networks using the --master-authorized-networks
-          flag which contains a list of up to 20 external networks that are allowed to
-          connect to your cluster's control plane through HTTPS. You provide these networks as
-          a comma-separated list of addresses in CIDR notation (such as 90.90.100.0/24).
-        scored: false
-
-      - id: 5.6.4
-        text: "Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a cluster with a Private Endpoint enabled and Public Access disabled by including
-          the --enable-private-endpoint flag within the cluster create command:
-
-            gcloud container clusters create <cluster_name> --enable-private-endpoint
-
-          Setting this flag also requires the setting of --enable-private-nodes, --enable-ip-alias
-          and --master-ipv4-cidr=<master_cidr_range>.
-        scored: false
-
-      - id: 5.6.5
-        text: "Ensure clusters are created with Private Nodes (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a cluster with Private Nodes enabled, include the --enable-private-nodes
-          flag within the cluster create command:
-
-            gcloud container clusters create <cluster_name> --enable-private-nodes
-
-          Setting this flag also requires the setting of --enable-ip-alias and
-          --master-ipv4-cidr=<master_cidr_range>.
-        scored: false
-
-      - id: 5.6.6
-        text: "Consider firewalling GKE worker nodes (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Use the following command to generate firewall rules, setting the variables as
-          appropriate:
-
-            gcloud compute firewall-rules create <firewall_rule_name> \
-            --network <network> --priority <priority> --direction <direction> \
-            --action <action> --target-tags <tag> \
-            --target-service-accounts <service_account> \
-            --source-ranges <source_cidr_range> --source-tags <source_tags> \
-            --source-service-accounts <source_service_account> \
-            --destination-ranges <destination_cidr_range> --rules <rules>
-        scored: false
-
-      - id: 5.6.7
-        text: "Ensure use of Google-managed SSL Certificates (Automated)"
-        type: "manual"
-        remediation: |
-          If services of type:LoadBalancer are discovered, consider replacing the Service with
-          an Ingress.
-
-          To configure the Ingress and use Google-managed SSL certificates, follow the
-          instructions as listed at: https://cloud.google.com/kubernetes-engine/docs/how-
-          to/managed-certs.
-        scored: false
-
-  - id: 5.7
-    text: "Logging"
-    checks:
-      - id: 5.7.1
-        text: "Ensure Logging and Cloud Monitoring is Enabled (Automated)"
-        type: "manual"
-        remediation: |
-          To enable Logging for an existing cluster, run the following command:
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-            --logging=<components_to_be_logged>
-
-          See https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--logging
-          for a list of available components for logging.
-
-          To enable Cloud Monitoring for an existing cluster, run the following command:
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-            --monitoring=<components_to_be_logged>
-
-          See https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--
-          monitoring for a list of available components for Cloud Monitoring.
-        scored: false
-
-      - id: 5.7.2
-        text: "Enable Linux auditd logging (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Download the example manifests:
-            curl https://raw.githubusercontent.com/GoogleCloudPlatform/k8s-node-tools/master/os-audit/cos-auditd-logging.yaml > cos-auditd-logging.yaml
-
-          Edit the example manifests if needed. Then, deploy them:
-            kubectl apply -f cos-auditd-logging.yaml
-
-          Verify that the logging Pods have started. If a different Namespace was defined in the
-          manifests, replace cos-auditd with the name of the namespace being used:
-            kubectl get pods --namespace=cos-auditd
-        scored: false
-
-  - id: 5.8
-    text: "Authentication and Authorization"
-    checks:
-      - id: 5.8.1
-        text: "Ensure authentication using Client Certificates is Disabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a new cluster without a Client Certificate:
-            gcloud container clusters create [CLUSTER_NAME] \
-              --no-issue-client-certificate
-        scored: false
-
-      - id: 5.8.2
-        text: "Manage Kubernetes RBAC users with Google Groups for GKE (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Follow the G Suite Groups instructions at: https://cloud.google.com/kubernetes-
-          engine/docs/how-to/role-based-access-control#google-groups-for-gke.
-
-          Then, create a cluster with:
-            gcloud container clusters create <cluster_name> --security-group <security_group_name>
-
-          Finally create Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings that
-          reference the G Suite Groups.
-        scored: false
-
-      - id: 5.8.3
-        text: "Ensure Legacy Authorization (ABAC) is Disabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To disable Legacy Authorization for an existing cluster, run the following command:
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-              --no-enable-legacy-authorization
-        scored: false
-
-  - id: 5.9
-    text: "Storage"
-    checks:
-      - id: 5.9.1
-        text: "Enable Customer-Managed Encryption Keys (CMEK) for GKE Persistent Disks (PD) (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Follow the instructions detailed at: https://cloud.google.com/kubernetes-engine/docs/how-to/using-cmek.
-        scored: false
-
-      - id: 5.9.2
-        text: "Enable Customer-Managed Encryption Keys (CMEK) for Boot Disks (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a new node pool using customer-managed encryption keys for the node boot
-          disk, of <disk_type> either pd-standard or pd-ssd:
-            gcloud container node-pools create <cluster_name> --disk-type <disk_type> \
-            --boot-disk-kms-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name>
-
-          Create a cluster using customer-managed encryption keys for the node boot disk, of
-          <disk_type> either pd-standard or pd-ssd:
-            gcloud container clusters create <cluster_name> --disk-type <disk_type> \
-            --boot-disk-kms-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name>
-        scored: false
-
-  - id: 5.10
-    text: "Other Cluster Configurations"
-    checks:
-      - id: 5.10.1
-        text: "Ensure Kubernetes Web UI is Disabled (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To disable the Kubernetes Dashboard on an existing cluster, run the following
-          command:
-            gcloud container clusters update <cluster_name> --zone <zone> \
-              --update-addons=KubernetesDashboard=DISABLED
-        scored: false
-
-      - id: 5.10.2
-        text: "Ensure that Alpha clusters are not used for production workloads (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Upon creating a new cluster
-            gcloud container clusters create [CLUSTER_NAME] \
-              --zone [COMPUTE_ZONE]
-
-          Do not use the --enable-kubernetes-alpha argument.
-        scored: false
-
-      - id: 5.10.3
-        text: "Consider GKE Sandbox for running untrusted workloads (Manual)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable GKE Sandbox on an existing cluster, a new Node pool must be created,
-          which can be done using:
-            gcloud container node-pools create <node_pool_name> --zone <compute-zone> \
-              --cluster <cluster_name> --image-type=cos_containerd --sandbox="type=gvisor"
-        scored: false
-
-      - id: 5.10.4
-        text: "Ensure use of Binary Authorization (Automated)"
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Update the cluster to enable Binary Authorization:
-            gcloud container cluster update <cluster_name> --zone <compute_zone> \
-            --binauthz-evaluation-mode=<evaluation_mode>
-
-          Example:
-            gcloud container clusters update $CLUSTER_NAME --zone $COMPUTE_ZONE \
-            --binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE
-
-          See: https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--binauthz-evaluation-mode
-          for more details around the evaluation modes available.
-
-          Create a Binary Authorization Policy using the Binary Authorization Policy Reference:
-          https://cloud.google.com/binary-authorization/docs/policy-yaml-reference for guidance.
-
-          Import the policy file into Binary Authorization:
-            gcloud container binauthz policy import <yaml_policy>
-        scored: false
-
-      - id: 5.10.5
-        text: "Enable Security Posture (Manual)"
-        type: "manual"
-        remediation: |
-          Enable security posture via the UI, gCloud or API.
-          https://cloud.google.com/kubernetes-engine/docs/how-to/protect-workload-configuration
-        scored: false

cfg/gke-1.6.0/master.yaml

@@ -1,6 +0,0 @@
----
-controls:
-version: "gke-1.6.0"
-id: 1
-text: "Control Plane Components"
-type: "master"

cfg/gke-1.6.0/node.yaml

@@ -1,506 +0,0 @@
----
-controls:
-version: "gke-1.6.0"
-id: 3
-text: "Worker Node Security Configuration"
-type: "node"
-groups:
-  - id: 3.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 3.1.1
-        text: "Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on each worker node.
-          For example,
-
-            chmod 644 $proxykubeconfig
-        scored: true
-
-      - id: 3.1.2
-        text: "Ensure that the proxy kubeconfig file ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on each worker node.
-          For example:
-
-            chown root:root $proxykubeconfig
-        scored: true
-
-      - id: 3.1.3
-        text: "Ensure that the kubelet configuration file has permissions set to 600 (Manual)"
-        audit: '/bin/sh -c ''if test -e /home/kubernetes/kubelet-config.yaml; then stat -c permissions=%a /home/kubernetes/kubelet-config.yaml; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "600"
-        remediation: |
-          Run the following command (using the kubelet config file location)
-
-            chmod 644 /home/kubernetes/kubelet-config.yaml
-        scored: true
-
-      - id: 3.1.4
-        text: "Ensure that the kubelet configuration file ownership is set to root:root (Manual)"
-        audit: '/bin/sh -c ''if test -e /home/kubernetes/kubelet-config.yaml; then stat -c %U:%G /home/kubernetes/kubelet-config.yaml; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identied in the Audit step)
-
-            chown root:root /home/kubernetes/kubelet-config.yaml
-        scored: true
-
-  - id: 3.2
-    text: "Kubelet"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that the Anonymous Auth is Not Enabled (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: "--anonymous-auth"
-              path: '{.authentication.anonymous.enabled}'
-              compare:
-                op: eq
-                value: false
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-
-            ps -ef | grep kubelet
-
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-
-            sudo less /home/kubernetes/kubelet-config.yaml
-
-          Disable Anonymous Authentication by setting the following parameter:
-
-            "authentication": { "anonymous": { "enabled": false } }
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-
-            --anonymous-auth=false
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-            systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.2
-        text: "Ensure that the --authorization-mode argument is not set to AlwaysAllow (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: --authorization-mode
-              path: '{.authorization.mode}'
-              compare:
-                op: nothave
-                value: AlwaysAllow
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-
-            ps -ef | grep kubelet
-
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-
-            sudo less /path/to/kubelet-config.json
-
-          Enable Webhook Authentication by setting the following parameter:
-
-            "authentication": { "webhook": { "enabled": true } }
-
-          Next, set the Authorization Mode to Webhook by setting the following parameter:
-
-            "authorization": { "mode": "Webhook }
-
-          Finer detail of the authentication and authorization fields can be found in the
-          Kubelet Configuration documentation (https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/).
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-
-              --authentication-token-webhook
-              --authorization-mode=Webhook
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-            systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.3
-        text: "Ensure that a Client CA File is Configured (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: --client-ca-file
-              path: '{.authentication.x509.clientCAFile}'
-              set: true
-        remediation: |
-          Remediation Method 1:
-          If configuring via the Kubelet config file, you first need to locate the file.
-          To do this, SSH to each node and execute the following command to find the kubelet
-          process:
-
-            ps -ef | grep kubelet
-
-          The output of the above command provides details of the active kubelet process, from
-          which we can see the location of the configuration file provided to the kubelet service
-          with the --config argument. The file can be viewed with a command such as more or
-          less, like so:
-
-            sudo less /path/to/kubelet-config.json
-
-          Configure the client certificate authority file by setting the following parameter
-          appropriately:
-
-            "authentication": { "x509": {"clientCAFile": <path/to/client-ca-file> } }"
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file on each worker node and
-          ensure the below parameters are part of the KUBELET_ARGS variable string.
-          For systems using systemd, such as the Amazon EKS Optimised Amazon Linux or
-          Bottlerocket AMIs, then this file can be found at
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf. Otherwise,
-          you may need to look up documentation for your chosen operating system to determine
-          which service manager is configured:
-
-            --client-ca-file=<path/to/client-ca-file>
-
-          For Both Remediation Steps:
-          Based on your system, restart the kubelet service and check the service status.
-          The following example is for operating systems using systemd, such as the Amazon
-          EKS Optimised Amazon Linux or Bottlerocket AMIs, and invokes the systemctl
-          command. If systemctl is not available then you will need to look up documentation for
-          your chosen operating system to determine which service manager is configured:
-
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-            systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.4
-        text: "Ensure that the --read-only-port argument is disabled (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              set: false
-            - flag: "--read-only-port"
-              path: '{.readOnlyPort}'
-              compare:
-                op: eq
-                value: 0
-          bin_op: or
-        remediation: |
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to 0
-
-            "readOnlyPort": 0
-
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-
-            --read-only-port=0
-
-          For each remediation:
-          Based on your system, restart the kubelet service and check status
-
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-            systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.5
-        text: "Ensure that the --streaming-connection-idle-timeout argument is not set to 0 (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              compare:
-                op: noteq
-                value: 0
-            - flag: --streaming-connection-idle-timeout
-              path: '{.streamingConnectionIdleTimeout}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet-config.yaml and set the below parameter to a non-zero
-          value in the format of #h#m#s
-
-            "streamingConnectionIdleTimeout": "4h0m0s"
-
-          You should ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not
-          specify a --streaming-connection-idle-timeout argument because it would
-          override the Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-
-            --streaming-connection-idle-timeout=4h0m0s
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "streamingConnectionIdleTimeout": by extracting the live configuration from the
-          nodes running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster (https://kubernetes.io/docs/tasks/administer-cluster/reconfigure-kubelet/),
-          and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-
-            kubectl proxy --port=8001 &
-            export HOSTNAME_PORT=localhost:8001 (example host and port number)
-            export NODE_NAME=gke-cluster-1-pool1-5e572947-r2hg (example node name from
-            "kubectl get nodes")
-            curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediations:
-          Based on your system, restart the kubelet service and check status
-
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-            systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.6
-        text: "Ensure that the --make-iptables-util-chains argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: --make-iptables-util-chains
-              path: '{.makeIPTablesUtilChains}'
-              compare:
-                op: eq
-                value: true
-            - flag: --make-iptables-utils-chains
-              path: '{.makeIPTablesUtilChains}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet/kubelet-config.json and set the below parameter to
-          true
-
-            "makeIPTablesUtilChains": true
-
-          Ensure that /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf
-          does not set the --make-iptables-util-chains argument because that would
-          override your Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-
-            --make-iptables-util-chains:true
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "makeIPTablesUtilChains.: true by extracting the live configuration from the nodes
-          running kubelet.
-
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster (https://kubernetes.io/docs/tasks/administer-cluster/reconfigure-kubelet/),
-          and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-
-            kubectl proxy --port=8001 &
-            export HOSTNAME_PORT=localhost:8001 (example host and port number)
-            export NODE_NAME=gke-cluster-1-pool1-5e572947-r2hg (example node name from
-            "kubectl get nodes")
-            curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediations:
-          Based on your system, restart the kubelet service and check status
-
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-            systemctl status kubelet -l
-        scored: true
-
-      - id: 3.2.7
-        text: "Ensure that the --eventRecordQPS argument is set to 0 or a level which ensures appropriate event capture (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /etc/systemd/system/kubelet.service.d/10-kubeadm.conf"
-        tests:
-          test_items:
-            - flag: --event-qps
-              path: '{.eventRecordQPS}'
-              set: true
-              compare:
-                op: eq
-                value: 0
-        remediation: |
-          If using a Kubelet config file, edit the file to set eventRecordQPS: to an appropriate level.
-
-          If using command line arguments, edit the kubelet service file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
-          on each worker node and set the below parameter in KUBELET_SYSTEM_PODS_ARGS variable.
-
-          Based on your system, restart the kubelet service. For example:
-
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-        scored: true
-
-      - id: 3.2.8
-        text: "Ensure that the --rotate-certificates argument is not present or is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              compare:
-                op: eq
-                value: true
-            - flag: --rotate-certificates
-              path: '{.rotateCertificates}'
-              set: false
-          bin_op: or
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.yaml file
-          /etc/kubernetes/kubelet/kubelet-config.yaml and set the below parameter to
-          true
-
-            "RotateCertificate":true
-
-          Additionally, ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not set the --RotateCertificate
-          executable argument to false because this would override the Kubelet
-          config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-
-            --RotateCertificate=true
-        scored: true
-
-      - id: 3.2.9
-        text: "Ensure that the RotateKubeletServerCertificate argument is set to true (Automated)"
-        audit: "/bin/ps -fC $kubeletbin"
-        audit_config: "/bin/cat /home/kubernetes/kubelet-config.yaml"
-        tests:
-          test_items:
-            - flag: RotateKubeletServerCertificate
-              path: '{.featureGates.RotateKubeletServerCertificate}'
-              compare:
-                op: eq
-                value: true
-        remediation: |
-          Remediation Method 1:
-          If modifying the Kubelet config file, edit the kubelet-config.json file
-          /etc/kubernetes/kubelet-config.yaml and set the below parameter to true
-
-            "featureGates": {
-            "RotateKubeletServerCertificate":true
-            },
-
-          Additionally, ensure that the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf does not set
-          the --rotate-kubelet-server-certificate executable argument to false because
-          this would override the Kubelet config file.
-
-          Remediation Method 2:
-          If using executable arguments, edit the kubelet service file
-          /etc/systemd/system/kubelet.service.d/10-kubelet-args.conf on each
-          worker node and add the below parameter at the end of the KUBELET_ARGS variable
-          string.
-
-            --rotate-kubelet-server-certificate=true
-
-          Remediation Method 3:
-          If using the api configz endpoint consider searching for the status of
-          "RotateKubeletServerCertificate": by extracting the live configuration from the
-          nodes running kubelet.
-          **See detailed step-by-step configmap procedures in Reconfigure a Node's Kubelet in a
-          Live Cluster (https://kubernetes.io/docs/tasks/administer-cluster/reconfigure-kubelet/),
-          and then rerun the curl statement from audit process to check for kubelet
-          configuration changes
-
-            kubectl proxy --port=8001 &
-            export HOSTNAME_PORT=localhost:8001 (example host and port number)
-            export NODE_NAME=gke-cluster-1-pool1-5e572947-r2hg (example node name from
-            "kubectl get nodes")
-            curl -sSL "http://${HOSTNAME_PORT}/api/v1/nodes/${NODE_NAME}/proxy/configz"
-
-          For all three remediation methods:
-          Restart the kubelet service and check status. The example below is for when using
-          systemctl to manage services:
-
-            systemctl daemon-reload
-            systemctl restart kubelet.service
-            systemctl status kubelet -l
-        scored: true

cfg/gke-1.6.0/policies.yaml

@@ -1,238 +0,0 @@
----
-controls:
-version: "gke-1.6.0"
-id: 4
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 4.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Automated)"
-        type: "manual"
-        remediation: |
-          Identify all clusterrolebindings to the cluster-admin role. Check if they are used and
-          if they need this role or if they could use a role with fewer privileges.
-
-          Where possible, first bind users to a lower privileged role and then remove the
-          clusterrolebinding to the cluster-admin role :
-
-            kubectl delete clusterrolebinding [name]
-        scored: false
-
-      - id: 4.1.2
-        text: "Minimize access to secrets (Automated)"
-        type: "manual"
-        remediation: |
-          Where possible, remove get, list and watch access to secret objects in the cluster.
-        scored: false
-
-      - id: 4.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Automated)"
-        type: "manual"
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: false
-
-      - id: 4.1.4
-        text: "Ensure that default service accounts are not actively used (Automated)"
-        type: "manual"
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific
-          access to the Kubernetes API server.
-
-          Modify the configuration of each default service account to include this value
-
-            automountServiceAccountToken: false
-        scored: false
-
-      - id: 4.1.5
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Automated)"
-        type: "manual"
-        remediation: |
-          Modify the definition of pods and service accounts which do not need to mount service
-          account tokens to disable it.
-        scored: false
-
-      - id: 4.1.6
-        text: "Avoid use of system:masters group (Automated)"
-        type: "manual"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: false
-
-      - id: 4.1.7
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-      - id: 4.1.8
-        text: "Avoid bindings to system:anonymous (Automated)"
-        type: "manual"
-        remediation: |
-          Identify all clusterrolebindings and rolebindings to the user system:anonymous.
-          Check if they are used and review the permissions associated with the binding using the
-          commands in the Audit section above or refer to GKE documentation
-          (https://cloud.google.com/kubernetes-engine/docs/best-practices/rbac#detect-prevent-default).
-
-          Strongly consider replacing unsafe bindings with an authenticated, user-defined group.
-          Where possible, bind to non-default, user-defined groups with least-privilege roles.
-
-          If there are any unsafe bindings to the user system:anonymous, proceed to delete them
-          after consideration for cluster operations with only necessary, safer bindings.
-
-            kubectl delete clusterrolebinding [CLUSTER_ROLE_BINDING_NAME]
-            kubectl delete rolebinding [ROLE_BINDING_NAME] --namespace [ROLE_BINDING_NAMESPACE]
-        scored: false
-
-      - id: 4.1.9
-        text: "Avoid non-default bindings to system:unauthenticated (Automated)"
-        type: "manual"
-        remediation: |
-          Identify all non-default clusterrolebindings and rolebindings to the group
-          system:unauthenticated. Check if they are used and review the permissions
-          associated with the binding using the commands in the Audit section above or refer to
-          GKE documentation (https://cloud.google.com/kubernetes-engine/docs/best-practices/rbac#detect-prevent-default).
-
-          Strongly consider replacing non-default, unsafe bindings with an authenticated, user-
-          defined group. Where possible, bind to non-default, user-defined groups with least-
-          privilege roles.
-
-          If there are any non-default, unsafe bindings to the group system:unauthenticated,
-          proceed to delete them after consideration for cluster operations with only necessary,
-          safer bindings.
-
-            kubectl delete clusterrolebinding [CLUSTER_ROLE_BINDING_NAME]
-            kubectl delete rolebinding [ROLE_BINDING_NAME] --namespace [ROLE_BINDING_NAMESPACE]
-        scored: false
-
-      - id: 4.1.10
-        text: "Avoid non-default bindings to system:authenticated (Automated)"
-        type: "manual"
-        remediation: |
-          Identify all non-default clusterrolebindings and rolebindings to the group
-          system:authenticated. Check if they are used and review the permissions associated
-          with the binding using the commands in the Audit section above or refer to GKE
-          documentation.
-
-          Strongly consider replacing non-default, unsafe bindings with an authenticated, user-
-          defined group. Where possible, bind to non-default, user-defined groups with least-
-          privilege roles.
-
-          If there are any non-default, unsafe bindings to the group system:authenticated,
-          proceed to delete them after consideration for cluster operations with only necessary,
-          safer bindings.
-
-            kubectl delete clusterrolebinding [CLUSTER_ROLE_BINDING_NAME]
-            kubectl delete rolebinding [ROLE_BINDING_NAME] --namespace [ROLE_BINDING_NAMESPACE]
-        scored: false
-
-  - id: 4.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the cluster enforces Pod Security Standard Baseline profile or stricter for all namespaces. (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that Pod Security Admission is in place for every namespace which contains
-          user workloads.
-          Run the following command to enforce the Baseline profile in a namespace:
-
-            kubectl label namespace pod-security.kubernetes.io/enforce=baseline
-        scored: false
-
-  - id: 4.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 4.3.1
-        text: "Ensure that the CNI in use supports Network Policies (Manual)"
-        type: "manual"
-        remediation: |
-          To use a CNI plugin with Network Policy, enable Network Policy in GKE, and the CNI plugin
-          will be updated. See Recommendation 5.6.7.
-        scored: false
-
-      - id: 4.3.2
-        text: "Ensure that all Namespaces have Network Policies defined (Automated)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as needed.
-          See: https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy#creating_a_network_policy
-          for more information.
-        scored: false
-
-  - id: 4.4
-    text: "Secrets Management"
-    checks:
-      - id: 4.4.1
-        text: "Prefer using secrets as files over secrets as environment variables (Automated)"
-        type: "manual"
-        remediation: |
-          if possible, rewrite application code to read secrets from mounted secret files, rather than
-          from environment variables.
-        scored: false
-
-      - id: 4.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 4.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 4.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-          Also see recommendation 5.10.4.
-        scored: false
-
-  - id: 4.6
-    text: "General Policies"
-    checks:
-      - id: 4.6.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 4.6.2
-        text: "Ensure that the seccomp profile is set to RuntimeDefault in your pod definitions (Automated)"
-        type: "manual"
-        remediation: |
-          Use security context to enable the RuntimeDefault seccomp profile in your pod
-          definitions. An example is as below:
-
-            {
-              "namespace": "kube-system",
-              "name": "metrics-server-v0.7.0-dbcc8ddf6-gz7d4",
-              "seccompProfile": "RuntimeDefault"
-            }
-        scored: false
-
-      - id: 4.6.3
-        text: "Apply Security Context to Your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply security contexts to your pods. For a
-          suggested list of security contexts, you may refer to the CIS Google Container-
-          Optimized OS Benchmark.
-        scored: false
-
-      - id: 4.6.4
-        text: "The default namespace should not be used (Automated)"
-        type: "manual"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: false

cfg/gke-1.8.0/config.yaml

@@ -1,9 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml
-
-node:
-  proxy:
-    defaultkubeconfig: "/var/lib/kubelet/kubeconfig"
-
-  kubelet:
-    defaultconf: "/etc/kubernetes/kubelet-config.yaml"

cfg/gke-1.8.0/controlplane.yaml

@@ -1,6 +0,0 @@
----
-controls:
-version: "gke-1.8.0"
-id: 2
-text: "Control Plane Configuration"
-type: "controlplane"

cfg/gke-1.8.0/managedservices.yaml

@@ -1,719 +0,0 @@
----
-controls:
-version: "gke-1.8.0"
-id: 5
-text: "Managed Services"
-type: "managedservices"
-groups:
-  - id: 5.1
-    text: "Image Registry and Image Scanning"
-    checks:
-      - id: 5.1.1
-        text: "Ensure Image Vulnerability Scanning is enabled (Automated)"
-        audit: "gcloud services list --enabled"
-        type: "manual"
-        remediation: |
-          For Images Hosted in GCR:
-          Using Google Cloud Console
-          Go to GCR by visiting: https://console.cloud.google.com/gcr
-          Select Settings and, under the Vulnerability Scanning heading, click the TURN ON button.
-          Using Command Line
-          gcloud services enable containeranalysis.googleapis.com
-          For Images Hosted in AR:
-          Using Google Cloud Console
-          Go to GCR by visiting: https://console.cloud.google.com/artifacts
-          Select Settings and, under the Vulnerability Scanning heading, click the ENABLE button.
-          Using Command Line
-          gcloud services enable containerscanning.googleapis.com
-        scored: false
-
-      - id: 5.1.2
-        text: "Minimize user access to Container Image repositories (Manual)"
-        audit: |
-          gcloud projects get-iam-policy <project_id> \
-          --flatten="bindings[].members" \
-          --format='table(bindings.members,bindings.role)' \
-          --filter="bindings.role:roles/storage.admin OR bindings.role:roles/storage.objectAdmin OR bindings.role:roles/storage.objectCreator OR bindings.role:roles/storage.legacyBucketOwner OR bindings.role:roles/storage.legacyBucketWriter OR bindings.role:roles/storage.legacyObjectOwner"
-        type: "manual"
-        remediation: |
-          For Images Hosted in AR:
-          Using Command Line:
-
-            gcloud artifacts repositories set-iam-policy <repository-name> <path-to-policy-file> \
-              --location <repository-location>
-
-          To learn how to configure policy files see: https://cloud.google.com/artifact-registry/docs/access-control#grant
-
-          For Images Hosted in GCR:
-          Using Command Line:
-          To change roles at the GCR bucket level:
-          Firstly, run the following if read permissions are required:
-
-            gsutil iam ch <type>:<email_address>:objectViewer gs://artifacts.<project_id>.appspot.com
-
-          Then remove the excessively privileged role (Storage Admin / Storage Object
-          Admin / Storage Object Creator) using:
-
-            gsutil iam ch -d <type>:<email_address>:<role> gs://artifacts.<project_id>.appspot.com
-
-          where:
-          <type> can be one of the following:
-            user, if the <email_address> is a Google account.
-            serviceAccount, if <email_address> specifies a Service account.
-            <email_address> can be one of the following:
-              a Google account (for example, someone@example.com).
-              a Cloud IAM service account.
-
-          To modify roles defined at the project level and subsequently inherited within the GCR
-          bucket, or the Service Account User role, extract the IAM policy file, modify it
-          accordingly and apply it using:
-
-            gcloud projects set-iam-policy <project_id> <policy_file>
-        scored: false
-
-      - id: 5.1.3
-        text: "Minimize cluster access to read-only for Container Image repositories (Manual)"
-        audit: |
-          gcloud projects get-iam-policy <project_id> \
-          --flatten="bindings[].members" \
-          --format='table(bindings.members,bindings.role)' \
-          --filter="bindings.role:roles/storage.admin OR bindings.role:roles/storage.objectAdmin OR bindings.role:roles/storage.objectCreator OR bindings.role:roles/storage.legacyBucketOwner OR bindings.role:roles/storage.legacyBucketWriter OR bindings.role:roles/storage.legacyObjectOwner"
-        type: "manual"
-        remediation: |
-          For Images Hosted in AR:
-          Using Command Line:
-          Add artifactregistry.reader role
-
-            gcloud artifacts repositories add-iam-policy-binding <repository> \
-            --location=<repository-location> \
-            --member='serviceAccount:<email-address>' \
-            --role='roles/artifactregistry.reader'
-
-          Remove any roles other than artifactregistry.reader
-
-            gcloud artifacts repositories remove-iam-policy-binding <repository> \
-            --location <repository-location> \
-            --member='serviceAccount:<email-address>' \
-            --role='<role-name>'
-
-          For Images Hosted in GCR:
-          For an account explicitly granted to the bucket:
-          Firstly add read access to the Kubernetes Service Account:
-
-            gsutil iam ch <type>:<email_address>:objectViewer gs://artifacts.<project_id>.appspot.com
-
-            where:
-              <type> can be one of the following:
-                user, if the <email_address> is a Google account.
-                serviceAccount, if <email_address> specifies a Service account.
-                <email_address> can be one of the following:
-                  a Google account (for example, someone@example.com).
-                  a Cloud IAM service account.
-
-          Then remove the excessively privileged role (Storage Admin / Storage Object
-          Admin / Storage Object Creator) using:
-
-            gsutil iam ch -d <type>:<email_address>:<role> gs://artifacts.<project_id>.appspot.com
-
-          For an account that inherits access to the GCR Bucket through Project level
-          permissions, modify the Projects IAM policy file accordingly, then upload it using:
-
-            gcloud projects set-iam-policy <project_id> <policy_file>
-        scored: false
-
-      - id: 5.1.4
-        text: "Ensure only trusted container images are used (Manual)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq .binaryAuthorization
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Update the cluster to enable Binary Authorization:
-
-            gcloud container cluster update <cluster_name> --enable-binauthz
-
-          Create a Binary Authorization Policy using the Binary Authorization Policy Reference:
-          https://cloud.google.com/binary-authorization/docs/policy-yaml-reference for guidance.
-
-          Import the policy file into Binary Authorization:
-
-            gcloud container binauthz policy import <yaml_policy>
-        scored: false
-
-  - id: 5.2
-    text: "Identity and Access Management (IAM)"
-    checks:
-      - id: 5.2.1
-        text: "Ensure GKE clusters are not running using the Compute Engine default service account (Automated))"
-        audit: |
-          gcloud container node-pools describe $NODE_POOL --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.config.serviceAccount'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a minimally privileged service account:
-
-            gcloud iam service-accounts create <node_sa_name> \
-              --display-name "GKE Node Service Account"
-            export NODE_SA_EMAIL=gcloud iam service-accounts list \
-              --format='value(email)' --filter='displayName:GKE Node Service Account'
-
-          Grant the following roles to the service account:
-
-            export PROJECT_ID=gcloud config get-value project
-            gcloud projects add-iam-policy-binding <project_id> --member \
-              serviceAccount:<node_sa_email> --role roles/monitoring.metricWriter
-            gcloud projects add-iam-policy-binding <project_id> --member \
-              serviceAccount:<node_sa_email> --role roles/monitoring.viewer
-            gcloud projects add-iam-policy-binding <project_id> --member \
-              serviceAccount:<node_sa_email> --role roles/logging.logWriter
-
-          To create a new Node pool using the Service account, run the following command:
-
-            gcloud container node-pools create <node_pool> \
-              --service-account=<sa_name>@<project_id>.iam.gserviceaccount.com \
-              --cluster=<cluster_name> --zone <compute_zone>
-
-          Note: The workloads will need to be migrated to the new Node pool, and the old node
-          pools that use the default service account should be deleted to complete the
-          remediation.
-        scored: false
-
-      - id: 5.2.2
-        text: "Prefer using dedicated GCP Service Accounts and Workload Identity (Manual)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq .workloadIdentityConfig
-        type: "manual"
-        remediation: |
-          Using Command Line:
-
-            gcloud container clusters update <cluster_name> --zone <cluster_zone> \
-            --workload-pool <project_id>.svc.id.goog
-
-          Note that existing Node pools are unaffected. New Node pools default to --workload-
-          metadata-from-node=GKE_METADATA_SERVER.
-
-          Then, modify existing Node pools to enable GKE_METADATA_SERVER:
-
-            gcloud container node-pools update <node_pool_name> --cluster <cluster_name> \
-              --zone <cluster_zone> --workload-metadata=GKE_METADATA
-
-          Workloads may need to be modified in order for them to use Workload Identity as
-          described within: https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity.
-          Also consider the effects on the availability of hosted workloads as Node pools
-          are updated. It may be more appropriate to create new Node Pools.
-        scored: false
-
-  - id: 5.3
-    text: "Cloud Key Management Service (Cloud KMS)"
-    checks:
-      - id: 5.3.1
-        text: "Ensure Kubernetes Secrets are encrypted using keys managed in Cloud KMS (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.databaseEncryption'
-        type: "manual"
-        remediation: |
-          To create a key:
-          Create a key ring:
-
-            gcloud kms keyrings create <ring_name> --location <location> --project \
-              <key_project_id>
-
-          Create a key:
-
-            gcloud kms keys create <key_name> --location <location> --keyring <ring_name> \
-              --purpose encryption --project <key_project_id>
-
-          Grant the Kubernetes Engine Service Agent service account the Cloud KMS
-          CryptoKey Encrypter/Decrypter role:
-
-            gcloud kms keys add-iam-policy-binding <key_name> --location <location> \
-            --keyring <ring_name> --member serviceAccount:<service_account_name> \
-            --role roles/cloudkms.cryptoKeyEncrypterDecrypter --project <key_project_id>
-
-          To create a new cluster with Application-layer Secrets Encryption:
-
-            gcloud container clusters create <cluster_name> --cluster-version=latest \
-            --zone <zone> \
-            --database-encryption-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name> \
-            --project <cluster_project_id>
-
-          To enable on an existing cluster:
-
-            gcloud container clusters update <cluster_name> --zone <zone> \
-            --database-encryption-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name> \
-            --project <cluster_project_id>
-        scored: false
-
-  - id: 5.4
-    text: "Node Metadata"
-    checks:
-      - id: 5.4.1
-        text: "Ensure the GKE Metadata Server is Enabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.nodePools[].config.workloadMetadataConfig'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-
-            gcloud container clusters update <cluster_name> --identity-namespace=<project_id>.svc.id.goog
-
-          Note that existing Node pools are unaffected. New Node pools default to --workload-
-          metadata-from-node=GKE_METADATA_SERVER.
-
-          To modify an existing Node pool to enable GKE Metadata Server:
-
-            gcloud container node-pools update <node_pool_name> --cluster=<cluster_name> \
-              --workload-metadata-from-node=GKE_METADATA_SERVER
-
-          Workloads may need modification in order for them to use Workload Identity as
-          described within: https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity.
-        scored: false
-
-  - id: 5.5
-    text: "Node Configuration and Maintenance"
-    checks:
-      - id: 5.5.1
-        text: "Ensure Container-Optimized OS (cos_containerd) is used for GKE node images (Automated)"
-        audit: |
-          gcloud container node-pools describe $NODE_POOL --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.config.imageType'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To set the node image to cos for an existing cluster's Node pool:
-
-            gcloud container clusters upgrade <cluster_name> --image-type cos_containerd \
-              --zone <compute_zone> --node-pool <node_pool_name>
-        scored: false
-
-      - id: 5.5.2
-        text: "Ensure Node Auto-Repair is enabled for GKE nodes (Automated)"
-        audit: |
-          gcloud container node-pools describe $POOL_NAME --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.management'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable node auto-repair for an existing cluster's Node pool:
-
-            gcloud container node-pools update <node_pool_name> --cluster <cluster_name> \
-              --zone <compute_zone> --enable-autorepair
-        scored: false
-
-      - id: 5.5.3
-        text: "Ensure Node Auto-Upgrade is enabled for GKE nodes (Automated)"
-        audit: |
-          gcloud container node-pools describe $POOL_NAME --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.management'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable node auto-upgrade for an existing cluster's Node pool, run the following
-          command:
-
-            gcloud container node-pools update <node_pool_name> --cluster <cluster_name> \
-              --zone <cluster_zone> --enable-autoupgrade
-        scored: false
-
-      - id: 5.5.4
-        text: "When creating New Clusters - Automate GKE version management using Release Channels (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq .releaseChannel.channel
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a new cluster by running the following command:
-
-            gcloud container clusters create <cluster_name> --zone <cluster_zone> \
-              --release-channel <release_channel>
-
-          where <release_channel> is stable or regular, according to requirements.
-        scored: false
-
-      - id: 5.5.5
-        text: "Ensure Shielded GKE Nodes are Enabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.shieldedNodes'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To migrate an existing cluster, the flag --enable-shielded-nodes needs to be
-          specified in the cluster update command:
-
-            gcloud container clusters update <cluster_name> --zone <cluster_zone> \
-              --enable-shielded-nodes
-        scored: false
-
-      - id: 5.5.6
-        text: "Ensure Integrity Monitoring for Shielded GKE Nodes is Enabled (Automated)"
-        audit: |
-          gcloud container node-pools describe $POOL_NAME --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq .config.shieldedInstanceConfig
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a Node pool within the cluster with Integrity Monitoring enabled, run the
-          following command:
-
-            gcloud container node-pools create <node_pool_name> --cluster <cluster_name> \
-              --zone <compute_zone> --shielded-integrity-monitoring
-
-          Workloads from existing non-conforming Node pools will need to be migrated to the
-          newly created Node pool, then delete non-conforming Node pools to complete the
-          remediation
-        scored: false
-
-      - id: 5.5.7
-        text: "Ensure Secure Boot for Shielded GKE Nodes is Enabled (Automated)"
-        audit: |
-          gcloud container node-pools describe $POOL_NAME --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq .config.shieldedInstanceConfig
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a Node pool within the cluster with Secure Boot enabled, run the following
-          command:
-
-            gcloud container node-pools create <node_pool_name> --cluster <cluster_name> \
-              --zone <compute_zone> --shielded-secure-boot
-
-          Workloads will need to be migrated from existing non-conforming Node pools to the
-          newly created Node pool, then delete the non-conforming pools.
-        scored: false
-
-  - id: 5.6
-    text: "Cluster Networking"
-    checks:
-      - id: 5.6.1
-        text: "Enable VPC Flow Logs and Intranode Visibility (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.networkConfig.enableIntraNodeVisibility'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          1. Find the subnetwork name associated with the cluster.
-
-            gcloud container clusters describe <cluster_name> \
-              --region <cluster_region> - -format json | jq '.subnetwork'
-
-          2. Update the subnetwork to enable VPC Flow Logs.
-            gcloud compute networks subnets update <subnet_name> --enable-flow-logs
-        scored: false
-
-      - id: 5.6.2
-        text: "Ensure use of VPC-native clusters (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.ipAllocationPolicy.useIpAliases'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable Alias IP on a new cluster, run the following command:
-
-            gcloud container clusters create <cluster_name> --zone <compute_zone> \
-              --enable-ip-alias
-        scored: false
-
-      - id: 5.6.3
-        text: "Ensure Control Plane Authorized Networks is Enabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.masterAuthorizedNetworksConfig'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable Control Plane Authorized Networks for an existing cluster, run the following
-          command:
-
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-              --enable-master-authorized-networks
-
-          Along with this, you can list authorized networks using the --master-authorized-networks
-          flag which contains a list of up to 20 external networks that are allowed to
-          connect to your cluster's control plane through HTTPS. You provide these networks as
-          a comma-separated list of addresses in CIDR notation (such as 90.90.100.0/24).
-        scored: false
-
-      - id: 5.6.4
-        text: "Ensure clusters are created with Private Endpoint Enabled and Public Access Disabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.privateClusterConfig.enablePrivateEndpoint'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a cluster with a Private Endpoint enabled and Public Access disabled by including
-          the --enable-private-endpoint flag within the cluster create command:
-
-            gcloud container clusters create <cluster_name> --enable-private-endpoint
-
-          Setting this flag also requires the setting of --enable-private-nodes, --enable-ip-alias
-          and --master-ipv4-cidr=<master_cidr_range>.
-        scored: false
-
-      - id: 5.6.5
-        text: "Ensure clusters are created with Private Nodes (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.privateClusterConfig.enablePrivateNodes'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To create a cluster with Private Nodes enabled, include the --enable-private-nodes
-          flag within the cluster create command:
-
-            gcloud container clusters create <cluster_name> --enable-private-nodes
-
-          Setting this flag also requires the setting of --enable-ip-alias and
-          --master-ipv4-cidr=<master_cidr_range>.
-        scored: false
-
-      - id: 5.6.6
-        text: "Consider firewalling GKE worker nodes (Manual)"
-        audit: |
-          gcloud compute instances describe $INSTANCE_NAME --zone $COMPUTE_ZONE --format json | jq '{tags: .tags.items[], serviceaccount:.serviceAccounts[].email, network: .networkInterfaces[].network}'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Use the following command to generate firewall rules, setting the variables as
-          appropriate:
-
-            gcloud compute firewall-rules create <firewall_rule_name> \
-            --network <network> --priority <priority> --direction <direction> \
-            --action <action> --target-tags <tag> \
-            --target-service-accounts <service_account> \
-            --source-ranges <source_cidr_range> --source-tags <source_tags> \
-            --source-service-accounts <source_service_account> \
-            --destination-ranges <destination_cidr_range> --rules <rules>
-        scored: false
-
-      - id: 5.6.7
-        text: "Ensure use of Google-managed SSL Certificates (Automated)"
-        audit: |
-          svc_json="$(kubectl get svc -A -o json 2>/dev/null                || echo '{"items":[],"__err":"SVC_FORBIDDEN"}')"
-          ing_json="$(kubectl get ingress -A -o json 2>/dev/null            || echo '{"items":[],"__err":"INGRESS_FORBIDDEN"}')"
-          mc_json ="$(kubectl get managedcertificates -A -o json 2>/dev/null || echo '{"items":[],"__err":"MC_FORBIDDEN"}')"
-
-          printf '%s\n%s\n%s\n' "$svc_json" "$ing_json" "$mc_json" \
-          | jq -rs '
-            (.[0] // {}) as $svcsRaw |
-            (.[1] // {}) as $ingsRaw |
-            (.[2] // {}) as $mcsRaw |
-
-            # If any list failed, surface an error and DO NOT print the success string
-            if ($svcsRaw.__err or $ingsRaw.__err or $mcsRaw.__err) then
-              "ERROR_KUBECTL_LIST:" +
-              ([
-                ($svcsRaw.__err // empty),
-                ($ingsRaw.__err // empty),
-                ($mcsRaw.__err // empty)
-              ] | join(","))
-            else
-              ($svcsRaw.items // []) as $svcs |
-              ($ingsRaw.items // []) as $ings |
-              ($mcsRaw.items // []) as $mcs |
-
-              def trim: gsub("^\\s+|\\s+$";"");
-              def hasmc($ns;$name): any($mcs[]?; .metadata.namespace==$ns and .metadata.name==$name);
-
-              ([
-                # Public Services (not eligible for managed certs)
-                $svcs[]? | select(.spec.type=="LoadBalancer")
-                | "FOUND_PUBLIC_LB_SERVICE:\(.metadata.namespace // "default"):\(.metadata.name)"
-              ] + [
-                # Ingresses missing managed-certs annotation
-                $ings[]? as $i
-                | ($i.metadata.annotations."networking.gke.io/managed-certificates" // "") as $ann
-                | select($ann=="")
-                | "FOUND_INGRESS_WITHOUT_MANAGED_CERT:\($i.metadata.namespace // "default"):\($i.metadata.name)"
-              ] + [
-                # Ingresses referencing non-existent ManagedCertificate(s)
-                $ings[]? as $i
-                | ($i.metadata.annotations."networking.gke.io/managed-certificates" // "") as $ann
-                | select($ann!="")
-                | ($i.metadata.namespace // "default") as $ns
-                | ($ann | split(",") | map(trim) | map(select(length>0)) | .[]) as $mc
-                | select(hasmc($ns;$mc) | not)
-                | "FOUND_MISSING_MANAGED_CERT_RESOURCE:\($ns):\($i.metadata.name):cert=\($mc)"
-              ]) as $f
-              | if ($f|length)>0
-                  then $f[]
-                  else "ALL_INGRESSES_USE_MANAGED_CERTS_AND_NO_PUBLIC_LB_SERVICES"
-                end
-            end
-          '
-        tests:
-          test_items:
-            - flag: "ALL_INGRESSES_USE_MANAGED_CERTS_AND_NO_PUBLIC_LB_SERVICES"
-              set: true
-              compare:
-                op: eq
-                value: "ALL_INGRESSES_USE_MANAGED_CERTS_AND_NO_PUBLIC_LB_SERVICES"
-        remediation: |
-          If services of type:LoadBalancer are discovered, consider replacing the Service with
-          an Ingress.
-
-          To configure the Ingress and use Google-managed SSL certificates, follow the
-          instructions as listed at: https://cloud.google.com/kubernetes-engine/docs/how-
-          to/managed-certs.
-        scored: true
-
-  - id: 5.7
-    text: "Logging"
-    checks:
-      - id: 5.7.1
-        text: "Ensure Logging and Cloud Monitoring is Enabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.loggingService'
-        type: "manual"
-        remediation: |
-          To enable Logging for an existing cluster, run the following command:
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-            --logging=<components_to_be_logged>
-
-          See https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--logging
-          for a list of available components for logging.
-
-          To enable Cloud Monitoring for an existing cluster, run the following command:
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-            --monitoring=<components_to_be_logged>
-
-          See https://cloud.google.com/sdk/gcloud/reference/container/clusters/update#--
-          monitoring for a list of available components for Cloud Monitoring.
-        scored: false
-
-      - id: 5.7.2
-        text: "Enable Linux auditd logging (Manual)"
-        audit: |
-          kubectl get daemonsets -A -o json | jq '.items[] | select (.spec.template.spec.containers[].image | contains ("gcr.io/stackdriver-agents/stackdriver-logging-agent"))'| jq '{name: .metadata.name, annotations: .metadata.annotations."kubernetes.io/description", namespace: .metadata.namespace, status: .status}'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Download the example manifests:
-            curl https://raw.githubusercontent.com/GoogleCloudPlatform/k8s-node-tools/master/os-audit/cos-auditd-logging.yaml > cos-auditd-logging.yaml
-
-          Edit the example manifests if needed. Then, deploy them:
-            kubectl apply -f cos-auditd-logging.yaml
-
-          Verify that the logging Pods have started. If a different Namespace was defined in the
-          manifests, replace cos-auditd with the name of the namespace being used:
-            kubectl get pods --namespace=cos-auditd
-        scored: false
-
-  - id: 5.8
-    text: "Authentication and Authorization"
-    checks:
-      - id: 5.8.1
-        text: "Ensure authentication using Client Certificates is Disabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.masterAuth.clientKey'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a new cluster without a Client Certificate:
-            gcloud container clusters create [CLUSTER_NAME] \
-              --no-issue-client-certificate
-        scored: false
-
-      - id: 5.8.2
-        text: "Manage Kubernetes RBAC users with Google Groups for GKE (Manual)"
-        audit: |
-          gcloud container clusters create <cluster_name> --security-group <security_group_name>
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Follow the G Suite Groups instructions at: https://cloud.google.com/kubernetes-
-          engine/docs/how-to/role-based-access-control#google-groups-for-gke.
-
-          Then, create a cluster with:
-            gcloud container clusters create <cluster_name> --security-group <security_group_name>
-
-          Finally create Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings that
-          reference the G Suite Groups.
-        scored: false
-
-      - id: 5.8.3
-        text: "Ensure Legacy Authorization (ABAC) is Disabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.legacyAbac'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To disable Legacy Authorization for an existing cluster, run the following command:
-            gcloud container clusters update <cluster_name> --zone <compute_zone> \
-              --no-enable-legacy-authorization
-        scored: false
-
-  - id: 5.9
-    text: "Storage"
-    checks:
-      - id: 5.9.1
-        text: "Enable Customer-Managed Encryption Keys (CMEK) for GKE Persistent Disks (PD) (Manual)"
-        audit: |
-          gcloud compute disks describe $PV_NAME --zone $COMPUTE_ZONE --format json | jq '.diskEncryptionKey.kmsKeyName'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Follow the instructions detailed at: https://cloud.google.com/kubernetes-engine/docs/how-to/using-cmek.
-        scored: false
-
-      - id: 5.9.2
-        text: "Enable Customer-Managed Encryption Keys (CMEK) for Boot Disks (Automated)"
-        audit: |
-          gcloud container node-pools describe $NODE_POOL --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Create a new node pool using customer-managed encryption keys for the node boot
-          disk, of <disk_type> either pd-standard or pd-ssd:
-            gcloud container node-pools create <cluster_name> --disk-type <disk_type> \
-            --boot-disk-kms-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name>
-
-          Create a cluster using customer-managed encryption keys for the node boot disk, of
-          <disk_type> either pd-standard or pd-ssd:
-            gcloud container clusters create <cluster_name> --disk-type <disk_type> \
-            --boot-disk-kms-key projects/<key_project_id>/locations/<location>/keyRings/<ring_name>/cryptoKeys/<key_name>
-        scored: false
-
-  - id: 5.10
-    text: "Other Cluster Configurations"
-    checks:
-      - id: 5.10.1
-        text: "Ensure Kubernetes Web UI is Disabled (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE  --format json | jq '.addonsConfig.kubernetesDashboard'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To disable the Kubernetes Dashboard on an existing cluster, run the following
-          command:
-            gcloud container clusters update <cluster_name> --zone <zone> \
-              --update-addons=KubernetesDashboard=DISABLED
-        scored: false
-
-      - id: 5.10.2
-        text: "Ensure that Alpha clusters are not used for production workloads (Automated)"
-        audit: |
-          gcloud container clusters describe $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.enableKubernetesAlpha'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          Upon creating a new cluster
-            gcloud container clusters create [CLUSTER_NAME] \
-              --zone [COMPUTE_ZONE]
-
-          Do not use the --enable-kubernetes-alpha argument.
-        scored: false
-
-      - id: 5.10.3
-        text: "Consider GKE Sandbox for running untrusted workloads (Manual)"
-        audit: |
-          gcloud container node-pools describe $NODE_POOL --cluster $CLUSTER_NAME --zone $COMPUTE_ZONE --format json | jq '.config.sandboxConfig'
-        type: "manual"
-        remediation: |
-          Using Command Line:
-          To enable GKE Sandbox on an existing cluster, a new Node pool must be created,
-          which can be done using:
-            gcloud container node-pools create <node_pool_name> --zone <compute-zone> \
-              --cluster <cluster_name> --image-type=cos_containerd --sandbox="type=gvisor"
-        scored: false
-
-      - id: 5.10.5
-        text: "Enable Security Posture (Manual)"
-        audit: "gcloud container clusters --location describe"
-        type: "manual"
-        remediation: |
-          Enable security posture via the UI, gCloud or API.
-          https://cloud.google.com/kubernetes-engine/docs/how-to/protect-workload-configuration
-        scored: false

cfg/gke-1.8.0/master.yaml

@@ -1,6 +0,0 @@
----
-controls:
-version: "gke-1.8.0"
-id: 1
-text: "Control Plane Components"
-type: "master"

cfg/gke-1.8.0/node.yaml

@@ -1,65 +0,0 @@
----
-controls:
-version: "gke-1.8.0"
-id: 3
-text: "Worker Nodes"
-type: "node"
-groups:
-  - id: 3.1
-    text: "Worker Node Configuration Files"
-    checks:
-      - id: 3.1.1
-        text: "Ensure that the kubeconfig file permissions are set to 644 or more restrictive (Automated)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c permissions=%a $proxykubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the below command (based on the file location on your system) on each worker node.
-          For example,
-
-            chmod 644 $proxykubeconfig
-        scored: true
-
-      - id: 3.1.2
-        text: "Ensure that the kubelet kubeconfig file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $proxykubeconfig; then stat -c %U:%G $proxykubeconfig; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the below command (based on the file location on your system) on each worker node.
-          For example:
-
-            chown root:root $proxykubeconfig
-        scored: true
-
-      - id: 3.1.3
-        text: "Ensure that the kubelet configuration file has permissions set to 644 (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c permissions=%a $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: "permissions"
-              compare:
-                op: bitmask
-                value: "644"
-        remediation: |
-          Run the following command (using the kubelet config file location)
-
-            chmod 644 $kubeletconf
-        scored: true
-
-      - id: 3.1.4
-        text: "Ensure that the kubelet configuration file ownership is set to root:root (Automated)"
-        audit: '/bin/sh -c ''if test -e $kubeletconf; then stat -c %U:%G $kubeletconf; fi'' '
-        tests:
-          test_items:
-            - flag: root:root
-        remediation: |
-          Run the following command (using the config file location identied in the Audit step)
-
-            chown root:root $kubeletconf
-        scored: true

cfg/gke-1.8.0/policies.yaml

@@ -1,473 +0,0 @@
----
-controls:
-version: "gke-1.8.0"
-id: 4
-text: "Kubernetes Policies"
-type: "policies"
-groups:
-  - id: 4.1
-    text: "RBAC and Service Accounts"
-    checks:
-      - id: 4.1.1
-        text: "Ensure that the cluster-admin role is only used where required (Automated)"
-        audit: |
-          kubectl get clusterrolebindings -o json | jq -r '
-            [
-              .items[]
-              | select(.roleRef.name == "cluster-admin")
-              | .subjects[]?
-              | select(.kind != "Group" or .name != "system:masters")
-            ]
-            | if length == 0
-              then "NO_CLUSTER_ADMIN_BINDINGS"
-              else "FOUND_CLUSTER_ADMIN_BINDING"
-              end
-          '
-        tests:
-          test_items:
-            - flag: "NO_CLUSTER_ADMIN_BINDINGS"
-              set: true
-              compare:
-                op: eq
-                value: "NO_CLUSTER_ADMIN_BINDINGS"
-        remediation: |
-          Identify all ClusterRoleBindings to the "cluster-admin" role and review their subjects:
-
-            kubectl get clusterrolebindings -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECTS:.subjects[*].name | grep cluster-admin
-
-          If non-system principals (users, groups, or service accounts) do not strictly require cluster-admin,
-          rebind them to a least-privileged (Cluster)Role and then remove the excessive binding:
-
-            kubectl delete clusterrolebinding <binding-name>
-
-          Notes:
-          - Do not modify bindings with the "system:" prefix that are required for core components.
-          - Prefer assigning narrowly scoped Roles/ClusterRoles that grant only the permissions needed.
-        scored: true
-
-      - id: 4.1.2
-        text: "Minimize access to secrets (Automated)"
-        audit: |
-          count=$(kubectl get roles --all-namespaces -o json | jq '
-            .items[]
-            | select(.rules[]?
-              | (.resources[]? == "secrets")
-              and ((.verbs[]? == "get") or (.verbs[]? == "list") or (.verbs[]? == "watch"))
-            )' | wc -l)
-
-          if [ "$count" -gt 0 ]; then
-            echo "SECRETS_ACCESS_FOUND"
-          fi
-        tests:
-          test_items:
-            - flag: "SECRETS_ACCESS_FOUND"
-              set: false
-        remediation: |
-          Where possible, remove get, list and watch access to Secret objects in the cluster.
-        scored: true
-
-      - id: 4.1.3
-        text: "Minimize wildcard use in Roles and ClusterRoles (Automated)"
-        audit: |
-          wildcards=$(kubectl get roles --all-namespaces -o json | jq '
-            .items[] | select(
-              .rules[]? | (.verbs[]? == "*" or .resources[]? == "*" or .apiGroups[]? == "*")
-            )' | wc -l)
-
-          wildcards_clusterroles=$(kubectl get clusterroles -o json | jq '
-            .items[] | select(
-              .rules[]? | (.verbs[]? == "*" or .resources[]? == "*" or .apiGroups[]? == "*")
-            )' | wc -l)
-
-          total=$((wildcards + wildcards_clusterroles))
-
-          if [ "$total" -gt 0 ]; then
-            echo "wildcards_present"
-          fi
-        tests:
-          test_items:
-            - flag: wildcards_present
-              set: false
-        remediation: |
-          Where possible replace any use of wildcards in clusterroles and roles with specific
-          objects or actions.
-        scored: true
-
-      - id: 4.1.4
-        text: "Ensure that default service accounts are not actively used (Automated)"
-        audit: |
-          echo "🔹 Default Service Accounts with automountServiceAccountToken enabled:"
-          default_sa_count=$(kubectl get serviceaccounts --all-namespaces -o json | jq '
-            [.items[] | select(.metadata.name == "default" and (.automountServiceAccountToken != false))] | length')
-          if [ "$default_sa_count" -gt 0 ]; then
-            echo "default_sa_not_auto_mounted"
-          fi
-
-          echo "\n🔹 Pods using default ServiceAccount:"
-          pods_using_default_sa=$(kubectl get pods --all-namespaces -o json | jq '
-            [.items[] | select(.spec.serviceAccountName == "default")] | length')
-          if [ "$pods_using_default_sa" -gt 0 ]; then
-            echo "default_sa_used_in_pods"
-          fi
-        tests:
-          test_items:
-            - flag: default_sa_not_auto_mounted
-              set: false
-            - flag: default_sa_used_in_pods
-              set: false
-        remediation: |
-          Create explicit service accounts wherever a Kubernetes workload requires specific
-          access to the Kubernetes API server.
-
-          Modify the configuration of each default service account to include this value
-
-            automountServiceAccountToken: false
-        scored: true
-
-      - id: 4.1.5
-        text: "Ensure that Service Account Tokens are only mounted where necessary (Automated)"
-        audit: |
-          echo "🔹 Pods with automountServiceAccountToken enabled:"
-          pods_with_token_mount=$(kubectl get pods --all-namespaces -o json | jq '
-            [.items[] | select(.spec.automountServiceAccountToken != false)] | length')
-
-          if [ "$pods_with_token_mount" -gt 0 ]; then
-            echo "automountServiceAccountToken"
-          fi
-        tests:
-          test_items:
-            - flag: automountServiceAccountToken
-              set: false
-        remediation: |
-          Modify the definition of pods and service accounts which do not need to mount service
-          account tokens to disable it.
-        scored: true
-
-      - id: 4.1.6
-        text: "Avoid use of system:masters group (Automated)"
-        audit: |
-          found=0
-          for csr in $(kubectl get csr -o name 2>/dev/null | sed 's|^.*/||'); do
-            req=$(kubectl get csr "$csr" -o jsonpath='{.spec.request}' 2>/dev/null)
-            [ -z "$req" ] && continue
-            if echo "$req" | base64 -d 2>/dev/null | openssl req -noout -text 2>/dev/null | grep -q 'O = system:masters'; then
-              conds=$(kubectl get csr "$csr" -o json | jq -r '[.status.conditions[]?.type] | join(",")')
-              echo "FOUND_SYSTEM_MASTERS_CSR:${csr}:${conds:-NONE}"
-              found=1
-            fi
-          done
-          if [ "$found" -eq 0 ]; then
-            echo "NO_SYSTEM_MASTERS_CREDENTIALS_FOUND"
-          fi
-        tests:
-          test_items:
-            - flag: "NO_SYSTEM_MASTERS_CREDENTIALS_FOUND"
-              set: true
-              compare:
-                op: eq
-                value: "NO_SYSTEM_MASTERS_CREDENTIALS_FOUND"
-        remediation: |
-          Remove the system:masters group from all users in the cluster.
-        scored: true
-
-      - id: 4.1.7
-        text: "Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster (Manual)"
-        type: "manual"
-        remediation: |
-          Where possible, remove the impersonate, bind and escalate rights from subjects.
-        scored: false
-
-      - id: 4.1.8
-        text: "Avoid bindings to system:anonymous (Automated)"
-        audit: |
-          # Flags any ClusterRoleBinding/RoleBinding that targets the user "system:anonymous".
-          # Prints "NO_ANONYMOUS_BINDINGS" when none are found.
-          (
-            kubectl get clusterrolebindings -o json | jq -r '
-              .items[]
-              | select((.subjects | length) > 0)
-              | select(any(.subjects[]?;
-                  .kind=="User" and .name=="system:anonymous"
-                ))
-              | "FOUND_ANONYMOUS:ClusterRoleBinding:\(.metadata.name):ROLE=\(.roleRef.kind)/\(.roleRef.name)"
-            ';
-            kubectl get rolebindings -A -o json | jq -r '
-              .items[]
-              | select((.subjects | length) > 0)
-              | select(any(.subjects[]?;
-                  .kind=="User" and .name=="system:anonymous"
-                ))
-              | "FOUND_ANONYMOUS:RoleBinding:\(.metadata.namespace):\(.metadata.name):ROLE=\(.roleRef.kind)/\(.roleRef.name)"
-            '
-          ) | (grep -q '^FOUND_ANONYMOUS:' && cat || echo 'NO_ANONYMOUS_BINDINGS')
-        tests:
-          test_items:
-            - flag: "NO_ANONYMOUS_BINDINGS"
-              set: true
-              compare:
-                op: eq
-                value: "NO_ANONYMOUS_BINDINGS"
-        remediation: |
-          Identify all clusterrolebindings and rolebindings to the user system:anonymous.
-          Check if they are used and review the permissions associated with the binding using the
-          commands in the Audit section above or refer to GKE documentation
-          (https://cloud.google.com/kubernetes-engine/docs/best-practices/rbac#detect-prevent-default).
-
-          Strongly consider replacing unsafe bindings with an authenticated, user-defined group.
-          Where possible, bind to non-default, user-defined groups with least-privilege roles.
-
-          If there are any unsafe bindings to the user system:anonymous, proceed to delete them
-          after consideration for cluster operations with only necessary, safer bindings.
-
-            kubectl delete clusterrolebinding [CLUSTER_ROLE_BINDING_NAME]
-            kubectl delete rolebinding [ROLE_BINDING_NAME] --namespace [ROLE_BINDING_NAMESPACE]
-        scored: true
-
-      - id: 4.1.9
-        text: "Avoid non-default bindings to system:unauthenticated (Automated)"
-        audit: |
-          # Flags any non-default binding to the group "system:unauthenticated".
-          # Prints "NO_NON_DEFAULT_UNAUTH_BINDINGS" when none are found.
-          (
-            kubectl get clusterrolebindings -o json | jq -r '
-              .items[]
-              | select(.metadata.name != "system:public-info-viewer")
-              | select((.subjects | length) > 0)
-              | select(any(.subjects[]?;
-                  .kind=="Group" and .name=="system:unauthenticated"
-                ))
-              | "FOUND_UNAUTH:ClusterRoleBinding:\(.metadata.name):ROLE=\(.roleRef.kind)/\(.roleRef.name)"
-            ';
-            kubectl get rolebindings -A -o json | jq -r '
-              .items[]
-              | select((.subjects | length) > 0)
-              | select(any(.subjects[]?;
-                  .kind=="Group" and .name=="system:unauthenticated"
-                ))
-              | "FOUND_UNAUTH:RoleBinding:\(.metadata.namespace):\(.metadata.name):ROLE=\(.roleRef.kind)/\(.roleRef.name)"
-            '
-          ) | (grep -q "^FOUND_UNAUTH:" && cat || echo "NO_NON_DEFAULT_UNAUTH_BINDINGS")
-        tests:
-          test_items:
-            - flag: "NO_NON_DEFAULT_UNAUTH_BINDINGS"
-              set: true
-              compare:
-                op: eq
-                value: "NO_NON_DEFAULT_UNAUTH_BINDINGS"
-        remediation: |
-          Identify all non-default clusterrolebindings and rolebindings to the group
-          system:unauthenticated. Check if they are used and review the permissions
-          associated with the binding using the commands in the Audit section above or refer to
-          GKE documentation (https://cloud.google.com/kubernetes-engine/docs/best-practices/rbac#detect-prevent-default).
-
-          Strongly consider replacing non-default, unsafe bindings with an authenticated, user-
-          defined group. Where possible, bind to non-default, user-defined groups with least-
-          privilege roles.
-
-          If there are any non-default, unsafe bindings to the group system:unauthenticated,
-          proceed to delete them after consideration for cluster operations with only necessary,
-          safer bindings.
-
-            kubectl delete clusterrolebinding [CLUSTER_ROLE_BINDING_NAME]
-            kubectl delete rolebinding [ROLE_BINDING_NAME] --namespace [ROLE_BINDING_NAMESPACE]
-        scored: true
-
-      - id: 4.1.10
-        text: "Avoid non-default bindings to system:authenticated (Automated)"
-        audit: |
-          # Flags any non-default binding to the group "system:authenticated".
-          # Allowed defaults (CRB): system:basic-user, system:discovery
-          # Prints "NO_NON_DEFAULT_AUTH_BINDINGS" when none are found.
-          (
-            kubectl get clusterrolebindings -o json | jq -r '
-              .items[]
-              | select((.metadata.name != "system:basic-user") and (.metadata.name != "system:discovery"))
-              | select((.subjects | length) > 0)
-              | select(any(.subjects[]?;
-                  .kind=="Group" and .name=="system:authenticated"
-                ))
-              | "FOUND_AUTH:ClusterRoleBinding:\(.metadata.name):ROLE=\(.roleRef.kind)/\(.roleRef.name)"
-            ';
-            kubectl get rolebindings -A -o json | jq -r '
-              .items[]
-              | select((.subjects | length) > 0)
-              | select(any(.subjects[]?;
-                  .kind=="Group" and .name=="system:authenticated"
-                ))
-              | "FOUND_AUTH:RoleBinding:\(.metadata.namespace):\(.metadata.name):ROLE=\(.roleRef.kind)/\(.roleRef.name)"
-            '
-          ) | (grep -q "^FOUND_AUTH:" && cat || echo "NO_NON_DEFAULT_AUTH_BINDINGS")
-        tests:
-          test_items:
-            - flag: "NO_NON_DEFAULT_AUTH_BINDINGS"
-              set: true
-              compare:
-                op: eq
-                value: "NO_NON_DEFAULT_AUTH_BINDINGS"
-        remediation: |
-          Identify all non-default clusterrolebindings and rolebindings to the group
-          system:authenticated. Check if they are used and review the permissions associated
-          with the binding using the commands in the Audit section above or refer to GKE
-          documentation.
-
-          Strongly consider replacing non-default, unsafe bindings with an authenticated, user-
-          defined group. Where possible, bind to non-default, user-defined groups with least-
-          privilege roles.
-
-          If there are any non-default, unsafe bindings to the group system:authenticated,
-          proceed to delete them after consideration for cluster operations with only necessary,
-          safer bindings.
-
-            kubectl delete clusterrolebinding [CLUSTER_ROLE_BINDING_NAME]
-            kubectl delete rolebinding [ROLE_BINDING_NAME] --namespace [ROLE_BINDING_NAMESPACE]
-        scored: true
-
-  - id: 4.2
-    text: "Pod Security Standards"
-    checks:
-      - id: 4.2.1
-        text: "Ensure that the cluster enforces Pod Security Standard Baseline profile or stricter for all namespaces. (Manual)"
-        type: "manual"
-        remediation: |
-          Ensure that Pod Security Admission is in place for every namespace which contains
-          user workloads.
-          Run the following command to enforce the Baseline profile in a namespace:
-
-            kubectl label namespace pod-security.kubernetes.io/enforce=baseline
-        scored: false
-
-  - id: 4.3
-    text: "Network Policies and CNI"
-    checks:
-      - id: 4.3.1
-        text: "Ensure that the CNI in use supports Network Policies (Manual)"
-        type: "manual"
-        remediation: |
-          To use a CNI plugin with Network Policy, enable Network Policy in GKE, and the CNI plugin
-          will be updated. See Recommendation 5.6.7.
-        scored: false
-
-      - id: 4.3.2
-        text: "Ensure that all Namespaces have Network Policies defined (Automated)"
-        audit: |
-          (kubectl get ns -o json; kubectl get networkpolicy -A -o json) \
-          | jq -rs '
-            (.[0].items | map(.metadata.name)
-             | map(select(.!="kube-system" and .!="kube-public" and .!="kube-node-lease"))) as $ns
-            |
-            ( (.[1].items // [])
-              | sort_by(.metadata.namespace)
-              | group_by(.metadata.namespace)
-              | map({key: .[0].metadata.namespace, value: length})
-              | from_entries
-            ) as $np
-            |
-            [ $ns[] | select( ($np[.] // 0) == 0 ) ] as $missing
-            |
-            if ($missing|length)>0
-            then ($missing[] | "FOUND_NAMESPACE_WITHOUT_NETWORKPOLICY:"+.)
-            else "ALL_NAMESPACES_HAVE_NETWORK_POLICIES"
-            end
-          '
-        tests:
-          test_items:
-            - flag: "ALL_NAMESPACES_HAVE_NETWORK_POLICIES"
-              set: true
-              compare:
-                op: eq
-                value: "ALL_NAMESPACES_HAVE_NETWORK_POLICIES"
-        remediation: |
-          Follow the documentation and create NetworkPolicy objects as needed.
-          See: https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy#creating_a_network_policy
-          for more information.
-        scored: true
-
-  - id: 4.4
-    text: "Secrets Management"
-    checks:
-      - id: 4.4.1
-        text: "Prefer using secrets as files over secrets as environment variables (Automated)"
-        audit: |
-          output=$(kubectl get all --all-namespaces -o jsonpath='{range .items[?(@..secretKeyRef)]} {.kind} {.metadata.name} {"\n"}{end}')
-          if [ -z "$output" ]; then echo "NO_ENV_SECRET_REFERENCES"; else echo "ENV_SECRET_REFERENCES_FOUND"; fi
-        tests:
-          test_items:
-            - flag: "NO_ENV_SECRET_REFERENCES"
-              set: true
-              compare:
-                op: eq
-                value: "NO_ENV_SECRET_REFERENCES"
-        remediation: |
-          if possible, rewrite application code to read secrets from mounted secret files, rather than
-          from environment variables.
-        scored: true
-
-      - id: 4.4.2
-        text: "Consider external secret storage (Manual)"
-        type: "manual"
-        remediation: |
-          Refer to the secrets management options offered by your cloud provider or a third-party
-          secrets management solution.
-        scored: false
-
-  - id: 4.5
-    text: "Extensible Admission Control"
-    checks:
-      - id: 4.5.1
-        text: "Configure Image Provenance using ImagePolicyWebhook admission controller (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and setup image provenance.
-          Also see recommendation 5.10.4.
-        scored: false
-
-  - id: 4.6
-    text: "General Policies"
-    checks:
-      - id: 4.6.1
-        text: "Create administrative boundaries between resources using namespaces (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the documentation and create namespaces for objects in your deployment as you need
-          them.
-        scored: false
-
-      - id: 4.6.2
-        text: "Ensure that the seccomp profile is set to RuntimeDefault in your pod definitions (Automated)"
-        type: "manual"
-        remediation: |
-          Use security context to enable the RuntimeDefault seccomp profile in your pod
-          definitions. An example is as below:
-
-            {
-              "namespace": "kube-system",
-              "name": "metrics-server-v0.7.0-dbcc8ddf6-gz7d4",
-              "seccompProfile": "RuntimeDefault"
-            }
-        scored: false
-
-      - id: 4.6.3
-        text: "Apply Security Context to Your Pods and Containers (Manual)"
-        type: "manual"
-        remediation: |
-          Follow the Kubernetes documentation and apply security contexts to your pods. For a
-          suggested list of security contexts, you may refer to the CIS Google Container-
-          Optimized OS Benchmark.
-        scored: false
-
-      - id: 4.6.4
-        text: "The default namespace should not be used (Automated)"
-        audit: |
-          output=$(kubectl get all -n default --no-headers 2>/dev/null | grep -v '^service\s\+kubernetes\s' || true)
-          if [ -z "$output" ]; then echo "DEFAULT_NAMESPACE_UNUSED"; else echo "DEFAULT_NAMESPACE_IN_USE"; fi
-        tests:
-          test_items:
-            - flag: "DEFAULT_NAMESPACE_UNUSED"
-              set: true
-              compare:
-                op: eq
-                value: "DEFAULT_NAMESPACE_UNUSED"
-        remediation: |
-          Ensure that namespaces are created to allow for appropriate segregation of Kubernetes
-          resources and that all new resources are created in a specific namespace.
-        scored: true

cfg/k3s-cis-1.23/config.yaml

@@ -1,47 +0,0 @@
----
-## Version-specific settings that override the values in cfg/config.yaml
-
-master:
-  components:
-    - apiserver
-    - scheduler
-    - controllermanager
-    - etcd
-    - policies
-
-  apiserver:
-    bins:
-      - containerd
-
-  scheduler:
-    bins:
-      - containerd
-
-  controllermanager:
-    bins:
-      - containerd
-
-  etcd:
-    bins:
-      - containerd
-    datadirs:
-      - /var/lib/rancher/k3s/server/db/etcd
-  node:
-    components:
-      - kubelet
-      - proxy
-
-    kubelet:
-      bins:
-        - containerd
-      defaultkubeconfig: /var/lib/rancher/k3s/agent/kubelet.kubeconfig
-      defaultcafile: /var/lib/rancher/k3s/agent/client-ca.crt
-
-    proxy:
-      bins:
-        - containerd
-      defaultkubeconfig: /var/lib/rancher/k3s/agent/kubeproxy.kubeconfig
-
-  policies:
-    components:
-      - policies

cfg/k3s-cis-1.23/controlplane.yaml

@@ -1,47 +0,0 @@
----
-controls:
-version: "k3s-cis-1.23"
-id: 3
-text: "Control Plane Configuration"
-type: "controlplane"
-groups:
-  - id: 3.1
-    text: "Authentication and Authorization"
-    checks:
-      - id: 3.1.1
-        text: "Client certificate authentication should not be used for users (Manual)"
-        type: "manual"
-        remediation: |
-          Alternative mechanisms provided by Kubernetes such as the use of OIDC should be
-          implemented in place of client certificates.
-        scored: false
-
-  - id: 3.2
-    text: "Logging"
-    checks:
-      - id: 3.2.1
-        text: "Ensure that a minimal audit policy is created (Manual)"
-        audit: "journalctl -m -u k3s | grep 'Running kube-apiserver' | tail -n1 | grep 'audit-policy-file'"
-        type: "manual"
-        tests:
-          test_items:
-            - flag: "--audit-policy-file"
-              set: true
-        remediation: |
-          Create an audit policy file for your cluster.
-        scored: false
-
-      - id: 3.2.2
-        text: "Ensure that the audit policy covers key security concerns (Manual)"
-        type: "manual"
-        remediation: |
-          Review the audit policy provided for the cluster and ensure that it covers
-          at least the following areas,
-          - Access to Secrets managed by the cluster. Care should be taken to only
-            log Metadata for requests to Secrets, ConfigMaps, and TokenReviews, in
-            order to avoid risk of logging sensitive data.
-          - Modification of Pod and Deployment objects.
-          - Use of `pods/exec`, `pods/portforward`, `pods/proxy` and `services/proxy`.
-          For most requests, minimally logging at the Metadata level is recommended
-          (the most basic level of logging).
-        scored: false

cfg/k3s-cis-1.23/etcd.yaml

@@ -1,137 +0,0 @@
----
-controls:
-version: "k3s-cis-1.23"
-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: "grep -A 4 'client-transport-security' $etcdconf | grep -E 'cert-file|key-file'"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "cert-file"
-              set: true
-            - flag: "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: "grep -A 4 'client-transport-security' $etcdconf | grep 'client-cert-auth'"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--client-cert-auth"
-              set: true
-            - flag: "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: "if grep -q '^auto-tls' $etcdconf;then grep '^auto-tls' $etcdconf;else echo 'notset';fi"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--auto-tls"
-              set: false
-            - flag: "--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: "grep -A 4 'peer-transport-security' $etcdconf | grep -E 'cert-file|key-file'"
-        tests:
-          bin_op: and
-          test_items:
-            - flag: "cert-file"
-              set: true
-            - flag: "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: "grep -A 4 'peer-transport-security' $etcdconf | grep 'client-cert-auth'"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--client-cert-auth"
-              set: true
-            - flag: "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: "if grep -q '^peer-auto-tls' $etcdconf;then grep '^peer-auto-tls' $etcdconf;else echo 'notset';fi"
-        tests:
-          bin_op: or
-          test_items:
-            - flag: "--peer-auto-tls"
-              set: false
-            - flag: "--peer-auto-tls"
-              compare:
-                op: eq
-                value: false
-              set: true
-        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 (Manual)"
-        audit: "if grep -q 'trusted-ca-file' $etcdconf;then grep 'trusted-ca-file' $etcdconf;else echo 'notset';fi"
-        tests:
-          test_items:
-            - flag: "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: false