Skip to main content

Azure DevOps Self-Hosted


It is possible to add the Checkmarx One external IP addresses to the customer Firewall allowlist - For more information see Checkmarx One External IPs

In addition, if the code repository is not internet accessible, it is possible to configure the code repository IP address instead of its hostname during the initial integration with the code repository - as it is not resolved via DNS.


Checkmarx One supports Azure DevOps integration, enabling automated scanning of your Azure DevOps projects whenever the code is updated. Checkmarx One's Azure DevOps integration listens for Azure DevOps commit events and uses a webhook to trigger Checkmarx scans when a push, or a pull request occurs. Once a scan is completed, the results can be viewed in the Checkmarx One Platform.

In addition, for pull requests, a comment is created in Azure DevOps, which includes a scan summary, list of vulnerabilities and a link to view the scan results in Checkmarx One.


This integration supports both public and private git based repos.

The integration is done on a per project basis, with a specific Checkmarx One Project corresponding to a specific Azure DevOps repo.


You can select several repos to create multiple integrations in a bulk action.


  • The source code for your project is hosted on a Azure DevOps repo.

  • You have an Checkmarx One account and have credentials to log in to your account.

  • The Azure DevOps user has admin privileges for this repo, see Code Repository Integrations

  • Verify that in the Azure DevOps Organization settings under Organization Settings → Policies → “Third-Party application access via OAuth” is enabled - For additional assistance use the following link: Azure DevOps connection and security policies

    For example:


To retrieve your Azure DevOps Username & Token, perform the following steps:

  1. In your Azure DevOps account, click on your user > Security

  2. Click on Personal Access Tokens > + New Token

    A panel will be opened on the right screen side

  3. Configure the following fields:

    • Name - Token name

    • Organization - All accessible organizations

    • Scopes - Custom defined

      • Code - Read, Status

      • Pull Request Thread - Read & write

    • Click Create

  4. Copy the token


Setting up the Integration and Initiating a Scan

To integrate your self hosted (on-prem) Azure DevOps organization with Checkmarx One, perform the following:

  1. In the Applications and Projects home page, click on New > New Project - Code Repository Integration.


    The Import From window opens.

  2. Select the Self-hosted → Azure

  3. Configure the following fields and click Next:

    • Domain Name or IP Address - Your Azure DevOps Self-Managed domain.

      For example: http://<domain> / or http:<IP>

    • Username - Azure DevOps username

    • Token - Azure DevOps token.

      For more information see Retrieving Azure DevOps Username & Token

  4. Select the Azure DevOps Organization or Group (for the requested repository) and click Select Organization

  5. Select the Repository inside the Azure DevOps organization and click Next


    • A separate Checkmarx One Project will be created for each repo that you import.

    • There can’t be more than one Checkmarx One Project per repo. Therefore, once a Project has been created for a repo, that repo is greyed out in the Import dialog.

  6. In the Repositories Settings screen, perform the following and click Next.

    • Select the scanners for All/Specific repositories.

    • Select which Protected Branches to scan for each Repository.


      For additional information about Protected Branches see About Protected Branches

    • It is possible to specify the Groups to which you would like to assign the Project.

    • You can also add Tags to the Project. Tags can be added as a simple strings or as key:value pairs.

  7. Select which Protected Branches to scan for each Repository and click Next


    For additional information about Protected Branches see About Protected Branches

  8. In the Advanced Options screen it is possible to select Scanning the default branch upon the creation of the Project

    Click Create Project

  9. The Project is successfully added to the Applications and Projects home page.


    In order to update the scanners see Imported Project Settings


Update Project Settings

See Imported Project Settings