Skip to main content

Impact & Risk Analysis

  • Severity: Medium
  • CIS Benchmark: CIS 4.5
  • Impact: Spoofing & Compromised Provenance. Content trust provides the ability to use digital signatures for data sent to and received from remote Docker registries. Without it, there is no client-side verification of the identity and the publisher of specific image tags, allowing potential spoofing or the use of compromised images.

Common Misconfiguration

Content trust is disabled by default in the Docker client. Unless explicitly enabled, Docker commands will not verify the signatures of images, and users might unknowingly pull malicious or untrusted images.

Vulnerable Example

Secure Example

Audit Procedure

You should execute the following command to verify if Content Trust is enabled:
  • Result: This should return a value of 1.
  • Fail: If it returns an empty line or 0, Content Trust is disabled.

Remediation

To enable content trust in a bash shell, you should enter the following command:
Alternatively, you could set this environment variable in your profile file (e.g., .bashrc or .zshrc) so that content trust is enabled on every login.