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-235860

CAT II (Medium)

Docker Enterprise TLS certificate authority (CA) certificate file permissions must be set to 444 or more restrictive.

Rule ID

SV-235860r961863_rule

STIG

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

Version

V2R2

CCIs

CCI-000366

Discussion

Verify that the TLS CA certificate file (the file that is passed along with --TLScacert parameter) has permissions of 444 or more restrictive. The TLS CA certificate file should be protected from any tampering. It is used to authenticate Docker server based on given CA certificate. Hence, it must have permissions of 444 to maintain the integrity of the CA certificate. By default, the permissions for TLS CA certificate file might not be 444. The default file permissions are governed by the system or user specific umask values.

Check Content

Ensure that TLS CA certificate file permissions are set to 444 or more restrictive.

Execute the below command to verify that the TLS CA certificate file has permissions of 444 or more restrictive:

stat -c %a <path to TLS CA certificate file>

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

Fix Text

chmod 444 <path to TLS CA certificate file>

This sets the file permissions of the TLS CA file to 444.