Server Host Requirements (v9.4.0 and up)

Server host requirements depend on whether the installation is Centralized or Distributed, and on how many lines of code will need to be scanned. These requirements are also applicable for CxAudit.

For POC, Microsoft SQL Express (pre-installed with CxSAST) can be used. For Production, we recommend working with a commercial version of Microsoft SQL Server. The version used will depend on your scalability and performance needs. For more details about features supported by the different editions of SQL Server, please use the following link.

In addition to the requirements in the table below, in general, CPU clock speed and disk speed will affect scan time. For exact tested versions, see the CxSAST Release Notes.

PurposeLines of CodeInstalled RAM**CoresCPU SpeedDiskOSWeb ServerOther Software
Centralized (POC)200K8 GB6-82.8 GHz80 GB (recommended)

See:






IIS 7/7.5/8/8.5/10

Windows Installer 3.1 or above

Run msiexec to check

.NET Framework 4.7.1

.NET Core 3.1.x Runtime & Hosting


For distributed installation, the .NET Core 3.1.x Runtime & Hosting is required where the CxManager is being installed.


Java 1.8 (Oracle or AdoptOpenJdk).

The minimum version for Oracle is 8u241 and for AdoptOpenJdk, it is 8u282.

C++ Redist 2010 and 2015 SP3

MS SQL Driver


(info) For specific details on required prerequisites per product component, see 
Required Prerequisites for Installing CxSAST in a Distributed Environment (v9.4.0 and up).

500K16 GB
Centralized (Production)200K10 GB

Minimum: 8 for 1 concurrent scan.
Additional 2 cores for each additional concurrent scan,
up to a maximum of 12 cores,
(Recommended: 4, 6, or 8 cores )

Max recommended concurrent scans: 3*

* Scans of 1M LOC or more are
recommended to limit concurrency or
run on their own distributed server.

2.8 GHz

250 GB
(recommended)

IIS 7/7.5/8/8.5/10

600K16 GB
1.2M24 GB2.8 GHz
2M40 GB
3M56 GB
4M72 GB

Distributed - CxEngine (Production)

For multiple CxEngine servers
(for concurrent scans),
each server should meet
the requirements.
200K6 GB

4 (for 1 concurrent scan)

Additional 2 cores for each additional concurrent scan (Recommended: 4, 6, or 8 cores)

Recommended socket configuration: Single socket

Recommended: 2.8 GHz

100 GB
(recommended)

NA
600K12 GB
1.2M20 GBRecommended: 2.8 GHz
2M32 GB
3M48 GB
4.5M72 GB
Distributed - CxManager with Management & Orchestration Layer (Production)
14 GB82.5 GHz

250 GB
(recommended)

IIS 7/7.5/8/8.5/10

Distributed - CxManager without Management & Orchestration Layer (Production)

or

Web Portal (apart of CxManager)


10 GB42.5 GHz

250 GB
(recommended)

IIS 7/7.5/8/8.5/10
Distributed - ActiveMQ (Production)
8 GB42.5 GHz250 GB
(recommended)

Distributed - Database (Production)



 12 GB6-82.5 GHz350-400 GB
(recommended)
NA

MS SQL Server
(Express not recommended)
2012/2014/2016/2017/2019

MSSQL 2019 is supported on CxSAST 9.3 and up

** Note: GB RAM / LOC numbers for Javascript are higher.

As of CxSAST 9.3 the engine can be installed on a Linux machine. For more details please refer to: Installing and Configuring the CxEngine Server on Linux (v9.3.0)

The Checkmarx Server requires dedicated memory allocation; features such as Memory Ballooning cannot be used.

Cloud Environments

For Cloud Environment installations (AWS, etc.), these requirements may not exactly match the ones for Centralized or Distributed installations because you are choosing from predefined hardware packages and not defining your own specifications.

Engine Socket configuration

To learn more about socket configuration, use our Engine Socket Configuration guide

DB Latency


Acceptable LatencyComponents
Network<5ms, ideally <1msCxManager(s), SQL Server(s), ActiveMQ
Network<30msCxEngines
Disk I/O<20ms avgCxManager, CxEngine, SQL Server, ActiveMQ


Server Hardening Checklist

CxSAST supports the following hardening policy: CIS Microsoft Windows Server 2016 Benchmark Level 1

The security hardening recommendations for the Checkmarx installation are the following:

Checkmarx Application - 

  • Configure Checkmarx System Admin login from dedicated IP`s only
  • Use SSL for HTTPS based browsing – prohibit using HTTP. For more information, see Enabling and Configuring SSL and TLS.
  • Use SAML based authentication for the system (replacing local users)
  • If applicable – enable 2FA/MFA through the SAML IDP (Checkmarx does not support that as a feature)
  • Install the Checkmarx application in a distributed mode exposing the least Checkmarx components to users as possible

Application Hosting Servers - 

Recommended Resolutions

For the CxSAST application, it is recommended to use a display with any one of the following resolutions; 1280x720, 1280x800, 1366x768, 1920x1080.