STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Docker Enterprise 2.x Linux/UNIX Security Technical Implementation Guide

V-235866

CAT I (High)

Docker Enterprise socket file permissions must be set to 660 or more restrictive.

Rule ID

SV-235866r961863_rule

STIG

Docker Enterprise 2.x Linux/UNIX Security Technical Implementation Guide

Version

V2R2

CCIs

CCI-000366

Discussion

Verify that the Docker socket file has permissions of 660 or more restrictive. Only root and members of docker group should be allowed to read and write to default Docker UNIX socket. Hence, the Docket socket file must have permissions of 660 or more restrictive. By default, the permissions for Docker socket file is correctly set to 660.

Check Content

Ensure that Docker socket file permissions are set to 660 or more restrictive.

Execute the below command to verify that the Docker socket file has permissions of 660 or more restrictive:

stat -c %a /var/run/docker.sock

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

Fix Text

chmod 660 /var/run/docker.sock

This sets the file permissions of the Docker socket file to 660.