lacework-global-350
Create administrative boundaries between resources using namespaces (Manual)
Profile Applicability
• Level 1
Description
Use namespaces to isolate your Kubernetes objects.
Rationale
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 an Amazon EKS 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.
Impact
You need to switch between namespaces for administration.
Audit
Run the below command and review the namespaces created in the cluster.
kubectl get namespaces
Ensure that these namespaces are the ones you need and are adequately administered as per your requirements.
Remediation
Follow the documentation and create namespaces for objects in your deployment as you need them.
References
https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
https://blog.kubernetes.io/2016/08/security-best-practices-kubernetes-deployment.html