> 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/third-party-services/appsec-cicd-97.md).

# Excessive GitHub App permissions

## Rule Details

|                       |                  |
| --------------------- | ---------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_97 |
| Category              | Supply Chain     |
| Severity              | HIGH             |

## Impact

A GitHub App with 'write' permissions to an organization that has not performed any actions requiring 'write' permissions for more than 30 days may not require these permissions. This poses a threat, as attackers who gain control of the GitHub App can potentially access the organization and its repositories, thereby enlarging the surface of the attack.

## Recommended Solution - Buildtime

If the GitHub App is not in use, delete the app from the organization. If the app is in use, but is not using its granted write permissions, consider asking the app creator to reduce the requested permissions to **read**.

**📌 NOTE**\
App creators, not organization admins, control the level of permission granted to GitHub Apps.


---

# 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/third-party-services/appsec-cicd-97.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.