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

Least privilege access and need to know must be required to access MKE runtime and instantiate container images.

DISA Rule

SV-260906r1015768_rule

Vulnerability Number

V-260906

Group Title

SRG-APP-000033-CTR-000095

Rule Version

CNTR-MK-000110

Severity

CAT I

CCI(s)

Weight

10

Fix Recommendation

To remove unauthorized users from the docker group, access the host CLI and run:

gpasswd -d docker [username to remove]

To ensure that docker.socket is group owned, execute the following:

chown root:docker /var/run/docker.sock

Set the file permissions of the Docker socket file to "660" execute the following:

chmod 660 /var/run/docker.sock

Check Contents

Access to use the docker CLI must be limited to root only.

1. Log on to the host CLI and execute the following:

stat -c %U:%G /var/run/docker.sock | grep -v root:docker

If any output is present, this is a finding.

2. Verify that the docker group has only the required users by executing:

getent group docker

If any users listed are not required to have direct access to MCR, this is a finding.

3. Execute the following command to verify the Docker socket file has permissions of 660 or more restrictive:
stat -c %a /var/run/docker.sock

If permissions are not set to "660", this is a finding.

Vulnerability Number

V-260906

Documentable

False

Rule Version

CNTR-MK-000110

Severity Override Guidance

Access to use the docker CLI must be limited to root only.

1. Log on to the host CLI and execute the following:

stat -c %U:%G /var/run/docker.sock | grep -v root:docker

If any output is present, this is a finding.

2. Verify that the docker group has only the required users by executing:

getent group docker

If any users listed are not required to have direct access to MCR, this is a finding.

3. Execute the following command to verify the Docker socket file has permissions of 660 or more restrictive:
stat -c %a /var/run/docker.sock

If permissions are not set to "660", this is a finding.

Check Content Reference

M

Target Key

5595