> 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-instance-as-an-asset/understand-and-prioritize-ci-cd-instance-assets.md).

# Understand and prioritize CI/CD instance assets

## How to access CI/CD instance assets

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

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

### CI/CD instance dashboard

The dashboard displays connected CI/CD providers and their discovered instances. Providers include Jenkins, GitHub Actions, GitLab CI, Azure Pipelines, and CircleCI.

Select a provider to filter the inventory table.

### CI/CD instance asset inventory

Select **Menu Settings** to view additional properties.

| Property           | Description                                                                                     |
| ------------------ | ----------------------------------------------------------------------------------------------- |
| **Name**           | The instance name discovered through the CI/CD integration. It is the primary asset identifier. |
| **Provider**       | The CI/CD platform hosting the instance, displayed with a provider icon.                        |
| **URL**            | A direct link to the CI/CD platform console.                                                    |
| **Last Observed**  | When the active integration last detected or synchronized the instance.                         |
| **Pipeline Count** | The number of pipelines hosted by the instance.                                                 |

## Filter and prioritize CI/CD instances

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

#### High-priority filtering workflows

Use these filters to prioritize remediation:

* **Scope by CI/CD provider:** Filter by **Provider** or select a dashboard provider. This isolates provider-specific misconfigurations.
* **Assess blast radius:** Review **Pipeline Count** to identify instances hosting many pipelines. Prioritize these platforms to reduce risk broadly.

## Next steps

[Investigate and manage CI/CD instance assets](/application-security/software-supply-chain-security/visibililty-and-inventory/supply-chain-assets/cicd-instance-as-an-asset/investigate-and-manage-ci-cd-instance-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-instance-as-an-asset/understand-and-prioritize-ci-cd-instance-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.