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

# Requestors allowed to self-approve pull requests on default branch

## Rule Details

|                       |                       |
| --------------------- | --------------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_180     |
| Category              | Pipeline Flow Control |
| Severity              | MEDIUM                |

## Impact

A requestor who opened a pull request can approve their own changes on an actively used repository\*. Repository policy requires approval from reviewers to merge pull requests which can result in a requestor being able to approve their own request, if the required number of reviewers is set to 1. If the number of reviewers is set to more than 1, the requestor is considered as one of the reviewers, reducing the number of additional reviewers required to approve the pull request. Attackers compromising such a user account can potentially directly push code, which is likely to flow through the pipeline and be used in production systems. \* 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 to prevent requestors from approving their own changes, and to require a minimum number of reviewers to approve pull requests in order to ensure that code is reviewed before merged:

1. In Azure DevOps, browse to **Repositories** under 'Project Settings'.
2. Select a repository and enter its policies.
3. Uncheck **Allow requestors to approve their own changes**.
4. Under **Automatically included reviewers** uncheck **Allow requestors to approve their own changes** for each reviewer.


---

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