Actively used GitLab repository lacks branch protection rules

Rule Details

Cortex AppSec Rule ID	APPSEC_CICD_3
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.