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

# Default workflow permissions in the organization set to 'read and write'

## Rule Details

|                       |                                |
| --------------------- | ------------------------------ |
| Cortex AppSec Rule ID | APPSEC\_CICD\_128              |
| 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 the pipeline's default permissions are set to 'read and write', the GITHUB\_TOKEN is assigned with 'write' permissions. An attacker gaining access to a GitHub Actions pipeline with 'write' permissions can push malicious code into the repository, which could potentially reach the production environment.

## Recommended Solution - Buildtime

Follow the least privileges principal and reduce the potential attack surface by making sure that the pipeline is granted the minimum required permissions. It’s a good security practice to set the default permission for the GITHUB\_TOKEN to read access only for repository contents. The permissions can then be increased, as required, for individual jobs within the pipeline file.

Prisma Cloud recommends configuring permissions at the highest level possible - Enterprise if your license supports it, otherwise at organization level, as all child entities will by default inherit the parent permissions.

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#managing-github-actions-permissions-for-your-repository>.


---

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