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

# Unrestricted usage of GitHub Actions allowed across the organization

## Rule Details

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

## Impact

Allowing all GitHub Actions to be used in all repositories across the organization regardless of their author, exposes the organization to the risk of a malicious actor taking control over an action's repository. A hijacked action in use in your pipeline can potentially execute malicious code which can reach the production environment.

## Recommended Solution - Buildtime

Enforce policies to control how organization repositories can use GitHub Actions:

1. Navigate to organization **Settings** > **Actions** > **General** tab.
2. If only using actions defined in repositories within the enterprise, select the **Allow enterprise actions and reusable workflows** policy setting.
3. If this policy is too restrictive, consider allowing specific actions, allowing actions created by GitHub and/or allowing actions by Marketplace verified creators.

Prisma Cloud recommends configuring permissions at the highest level possible, that is Enterprise, if your license supports it. If Enterprise is not available, configure permissions at the organization level, as all child entities will by default inherit the parent permissions.

For more information refer to: <https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-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 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-130.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.