Details

Verify that the ‘docker.socket’ file ownership and group ownership is correctly set to ‘root’.

Rationale:

‘docker.socket’ file contains sensitive parameters that may alter the behavior of Docker remote API. Hence, it should be owned and group-owned 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 the ownership and group ownership for the file to ‘root’.

For example,

chown root:root /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 ownership and group-ownership for this file is correctly set to ‘root’.

Supportive Information

The following resource is also helpful.

• https://workbench.cisecurity.org/files/1476

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.

References

• 800-53|CM-6b.

Source

• Tenable.com/audits