Cis Eks V170 4.1.2

4.1.2 Minimize access to secrets (Automated)

Profile Applicability

• Level 1

Description

The Kubernetes API stores secrets, which may be service account tokens for the Kubernetes API or credentials used by workloads in the cluster. Access to these secrets should be restricted to the smallest possible group of users to reduce the risk of privilege escalation.

Rationale

Inappropriate access to secrets stored within the Kubernetes cluster can allow for an attacker to gain additional access to the Kubernetes cluster or external resources whose credentials are stored as secrets.

Impact

Care should be taken not to remove access to secrets to system components which require this for their operation.

Audit Procedure

Review the users who have get, list or watch access to secrets objects in the Kubernetes API.

kubectl get clusterrolebindings -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECT:.subjects[*].name
kubectl get rolebindings --all-namespaces -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECT:.subjects[*].name

Remediation

Where possible, remove get, list and watch access to secret objects in the cluster.

Default Value

By default, the following list of principals have get privileges on secret objects:

References

None specified.

CIS Controls