lacework-global-339
note
This policy has been deprecated in favor of lacework-global-650.
See Adjusted Rules - CIS Amazon EKS 1.1.0 for further details.
4.2.3 Minimize the admission of containers wishing to share the host IPC namespace (Automated)
Profile Applicability
• Level 1
Description
Do not generally permit containers to be run with the hostIPC
flag set to true.
Rationale
A container running in the host's IPC namespace can use IPC to interact with processes outside the container.
There should be at least one PodSecurityPolicy (PSP) defined which does not permit containers to share the host IPC namespace.
If you have a requirement to containers which require hostIPC, this should be defined in a separate PSP and you should carefully check RBAC controls to ensure that only limited service accounts and users are given permission to access that PSP.
Impact
Pods defined with spec.hostIPC: true
will not be permitted unless they are run under a specific PSP.
Audit
Get the set of PSPs with the following command:
kubectl get psp
For each PSP, check whether privileged is enabled:
kubectl get psp <name> -o=jsonpath='{.spec.hostIPC}'
Verify that there is at least one PSP which does not return true.
Remediation
Create a PSP as described in the Kubernetes documentation, ensuring that the .spec.hostIPC
field is omitted or set to false.
References
https://kubernetes.io/docs/concepts/policy/pod-security-policy