Ensure the build environment is logged

MediumLevel 1Manual reviewgitlab

Description

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.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --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

How it is fixed

Fix method: Guidance or infrastructure patch

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.

Properties

Operating systems: Any
Tags: devsecopsgitlablogging
Reference: CIS GitLab Benchmark v1.0.1 - 2.1.3 Ensure the build environment is logged