> 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/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/ci-scans/references/reference-f-ci-scan-sources.md).

# Reference F: CI scan sources

Two integration families write results to the CI Scans inventory. Both evaluate policies at the **CI Scan** trigger. Both block through **Block CI/CD**. Their enforcement mechanisms differ.

| Source                                                                                      | How the scan starts                                           | How a block is enforced                                            | Notes                                                                                  |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------ | -------------------------------------------------------------------------------------- |
| **Cortex CLI in a pipeline** — Cortex CLI, CircleCI, GitHub Actions, Jenkins, AWS CodeBuild | A pipeline step invokes the Cortex CLI.                       | The CLI returns exit code `1`. The pipeline fails the step.        | This guide covers this workflow.                                                       |
| **Terraform run tasks** — HCP Terraform, Terraform Enterprise                               | A Terraform run task calls Cortex Cloud during plan or apply. | Cortex Cloud posts a result that governs whether the run proceeds. | Results appear in the same inventory. Configure enforcement in the Terraform run task. |

{% hint style="info" %}
Both sources share one inventory. A repository can produce rows from a pipeline, a Terraform run task, or both. Enable the hidden **Provider** column to distinguish them. Confirm the source before determining pipeline coverage.
{% 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 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/code-security/application-security-scans-management/manage-scans-through-the-tenant-ui/ci-scans/references/reference-f-ci-scan-sources.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.