/
Kubernetes Clusters Should Not Use the Default Namespace

Kubernetes Clusters Should Not Use the Default Namespace

Description:

Prevent usage of the default namespace in Kubernetes clusters to protect against unauthorized access for ConfigMap, Pod, Secret, Service, and ServiceAccount resource types.



Remediation/Reference:

Security Center lists the components using the default namespace.
1. From the unhealthy resources tab, select a cluster.
2. Define a namespace for the components.
3. After making your changes, redeploy the components with the updated namespace. For more information, see https://kubernetes.io/docs/tasks/administer-cluster/namespaces/#creating-a-new-namespace

Related content

Containers Sharing Sensitive Host Namespaces Should Be Avoided
Containers Sharing Sensitive Host Namespaces Should Be Avoided
More like this
Privileged Containers Should be Avoided
Privileged Containers Should be Avoided
More like this
Ensure Legacy Authorization is set to Disabled on Kubernetes Engine Clusters
Ensure Legacy Authorization is set to Disabled on Kubernetes Engine Clusters
More like this
Ensure Automatic node upgrades is enabled on Kubernetes Engine Clusters nodes
Ensure Automatic node upgrades is enabled on Kubernetes Engine Clusters nodes
More like this
Ensure automatic node repair is enabled for Kubernetes Clusters
Ensure automatic node repair is enabled for Kubernetes Clusters
More like this
Container Images Should be Deployed from Trusted Registries Only
Container Images Should be Deployed from Trusted Registries Only
More like this