Ensure build secrets are limited to the minimal necessary scope

高等級 2人工審核gitlab

說明

Build tools providers offer a secure way to store secrets that should be used during the build process. These secrets will often be credentials used to access other tools, for example for pulling code or for uploading artifacts. Access to these secrets can be defined on various scopes. To protect these critical assets it is important to choose the most restrictive scope necessary. Allowing over permissive access to these secrets may affect on their exposure. For example if a secret is defined in an organization level, and users can create new repositories, there is a scenario where a user can create a new repo and run a controlled build just to exfiltrate these secrets.

檢查方式

稽核方法: 人工審核

此項建議無法自動檢查。當您傳入 --include-manual 時，掃描結果會列出此項目並附帶這些說明。

In the gitlab-ci.yml file, review the secrets permission scope defined in either a file or in an external secrets manager.

修補方式

修補方法: 操作指南或基礎設施修補檔

In the gitlab-ci.yml file, review the secrets defined in either a file or in an external secrets manager and change over permissive scopes to more restrictive ones based on the required access.

屬性

作業系統: 不限
標籤: devsecopsgitlab
參考資料: CIS GitLab Benchmark v1.0.1 - 2.1.7 Ensure build secrets are limited to the minimal necessary scope