> 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/pipeline-based-access-controls/appsec-cicd-156.md).

# Excessive pipeline permissions on the repository

## Rule Details

|                       |                                |
| --------------------- | ------------------------------ |
| Cortex AppSec Rule ID | APPSEC\_CICD\_156              |
| Category              | Pipeline Based Access Controls |
| Severity              | MEDIUM                         |

## Impact

When a pipeline is executed, GitHub creates a short-lived token for interacting with the repository named GITHUB\_TOKEN. If permissions granted to the GITHUB\_TOKEN are not defined in the pipeline's yaml file, the pipeline's default permissions are set to either 'read and write' (default setting) or 'read repository contents' for all scopes, without considering the specific requirements of the workflow. Another security concern is when either "read-all" or "write-all" permissions are defined in a pipeline, as this grants the GITHUB\_TOKEN permissions to all scopes. An attacker gaining access to a GitHub Actions pipeline with excessive permissions can take full advantage of the permissive GITHUB\_TOKEN.

## Recommended Solution - Buildtime

Use the `permissions` attribute in the workflow yaml file to modify the default permissions granted to the GITHUB\_TOKEN, allowing only the minimum permissions required to execute a pipeline.

In addition, we recommend specifying permissions for each job in the pipeline. This will limit the exposure of binaries and actions in the pipeline to the repository to the minimum. For more information refer to <https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs>.

We also recommend changing the pipeline’s default permissions to \`read repository contents\`\` at the highest possible level (organization or enterprise, as applicable). This would limit the potential attack surface for all pipelines that do not have permissions explicitly defined.

For more information refer to <https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-default-github\\_token-permissions>.


---

# 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/pipeline-based-access-controls/appsec-cicd-156.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.