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

# "Require review from Code Owners" Branch Protection rule was disabled

## Rule Details

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

## Impact

Disabling the "Require review from Code Owners" rule creates a critical Supply Chain vulnerability by allowing unauthorized changes to reach your production environment without expert oversight. This bypasses the "Four-Eyes" principle, enabling a compromised account or insider threat to inject malicious code into sensitive files like build scripts, CI/CD pipelines, or dependency manifests. Consequently, an attacker can ship a backdoored version of your software that appears legitimate to downstream customers because it was signed and distributed by your trusted internal processes.

## Recommended Solution - Buildtime

* Verify the reason for removing the CODEOWNERS file.
* Consider restoring the deleted CODEOWNERS file.


---

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