> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrations-overview.md).

# Integrations Overview

Organizations rely on a diverse ecosystem of tools. OpsMx integrates with existing scanners, CI/CD systems, cloud platforms, ticketing systems, and developer tools to work seamlessly within current workflows.

These integrations allow Delivery Shield to **collect, correlate, and act on** security data from across your entire toolchain — without replacing the tools you already use. OpsMx integrates with code, CI/CD, cloud, security, observability, and collaboration systems — bringing execution and decision context together in one place.

## How Integrations Work

When you connect a tool to Delivery Shield:

1. Delivery Shield **authenticates** with the tool using an API token or credential
2. It **listens** for pipeline events or performs periodic scans
3. Scan results and metadata are **pulled into** the Delivery Shield platform
4. Data is **analyzed** against your security policies and contributes to the application's **overall security score**
5. Findings are surfaced in the **unified dashboard**, DBOM, and vulnerability pages

All integrations are managed from **Setup → Integrations** in the Delivery Shield console.

## Integration Categories

**CI/CD Platforms**

Connect your delivery pipelines so Delivery Shield can trigger and monitor security scans automatically at every pipeline stage.

Delivery Shield is compatible with Argo CD, Jenkins, Flux, Spinnaker, GitHub Actions, and Azure DevOps.

**Source Control**

Connect your repositories for code scanning, secrets detection, and Git security posture evaluation.

**SAST / DAST Tools**

Static and dynamic analysis tools that scan your code and running applications for vulnerabilities.

**Software Composition Analysis (SCA)**

Tools that scan open-source dependencies, libraries, and packages for known vulnerabilities.

**Container Registries**

Delivery Shield connects to container registries to scan images for vulnerabilities before and after deployment.

Expanded support for artifact scanning covers GitLab Container Registry, Docker Hub, Azure Container Registry (ACR), Google Container Registry (GCR), Google Cloud Storage (GCS), Amazon ECR, JFrog Artifactory, and Quay.

**Cloud Security**

Scan cloud environments for misconfigurations, compliance gaps, and security posture issues.

**Kubernetes Platforms**

Delivery Shield auto-discovers applications from GKE, EKS, AKS, self-managed clusters, and OpenShift.

**Secrets Management**

Detect hardcoded credentials, API keys, and tokens in your source code and pipeline.

**Artifact Management**

**Ticketing & Collaboration**

Connect Delivery Shield to your team's workflow tools for automated issue tracking and notifications.

**AI & Intelligence**

#### Adding an Integration

All integrations follow the same setup pattern in Delivery Shield:

1. Navigate to **Setup → Integrations**
2. Select the tool category (Source, Artifact, Security Scanning, Cloud, etc.)
3. Click **+ New Account** and provide the required credentials or API token
4. Select the **Teams** and **Environments** for which the integration should be available. 
5. Click **Save**. 

Delivery Shield will begin collecting data on the next pipeline trigger or scheduled scan. 

{% hint style="info" %}
Each integration account can be assigned to up to 5 teams. Applications belonging to unassigned teams will not have access to that integration account.
{% endhint %}