> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-systems/add-jenkins-cicd-system.md).
# Jenkins Server
Integrate Prisma Cloud with your Jenkins server to gain visibility into and monitor the systems, technologies, configurations, and pipelines that make up the Jenkins platform. Integrating Jenkins will allow you to conduct security scans to identify issues such as CI/CD pipeline risks, vulnerabilities, and exposed secrets in the Jenkins environment, allowing you to understand and fix issues as soon as they are detected.
1. Before you begin.
1. [Create a Service Account](/content-collections/administration/add-service-account-prisma-cloud.md) to enable access to Prisma Cloud.
* Following the principle of least privilege, it is recommended to assign the access token the **Developer** role when creating the Service Account. This grants only the necessary permissions and minimizes potential security risks
* Copy and save the generated access key (key ID and secret) for your Service Account.
2. Add the Prisma Cloud IP addresses and hostname for Application Security to an [allow list](/content-collections/get-started/console-prerequisites.md) to enable access to the Prisma Cloud Console.
2. On the Prisma Cloud console.
1. In Application Security, select **Home** > **Settings** > **Connect Provider** > **Code & Build Providers**.
2. Select **Jenkins Server** (under CI/CD Systems) in the catalog that is displayed.
3. Select **Add Integration** from the Jenkins integration wizard.
4. Provide a **Jenkins Instance Display Name** > **Next**.
A unique **Jenkins instance identifier** is automatically generated after providing the Jenkins instance display name. This display name is an alias of your choice, allowing you to identify the integration.
5. Select **Download** in *step 1* of the wizard to download the Prisma Cloud Application Security Jenkins plugin **prisma-cloud.hpi** file.
6. Copy and save the unique Jenkins instance identifier from *step 2* of the wizard.
7. Select **Done**.
The integration is added in the UI but integration is pending only and will only be completed after completing step 3 below.
You can retrieve your Jenkins instance identifier by accessing the integrated Jenkins Server (see step 1 above) > selecting the **Actions** menu of an integration in the wizard > **Copy instance identifier**.
3. In Jenkins.
1. If your Jenkins server has limited outgoing connections, make sure to permit an outgoing connection from the Jenkins server to Prisma IP addresses - see *step 1* above.
2. Install the plugin on your Jenkins server.
* Open Jenkins and select: **Manage Jenkins** > **Plugins** (under *System Configuration*) > **Advanced settings**.
* Select **Choose File** in the **Deploy Plugin** section > browse for the **PrismaCloudPlugin.hpi** file > **Upload** > **Deploy**.
3. Configure the plugin.
* Open **Jenkins** > Select **Manage Jenkins** > **System** (under *System Configuration*) > **Prisma Cloud**.
* Fill in the provided fields.
* **Jenkins Instance Display Name**: The alias that you provided in *step 2* above
* **Jenkins Instance Identifier**: The identifier generated when creating the Jenkins instance display name
* **Access Key ID**: Generated in *step 1* above
* **Access Key Secret**: Generated in *step 1* above
* **Reports Recurrence Period** (Value: minutes): The frequency with which reports are generated. We recommend that you do not change the default value
The Prisma Cloud Application Security module is integrated with your Jenkins system.
Always refer to the official [Jenkins documentation](https://www.jenkins.io/doc/book/managing/plugins/) when installing plugins on Jenkins servers.
4. Verify integration.
1. In **Application Security**, select **Home** > **Settings** > **CI/CD Systems** tab.
2. Confirm that the status of the **Jenkins** instance displays **Active** under **Status**.
It may take up to 3 minutes for the integration status to be updated.
5. Next step: Monitor and manage scan results.
The next scan of your Jenkins servers will include the new integration, and the results will be displayed in [Repositories](/content-collections/application-security/visibility/repositories.md).
## Support for Multiple Integrations
Prisma Cloud supports multiple integrations for Jenkins Server instances.
Multiple integrations from a single Prisma Cloud account enables you to:
* View a list of integrations on a single console
* Delete an existing integration
1. Add additional Jenkins Server integrations.
1. In Application Security, select **Home** > **Settings > \*Connect Provider** > **Code & Build Providers** > **Jenkins Server** (under CI/CD Systems).
2. Select **Add integration** in the wizard.
3. Repeat the integration process above.
The new integration is displayed on the landing page of the integration wizard. To view scan results, see the integration process above.
## Manage Integrations
Manage integrations from the integration wizard.
1. Access the Jenkins integration wizard - see **step 1** of [Support for Multiple Integrations](#support-multi-integrate) above > select the menu under **Actions**.
2. From *Actions* you can:
* Remove integrations
* Edit integration names
* Copy an instance identifier
---
# 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://docs.prismacloud.io/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-systems/add-jenkins-cicd-system.md?ask=&goal=
```
`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.