> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/flow-control-mechanism/appsec-cicd-2.md).

# 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>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/flow-control-mechanism/appsec-cicd-2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.