> 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-git-5.md).

# GitHub pull request configurations defined in Terraform have less than 2 approvals misconfiguration

## GitHub pull request configurations defined in Terraform have less than 2 approvals misconfiguration detected in code

### Rule Details

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

### Impact

Pull request approvals are a critical part of the GitHub workflow, serving as a quality control measure to ensure code is reviewed and vetted before it is merged. Requiring at least two approvals for a pull request before merging can enhance the security and integrity of the code by ensuring that at least two separate individuals have reviewed the changes.

This rule checks that GitHub branch protection rules require at least two approvals on pull requests, which helps prevent unreviewed code from being merged into protected branches.

### How to Fix

Ensure your GitHub branch protection rules specify that at least 2 approvals are required before a pull request can be merged.

### Adjust the `required_approving_review_count` to `2` or more to comply with this rule. This change enforces that at least two separate approvals are required, thus implementing a two-person review process for any changes to the code base. \[source,go]

resource "github\_branch\_protection" "example" { repository\_id = github\_repository.example.node\_id pattern = "main"

required\_pull\_request\_reviews {

* required\_approving\_review\_count = 2

## ... other configurations ...

}

## ... 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-git-5.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.