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

СреднийУровень 1Ручная проверкаgitlab

Описание

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...

Как проверяется

Метод проверки: Ручная проверка

Эту рекомендацию нельзя проверить автоматически. Сканирование выводит её вместе с этими инструкциями при указании флага --include-manual.

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

Как исправляется

Метод исправления: Рекомендация или патч инфраструктуры

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

Свойства

Операционные системы: Любая
Теги: devsecopsgitlab
Источник: CIS GitLab Benchmark v1.0.1 - 5.1.7 Ensure deployment configuration manifests are pinned to a specific, verified version