Ensure all build steps are defined as code

MediumLevel 1Manual reviewgithub

Description

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. Reported as a manual review item: no reliable read-only gh api check exists for this control.

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 all build steps are defined as code and stored in a version control system. Expected state: Convert pipeline instructions into code-based syntax and upload them to the organization's version control platform.

How it is fixed

Fix method: Guidance or infrastructure patch

Convert pipeline instructions into code-based syntax and upload them to the organization's version control platform.

Properties

Operating systems: Any
Tags: githubbuild-pipelines
Reference: CIS GitHub Benchmark v1.2.0 - 2.3.1 Ensure all build steps are defined as code