Ensure all external dependencies used in the build process are locked

MediumLevel 1Manual reviewgitlab

Description

External dependencies may be public packages needed in the pipeline, or perhaps the public image being used for the build worker. Lock these external dependencies in every build pipeline. External dependencies are sources of code that aren't under organizational control. They might be intentionally or unintentionally infected with malicious code or have known vulnerabilities, which could result in sensitive data exposure, data harvesting, or the erosion of trust in an organization. Locking each external dependency to a specific, safe version gives more control and less chance for risk.

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.

Ensure every external dependency being used in pipelines is locked. - Go to Code > Repository in your project - Review the following files at the root of your repository: o Gemfiles o package.jsons o go.sum - Review the versions of the external dependencies

How it is fixed

Fix method: Guidance or infrastructure patch

For all external dependencies being used in pipelines, verify they are locked. - Go to Code > Repository in your project - Review the following files at the root of your repository: o Gemfiles o package.jsons o go.sum - Ensure the version of the external dependencies corresponds to your internal policies

Properties

Operating systems: Any
Tags: devsecopsgitlab
Reference: CIS GitLab Benchmark v1.0.1 - 2.4.2 Ensure all external dependencies used in the build process are locked