Control: 7.1.1.1 Ensure Kubernetes secrets data is encrypted with bring your own key (BYOK)

Description

IBM® Key Protect for IBM CloudTM helps you provision encrypted keys for apps across IBM Cloud services. Use the IBM Key Protect for IBM Cloud key management service (KMS) to encrypt data in Kubernetes secrets and prevent unauthorized users from accessing sensitive app information (for example, credentials and keys). Keys are generated by FIPS 140-2 Level 3 certified hardware security modules (HSMs) that are located in secure IBM Cloud data centers.

Remediation

From Console

Log in to your IBM Cloud account.
To view the list of services that are available on IBM Cloud, click Catalog.
From the All Categories navigation pane, click the Security and Identity category.
From the list of services, click the Key Protect tile.
Select a service plan, and click Create to provision an instance of Key Protect in the account, region, and resource group where you are logged in.
To view a list of your resources, go to Menu > Resource List.
From your IBM Cloud resource list, select your provisioned instance of Key Protect.
To create a new key, click Add key and select the Create a key window. Specify the key's name and key type.
When you are finished filling out the key's details, click Create key to confirm.
From the Clusters console, select the cluster that you want to enable encryption for.
From the Overview tab, in the Summary > Key management service section, click Enable.
Select the Key management service instance and Root key that you want to use for the encryption.
Click Enable.
Verify that the KMS enablement process is finished. From the Summary > Master status section, you can check the progress.
After the KMS provider is enabled in the cluster, data in etcd and new secrets that are created in the cluster are automatically encrypted by using your root key.
To encrypt existing secrets with the root key, rewrite the secrets. This cannot be done from the console. See the From Command Line section.

From Command Line:

ibmcloud login [--sso]

Select the region and resource group where you want to create a Key Protect instance.

ibmcloud target -r <region_name> -g <resource_group_name>

Provision a public or private Key Protect instance.

ibmcloud resource service-instance-create <instance_name> kms tiered-pricing
<region> [-p '{"allowed_network": "private-only"}']

Create a customer root key (CRK) in your KMS instance. You can't use the CLI for this action; you must use the GUI or API. See the above From Console section.
Get the ID of the KMS instance that you previously created.

ibmcloud ks kms instance ls

Get the ID of the root key that you previously created.

ibmcloud ks kms crk ls --instance-id <KMS_instance_ID>

Enable the KMS provider to encrypt secrets in your cluster. Fill in the options with the information that you previously retrieved. The KMS provider's private service endpoint is used by default to download the encryption keys. To use the public service endpoint instead, include the --public-endpoint option. The enablement process can take some time to complete.

ibmcloud ks kms enable -c <cluster_name_or_ID> --instance-id
<kms_instance_ID> --crk <root_key_ID> [--public-endpoint]

Verify that the KMS enablement process is finished. The process is finished when the Master Status is Ready.
After the KMS provider is enabled in the cluster, data in etcd and new secrets that are created in the cluster are automatically encrypted by using your root key.
Set the context for your cluster.

ibmcloud ks cluster config -c <cluster_name_or_ID>

With cluster-admin access, rewrite the secrets to encrypt them.

kubectl get secrets --all-namespaces -o json | kubectl replace -f -

Usage

Run the control in your terminal:

powerpipe control run ibm_compliance.control.cis_v100_7_1_1_1

Snapshot and share results via Turbot Pipes:

powerpipe login
powerpipe control run ibm_compliance.control.cis_v100_7_1_1_1 --share

SQL

This control uses a named query:

manual_control