> 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/data-protection/appsec-cicd-19.md).

# Forking of a private repository is allowed

## Rule Details

|                       |                  |
| --------------------- | ---------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_19 |
| Category              | Data Protection  |
| Severity              | MEDIUM           |

## Impact

Misconfiguration of private repositories may allow sensitive code to be inadvertently/intentionally leaked. A user account might fork the repository to another project, leading to leakage of code. It can also lead to the creation of pull requests from the forked repository to the original repository. This can lead to the execution of malicious code on the CI, even by users with read-only permissions on the original repository.

## Recommended Solution - Buildtime

When not required, disable the forking of private repositories.

To restrict forking of a private repository:

1. Browse to project **Settings**.
2. Under **Visibility**, select **Project Features**.
3. Disable the **Fork** setting under the **Permissions** section.


---

# 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/data-protection/appsec-cicd-19.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.