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

# Jenkins credentials stored with global scope

## Rule Details

|                       |                    |
| --------------------- | ------------------ |
| Cortex AppSec Rule ID | APPSEC\_CICD\_38   |
| Category              | Credential Hygiene |
| Severity              | HIGH               |

## Impact

By default, Jenkins credentials are stored under the global scope. Global scope credentials are accessible by all Jenkins jobs, which increases the risk of credential theft by executing a malicious job in the instance.

## Recommended Solution - Buildtime

Avoid setting credentials with global scope. Instead, limit the scope of credentials so that the credentials are only accessible on jobs where they are required.

### EXAMPLES

* **Limit the scope of Jenkins credentials using folder scopes**
  1. Install the [Folders](https://plugins.jenkins.io/cloudbees-folder/) plugin.
  2. Create a folder for each group of pipelines that require access to a set of credentials, and move the pipelines to the folder.
  3. Create the credentials and set it with the folder’s scope.
* **Limit the scope of Jenkins credentials using user scopes**

  Refer to the instructions in the following link: <https://docs.cloudbees.com/docs/admin-resources/latest/pipelines/user-scoped-creds#\\_adding\\_user\\_scoped\\_credentials\\_to\\_your\\_user\\_account>.


---

# 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/credential-hygiene/appsec-cicd-38.md?ask=<question>&goal=<user_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.