Title

Rancher RKE2 keystore must implement encryption to prevent unauthorized disclosure of information at rest within Rancher RKE2. (Cat I impact)

Discussion

Encrypting secrets at rest in etcd. By default, RKE2 will create an encryption key and configuration file and pass these to the Kubernetes API server. The result is that RKE2 automatically encrypts Kubernetes Secret objects when writing them to etcd.

Check Content

This is Not Applicable for RKE2 versions 1.20 and greater. Review the encryption configuration file. As root or with root permissions, run the following command: view /var/lib/rancher/rke2/server/cred/encryption-config.json Ensure the RKE2 configuration file on all RKE2 servers, located at /etc/rancher/rke2/config.yaml, does NOT contain: secrets-encryption: false If secrets encryption is turned off, this is a finding.

Fix Text

This is Not Applicable for RKE2 versions 1.20 and greater. Enable secrets encryption. Edit the RKE2 configuration file on all RKE2 servers, located at /etc/rancher/rke2/config.yaml, so that it contains: secrets-encryption: true

Additional Identifiers

Rule ID: SV-254573r1016545_rule

Vulnerability ID: V-254573

Group Title: SRG-APP-000429-CTR-001060

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.