> 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-71.md). # GitLab project job token authorized to access other projects ## Rule Details | | | | --------------------- | ------------------------------ | | Cortex AppSec Rule ID | APPSEC\_CICD\_71 | | Category | Pipeline Based Access Controls | | Severity | LOW | ## Impact GitLab pipeline jobs are assigned with a token that enables authenticating to specific GitLab API endpoints. The token is assigned with the same permissions as the user who triggered the pipeline job. The token scope can be limited to the current project only, or to be authorized with access to any private project as the triggering user account. An unlimited token can allow attackers compromising the pipeline job to misuse the permissions granted by the token scope to expand their attack surface by executing further attacks against additional projects. ## Recommended Solution - Buildtime Limit pipeline job token scope: 1. Browse to the project **Settings**. 2. Under **CI/CD**, expand **Token Access** and enable the **Limit CI\_JOB\_TOKEN access** setting. --- # 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/pipeline-based-access-controls/appsec-cicd-71.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.