Ensure build secrets are limited to the minimal necessary scope

高级别 2人工审核github

说明

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. 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 ... Reported as a manual review item: no reliable read-only gh api check exists for this control.

检查方式

审计方法: 人工审核

此项建议无法自动检查。当您传入 --include-manual 时，扫描结果会列出该项并附带这些说明。

For each build tool in use, review the secrets defined and the permission scopes they are assigned. Expected state: For each build tool, review the secrets defined and their permissions scope and change over permissive scopes to more restrictive ones based on the required access.

修复方式

修复方法: 操作指南或基础设施补丁

For each build tool, review the secrets defined and their permissions scope and change over permissive scopes to more restrictive ones based on the required access.

属性

操作系统: 任意
标签: githubbuild-pipelines
参考: CIS GitHub Benchmark v1.2.0 - 2.1.7 Ensure build secrets are limited to the minimal necessary scope