Actively used repository lacks branch protection rules

Rule Details

Cortex AppSec Rule ID	APPSEC_CICD_2
Category	Flow Control Mechanism
Severity	MEDIUM

Impact

An actively used repository does not have any protected branch settings configured. Protected branch settings are recommended to enforce stronger controls around the conditions that enable pushing code to important branches within a sensitive repo. Protected branch settings define whether collaborators can delete or force pushing to the branch. They also set requirements for any pushes to the branch, such as passing status checks or a linear commit history. Lack of protected branch settings can allow collaborators to inadvertently/intentionally push code, which introduces security risks to production. An actively used repository has at least two contributors, over 50 commits, and was updated in the last 90 days.

Recommended Solution - Buildtime

It is recommended that protected branch settings be configured on the repository. This ensures that code going through the pipeline meets the relevant security requirements, and it minimizes the risk of insecure/malicious code being pushed directly to production bound branches.

Branches used to push code further down the pipeline (for example those that trigger a build), and branches used as libraries in other code sources, are those that should be chosen for protection.

For additional information on configuring protected branch settings in GitHub, refer to: https://docs.github.com/en/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches