Details
Verify that the ‘docker.socket’ file permissions are correctly set to ‘644’or more restrictive.
Rationale:
‘docker.socket’ file contains sensitive parameters that may alter the behavior of Docker remote API. Hence, it should be writable only by ‘root’ to maintain the integrity of the file.
Solution
Step 1: Find out the file location:
systemctl show -p FragmentPath docker.socket
Step 2: If the file does not exist, this recommendation is not applicable. If the file exists, execute the below command with the correct file path to set thefile permissions to ‘644’.
For example,
chmod 644 /usr/lib/systemd/system/docker.socket
Impact:
None.
Default Value:
This file may not be present on the system. In that case, this recommendation is not applicable. By default, if the file is present, the file permissions for this file are correctly set to ‘644’.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.