Ensure deployment configuration manifests are pinned to a specific, verified version

MediumLevel 1Manual reviewgithub

Description

Deployment configuration is often stored in a version control system and is pulled from there. Pin the configuration used to a specific, verified version or commit Secure Hash Algorithm (SHA). Avoid referring configuration without its version tag specified. Deployment configuration manifests are often stored in version control systems and pulled from there either by automation platforms, for example Ansible, or GitOps platforms, such as ArgoCD. Reported as a manual review item: no reliable read-only gh api check exists for this control.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

For every deployment configuration manifest in use, ensure it is pinned to a specific version or commit Secure Hash Algorithm (SHA). Expected state: For every deployment configuration manifest in use, pin to a specific version or commit Secure Hash Algorithm (SHA).

How it is fixed

Fix method: Guidance or infrastructure patch

For every deployment configuration manifest in use, pin to a specific version or commit Secure Hash Algorithm (SHA).

Properties

Operating systems: Any
Tags: githubdeployment
Reference: CIS GitHub Benchmark v1.2.0 - 5.1.7 Ensure deployment configuration manifests are pinned to a specific, verified version