Skip to content

Commit b0a2a7f

Browse files
authored
Merge pull request #24405 from craig-osterhout/dhi-docs-scanner-1
dhi: updates from scanner
2 parents 6b1ebe4 + e7281bd commit b0a2a7f

3 files changed

Lines changed: 6 additions & 9 deletions

File tree

content/manuals/dhi/core-concepts/cis.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ Following the CIS Docker Benchmark helps organizations:
2424
## How Docker Hardened Images comply with the CIS Benchmark
2525

2626
Docker Hardened Images (DHIs) are designed with security in mind and are
27-
verified to be compliant with the relevant controls from the latest CIS
28-
Docker Benchmark (v1.8.0) for the scope that applies to container images and
29-
Dockerfile configuration.
27+
verified to be compliant with the relevant controls from the CIS Docker
28+
Benchmark for the scope that applies to container images and Dockerfile
29+
configuration.
3030

3131
CIS-compliant DHIs are compliant with all controls in Section 4, with the sole
3232
exception of the control requiring Docker Content Trust (DCT), which [Docker

content/manuals/dhi/core-concepts/cves.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -160,9 +160,6 @@ $ docker scout vex get dhi.io/<image>:<tag> --output vex.json
160160

161161
> [!NOTE]
162162
>
163-
> The `docker scout vex get` command requires [Docker Scout
164-
> CLI](https://github.com/docker/scout-cli/) version 1.18.3 or later.
165-
>
166163
> If the image exists locally on your device, you must prefix the image name with `registry://`. For example, use
167164
> `registry://dhi.io/python:3.13` instead of `dhi.io/python:3.13`.
168165

content/manuals/dhi/core-concepts/sscs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ ensuring the integrity and security of these elements is paramount
1717

1818
## Why is SSCS important?
1919

20-
The significance of SSCS has escalated due to the rise in sophisticated
21-
cyberattacks targeting software supply chains. Recent incidents and the
22-
exploitation of vulnerabilities in open-source components have underscored the
20+
The significance of SSCS has escalated due to sophisticated cyberattacks
21+
targeting software supply chains. High-profile supply chain attacks and the
22+
exploitation of vulnerabilities in open-source components underscore the
2323
critical need for robust supply chain security measures. Compromises at any
2424
stage of the software lifecycle can lead to widespread vulnerabilities, data
2525
breaches, and significant financial losses.

0 commit comments

Comments
 (0)