TMA-GITLAB-2.1.7
Ensure build secrets are limited to the minimal necessary scope
说明
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