docker-bench-security

Check Docker deployment against CIS benchmarks

docker/docker-bench-security · Container Security › Image Scanning · scanned v1.6.1 (released 2023-12-20) · commit ba0b402ea56a · last scan 2026-11-02

6
declared dependencies
0 / 0
critical / high advisories
0
advisories with a fixed version
6.7
OpenSSF Scorecard (of 10); OpenSSF public dataset
no Linux binary
release verification

Changes since last week

no change.

Known vulnerabilities

No known advisories matched the declared dependencies.

Second opinion: OSV-Scanner

OSV-Scanner found 0 advisories in the same files; 0 of Grype's matches are confirmed by it (marked ✓ above). 0 advisories were reported only by OSV-Scanner.

Release integrity

Verdict: no Linux binary.

Verified means a signature, provenance, or attestation was checked against an identity in docker/docker-bench-security's own GitHub Actions workflows.

Repository security (OpenSSF Scorecard)

Score 6.7/10, assessed 2026-10-26 (OpenSSF public dataset). Scorecard viewer

All checks
CheckScoreReason
CII-Best-Practices0no effort to earn an OpenSSF best practices badge detected
Fuzzing0project is not fuzzed
Maintained00 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
SAST0SAST tool is not run on all commits -- score normalized to 0
Branch-Protection5branch protection is not maximal on development and all release branches
Code-Review6Found 8/13 approved changesets -- score normalized to 6
Binary-Artifacts10no binaries found in the repo
Dangerous-Workflow10no dangerous workflow patterns detected
License10license file detected
Pinned-Dependencies10all dependencies are pinned
Security-Policy10security policy file detected
Signed-Releases103 out of the last 3 releases have a total of 3 signed artifacts.
Token-Permissions10GitHub workflow tokens follow principle of least privilege
Packaging—packaging workflow not detected

GitHub Actions workflow audit (zizmor)

4 potential issues in 2 workflow files at this release: 1 high, 0 medium, 2 low severity (medium or high confidence only). Each is a pattern to review, not a confirmed vulnerability.

All findings
SeverityRuleLocationNote
Highunpinned-uses
unpinned action reference
.github/workflows/slsa.yml:43this job
Lowtemplate-injection
code injection via template expansion
.github/workflows/slsa.yml:25this step
Lowtemplate-injection
code injection via template expansion
.github/workflows/slsa.yml:29this step
Informationalsuperfluous-actions
action functionality is already included by the runner
.github/workflows/slsa.yml:71this step

Dependencies (6)

By ecosystem: github 6.

Licenses (as declared in the SBOM): unknown 6.

github (6)
NameVersionLicenseDeclared in
actions/checkout27135e314dd1818f797af1db9dae03a9f045786b.github/workflows/slsa.yml
actions/download-artifactv2.1.1.github/workflows/slsa.yml
actions/upload-artifactv3.1.2.github/workflows/slsa.yml
pozil/auto-assign-issuev1.11.0.github/workflows/issues.yml
slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.ymlv1.5.0.github/workflows/slsa.yml
softprops/action-gh-releasev0.1.15.github/workflows/slsa.yml

History

WeekVersionDependenciesCriticalHighMediumLowUnknownChanges
2026-11-02v1.6.1600000—
2026-11-01v1.6.1600000—

SBOM minimum elements

Scored by sbomlyze on the generated source SBOM. A source SBOM usually lacks supplier and hash data, so these scores mostly reflect what the project's manifests declare.

StandardScoreChecks passedFailed checks
NTIA 2021715/7Supplier Name, Dependency Relationship
CISA 2025505/10Software Producer, Dependency Relationship, License Information, Component Hash, SBOM Author
BSI TR-03183444/9Component Creator, Distribution Licences, SHA-512 Hash, Dependency Relationship, SBOM Creator Contact

Evidence

Downloads for this week: CycloneDX SBOM · Grype report

Permanent copy of the raw SBOM, Grype, OSV-Scanner, and govulncheck output and release checks: release report-2026-11-02, folder supply-chain-shard-*/docker__docker-bench-security/.

2 manifests and lockfiles scanned

.github/workflows/issues.yml, .github/workflows/slsa.yml

Full JSON for this project · Atom feed of weekly changes

Badges

shields.io endpoints refreshed with each weekly scan. They report this week's result for the latest release, nothing more.

[![release verification](https://img.shields.io/endpoint?url=https%3A%2F%2Frezmoss.github.io%2Fawesome-security-pipeline%2Fbadges%2Fdocker%2Fdocker-bench-security%2Frelease.json)](https://rezmoss.github.io/awesome-security-pipeline/projects/docker/docker-bench-security/index.html)

How this report is made

Every Sunday a GitHub Actions workflow resolves each catalog tool to its latest release and runs the checks below. Every tool is installed from its own latest release and verified against its published checksum or digest. Nothing from the scanned projects is built or executed; release binaries are analyzed as files.

How the weekly supply-chain report is producedEvery Sunday the catalog's tools are resolved to their latest release. Manifests and workflows go to Syft, Grype, OSV-Scanner, sbomlyze, and zizmor; the release binary and its signatures go to govulncheck, Cosign, slsa-verifier, and GitHub attestation verification; the repository goes to OpenSSF Scorecard. Results are compared with the previous week and published here.Catalog78 tools in READMELatest releaseGitHub API, every SundayManifests & workflowssparse checkout, no testsRelease binaryLinux amd64 + signaturesRepositoryGitHub & OpenSSF dataSyftSBOMGrype + OSV-Scannerknown advisoriessbomlyzediff + minimum elementszizmorworkflow auditgovulncheckvulnerable code in binaryCosign · slsa-verifier · ghrelease verificationOpenSSF Scorecardrepository practicesCompare with last weekdata branch historyThis reportoverview + project pages
ToolWhat it does hereVersion this week
SyftGenerates a CycloneDX SBOM from each release's manifests and lockfiles.1.55.0
GrypeMatches the SBOM against known vulnerabilities.0.121.0
OSV-ScannerChecks the same files against the OSV database to confirm or add matches.2.7.0
govulncheckFor Go tools, finds which advisories have vulnerable code compiled into the released Linux binary.1.9.0
zizmorAudits the project's GitHub Actions workflows for injection, unpinned actions, and excessive permissions.1.31.1
OpenSSF ScorecardScores repository security practices such as code review, branch protection, and pinned dependencies.5.6.0
CosignVerifies Sigstore signatures on the release binary or its checksums file.3.1.4
slsa-verifierVerifies SLSA build provenance published with the release.2.7.1
GitHub CLI attestationsVerifies GitHub artifact attestations for the release binary.—
sbomlyzeDiffs each SBOM against last week and scores NTIA, CISA, and BSI minimum elements. Maintained by this repository's maintainer.0.6.0