Minimize the admission of privileged containers

CriticalLevel 1Manual reviewopenshift

Description

Do not generally permit containers to be run with the securityContext.privileged flag set to true. The benchmark marks this recommendation Manual.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

The set of SCCs that admission uses to authorize a pod are determined by the user identity and groups that the user belongs to. Additionally, if the pod specifies a service account, the set of allowable SCCs includes any constraints accessible to the service account. Admission uses the following approach to create the final security context for the pod: • Retrieve all SCCs available for use. • Generate field values for security context settings that were not specified on the request. • Validate the final settings against the available constraints.

How it is fixed

Fix method: Guidance or infrastructure patch

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

Properties

Operating systems: Any
Tags: openshiftpoliciespod-security
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.2.1 Minimize the admission of privileged containers