Minimize access to secrets

HighLevel 1Manual reviewopenshift

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. The benchmark marks this recommendation Manual.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

Review the users who have get, list or watch access to secrets objects in the Kubernetes API. Executing the command below will return a list of users and groups who are allowed to get secrets: oc adm policy who-can get secrets The following command returns the users and groups who are allowed to list secrets: oc adm policy who-can list secrets The following command returns the users and groups who are allowed to watch secrets: oc adm policy who-can watch secrets

How it is fixed

Fix method: Guidance or infrastructure patch

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

Properties

Operating systems: Any
Tags: openshiftpoliciesrbacsecrets
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.1.2 Minimize access to secrets