--service-account-private-key-file argument is set as appropriate
Incident Management is now generally available! Incident Management is now generally available!
<  Back to rules search

--service-account-private-key-file argument is set as appropriate

kubernetes

Classification:

compliance

Framework:

cis-kubernetes

Control:

1.3.4

Set up the kubernetes integration.

Overview

Description

Explicitly set a service account private key file for service accounts on the controller manager.

Rationale

To ensure that keys for service account tokens can be rotated as needed, a separate public/private key pair should be used for signing service account tokens. The private key should be specified to the controller manager with --service-account-private-key-file as appropriate.

Audit

Run the following command on the master node:

ps -ef | grep kube-controller-manager

Verify that the --service-account-private-key-file argument is set as appropriate.

Remediation

Edit the Controller Manager pod specification file /etc/kubernetes/manifests/kube-controller-manager.yaml on the master node and set the --service-account-private-key-file parameter to the private key file for service accounts:

--service-account-private-key-file=<filename>

Impact

You would need to securely maintain the key file and rotate the keys based on your organization’s key rotation policy.

Default Value

By default, --service-account-private-key-file it not set.

References

  1. https://kubernetes.io/docs/admin/kube-controller-manager/

CIS Controls

Version 6.14 Controlled Access Based on the Need to Know

Version 7.4 Controlled Use of Administrative Privileges