Merge pull request ComplianceAsCode#6565 from mrogers950/cis_1234

CIS 1.2.34: update api_server_encryption_provider_cipher

applications/openshift/api-server/api_server_encryption_provider_cipher/kubernetes/shared.yml

@@ -0,0 +1,8 @@
+# platform = multi_platform_ocp
+apiVersion: config.openshift.io/v1
+kind: APIServer
+metadata:
+  name: cluster
+spec:
+  encryption:
+    type: aescbc

applications/openshift/api-server/api_server_encryption_provider_cipher/rule.yml

@@ -5,20 +5,13 @@ prodtype: ocp4
 title: 'Configure the Encryption Provider Cipher'
 
 description: |-
-    To configure OpenShift to use the <tt>aescbc</tt> encryption provider,
-    follow the OpenShift documentation to create or modify an
-    <tt>EncryptionConfig</tt> file.
-    In this file, choose <tt>aescbc</tt> as the encryption provider:
-    <pre>kind: EncryptionConfig
-    apiVersion: v1
-    resources:
-      - resources:
-        - secrets
-        providers:
-        - aescbc:
-            keys:
-            - name: key1
-              secret: <i>32-byte base64-encoded secret</i></pre>
+    To ensure the correct cipher, set the encryption type <tt>aescbc</tt> in the
+    <tt>apiserver</tt> object which configures the API server itself.
+    <pre>
+    spec:
+      encryption:
+        type: aescbc
+    </pre>
 
 rationale: |-
     <tt>aescbc</tt> is currently the strongest encryption provider, it should
@@ -33,7 +26,21 @@ ocil_clause: '<tt>aescbc</tt> is not configured as the encryption provider'
 
 ocil: |-
     Run the following command:
-    <pre>$ oc get secrets encryption-config -n openshift-kube-apiserver -o json | jq -r '.data["encryption-config"]' | base64 -d | jq -r '.resources'</pre>
-    Verify that the <tt>aescbc</tt> encryption provider is used for all the desired
-    <tt>resources</tt>.
-
+    <pre>$ oc get apiserver cluster -ojson | jq -r '.spec.encryption.type'</pre>
+    The output should return <tt>aescdc</tt> as the encryption type.
+
+warnings:
+- general: |-
+    {{{ openshift_cluster_setting("/apis/config.openshift.io/v1/apiservers/cluster") | indent(4) }}}
+
+template:
+  name: yamlfile_value
+  vars:
+    ocp_data: "true"
+    entity_check: "at least one"
+    filepath: '/apis/config.openshift.io/v1/apiservers/cluster'
+    yamlpath: '.spec.encryption.type'
+    values:
+    - value: 'aescbc'
+      type: "string"
+      operation: "pattern match"

applications/openshift/api-server/api_server_encryption_provider_cipher/tests/ocp4/e2e-remediation.sh

@@ -0,0 +1,20 @@
+#!/bin/bash
+#
+# This waits for etcd encryption to be enabled. The operator can apply the
+# remediation, but waiting for this to get applied is still something that
+# needs to be done outside of the operator.
+#
+# This patch sets the encryption setting and waits for it to be applied
+
+while true; do
+    status=$(oc get openshiftapiserver -o=jsonpath='{range .items[0].status.conditions[?(@.type=="Encrypted")]}{.reason}')
+
+    echo "Current Encryption Status:"
+    oc get openshiftapiserver -o=jsonpath='{range .items[0].status.conditions[?(@.type=="Encrypted")]}{.reason}{"\n"}{.message}{"\n"}'
+
+    if [ "$status" == "EncryptionCompleted" ]; then
+        exit 0
+    fi
+
+    sleep 5
+done

applications/openshift/api-server/api_server_encryption_provider_cipher/tests/ocp4/e2e.yml

@@ -0,0 +1,3 @@
+---
+default_result: FAIL
+result_after_remediation: PASS