From e7281bde3d17dbc86cf5fbbce5bc734ff8cbec3c Mon Sep 17 00:00:00 2001 From: Craig Osterhout Date: Wed, 18 Mar 2026 14:08:59 -0700 Subject: [PATCH] dhi: updates from scanner Signed-off-by: Craig Osterhout --- content/manuals/dhi/core-concepts/cis.md | 6 +++--- content/manuals/dhi/core-concepts/cves.md | 3 --- content/manuals/dhi/core-concepts/sscs.md | 6 +++--- 3 files changed, 6 insertions(+), 9 deletions(-) diff --git a/content/manuals/dhi/core-concepts/cis.md b/content/manuals/dhi/core-concepts/cis.md index 7b88fa756055..426f85136ca2 100644 --- a/content/manuals/dhi/core-concepts/cis.md +++ b/content/manuals/dhi/core-concepts/cis.md @@ -24,9 +24,9 @@ Following the CIS Docker Benchmark helps organizations: ## How Docker Hardened Images comply with the CIS Benchmark Docker Hardened Images (DHIs) are designed with security in mind and are -verified to be compliant with the relevant controls from the latest CIS -Docker Benchmark (v1.8.0) for the scope that applies to container images and -Dockerfile configuration. +verified to be compliant with the relevant controls from the CIS Docker +Benchmark for the scope that applies to container images and Dockerfile +configuration. CIS-compliant DHIs are compliant with all controls in Section 4, with the sole exception of the control requiring Docker Content Trust (DCT), which [Docker diff --git a/content/manuals/dhi/core-concepts/cves.md b/content/manuals/dhi/core-concepts/cves.md index 2aa1544fdd73..a3c0a91c2c65 100644 --- a/content/manuals/dhi/core-concepts/cves.md +++ b/content/manuals/dhi/core-concepts/cves.md @@ -160,9 +160,6 @@ $ docker scout vex get dhi.io/: --output vex.json > [!NOTE] > -> The `docker scout vex get` command requires [Docker Scout -> CLI](https://github.com/docker/scout-cli/) version 1.18.3 or later. -> > If the image exists locally on your device, you must prefix the image name with `registry://`. For example, use > `registry://dhi.io/python:3.13` instead of `dhi.io/python:3.13`. diff --git a/content/manuals/dhi/core-concepts/sscs.md b/content/manuals/dhi/core-concepts/sscs.md index bd6a58b1d677..52f7c28f6675 100644 --- a/content/manuals/dhi/core-concepts/sscs.md +++ b/content/manuals/dhi/core-concepts/sscs.md @@ -17,9 +17,9 @@ ensuring the integrity and security of these elements is paramount ## Why is SSCS important? -The significance of SSCS has escalated due to the rise in sophisticated -cyberattacks targeting software supply chains. Recent incidents and the -exploitation of vulnerabilities in open-source components have underscored the +The significance of SSCS has escalated due to sophisticated cyberattacks +targeting software supply chains. High-profile supply chain attacks and the +exploitation of vulnerabilities in open-source components underscore the critical need for robust supply chain security measures. Compromises at any stage of the software lifecycle can lead to widespread vulnerabilities, data breaches, and significant financial losses.