The API server should explicitly set a service account public key file

문서 > Datadog 보안 > OOTB Rules > The API server should explicitly set a service account public key file

Classification:

compliance

Framework:

cis-kubernetes

Control:

1.2.28

Set up the kubernetes integration.

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Description

Explicitly set a service account public key file for service accounts on the apiserver.

Rationale

By default, if no –service-account-key-file is specified to the apiserver, it uses the private key from the TLS serving certificate to verify service account tokens. To ensure that the keys for service account tokens could be rotated as needed, a separate public/private key pair should be used for signing service account tokens. Hence, the public key should be specified to the apiserver with –service-account-key-file.

Audit

Run the following command on the master node:

ps -ef | grep kube-apiserver

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

Remediation

Edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the --service-account-key-file parameter to the public key file for service accounts: --service-account-key-file=<filename>

Impact

The corresponding private key must be provided to the controller manager. 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-key-file argument is not set.

References

CIS controls

Version 6 3 Secure Configurations for Hardware and Software on Mobile Devices, Laptops, Workstations, and Servers Version 7 5 Secure Configuration for Hardware and Software on Mobile Devices, Laptops, Workstations and Servers