> 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/identity-access-management/appsec-cicd-35.md).

# Outside collaborators have admin access to a repository

## Rule Details

|                       |                  |
| --------------------- | ---------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_35 |
| Category              | IAM              |
| Severity              | HIGH             |

## Impact

Outside collaborators are not explicit members of the GitHub organization, and are usually used to allow contributors from outside the company (as contractors) to collaborate on specific repositories. In contrast to organization members, where the security of their accounts is the responsibility of the organization (such as mailbox protection, phishing and security awareness), the security level of outside collaborators are outside of the organization's jurisdiction. Therefore, outside collaborators should carefully be granted access to the organization and its repositories, in order to limit the potential damage in case of compromise of their account. Outside collaborators granted admin access to repositories induce high risk to the organization, as they are able to administer the repository and commit malicious code while circumventing security measures.


---

# 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/identity-access-management/appsec-cicd-35.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.