Checkmarx

Depending on the SAST tool used, we support different methods of consuming the SAST result for Mobb to generate automated remediations. In this example, we will see how Mobb works with Checkmarx.

With Checkmarx, we support 3 different methods:

• Upload Vulnerability Report

• Scan via Mobb CLI

• Browse Checkmarx Projects

Option 1 - Upload Vulnerability Report

Select "Upload Vulnerability Report"

The 3 methods to consume Checkmarx SAST scan results

Next, you must upload a Checkmarx SAST report in .json or .xml format. Once the report is uploaded, click “Continue”.

If you need help generating a .json report in CxOne, refer to Checkmarx documentation here

The next screen prompts you to connect to your code repository. Mobb currently supports GitHub, GitLab, Azure DevOps and Bitbucket as SCM tools.

You can either use the “Pick a repository from your list” where Mobb will prompt you to connect to your repository, or use the second option - “Add a specific code repository” to supply the URL.

• Pick a repository from your list - This option provides you the ability to look up your connected GitHub, GitLab, Azure Repo or Bitbucket Cloud accounts to pick a repository.

• Add a specific code repository - This option allows you to specify a public or private repository URL.

  • Public repository - Mobb will instantly connect to the repository to extract the content required to generate the fix data

  • Private repository

    • Accessible repository: If your SCM is already connected and the private repository is in these accounts, Mobb will instantly connect to the repository to extract the content required to generate the fix data

    • Inaccessible repository: If your SCM is not connected, Mobb will prompt you to connect your SCM account. Alternatively, you can also upload the source code in a zip file.

If your SCM tool is hosted on-premise, you will either need to deploy a Mobb broker, or use the "upload zip file" feature.

Example 1 - A repo that is directly accessible by Mobb

Example of a repository that is accessible

Example 2 - A repo that is not yet accessible by Mobb (Requires connection to be setup)

Example of a repository that is inaccessible

Example 3 - Connecting the repository by uploading the source code in a zip file

Example of uploading the source code via a zip file

Once you have connected your repository, you are ready to run the analysis. To do so, click on “Continue”.

Confirmation screen before submitting the fix analysis

Note that if you are getting a warning that says "The code provided has been updated after the vulnerabilities were detected. Some vulnerabilities might be missing." You may want to provide a more recent SAST report or adjust your Git branch to an earlier one.

After the analysis, you can review the available fixes on the project page. To access the fix page, click the “Link to fix” button next to the issue you wish to review.

Mobb provides an intuitive UI that allows you to influence the fix's direction through simple questions. Once you are satisfied with the fix recommendation, you can either commit the changes back to your source code repository, download the .diff file, or save fix data:

• Create a Pull Request - This allows you to commit the fix directly to your source code repository by automatically creating a Pull Request.

• Commit directly to target branch - This option will commit the fix directly to a specified branch

• Download the .diff file - This option allows you to download the .diff file and apply the fix manually through your IDE.

Here are the options to either create a pull request or commit directly to a target branch

Here is how to download the fix as a patch (.diff) file

This tutorial will use the “Create Pull Request”. To do so, click on "More Options" to expand the pull request options. Mobb will create a temporary branch for this pull request and auto-populate the pull request title as well as the pull request description.

Once you are satisfied, click “Propose changes”. This will initiate a Pull Request in your SCM.

Create a pull request screen

Option 2 - Scan via Mobb CLI

This option provides you with a CLI command that you can run on your workstation to perform both a SAST scan followed by the Mobb analysis.

Please note that this option will require you to have access to your own Checkmarx (CxOne) account and is not supported with the on-prem CxSAST version

To use this option, select “Scan via Mobb CLI”.

Scan via Mobb CLI

Next, we will need to pick a repository. Same as the previous option, you can either use the “Pick a repository from your list” to establish a connection to your SCM account or alternatively, you can use the second option - “Add a specific code repository” to supply the URL to your repository.

Once we have specified the source code repository, we will be presented with the command to run in our own desktop environment.

Please note that for this step, you must have the latest nodeJS version installed. To install Node.js, visit the URL:

https://nodejs.org/en/download

Pick the latest version of Node.js supported for your platform and install it.

Note that if you are running this command in a Windows command prompt, make sure you edit the multi-line character from \ to^.

Example for windows command prompt:

npx mobbdev@latest scan ^
--mobb-project-name "antonychiu/mobb-cx-integration" ^
--repo https://gitlab.com/antonychiu/mobb-cx-integration ^
--scanner checkmarx ^
--ref main ^
--cx-project-name antonychiu/mobb-cx-integration

During the command prompt, Mobb CLI will ask for a few Checkmarx-related inputs that you will need to provide to complete the SAST scan.

Once the analysis is complete, press any key to open the link to the analysis. If the page to the Mobb analysis doesn’t open, you can copy the URL and paste it into your browser.

Running the Mobb CLI in a terminal with CX scan

Like before, you will see the analysis page and the available fixes. From there, you can review the fixes and commit them back to your source code repository.

Option 3 - Browse Checkmarx Projects

This option allows you to connect to your own Checkmarx (CxOne) account directly and access the scan results from the Checkmarx Projects.

Please note that this option will require you to have access to your own Checkmarx (CxOne) account and is not available for CxSAST (on-prem)

To use this option, select the “Browse Checkmarx projects” option.

In the next screen, you will be required to provide your tenant information as well as the Checkmarx API key. Once ready, click on “Continue”.

On the next screen, you can browse through your Checkmarx projects to select which ones you wish to perform analysis against SAST findings. Once you have selected the projects, click on “Continue”.

This will take you to the analysis page of the first Checkmarx project you selected, along with the available fixes. From there, you can review the fixes and commit them back to your source code repository, or use the side menu to move to other projects.