> 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.md).

# CI/CD instance as an asset

Cortex Cloud Application Security discovers CI/CD platform instances through active CI/CD integrations. Each instance is a platform-level asset that hosts and executes CI/CD pipelines.

## Prerequisites

Before viewing and managing CI/CD instance assets, verify the following:

| Prerequisite          | Description                                                                             |
| --------------------- | --------------------------------------------------------------------------------------- |
| **License**           | An active Cortex Cloud license with Application Security entitlements.                  |
| **RBAC role**         | The AppSec Admin or SOC Analyst role, or an equivalent custom role.                     |
| **CI/CD integration** | An active GitHub Actions, GitLab CI, Jenkins, Azure Pipelines, or CircleCI integration. |
| **Completed scan**    | A completed periodic scan with CI/CD configuration results.                             |

## Core capabilities and scope

* **Discovery and visibility**: Identifies platform instances, their providers, versions, URLs, and hosted pipelines.
* **Aggregated posture**: Aggregates CI/CD configuration risks across pipelines into an instance health profile.
* **Scope constraints**: Represents a CI/CD platform instance. It does not represent pipelines, pipeline runs, build logs, or VCS organizations.

## Key achievements

* **Instance discovery and identity**: Registers each integrated platform with a persistent identity record.
* **Platform-level risk assessment**: Surfaces systemic configuration risks using aggregated severity findings.
* **Pipeline visibility**: Displays pipelines hosted by the instance for cross-pipeline assessment.
* **Coverage measurement**: Helps identify platforms that are not actively monitored for configuration risks.

## Relationship model

The CI/CD instance provides organizational context and aggregates platform security posture.

* **Parent - VCS organization**: Provides the associated organization, provider type, and organizational context.
* **Child - CI/CD pipeline**: Pipelines inherit provider context. Their CI/CD configuration risks aggregate into instance health.

## Next steps

* [Understand and prioritize CI/CD instance assets](/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)
* [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.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.