Ensure all build steps are defined as code

中等級 1人工審核gitlab

說明

Use pipeline as code for build pipelines and their defined steps. Storing pipeline instructions as code in a version control system means automation of the build steps and less room for human error, which could potentially lead to a security breach. Additionally, It creates the ability to revert back to a previous pipeline configuration in order to pinpoint the affected change should a malicious incident occur.

檢查方式

稽核方法: 人工審核

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

Verify that all build steps are defined as code and stored in a version control system. - On the left sidebar, select Code > Repository. - Check if a .gitlab-ci.yml file is at the root of your repository

修補方式

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

Convert pipeline instructions into code-based syntax and upload them to the organization's version control platform. - On the left sidebar, select Code > Repository. - Above the file list, select the branch you want to commit to. If you’re not sure, leave master or main. Then select the plus icon () and New file: - For the Filename, type .gitlab-ci.yml. - Select Commit changes.

屬性

作業系統: 不限
標籤: devsecopsgitlab
參考資料: CIS GitLab Benchmark v1.0.1 - 2.3.1 Ensure all build steps are defined as code