> 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/system-configurations/appsec-cicd-181.md).

# Self-hosted runner group allows public repositories

## Rule Details

|                       |                      |
| --------------------- | -------------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_181    |
| Category              | System Configuration |
| Severity              | HIGH                 |

## Impact

Using a self-hosted runner with a public GitHub repository carries significant security risks, due to the fact that self-hosted runners are naturally less secure, as you have to design and maintain a secure solution for the runner. An attacker who forks public repositories can potentially run malicious code on self-hosted runners by creating a pull request that triggers a workflow, achieving persistence on the runner and access to local files and leftover secrets, as well as accessing internal infrastructure.

## Recommended Solution - Buildtime

Evaluate the need to allow self-hosted runners to run on public repositories. If not required, use a hosted runner.

In addition, make sure to disable the `Allow public repositories` setting: Browse to **Organization Settings** > **Actions** > **Runner Groups**.

If you must use a self-hosted runner, implement mechanisms such as sandboxing, ephemeral build environments, and job isolation to mitigate risks.

For more information, please refer to <https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group>.


---

# 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/ci-cd-security/system-configurations/appsec-cicd-181.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.