The default namespace should not be used

FaibleNiveau 2Revue manuelleopenshift

Description

Kubernetes provides a default namespace, where objects are placed if no namespace is specified for them. Placing objects in this namespace makes application of RBAC and other controls more difficult. 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.

In OpenShift, projects (namespaces) are used to group and isolate related objects. When a request is made to create a new project using the web console or oc new-project command, an endpoint in OpenShift Container Platform is used to provision the project according to a template, which can be customized. The cluster administrator can allow and configure how developers and service accounts can create, or self-provision, their own projects. Regular users do not have access to the default project.

Méthode de correction

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

Ensure that namespaces are created to allow for appropriate segregation of Kubernetes resources and that all new resources are created in a specific namespace.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: openshiftpolicies
Référence: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.7.4 The default namespace should not be used