> 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/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/cicd-pipeline-as-an-asset/understand-and-prioritize-ci-cd-pipeline-assets.md).

# Understand and prioritize CI/CD pipeline assets

## How to access CI/CD pipeline assets

Under **Inventory**, select **All Assets** → **Code** → **CI/CD Pipelines**.

The CI/CD Pipelines page includes a dashboard and an inventory.

### CI/CD pipeline dashboard

The dashboard displays connected CI/CD providers and their discovered pipelines. Providers include GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines, CircleCI, Argo CD, and AWS CodeBuild.

Select a provider to filter the inventory table.

### CI/CD pipeline asset inventory

Select **Menu Settings** to view additional properties, including last job execution time and file contributors.

| Property                       | Description                                                                                     |
| ------------------------------ | ----------------------------------------------------------------------------------------------- |
| **Name**                       | The pipeline name discovered through the CI/CD integration. It is the primary asset identifier. |
| **CI/CD Provider**             | The platform hosting the pipeline.                                                              |
| **CI Instance**                | The CI/CD platform instance that executes the pipeline.                                         |
| **Repository**                 | The parent repository containing the pipeline definition.                                       |
| **VCS Provider**               | The VCS provider hosting the parent repository.                                                 |
| **CI File Path**               | The path to the pipeline definition file.                                                       |
| **Business Application Names** | Applications inherited from the parent repository, including business criticality.              |

## Filter and prioritize CI/CD pipelines

Use search and filters to narrow the inventory by operational and security metadata.

#### High-priority filtering workflows

Use these filters to prioritize remediation:

* **Prioritize active workflows:** Sort **Last Job Execution** by most recent. Focus on pipelines that actively run.
* **Scope by CI/CD provider:** Filter by **CI/CD Provider** or select a dashboard provider. This isolates provider-specific misconfigurations.

## Next steps

[Investigate and manage CI/CD pipeline assets](/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/cicd-pipeline-as-an-asset/investigate-and-manage-ci-cd-pipeline-assets.md)


---

# 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://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/cicd-pipeline-as-an-asset/understand-and-prioritize-ci-cd-pipeline-assets.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.