> 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/investigate-and-manage-ci-cd-pipeline-assets.md).

# Investigate and manage CI/CD pipeline assets

The CI/CD pipeline inventory supports quick agentic queries and detailed side-panel investigation.

Select a CI/CD pipeline row to open its side panel. The side panel provides a consolidated workspace for reviewing pipeline security posture and deployment lineage.

### Ask the AppSec agentic assistant

From the CI/CD Pipelines table, right-click a pipeline. Select **Open in Agentic Assistant** → **Application Security** to query pipeline-specific insights.

You can also select **Ask AI** in the side panel.

### Explore the pipeline context and lineage

Use these side-panel tabs to review pipeline context and assess production impact:

* **Overview tab:** Displays pipeline properties and CI/CD configuration risk severity. Use **Deployed to runtime**, **Internet Exposed**, **Public**, and **Deprecated** to prioritize pipelines.
* **Applications tab:** Lists inherited business applications, including criticality ratings and risk scores.
* **Instances tab:** Displays associated CI/CD instances. Select an instance to view its details.
* **Code to Cloud tab:** Visualizes lineage from the pipeline to its repository, container images, VM images, and cloud resources.

{% hint style="info" %}
Code-to-Cloud lineage requires active CI/CD integrations and successful build-log analysis. Without it, only repository and pipeline nodes appear.
{% endhint %}

## Investigate and remediate issues

From the **Overview** tab, select an issue or case associated with the pipeline.

Selecting an issue opens an issue side card over the inventory. Review evidence and remediation guidance without leaving the asset inventory.

{% hint style="info" %}
Manage CI/CD risks at scale in **Application Security** → **Issues** → **CI/CD Risks**. Use bulk updates, assignments, and SLA tracking.
{% endhint %}

### Execute asset actions

Select **View asset data** from the side-panel **Actions** menu or the row context menu. Review raw pipeline data in `JSON` or tree view.

## Manage CI/CD pipeline assets

### Asset actions

* Right-click an inventory asset. From **Actions**, select an action:
  * **Open in new tab**: Opens the asset description tab for detailed analysis.
  * **View asset data**: Opens data from the latest scan in JSON or tree view.
  * **Copy text to clipboard**: Copies selected text.
  * **Copy entire row**: Copies the selected row data.
  * **Show/hide rows**: Filters the inventory using the selected attribute.
  * **Open in Cortex Assistant/Open in Cortex Agentic Assistant**: Opens the asset in the assistant.
* **Export asset data**: Select the download icon, labelled **Export to file**.
* **View Dashboard**: Opens the [Application Security dashboard](/application-security/application-security/cortex-cloud-application-security-dashboard.md).

## Limitations

| Limitation                           | Description                                                                                                                                             |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **CI/CD integration required**       | Pipelines require active CI/CD integrations. Repositories without integrations do not create pipeline assets.                                           |
| **Provider support scope**           | Discovery supports GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, Bitbucket Pipelines, CircleCI, Argo CD, AWS CodeBuild, TeamCity, and Travis CI. |
| **Code-to-Cloud mapping dependency** | Full runtime lineage requires successful build-log analysis.                                                                                            |
| **Build activity freshness**         | Build activity updates during periodic scans and integration synchronization.                                                                           |
| **Build-log secret scanning scope**  | Build-log scanning detects printed secrets. Some providers do not support log ingestion.                                                                |
| **Policy restrictions**              | CI/CD Configuration Scan policies support only the Periodic Scan trigger.                                                                               |


---

# 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/investigate-and-manage-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.