> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/get-started/onboarding-to-ox/source-control.md).

# Connect Your Source Control

OX Security integrates directly with a wide range of source control systems, providing complete visibility into the security posture of your code from the earliest stages of development.

By connecting your source control platforms, whether hosted in the cloud, on-premises, or hybrid, you can continuously scan repositories for vulnerabilities, secrets, misconfigurations, open source risks, and compliance violations.

Why connect your source control system:

* **Shift security left** by identifying issues in code as soon as it's written.
* **Automatically scan** all repositories, including new ones, with minimal manual effort.
* **Map findings to code ownership** by linking vulnerabilities to specific commits, pull requests, and authors.
* **Unify visibility** across your entire codebase, regardless of where it’s hosted or how it’s structured.
* **Maintain coverage** across SaaS-hosted and self-managed environments without duplicating effort.

## Supported systems

OX currently supports integration with the following source control platforms:

* [GitHub](https://docs.ox.security/get-started/onboarding-to-ox/source-control/github.md)
* [GitLab](https://docs.ox.security/get-started/onboarding-to-ox/source-control/gitlab.md)
* [Bitbucket Cloud](https://docs.ox.security/get-started/onboarding-to-ox/source-control/bitbucket.md)
* [Bitbucket Data Center / Server](https://docs.ox.security/get-started/onboarding-to-ox/source-control/bitbucket.md)
* [Azure Repos](https://docs.ox.security/get-started/onboarding-to-ox/source-control/azure.md)
* Azure TFS (Team Foundation Server / Azure DevOps Server)
* AWS CodeCommit
* Gerrit Code Review


---

# 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://docs.ox.security/get-started/onboarding-to-ox/source-control.md?ask=<question>&goal=<user_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.
