Skip to content
Back to skills

Cis Docker V170 4.5

ASecurity

Ensure Content trust for Docker is Enabled

  • 2,182 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 3, 2026
securityrustgoshellbashdockergitsecurity

Works with

  • cli

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-docker-v170-4.5 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis Docker V170 4.5?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis Docker V170 4.5
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-docker-v170-4-5/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-docker-v170-4-5)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-docker-v170-4.5
description: "Ensure Content trust for Docker is Enabled"
category: cis-docker
version: "1.7.0"
author: cyberstrike-official
tags: [cis, docker, images, configuration, signing]
cis_id: "4.5"
cis_benchmark: "CIS Docker Benchmark v1.7.0"
tech_stack: [docker]
cwe_ids: [CWE-345]
chains_with: []
prerequisites: []
severity_boost: {}
---

# CIS Docker Benchmark v1.7.0 - Control 4.5

## Profile Applicability

- Level 2 - Docker - Linux

## Description

Content trust is disabled by default and should be enabled in line with organizational security policy.

## Rationale

Content trust provides the ability to use digital signatures for data sent to and received from remote Docker registries. These signatures allow client-side verification of the identity and the publisher of specific image tags and ensures the provenance of container images.

## Impact

In an environment where `DOCKER_CONTENT_TRUST` is set, you are required to follow trust procedures whilst working with the image related commands - `build`, `create`, `pull`, `push` and `run`. You can use the `--disable-content-trust` flag to run individual operations on tagged images without content trust on an as needed basis, but this defeats the purpose of enabling content trust and therefore should be avoided wherever possible.

Note: Content trust is currently only available for users of the public Docker Hub. It is currently not available for the Docker Trusted Registry or for private registries.

## Audit Procedure

You should execute the following command:

```bash
echo $DOCKER_CONTENT_TRUST
```

This should return a value of `1`.

## Remediation

To enable content trust in a bash shell, you should enter the following command:

```bash
export DOCKER_CONTENT_TRUST=1
```

Alternatively, you could set this environment variable in your profile file so that content trust is enabled on every login.

## Default Value

By default, content trust is disabled.

## References

1. https://docs.docker.com/engine/security/trust/
2. https://docs.docker.com/notary/service_architecture/
3. https://docs.docker.com/engine/reference/commandline/cli/#environment-variables

## CIS Controls

**v8:**

- 3 Data Protection - Develop processes and technical controls to identify, classify, securely handle, retain, and dispose of data.

**v7:**

- 13 Data Protection - Data Protection

## Assessment Status

Manual

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…