Azure DevOps Cloud
Overview
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 Checkmarx One.
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.
Notice
This integration supports both public and private git based repos.
Checkmarx One does not support integration with Team Foundation Version Control (TFVC) based repos using the UI.
Team Foundation Version Control (TFVC) based repos are only supported by using Checkmarx One Azure DevOps Plugin
The integration is done on a per project basis, with a specific Checkmarx One Project corresponding to a specific Azure DevOps repo.
Notice
You can select several repos to create multiple integrations in a bulk action.
Prerequisites
The source code for your project is hosted on a Azure DevOps repo.
You have a Checkmarx One account and have credentials to log in to your account.
The Azure DevOps user has admin privileges for this repo, see Azure DevOps.
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:
Setting up the Integration and Initiating a Scan
To integrate your Azure DevOps organization with Checkmarx One, perform the following:
In the Applications and Projects home page, click on the
button and then select New Project - Code Repository Integration.
The Import From window opens.
Select Azure
Sign in to Azure DevOps account
Approve the Checkmarx One request to access the Azure DevOps account by clicking Accept
Select the Azure DevOps Organization or Group (for the requested repository) and click Select Organization
Click Back to return to the Select Service screen.
Select the Repository inside the Azure DevOps organization and click Next
Click Back to return to the Select Organization screen.
Note
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.
In the Repositories Settings screen, perform the following and click Next.
Click Back to return to the Select Repositories screen.
Select the scanners for All/Specific repositories
Select which Protected Branches to scan for each Repository.
Note
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.
Select which Protected Branches to scan for each Repository and click Next
Click Back to return to the Repositories Settings screen.
Note
For additional information about Protected Branches see About Protected Branches
In the Advanced Options screen it is possible to select Scanning the default branch upon the creation of the Project
Click Create Project
Click Back to return to the Select Branches screen.
The Project is successfully added to the Applications and Projects home page.
Note
In order to update the scanners see Imported Project Settings