> 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/governance-and-enforcement/cicd-policies/reference-b-scope-asset-types.md). # Reference B: Scope Asset Types Supported asset types and values for CI/CD policy scope. The following asset types and values are supported: | Asset type | Values or input | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Category** | Application, CI/CD Instance, CI/CD Pipeline, VCS Collaborator, VCS Organization. Selecting a category displays its available asset values. The policy applies to every displayed asset unless you add another attribute filter, such as **Business Application Names**. | | **Business Application Names** | Enter names in the text field | | **Application Business Criticality** | Critical, High, Medium, Low | | **Application Business Owner** | Enter names in the text field. | | **CI/CD Instance Name** | Enter instance names in the text field | | **CI/CD Instance ID** | Enter Instance IDs in the text field | | **CI/CD Pipeline Name** | Enter pipeline names in the text field | | **CI/CD Pipeline ID** | Enter pipeline IDs in the text field | | **VCS Collaborator Name** | Enter user names in the text field | | **VCS Collaborator Email** | Enter user emails in the text field | | **VCS Collaborator MFA Enabled** | Select All, Yes, No | | **VCS Collaborator Last Observed** | The type of user | | **VCS Organization Name** | Enter VCS organization names in the text field. | | **Repository Name** | Enter repository names in the text field. | | **Is Public Repository** | Select All, Yes, No | | **Provider** | AWS Code Build, AWS Code Commit, Azure Repos, Bitbucket, Bitbucket Data Center, Circle CI, Cortex CLI, GiHub, GitHub Actions, GitLab, GitLab Self-Managed, HCP Terraform Tasks, HCP Terraform Enterprise Run Tasks, Jenkins | {% hint style="info" %} SBAC scope-based limitations do not apply to **Asset Types**. {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/application-security/software-supply-chain-security/governance-and-enforcement/cicd-policies/reference-b-scope-asset-types.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.