Minimize access to secrets

ÉlevéeNiveau 1Revue manuelleopenshift

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.

Méthode de vérification

Méthode d'audit: Revue manuelle

Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --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

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

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

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: openshiftpoliciesrbacsecrets
Référence: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.1.2 Minimize access to secrets