> 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/application-security/onboard-data-sources/onboard-cicd-systems.md).

# Onboard CI/CD systems

Onboard CI/CD systems to scan for configuration threats in your organization's instance, pipelines, and individual repositories. By onboarding supported version control systems (such as GitHub and GitLab) , you gain out-of-the-box CI/CD scanning capabilities. However, you must explicitly onboard CircleCI and Jenkins to enable scanning for these systems.

Onboarding CI/CD systems provides the following:

* **Organization instance configuration threats:** This type of scan detects security issues at the level of the overall organization's instance of a version control system (VCS), such as GitHub. For example, it can flag risks such as **Project webhook SSL verification disabled** or **Variable is not scoped to an environment**.
* **Pipeline configuration risks:** This scan identifies security risks within the configuration of your pipelines. Examples of risks it detects include **Excessive GitHub Action permissions, using an unpinned container image in a pipeline**, or **CI instance accesses cloud provider using insecure long-term credentials**
* **Repository configuration issues:** This scan checks problems with the settings and configurations of individual code repositories. Examples include **Forking of a private repository is allowed** and **A change in settings so that a review is no longer required before merging code**

### Supported CI/CD systems

* [CircleCI for CI/CD pipeline scans](/application-security/application-security/onboard-data-sources/onboard-cicd-systems/circleci-for-cicd-pipeline-scans.md)
* [Jenkins for CI/CD pipeline scans](/application-security/application-security/onboard-data-sources/onboard-cicd-systems/jenkins-for-cicd-pipeline-scans.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/application-security/onboard-data-sources/onboard-cicd-systems.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.
