> 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/identity-access-management/appsec-cicd-184.md). # Any organization member can create internal repositories ## Rule Details | | | | --------------------- | ----------------- | | Cortex AppSec Rule ID | APPSEC\_CICD\_184 | | Category | IAM | | Severity | LOW | ## Impact All members of an organization have privileges to create internal repositories. If a member's account or access token is compromised, a malicious actor could create such a repository and access all of the organization's secrets scoped to private and internal repositories. For example, if the scope of a GitHub organization secret is not limited to specific repositories, any member of the organization can create an internal repository and configure a GitHub Actions workflow to retrieve the secret. In addition, internal repositories are accessible to any member in the enterprise, which could potentially allow unauthorized access to these repositories. ## Recommended Solution - Buildtime Disable the excessive permissions granted to all organization members to create private repositories. To disable internal repository creation refer to . If the above mitigation is not possible, or in addition to it, 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 privileges. 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-184.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.