TMAegis
gitlab 관련 규칙 더 보기

TMA-GITLAB-2.3.5

Ensure access to build process triggering is minimized

보통레벨 1수동 검토gitlab

설명

Restrict access to pipeline triggers. Build pipelines are used for multiple reasons. Some are very sensitive, such as pipelines which deploy to production. In order to protect the environment from malicious acts or human mistakes, such as a developer deploying a bug to production, it is important to apply the Least Privilege principle to pipeline triggering. This principle requires restrictions placed on which users can run which pipeline. It allows for sensitive pipelines to only be run by administrators, who are generally the most trusted and skilled members of the organization.

점검 방법

감사 방식: 수동 검토

이 권장 사항은 자동으로 점검할 수 없습니다. --include-manual 옵션을 전달하면 스캔 결과에 이 지침과 함께 표시됩니다.

For every pipeline in use, verify only the necessary users have permission to trigger it. - On the left sidebar, select Search or go to and find your project. - Select Manage > Members - At the top of the member list, from the dropdown list, sort by Max role the members have in the group - Review the members to ensure relevant members are allowed to trigger pipelines in protected environments.

조치 방법

조치 방식: 가이드 또는 인프라 패치

For every pipeline in use, grant only the necessary users permission to trigger it. - On the left sidebar, select Search or go to and find your project. - Select Settings > CI/CD. - Expand Protected environments. - Select Protect an environment. - From the Environment list, select the environment you want to protect. - In the Allowed to deploy list, select the role, users, or groups you want to give deploy access to. Keep in mind that: o There are two roles to choose from: ▪ Maintainers: Allows access to all of the project’s users with the Maintainer role. ▪ Developers: Allows access to all of the project’s users with the Maintainer and Developer role. o You can only select groups that are already invited to the project. o Users must have at least the Developer role to appear in the Allowed to deploy list. - In the Approvers list, select the role, users, or groups you want to give deploy access to. Keep in mind that: o There are two roles to choose from: ▪ Maintainers: Allows access to all of the project’s users with the Maintainer role. ▪ Developers: Allows access to all of the project’s users with the Maintainer and Developer role. o You can only select groups that are already...

속성

운영 체제
모두
태그
access-controldevsecopsgitlab
참고 자료
CIS GitLab Benchmark v1.0.1 - 2.3.5 Ensure access to build process triggering is minimized