5.2.3 Minimize the admission of containers wishing to share the host IPC namespace

Information

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 Security Context Constraint (SCC) 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 SCC and you should carefully check RBAC controls to ensure that only limited service accounts and users are given permission to access that SCC.

Impact:

Pods defined with Allow Host IPC: true will not be permitted unless they are run under a specific SCC.

Solution

Create an SCC that sets allowHostIPC to false and take it into use by assigning it to applicable users and groups.

Default Value:

By default, the following SCCs do not allow users to run within the host IPC namespace:

'anyuid'

'hostmount-anyuid'

'hostnetwork'

'hostnetwork-v2'

'machine-api-termination-handler'

'node-exporter'

'nonroot'

'nonroot-v2'

'restricted'

'restricted-v2'

See Also

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

Item Details

Category: SYSTEM AND COMMUNICATIONS PROTECTION

References: 800-53|SC-7(8), CSCv7|12.9

Plugin: OpenShift

Control ID: 3f763c950abe3d9ab2179e8bf57cac488c22c45da19eef991180524172ced966