# CI/CD CI/CD connectors connect OX to continuous integration and continuous delivery platforms that automate the building, testing, and deployment of software across your development pipelines. OX imports data from these tools through APIs, enriches it with OX context (application mapping, ownership, workflows, and compliance), and presents it alongside findings from other scanners and tools in a unified view. ## What OX adds * **Context and correlation:** OX maps findings to applications, services, and teams to show impact and ownership. * **Prioritization with severity factors:** OX may reprioritize scanner severities when exploitability and environment context reduce risk (for example, Critical → High). Severity factors explain why the priority changed. * **Evidence at a glance:** When available, OX displays scanner evidence, file locations, and remediation guidance alongside OX analytics to speed triage. ## **Where data appears in OX** * **Active Issues:** Filter by **Source tool** to focus on findings from a specific connector. * **Issue details:** Tabs show scanner evidence, asset data, and OX correlations such as application and repository mapping. * **Assets and applications:** Imported assets appear in asset views, application context, and dashboards. * **Risk prioritization:** Findings are ranked using combined development, pipeline, and runtime signals. ## Supported connectors * Azure Pipelines * CircleCI * Drone CI * GitHub Actions * GitLab CI/CD * Jenkins * TeamCity * Travis CI --- # Agent Instructions: 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: ``` GET https://docs.ox.security/ox-integrations/3rd-party-integrations/ci-cd.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.