Ensure insecure registries are not used
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-docker-2.5 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Docker 2.5?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-docker-2-5)More formats (shields.io, HTML) on the badges page.
---
name: cis-docker-2.5
description: "Ensure insecure registries are not used"
category: cis-docker
version: "1.8.0"
author: cyberstrike-official
tags: [cis, docker, linux, containers, daemon-configuration, registry, tls, encryption]
cis_id: "2.5"
cis_benchmark: "CIS Docker Benchmark v1.8.0"
tech_stack: [linux, docker]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# Ensure insecure registries are not used (Manual)
## Profile Applicability
• Level 1 - Docker - Linux
## Description
Docker considers a private registry either secure or insecure. By default, registries are considered secure.
## Rationale
A secure registry uses TLS. A copy of registry's CA certificate is placed on the Docker host at `/etc/docker/certs.d/<registry-name>/` directory. An insecure registry is one which does not have a valid registry certificate, or one not using TLS. Insecure registries should not be used as they present a risk of traffic interception and modification.
Additionally, once a registry has been marked as insecure commands such as `docker pull`, `docker push`, and `docker search` will not result in an error message and users may indefinitely be working with this type of insecure registry without ever being notified of the risk of potential compromise.
## Impact
None.
## Audit Procedure
You should execute the command below to find out if any insecure registries are in use:
```bash
docker info --format 'Insecure Registries:'
```
## Remediation
You should ensure that no insecure registries are in use.
## Default Value
By default, Docker assumes all, but local, registries are secure.
## Additional Information
Docker engine always include 127.0.0.0/8 and ::1/128 as insecure registers
## References
None listed in the benchmark.
## CIS Controls
**Controls Version:** v8
**Control:** 2.5 Allowlist Authorized Software
Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
**IG 1:**
**IG 2:** ●
**IG 3:** ●
---
**Controls Version:** v7
**Control:** 14.4 Encrypt All Sensitive Information in Transit
Encrypt all sensitive information in transit.
**IG 1:**
**IG 2:** ●
**IG 3:** ●
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!