> 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/pipeline-tools.md).

# Pipeline Tools

**Pipeline Tools** provides an inventory of all third party services and tools used by an organization’s CI/CD pipeline. This visibility is invaluable, as it reveals the tools running in your CI/CD systems that are highly sensitive. We recommend reviewing the tools detected and displayed in the inventory with your engineering teams to ensure that the tools are all recognized and approved. Special attention should be given to tools with names designated as **Not Available**, as this could indicate less popular tools, or in some cases, even malicious ones.

You can gain insights into the scripts running in the CI pipeline and their usage, allowing you to understand risks and take action to reduce your attack surface.

'Pipeline Tools' currently supports Jenkins declarative pipelines, CircleCI, GitLab CI, GitHub Actions and Azure Pipelines.

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

<figure><img src="/files/sijS1oNtnhCmN9e3eiUd" alt="technologies pipelinetools intro3.1"><figcaption></figcaption></figure>

Pipeline Tools includes the following details.

* **Tool Name**: The name of the tool in the pipeline

  When the 'Not available' status is displayed, it indicates that the tool is not in Prisma Cloud’s Pipeline Tools catalog. This could be because it is either an internal tool or a public tool.
* **Insights**: Meaningful understandings gained by Palo Alto Networks from the data collected, analyzed and interpreted, about the pipeline tool. See below for more details. Values include:
  * **Suspicious Tool**: Prisma Cloud suspects that the tool may be malicious
  * **Unverified tool creator**: The tool owner is not verified by the hosted marketplace
  * **Low popularity**: The tool has minimal usage or stars in the hosted marketplace
  * **Archived Tool Repository**: The tool’s code repository has been archived and is no longer maintained
* **Executable**: Details of the executable including stars received from GitHub, the number of downloads a tool has from the CircleCI Orbs marketplace(UsedBy) and the identity of the tool creator - see below for more details.
* **Description**: A description of the tool- see below for more details.
* **Vendor**: The tool vendor
* **Pipelines**: The pipeline in which the tool is found. A number indicates the amount of pipelines that the tool is detected in. Hovering over a value displays all pipelines including the tool

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

* The **Details** tab opens as the default view, providing pipeline tool metadata such as a description of the tool, the tool vendor, the number of pipelines in which the tool was detected, and a link to the location containing the tool.

  <figure><img src="/files/pTsl4JUeZ9NjyySjjMom" alt="technologies pipelinetools details3.1"><figcaption></figcaption></figure>
* **Executable**: Details of the executable including where installed, stars received from GitHub, the number of downloads a tool has from the CircleCI Orbs marketplace(UsedBy) and the identity of the tool creator.

  <figure><img src="/files/moJM8tidLKMfaWQdqaUY" alt="technologies pipelinetools executable3.1"><figcaption></figcaption></figure>
* **Usage**: A list of pipelines in which the tool is found, as well as the command that runs the tool in the pipeline

  <figure><img src="/files/wLOoFiZubDMbgAEylRJL" alt="technologies pipelinetools usage3.1"><figcaption></figcaption></figure>
* **Insights**: The tool executables and categories that they are assigned to

  <figure><img src="/files/pdV2OUEsRrP5E4NTCG66" alt="technologies pipelinetools insights3.1"><figcaption></figcaption></figure>

## Filters

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

* **Tool Name**: Filter by tool name
* **Insights**: Filter by insights
* **Executable**: Filter by the usage of the tool
* **Pipelines**: Filter by pipeline that a tool is found in
* **Vendor**: Filter by tool vendor


---

# 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/pipeline-tools.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.