> 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/iac-security/iam/appsec-glb-2.md).

# Gitlab branch protection rules defined in Terraform allow force push misconfiguration detected in co

## Gitlab branch protection rules defined in Terraform allow force push misconfiguration detected in code

### Rule Details

|                        |                         |
| ---------------------- | ----------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GLB\_2          |
| Category - Subcategory | IAM - Overly Permissive |
| Provider               | OTHER                   |
| Severity               | MEDIUM                  |
| Framework              | Terraform               |

### Impact

Force pushing to a Git branch overrides the existing history on that branch, which can lead to irreversible loss of data and potential disruption in the collaborative development process. It can also inadvertently overwrite changes made by others, leading to confusion and conflicts within the team. This rule ensures that GitLab branch protection rules are set to prevent force pushes, thereby preserving the integrity of the branch history.

### How to Fix

To adhere to this rule, ensure that the `allow_force_push` setting in GitLab branch protection is set to `false`.

### By setting `allow_force_push` to `false`, you ensure that the historical integrity of the branch is preserved and that force pushes, which can potentially disrupt the repository's history and ongoing work, are not allowed. \[source,go]

resource "gitlab\_branch\_protection" "example" { project = gitlab\_project.example.id branch = "main"

## Disable force pushes to the protected branch

* allow\_force\_push = false

## ... other branch protection settings ...

### }


---

# 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/iac-security/iam/appsec-glb-2.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.