STIGQter STIGQter: STIG Summary: Mirantis Kubernetes Engine Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 24 Jul 2024:

All containers must be restricted to mounting the root filesystem as read only.

DISA Rule

SV-260936r966165_rule

Vulnerability Number

V-260936

Group Title

SRG-APP-000342-CTR-000775

Rule Version

CNTR-MK-001160

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

When using Kubernetes orchestration, this check is Not Applicable.

When using Swarm orchestration, review and remove nonsystem containers previously created by these users with read write permissions using:

docker container rm [container]

Add a --read-only flag at a container's runtime to enforce the container's root filesystem to be mounted as read only:

docker run <Run arguments> --read-only <Container Image Name or ID> <Command>

Enabling the --read-only option at a container's runtime must be used by administrators to force a container's executable processes to only write container data to explicit storage locations during the container's runtime.

Examples of explicit storage locations during a container's runtime include, but are not limited to:

1. Use the --tmpfs option to mount a temporary file system for nonpersistent data writes. Example:

docker run --interactive --tty --read-only --tmpfs "/run" --tmpfs "/tmp" [image] [command]

2. Enabling Docker rw mounts at a container's runtime to persist container data directly on the Docker host filesystem. Example:

docker run --interactive --tty --read-only -v /opt/app/data:/run/app/data:rw [image] [command]

3. Utilizing Docker shared-storage volume plugins for Docker data volume to persist container data.

docker volume create -d convoy --opt o=size=20GB my-named-volume

docker run --interactive --tty --read-only -v my-named-volume:/run/app/data [image] [command]

Check Contents

When using Kubernetes orchestration, this check is Not Applicable.

For Swarm orchestration, check via CLI:

Linux: As an MKE Admin, execute the following command using a Universal Control Plane (MKE) client bundle:

docker ps --quiet --all | xargs -L 1 docker inspect --format '{{ .Name }}: ReadonlyRootfs={{ .HostConfig.ReadonlyRootfs }}'

If ReadonlyRootfs=false, it means the container's root filesystem is writable and this is a finding.

Vulnerability Number

V-260936

Documentable

False

Rule Version

CNTR-MK-001160

Severity Override Guidance

When using Kubernetes orchestration, this check is Not Applicable.

For Swarm orchestration, check via CLI:

Linux: As an MKE Admin, execute the following command using a Universal Control Plane (MKE) client bundle:

docker ps --quiet --all | xargs -L 1 docker inspect --format '{{ .Name }}: ReadonlyRootfs={{ .HostConfig.ReadonlyRootfs }}'

If ReadonlyRootfs=false, it means the container's root filesystem is writable and this is a finding.

Check Content Reference

M

Target Key

5595