Ensure the build environment is logged

中等級 1人工審核gitlab

說明

Keep build logs of the build environment detailing configuration and all activity within it. Also, consider to store them in a centralized organizational log store. Logging the environment is important for two primary reasons: one, for debugging and investigating the environment in case of a bug or security incident; and two, for reproducing the environment easily when needed. Storing these logs in a centralized organizational log store allows the organization to generate useful insights and identify anomalies in the build process faster.

檢查方式

稽核方法: 人工審核

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

Verify that the build environment is logged and stored in a centralized organizational log store. When a build environment is created, all information related to the environment is logged as part of the job logs. Depending on the stage in the build environment lifecycle, the path to retrieve the logs will differ: - When a job is running: #{ROOT_PATH}/gitlab- ci/builds/#{YYYY_mm}/#{project_id}/#{job_id}.log - After a job is finished: #{ROOT_PATH}/gitlab- rails/shared/artifacts/#{disk_hash}/#{YYYY_mm_dd}/#{job_id}/#{job_artifact_id}/jo b.log - After a log is archived: #{bucket_name}/#{disk_hash}/#{YYYY_mm_dd}/#{job_id}/#{job_artifact_id}/job.lo g

修補方式

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

Keep logs of the build environment. Also, store the logs in a centralized organizational log store. This is automatically done by GitLab and can be retrieved in the paths mentioned in the audit section.

屬性

作業系統: 不限
標籤: devsecopsgitlablogging
參考資料: CIS GitLab Benchmark v1.0.1 - 2.1.3 Ensure the build environment is logged