Skip to main content

Understanding How Checkmarx SCA Scans Run Using Various Methods

Main Checkmarx SCA Processes

The following are the main processes that take place when you run a Checkmarx SCA scan. Some processes are always run in the cloud, while others can be run either on-prem or in the Checkmarx SCA Cloud, depending on which method you use to initiate the scan.

  1. File Analysis – Checkmarx SCA identifies all files in your project that may be part of a 3rd party package, and analyzes them in order to determine which packages are being used. This is done by comparing the hashes and metadata of the relevant files (e.g., .jar files for Java, .js files for JS) in the scanned project with the hashes and metadata of packages that are catalogued in our database.

  2. Dependency Resolution - Checkmarx SCA uses package managers to resolve the dependencies against customer-defined or public repositories and extract the dependency trees.

  3. Evidence Analysis - Checkmarx SCA takes the output of the previous steps and uses it to identify the specific risks that affect the packages in your project. This is done by checking the packages that were identified against our extensive database of vulnerabilities as well as checking for legal and supply chain risks.

Methods for Running Scans

  • Web Portal - When scans are initiated by the Checkmarx SCA web portal, the source code and manifest files are sent to the cloud and all of the processing is done in the cloud. In this case, Checkmarx SCA’s preconfigured package managers are used for resolving the manifest files. This is the simplest method, as it doesn’t require any prior configuration or setup. However, it limits the customer’s ability to customize how the resolving is done and doesn’t enable access to private repositories. It also requires sending the actual source code to the Checkmarx SCA Cloud.

  • Checkmarx SCA Resolver - When scans are initiated using Checkmarx SCA Resolver, the File Analysis and Dependency Resolution are both done on-prem and only the output of the analysis, the “evidence files”, are sent to the cloud for the final process of Evidence Analysis. This method enables maximum flexibility for customizing how the package managers run and it enables access to your private repositories. However, it requires that you have all of the relevant package managers configured on your local environment (see Installing Supported Package Managers for Resolver).


The default behavior for Checkmarx SCA Resolver is that the manifest files are sent to the cloud together with the evidence files. This enables Checkmarx SCA to recommend remediation actions relating to the manifest files. There is an option to use the --no-upload-manifest flag to block uploading of manifest files. This doesn’t interfere with the effectiveness of the scan, but it may limit Checkmarx SCA’s ability to suggest precise mitigation actions.

  • Plugins - When scans are initiated using Checkmarx plugins (CLI, Jenkins, etc.), the default behavior is that the File Analysis is done on-prem and then the “evidence files” as well as the manifest files are sent to the Checkmarx SCA Cloud where the Dependency Resolution and Evidence Analysis are performed.


There is an option to configure the plugins to use the Checkmarx SCA Resolver. This requires installing the Checkmarx SCA Resolver locally. In this case, both File Analysis and Dependency Resolution are done on-prem.

There is also an option to configure the plugins to run all processes in the cloud. This is done by using the -includesource upload flag to send the source code to the cloud.

  • Checkmarx One - When an SCA scan is run via Checkmarx One, the default behavior is that all of the processing is done in the cloud (similar to a Checkmarx SCA web portal scan). This is true whether the scan is initiated by the Checkmarx One Web Platform, the Checkmarx One CLI Tool or Checkmarx One plugins. The Checkmarx One CLI Tool and plugins have an option to run scans using the Checkmarx SCA Resolver, in which case the File Analysis and Dependency Resolution are done on-prem.

What is Sent to the SCA Cloud?

For scans that don’t require sending the actual source code, as described above (i.e., using Resolver), the following data is sent to the cloud:

  • The project name

  • List of all file names and relative paths (except the ones that were excluded from the scan)

  • Various checksums of the files (SHA-1, SHA-1 on content without spaces, etc.)

  • Manifest files (except for scans run via Resolver with the --no-upload-manifest flag)


The complete list of files that are sent to the cloud can be seen in Files Used for Manifest Resolution.

  • Names of dependencies extracted from the manifest files

  • Scan errors and warnings such as “Failed resolving dependencies”. Each warning message may contain a file path as an argument.

  • SAST Exploitable Path Query result (for Exploitable Path scans)