TMA-GITLAB-2.4.2
Ensure all external dependencies used in the build process are locked
說明
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.
檢查方式
稽核方法: 人工審核
此項建議無法自動檢查。當您傳入 --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
修補方式
修補方法: 操作指南或基礎設施修補檔
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
屬性
- 作業系統
- 不限
- 標籤
- devsecopsgitlab
- 參考資料
- CIS GitLab Benchmark v1.0.1 - 2.4.2 Ensure all external dependencies used in the build process are locked