Detections
Analytics

4.6.1 Create administrative boundaries between resources using namespaces

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Use namespaces to isolate your Kubernetes objects.

Limiting the scope of user permissions can reduce the impact of mistakes or malicious activities. A Kubernetes namespace allows you to partition created resources into logically named groups. Resources created in one namespace can be hidden from other namespaces. By default, each resource created by a user in Kubernetes cluster runs in a default namespace, called default . You can create additional namespaces and attach resources and users to them. You can use Kubernetes Authorization plugins to create policies that segregate access to namespace resources between different users.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Follow the documentation and create namespaces for objects in your deployment as you need them.

Impact:

You need to switch between namespaces for administration.

See Also

https://workbench.cisecurity.org/benchmarks/24112

Item Details

References: CSCv7|12

Plugin: GCP

Control ID: d58f7230f083c28023bf1a27300bc6d2b78dab566fe2b56599372f6cf822e47e