Skip to content
Back to skills

Cis Docker V170 4.11

ASecurity

Ensure only verified packages are installed

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

Security analysis

A100/100

Scanned September 3, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Cis Docker V170 4.11?

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

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

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.11
description: "Ensure only verified packages are installed"
category: cis-docker
version: "1.7.0"
author: cyberstrike-official
tags: [cis, docker, images, configuration, package-verification]
cis_id: "4.11"
cis_benchmark: "CIS Docker Benchmark v1.7.0"
tech_stack: [docker]
cwe_ids: [CWE-494]
chains_with: []
prerequisites: []
severity_boost: {}
---

# CIS Docker Benchmark v1.7.0 - Control 4.11

## Profile Applicability

- Level 2 - Docker - Linux

## Description

You should verify the authenticity of packages before installing them into images.

## Rationale

Verifying authenticity of software packages is essential for building a secure container image. Packages with no known provenance could potentially be malicious or have vulnerabilities that could be exploited.

## Impact

None

## Audit Procedure

Run the command below to get the list of images:

```bash
docker images
```

Run the command below for each image in the list above, and check how the authenticity of the packages is being determined. This could be via the use of GPG keys or other secure package distribution mechanisms.

```bash
docker history <IMAGE_ID>
```

Alternatively, if you have access to Dockerfile for the image, verify that the authenticity of the packages is checked.

## Remediation

You should use a secure package distribution mechanism of your choice to ensure the authenticity of software packages.

## Default Value

Not Applicable

## References

1. https://www.redhat.com/sysadmin/rpm-gpg-verify-packages
2. https://help.ubuntu.com/community/SecureApt

## CIS Controls

**v8:**

- 2.2 Ensure Authorized Software is Currently Supported - Ensure that only currently supported software is designated as authorized in the software inventory for enterprise assets. If software is unsupported, yet necessary for the fulfillment of the enterprise's mission, document an exception detailing mitigating controls and residual risk acceptance. For any unsupported software without an exception documentation, designate as unauthorized. Review the software list to verify software support at least monthly, or more frequently.

**v7:**

- 18.3 Verify That Acquired Software is Still Supported - Verify that the version of all software acquired from outside your organization is still supported by the developer or appropriately hardened based on developer security recommendations.

## 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…