Classification:
compliance
Framework:
cis-docker
Control:
3.4
You should verify that the file permissions on the docker.socket file are correctly set to 644 or more restrictively.
The docker.socket file contains sensitive parameters that may alter the behavior of the Docker remote API. It should therefore be writeable only by root in order to ensure that it is not modified by less privileged users.
docker.socket
file by running:systemctl show -p FragmentPath docker.socket
644
or more restrictively, by running the following command with the correct filepath:stat -c %a /usr/lib/systemd/system/docker.socket
systemctl show -p FragmentPath docker.socket
chmod 644 /usr/lib/systemd/system/docker.socket
None
This file may not be present on the system and in that case, this recommendation is not applicable. By default, if the file is present, the permissions should be set to 644 or more restrictively.
Version 6
14.4 Protect Information With Access Control Lists - All information stored on systems shall be protected with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities.
Version 7
14.6 Protect Information through Access Control Lists - Protect all information stored on systems with file system, network share, claims, application, or database specific access control lists. These controls will enforce the principle that only authorized individuals should have access to the information based on their need to access the information as a part of their responsibilities.