> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/security-testing-orchestration/use-sto/integrations.md).

# Integrations

The Integrations page provides a centralized view of all connectors configured for source code management (SCM) providers and for security scanners in Harness Security Testing Orchestration (STO). It eliminates the need to navigate through different settings to locate integrations. You can quickly find a repository provider or scanner, check the number of active and inactive configurations, and access the relevant configurations to manage your connections.

## What you will learn from this topic

By the end of this topic, you will be able to:

* Understand the purpose and structure of the Integrations page.
* Identify the available SCM providers and security scanner integrations.
* Understand the active and inactive configuration counts displayed for each integration.

## Before you begin

* Make sure that STO is enabled for your account, organization, and project.
* You must have the necessary permissions to view the connectors and configurations.

***

## Understand Integrations

STO uses connectors to connect to SCM providers and configurations to integrate with supported security scanners. When setting up STO scans through the Get Started page, users can select the appropriate scanner configuration for their security scanning requirements. Integrations provides a centralized view of SCM connectors and scanner configurations, making it easier to track available integrations in STO.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2Fgit-blob-ba49025f1078f14bb912d1b3eb016917f1d7563d%2Fintegrations-overview.png?alt=media" alt="Integrations overview"><figcaption><p>Integrations overview</p></figcaption></figure>

STO groups integrations into Repositories and Scanners. Repositories contain the connectors configured for SCM providers, while Scanners contain the configurations available for security scanners. Each integration displays the number of active and inactive configurations associated with it. You can open an integration to view its existing configurations, create new configurations, or modify existing ones. This helps you manage connections and keep integration settings up to date.

| When do you use it?                                                                         | Why use it?                                                                                                                            | How can you leverage it?                                                                                |
| ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| You need to find a connector for an SCM provider or a configuration for a security scanner. | Integrations for different providers and scanners are managed in one place, eliminating the need to search through different settings. | Browse the **Repositories** or **Scanners** categories to find the required integration.                |
| You need to check the status of existing configurations.                                    | Active and inactive configuration counts provide visibility into the status of configurations associated with each integration.        | Review the counts displayed on integration cards to identify integrations with inactive configurations. |
| You need to create a new configuration or modify an existing one.                           | Managing configurations from the relevant integration helps you maintain the connections used by STO.                                  | Open an integration to view its configurations, create new ones, or modify existing configurations.     |

***

## Key components of the Integrations page

Navigate to **Security Testing Orchestration** → **Code Repositories** to open the page. It has three parts: a navigation filter, repository cards, and the scanner cards.

#### Navigation filter

The navigation filter organizes integrations into two categories: **Repositories** and **Scanners**. Repositories display the available SCM providers. Scanners expand into four categories: **All scanners**, **Third-party scanners**, **Open source scanners**, and **Supply chain scanners**. Selecting a category displays the integrations associated with it.

#### Repository cards

Repository cards represent the SCM providers supported by STO. Each card displays the provider name and the number of active and inactive connector configurations associated with that provider. Select a card to view existing connectors, create new connectors, or modify existing ones.

| SCM provider | Description                                                                                     |
| ------------ | ----------------------------------------------------------------------------------------------- |
| GitHub       | Displays the number of active and inactive connectors configured for GitHub repositories.       |
| Bitbucket    | Displays the number of active and inactive connectors configured for Bitbucket repositories.    |
| Harness Code | Displays the number of active and inactive connectors configured for Harness Code repositories. |

#### Security scanner cards

Security scanner cards represent the security scanners supported by STO. Each card displays the scanner name and the number of active and inactive configurations associated with that scanner. These counts help you track scanner configuration status. Select a card to view existing configurations, create new configurations, or modify existing ones.

| Security Scanners        | Description                                                                                             |
| ------------------------ | ------------------------------------------------------------------------------------------------------- |
| GitHub Advanced Security | Supports SAST, SCA, and Secret Detection scans. Displays active and inactive configuration counts.      |
| SonarQube                | Supports SAST scans. Displays active and inactive configuration counts.                                 |
| Mend                     | Supports SAST and SCA scans. Displays active and inactive configuration counts.                         |
| Veracode                 | Supports SAST and SCA scans. Displays active and inactive configuration counts.                         |
| Black Duck Hub           | Supports SAST scans. Displays active and inactive configuration counts.                                 |
| CheckmarxOne             | Supports IaC, SAST, SCA, and Secret Detection scans. Displays active and inactive configuration counts. |
| Snyk                     | Supports IaC, SAST, and SCA scans. Displays active and inactive configuration counts.                   |
| Wiz                      | Supports IaC, SAST, and SCA scans. Displays active and inactive configuration counts.                   |
| Checkmarx                | Supports SAST and SCA scans. Displays active and inactive configuration counts.                         |
| Sonatype Nexus           | Supports SCA scans. Displays active and inactive configuration counts.                                  |

***

## Next steps

* [Static Application Security Testing - SAST](https://developer.harness.io/security-testing-orchestration/use-sto/set-up-sto-scans/static-application-security-testing): Learn how to set up Static Application Security Testing (SAST) scans to identify potential vulnerabilities in source code or binaries without executing the application.
* [Software Composition Analysis - SCA](https://developer.harness.io/security-testing-orchestration/use-sto/set-up-sto-scans/software-composition-analysis): Learn how to set up Software Composition Analysis (SCA) scans to identify vulnerabilities in open-source dependencies and third-party libraries.
* [Infrastructure as Code scanning - IaC](https://developer.harness.io/security-testing-orchestration/use-sto/set-up-sto-scans/infrastructure-as-code-scanning): Learn how to set up Infrastructure as Code (IaC) scans to detect security misconfigurations, vulnerabilities, and compliance issues in infrastructure configuration files before deployment.
