Skip to main content

Using the Checkmarx One JetBrains Plugin

Once you have run a Checkmarx One scan on the source code of your JetBrains project, you can import the scan results into your JetBrains IDE. The results are integrated within the IDE in a manner that makes it easy to identify the vulnerable code triage the results and take the required remediation actions.

First you need to import the results from the latest scan of your JetBrains project. Then you can view the results in your JetBrains IDE.


Alternatively, you can run a new can on an existing Checkmarx One project from your IDE and load the results.

Importing your Checkmarx One Scan Results

To import results from a scan:

  1. In your JetBrains project, click on Checkmarx (on the bottom of the screen) to open the Checkmarx panel.


    The Checkmarx panel opens on the bottom of the screen.


    The plugin will try to automatically show results for the relevant scan by matching your project and VCS branch to an existing Checkmarx One scan.

  2. If the desired scan is not displayed, you can select the scan manually by entering the Scan ID of the desired scan in the Scan field.

    Use one of the following methods to submit the relevant Scan ID.

Running Scans from JetBrains

You can run a new Checkmarx One scan on the project that is open in your JetBrains workspace.

You must first create a Checkmarx project and run the initial scan using some other method, e.g., web portal, API, CLI etc. Then, you are able to run subsequent scans on that project from the JetBrains console.


The scan applies the scan configuration that was used for the previous scan of this project. For example, if the last time you scanned this project you excluded certain files, those files will be excluded also from the current scan.


This feature needs to be enabled for your organization's account by a Checkmarx admin user under Settings.pngSettings > Global Settings > Plugins in the Checkmarx One web portal. Before enabling this feature, you should consider the ramifications; since there is a limitation to the number of concurrent scans that you can run based on your license, enabling IDE scans may cause scans triggered by CI/CD pipelines and SCM integrations to be added to the scan queue (run on a "first in first out" basis), causing major delays for those scans.

Figure 1. Running Scans from the IDE
Running Scans from the IDE

GIF - How to run a new scan from the IDE

To run a scan:

  1. In the Checkmarx panel in your IDE, open the existing Checkmarx project under which your current workspace has already been scanned.

  2. Click on the "play" button that appears next to the project name.



    Checkmarx runs a sanity check to verify that your current workspace matches the files that were previously scanned under this Checkmarx project. If a mismatch is detected, a warning is shown. You are given the option to run the scan despite the mismatch.

  3. When the scan is completed, a dialog appears, asking if you would like to load the results from the new scan. Click Yes to show the new scan results in the Checkmarx panel.

Viewing Checkmarx One Scan Results

There are two methods for viewing Checkmarx One scan results in JetBrains:

Viewing Checkmarx One Scan Results in the Checkmarx Panel

You can open the Checkmarx panel below your project and navigate the tree display to view details about a specific vulnerability.


In order to show the source code for a specified attack vector, you need to have the relevant project open in your JetBrains console.

To view the Checkmarx One results in the Checkmarx panel:

  1. After you import the scan results, and the results are shown in the Checkmarx panel, click on an arrow or double-click a node to expand that node in the tree.

  2. You can use the Checkmarx Toolbar (on the left) to adjust the display, see below.

  3. Click on a SAST vulnerability.

    The details panel is shown on the right. It opens showing the Description tab, which includes a summary of the vulnerability info.

  4. You can click on the Changes tab to view all changes that have been made to the result predicate of the vulnerability (severity, status and comments), see Triaging Results.

  5. You can click on the Learn More tab to view additional details about the vulnerability, including recommended remediation actions.

  6. You can click on the Remediation Examples tab to view a sample of code that is subject to this vulnerability, followed by a remediated version of that code.

  7. Click on a node in the Attack Vector tab.

    An editor opens containing the source code in the respective file and location for the selected node.

  8. Hovering over an error or warning in the code shows a tooltip showing info about the vulnerability.


Viewing and Remediating SCA Results

Figure 2. 

GIF - How to automatically remediate SCA vulnerabilities

  1. Click on an SCA vulnerability in the results tree.

    Detailed info about the vulnerability is shown in the results window. This includes a description of the vulnerability, info about the package where it was identified and a detailed breakdown of the metrics contributing to the CVSS score.

  2. Checkmarx offers remediation recommendations. When the Remediation recommendation is highlighted, this indicates that you can automatically upgrade to the recommended version by clicking on the link.


    This feature is currently supported only for direct npm dependencies.

Checkmarx Toolbar

On the sidebar, on the left side of the Checkmarx panel, a toolbar with the following actions is available:






Opens the Checkmarx One JetBrains plugin configuration settings



Clear Project, Branch and Scan selection and refresh the Project selection list


Filter High

Show/hide high severity vulnerabilities


Filter Medium

Show/hide medium severity vulnerabilities


Filter Low

Show/hide low severity vulnerabilities


Filter Info

Show/hide info severity vulnerabilities


Filter by state

Filter results by state (multi-select, by default all are selected)


Group By

Select criteria for grouping the results (e.g., severity and query name)


Expand All

Fully expand the results tree


Collapse All

Fully collapse the results tree

Managing (Triaging) Results

Checkmarx One tracks specific vulnerability instances throughout your SDLC. Each vulnerability instance has a ‘Predicate’ associated with it, which is comprised of the following attributes: ‘state’, ‘severity’ and ‘comments’. After reviewing the results of a scan, you have the ability to triage the results and modify these predicates accordingly. For more info about triaging results in Checkmarx One, see Managing (Triaging) Vulnerabilities.

You can manage the results directly in the JetBrains console.


Only users with the Checkmarx One role update-result (e.g., a risk-manager) are authorized to make changes to the predicate. Only users with the role update-result-not-exploitable (e.g., an admin) are authorized to mark a vulnerability as ‘Not Exploitable’.


Triaging via the IDE is not currently supported for SCA vulnerabilities.

Figure 3. 

GIF - How to triage results in your IDE

To edit the result predicate:

  1. Navigate to the vulnerability that you would like to edit.

  2. To adjust the severity, click on the Severity field, and select from the dropdown list the severity that you would like to assign. Options are: High, Medium, Low or Info.

  3. To adjust the state, click on the State field, and select from the dropdown list the state that you would like to assign. For SAST and IaC Security, options are: To Verify, Not Exploitable, Proposed Not Exploitable, Confirmed or Urgent.


    If you mark a vulnerability as Not Exploitable it will not be shown in the results in the web app for this scan or for subsequent scans of this Project.

  4. To add a comment, enter your comment in the field Comment.

  5. In order to apply your changes, click Update.

    The new predicate is applied to the vulnerability instance in this scan as well as to recurring instances of the vulnerability in subsequent scans of the Project. The changes made to the predicate are shown in the Changes tab.

Viewing Checkmarx One Results Using the Code Analyzer

You can leverage the JetBrains code analyzer to display the results, see You can analyze the whole project or set a custom scope. The results of the Checkmarx One scan are shown together with other problems identified by JetBrains in the Problems tab.

To use the Code Analyzer:

  1. After you retrieve the scan results, and the scan ID is shown in the Checkmarx panel, click Code > Analyze Code > Run Inspection by Name.


    The Enter inspection name window is shown.

  2. In the search field, type Checkmarx to locate Checkmarx AST, and press Enter.


    The Run 'Checkmarx AST' window is shown.

  3. For Inspections Scope, leave the Whole project radio button selected (default) to inspect the entire project or select Custom scope and specify the places that you want to inspect, then click OK.

  4. Click on Problems (at the bottom of the screen) to open the Problems tool window.


    The Problems tool window is shown with any problems that were found, including the Checkmarx One vulnerabilities.