> 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/credential-hygiene/appsec-cicd-178.md).

# GitHub Organization secret not scoped

## Rule Details

|                       |                    |
| --------------------- | ------------------ |
| Cortex AppSec Rule ID | APPSEC\_CICD\_178  |
| Category              | Credential Hygiene |
| Severity              | MEDIUM             |

## Impact

In GitHub organizations where secrets are not scoped to specific repositories and GitHub Actions is enabled, a malicious actor who has access to the organization could access these secrets by creating a workflow or modifying an existing workflow. This creates a security risk, as sensitive information could be exposed to unauthorized parties.

## Recommended Solution - Buildtime

It’s important to scope organization secrets to specific repositories and grant permission on a need-to-access basis only, following the principle of least privilege.

To change the scope of a GitHub organization secret:

1. Browse to the **Settings** tab of your GitHub organization’s repository where the secret is located.
2. Click on the **Secrets** menu located in the left-hand side of the page.
3. Select the required secret and click on its name to open the details page.
4. Click on the **Edit** button on the top right-hand corner of the page.
5. Under **Repository access**, select the repositories that should have access to the secret.
6. Click on the **Update secret** button to save the changes.

For more information refer to <https://docs.github.com/en/enterprise-cloud@latest/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-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 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/credential-hygiene/appsec-cicd-178.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.