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

# Permissive organization base permissions

## Rule Details

|                       |                  |
| --------------------- | ---------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_29 |
| Category              | IAM              |
| Severity              | LOW              |

## Impact

Organization base permissions apply to all organization members when accessing any organization repository. Any permission besides None, potentially allows compromised accounts to be used by attackers to steal all code stored in the organization repositories. In addition, Read permissions and higher can potentially allow executing attacks against CI/CD pipelines by triggering builds based on forks containing malicious code.

## Recommended Solution - Buildtime

It is recommended to apply the principle of least privilege, by setting the organization base permissions to None, and grant granular permissions on repositories based on the organization needs. To configure base permissions for an organization, refer to GitHub documentation: <https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization>.


---

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