-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add CIS kubernetes CIS-1.9 for k8s v1.27 - v1.29 (#1617)
* Create cis-1.9 yamls and Update info
- policies.yaml
- 5.1.1 to 5.1.6 were adapted from Manual to Automated
- 5.1.3 got broken down into 5.1.3.1 and 5.1.3.2
- 5.1.6 got broken down into 5.1.6.1 and 5.1.6.2
- version was set to cis-1.9
- node.yaml master.yaml controlplane.yaml etcd.yaml
- version was set to cis-1.9
* Adapt master.yaml
- Expand 1.1.13/1.1.14 checks by adding super-admin.conf to the permission and ownership verification
- Remove 1.2.12 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used (Manual)
- Adjust numbering from 1.2.12 to 1.2.29
* Adjust policies.yaml
- Check 5.2.3 to 5.2.9 Title Automated to Manual
* Append node.yaml
- Create 4.3 kube-config group
- Create 4.3.1 Ensure that the kube-proxy metrics service is bound to localhost (Automated)
* Adjust policies 5.1.3 and 5.1.6
- Merge 5.1.3.1 and 5.1.3.2 into 5.1.3 (use role_is_compliant and clusterrole_is_compliant)
- Remove 5.1.6.1 and promote 5.1.6.2 to 5.1.6 since it natively covered 5.1.6.1 artifacts
* Add kubectl dependency and update publish
- Download kubectl (build stage) based on version and architecture
- Add binary checksum verification
- Use go env GOARCH for ARCH- Loading branch information
1 parent
d8fc376
commit 7027b6b
Showing
15 changed files
with
2,027 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| --- | ||
| ## Version-specific settings that override the values in cfg/config.yaml |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| --- | ||
| 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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,135 @@ | ||
| --- | ||
| 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 |
Oops, something went wrong.