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

Additionally, 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.

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

The integration is performed on a per-project basis, where a dedicated Checkmarx One Project corresponds to a specific Azure DevOps repository. You can select several repositories to create multiple integrations in a bulk action.

Checkmarx One supports integration with only one Azure DevOps self-hosted instance. Following a successful integration, the instance cannot be removed but can be updated, provided there are sufficient Checkmarx One permissions. To remove an existing instance please contact Checkmarx One support team.


This integration supports both public and private git based repos.


  • 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. Click on Workspace Workspace.png > Projects.

  2. Click on New > New Project - Code Repository Integration.


    The Import From window opens.

  3. Select Self-hosted → Azure.

  4. Configure the following fields and click Test Connection.

    • Instance Name - Free text field.

    • 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.

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

  6. 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.

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

    • Permissions:

      • Scan Trigger: Push, Pull request - Enable/disable automatic scans for every push event or pull request.

    • Scanners: Select the scanners for All/Specific repositories. At lease 1 scanner must be selected for each repository.

    • Protected Branches: Select which Protected Branches to scan for each repository.


      For additional information about Protected Branches see About Protected Branches

    • Add SSH key.

    • Assign Groups: Specify the Groups to which you would like to assign the project.

    • Assign Tags: Add Tags to the Project. Tags can be added as a simple strings or as key:value pairs.

    • Set Criticality Level: Manually set the project criticality level.

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


    For additional information about Protected Branches see About Protected Branches

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

    Click Create Project.

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


    In order to update the scanners see Imported Project Settings


Updating an Existing Instance


Only users with ast-admin or update-tenant-params permission can update an existing instance.

Users with the view-tenant-params permission can only view an existing instance but do not have the ability to update it.

Azure DevOps self-hosted instance can be updated from Global Settings.

Global Settings can be opened by one of the options below:

  • Click on Edit an existing instance in the Import wizard.


    Click on Settings > Code Repository.

  • Click on Settings > Global Settings, and then select the Code Repository option.


Update Project Settings

See Imported Project Settings.