Control: 5.2.3 Minimize the admission of containers wishing to share the host IPC namespace
Description
Do not generally permit containers to be run with the hostIPC flag set to true.
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.
Remediation
Create a PSP as described in the Kubernetes documentation, ensuring that the .spec.hostIPC field is omitted or set to false.
References
Usage
Run the control in your terminal:
powerpipe control run kubernetes_compliance.control.cis_kube_v120_v100_5_2_3Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run kubernetes_compliance.control.cis_kube_v120_v100_5_2_3 --shareSQL
This control uses a named query:
select coalesce(uid, concat(path, ':', start_line)) as resource, case when host_ipc then 'alarm' else 'ok' end as status, case when host_ipc then 'Pod security policy ' || name || ' pods can share host IPC namespaces.' else 'Pod security policy ' || name || ' pods cannot share host IPC namespaces.' end as reason , coalesce(context_name, '') as context_name, source_type, coalesce(path || ':' || start_line || '-' || end_line, '') as pathfrom kubernetes_pod_security_policy;