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

# Push restrictions not enforced on the default branch

## Rule Details

|                       |                        |
| --------------------- | ---------------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_69       |
| Category              | Flow Control Mechanism |
| Severity              | MEDIUM                 |

## Impact

An actively used repository\* does not enforce restrictions limiting who can push or merge code directly to the default branch. This configuration allows users with 'write' permissions to bypass mandatory review and approval processes (such as pull requests). This lack of flow control creates a significant risk, as malicious code can be injected directly into the default branch, flow through the CI/CD pipeline, and reach production systems.

* An actively used repository has at least two contributors, over 50 commits, and has been updated in the last 90 days.

## Recommended Solution - Buildtime

We recommend removing all entities from the **Write access** field of the default branch protection rule (which is unrelated to repository write permissions), to prevent unreviewed push of code:

1. Open the default branch settings editor: navigate to repository **Settings** > **Branch permissions** > edit the rule that applies to the default branch.
2. Delete all users and groups from the **Write access** field.


---

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