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

OrtaDüzey 1Manuel incelemegitlab

Açıklama

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. When a manifest is pulled from a version control system without tag or commit Secure Hash Algorithm (SHA) specified, it is pulled from the HEAD revision, which is equal to the 'latest' tag, and pulls the last change made. This increases the risk of encountering a new, potentially malicious configuration. If an attacker pushes malicious configuration to the version control system, the next user who pulls the HEAD revision will pull it and risk a...

Nasıl denetlenir

Denetim yöntemi: Manuel inceleme

Bu öneri otomatik olarak denetlenemez. --include-manual parametresini verdiğinizde tarama bunu bu talimatlarla birlikte listeler.

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

Nasıl düzeltilir

Düzeltme yöntemi: Kılavuz veya altyapı yaması

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

Özellikler

İşletim sistemleri: Herhangi biri
Etiketler: devsecopsgitlab
Referans: CIS GitLab Benchmark v1.0.1 - 5.1.7 Ensure deployment configuration manifests are pinned to a specific, verified version