From 7049b4f398ff67a22fe9aced12359b8d87329414 Mon Sep 17 00:00:00 2001 From: Lance Bragstad Date: Wed, 26 Jun 2024 14:43:41 -0500 Subject: [PATCH] Update status for CIS 1.2.31 We implemented support for checking aesgcm encryption ciphers in https://github.com/ComplianceAsCode/content/pull/10974 but never removed the comment or updated the status in the control file. This commit updates the status since it's now automated to include both ciphers. --- controls/cis_ocp_1_4_0/section-1.yml | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/controls/cis_ocp_1_4_0/section-1.yml b/controls/cis_ocp_1_4_0/section-1.yml index 7e9c932655da..79f985b5cfb2 100644 --- a/controls/cis_ocp_1_4_0/section-1.yml +++ b/controls/cis_ocp_1_4_0/section-1.yml @@ -384,15 +384,10 @@ controls: levels: [ level_1, ] - id: 1.2.31 title: Ensure that encryption providers are appropriately configured - status: partial + status: automated rules: - api_server_encryption_provider_cipher levels: [ level_1, ] - # Remove this comment once https://github.com/ComplianceAsCode/content/issues/10868 is fixed. - # tickets: - # - https://issues.redhat.com/browse/CMP-1973 - notes: |- - Ticket 1973 tracks adding the aesgcm encryption method for OCP 4.13+ - id: 1.2.32 title: Ensure that the API Server only makes use of Strong Cryptographic Ciphers status: automated