> 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-4.md).

# Actively used BitBucket repository lacks branch protection rules

## Rule Details

|                       |                        |
| --------------------- | ---------------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_4        |
| 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.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.