TMA-GITLAB-2.2.1
Ensure build workers are single-used
설명
Use a clean instance of build worker for every pipeline run. Using a clean instance of build worker for every pipeline run eliminates the risks of data theft, data integrity breaches, and unavailability. It limits the pipeline's access to data stored on the file system from previous runs, and the cache is volatile. This prevents malicious changes from affecting other pipelines or the Continuous Integration/Continuous Delivery system itself.
점검 방법
감사 방식: 수동 검토
이 권장 사항은 자동으로 점검할 수 없습니다. --include-manual 옵션을 전달하면 스캔 결과에 이 지침과 함께 표시됩니다.
Ensure that every pipeline that is being run has its own clean, new runner. In GitLab, each of your jobs runs in a newly provisioned VM, which is dedicated to the specific job. The VM is active only for the duration of the job and immediately deleted. This means that any changes that your job makes to the virtual machine will not be available to a subsequent job. The virtual machine where your job runs has sudo access with no password.
조치 방법
조치 방식: 가이드 또는 인프라 패치
Create a clean build worker for every pipeline that is being run, or use build platform- hosted runners, as they typically offer a clean instance for every run. In GitLab, use Runner SaaS to ensure all of these settings are available by default and that each job runs in a dedicated VM.
속성
- 운영 체제
- 모두
- 태그
- devsecopsgitlab
- 참고 자료
- CIS GitLab Benchmark v1.0.1 - 2.2.1 Ensure build workers are single-used