> 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/visibility/technologies/jenkins-plugins.md).

# Jenkins Plugins

**Jenkins Plugins** displays an inventory and details of Jenkins plugins across your organization’s Jenkins servers which have been integrated with Prisma Cloud, including the amount of installations and location. You can identify and remove unused plugins, reducing your attack surface. In addition, you can view all CVE vulnerabilities detected and their severity CVSS score, allowing you to prioritize remediation efforts.

To access 'Jenkins Plugins', in **Application Security** select > **Home** > **Technologies** > click on the **Jenkins Plugins** tab.

<figure><img src="/files/kr5EOOoI5Dk9vfHiE5MQ" alt="jenkins plugin2.0"><figcaption></figcaption></figure>

Jenkins Plugins includes the following details:

* **Plugin Name**: The name of the plugin
* **Version**: The plugin version
* **Installations**: The number of plugin installations
* **Installed on**: The Jenkins server that the plugin is installed on. See the 'Installed On' tab of the resource explorer below for more details about on plugin vulnerabilities
* **Vulnerabilities**: The name of the vulnerability found in the plugin, including a link to the [NIST national vulnerability database](https://nvd.nist.gov/vuln). Refer to the 'Vulnerabilities' tab of the resource explorer below for more details about on plugin vulnerabilities
* **Highest Severity**: The CVSS score of the most severe vulnerability found in the plugin

Selecting a plugin in the inventory table opens the **resource explorer**, displaying additional information about the entity.

* The **Details** tab opens as the default view, providing plugin metadata such as the version, amount of installations, and the number of vulnerabilities detected in the plugin, categorized by severity

  <figure><img src="/files/3u8tYIxuo6KwWPY1pWxo" alt="jenkins plugin details2.0"><figcaption></figcaption></figure>
* **Installed On**: Details of the Jenkins servers where the plugin is installed, including whether the plugins are enabled or disabled

  <figure><img src="/files/roXvAG1lNRdoIs3moHTW" alt="jenkins plugin installon2.0"><figcaption></figcaption></figure>
* **Vulnerabilities**: Details of vulnerabilities detected in the plugins, including the CVE ID with a link to the database for more details, and the CVSS score associated with each vulnerability

  <figure><img src="/files/L2ocwjpYU3AfV9bQmA1Q" alt="jenkins plugin vulnerabilities1.2"><figcaption></figcaption></figure>

## Filters

You can apply the following filters to narrow a search for a plugin.

* **Plugin Name**: Filter by the plugin name
* **Installed On**: Filter by the Jenkins server that the plugin is installed on
* **Vulnerabilities**: Filter by the vulnerability CVE ID
* **Severity**: Filter by the severity of the vulnerability. Values: 'Critical', 'High', 'Medium', 'Low'


---

# 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/visibility/technologies/jenkins-plugins.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.