Checkmarx One – DAST Connector

The Checkmarx One – DAST (Dynamic Application Security Testing) connector integrates with the Checkmarx One platform to ingest application security findings into Qualys Enterprise TruRisk Management (ETM). By simulating real-world attack scenarios against running web applications, Checkmarx One – DAST identifies vulnerabilities. The Qualys connector allows you to centralize these findings in ETM, enabling risk visualization, prioritization, and remediation efforts through TruRisk Insights.

Category Supported Asset Type Supported Finding Type
API Connector Host Asset Web Application Vulnerabilities

Prerequisites

The Checkmarx One – DAST Connector is available on demand. To activate it for your subscription, please contact your Technical Account Manager (TAM) or Qualys Support.

Authentication Details

Name

Key

Type

Description

Domain Name

domainName

String

Base URL of Checkmarx One environment.
Example: https://deu.ast.checkmarx.net

Tenant Name

tenantName

String

Tenant ID for the user profile.

Client ID

client_id

String

Client ID generated from Checkmarx One
(acts as username).

Client Secret

client_secret

Encrypted

Secret key generated for the client.

Setting Up Client ID and Client Secret

Reference: Creating OAuth Clients – Checkmarx Docs

  1. Log in to your Checkmarx One environment (choose the appropriate server base URL).
    Checkmarx One Server Base URLs:
  2. Navigate to Settings > Identity and Access Management.
  3. Go to OAuth Clients and click Create Client.
  4. Enter a descriptive Client ID and click Create.
  5. Copy the Client ID and generate a Client Secret by clicking Regenerate.
  6. Copy the secret and store it securely.
  7. Adjust optional client settings (Name, Description, Expiry, etc.).
  8. Under Role Mapping, assign the following required roles (Read more about minimum required roles here):
    • CxOne composite role: ast-scanner
    • CxOne role: view-policy-management (not required for IDE plugins)
    • IAM role: default-roles
  9. Save the client configuration.

Configure Checkmarx One Connector

  1. Log in to your Qualys account and go to the Connectors module.
  2. Navigate to the Integration tab, locate the Checkmarx One – DAST connector, and click Manage.

Basic Details

Provide the following details

  1. Connector Name and Description
  2. Type of findings (Web Application Vulnerabilities)
  3. Authentication details (Domain Name, Tenant Name, Client ID, Client Secret)

Data Model

The Checkmarx One – DAST connector provides a default schema (based on Checkmarx APIs) to map findings with Qualys ETM schema.

Transform Maps

The connector includes a default transformation map. You may clone or create new maps to customize transformations.

Profile Configuration

Create a profile with Name, Description, Transform Map, Status (Active/Inactive), and Schedule (Single or Recurring).

Scoring

The Scoring screen allows mapping of non-CVE vendor vulnerability severities to Qualys Detection Score (QDS).

  • Fill out 5 rows mapping vendor severity levels to QDS values (0–100).
  • Default Severity can be set (applied when vendor scores do not match mapping).

How Does the Connection Work?

On schedule (or on-demand), the connector fetches Checkmarx One findings and imports them into ETM. Profiles define what is synchronized and when. The Checkmarx One vulnerability connector performs a full pull on each execution.

In the Connector screen, you can find your newly configured connector listed and marked in the Processed state.

Connector States

A successfully configured connector goes through 4 states.

  1. Registered - The connector is successfully created and registered to fetch data from the vendor.
  2. Scheduled - The connector is scheduled to execute a connection with the vendor.
  3. Processing - A connection is executed and the connector is fetching the asset and findings data.
  4. Processed - The connector has successfully fetched the assets, it may still be under process of fetching the findings. Wait for some more time for the connector to fetch the findings completely.

The Processed state indicates that the Connector is successfully configured but it is under the process of importing all your assets and findings. This process (specifically for findings) may take some time.

This entire process may take up to 2 hours for completion. Once it is done, you can find the imported data in Enterprise TruRisk Management (ETM).

Viewing Assets and Findings in ETM

  1. Navigate to Enterprise TruRisk Management > Inventory.
    • Go to Assets > Web Applications to view imported Checkmarx applications.
  2. Navigate to Risk Management > Findings > Vulnerability.
    • Use filter: finding.vendorProductName:"Checkmarx" to list Checkmarx findings.

Activating Web Applications in WAS

Web applications synced from the Checkmarx One - DAST Connector appear in:

  • ETM

  • CSAM

  • WAS 

By default, these applications are not activated for scanning in WAS.

To activate web applications in WAS:

  1. Navigate to CSAM > Web Applications.

  2. Select the desired web application.

  3. Choose Quick Actions > Activate WAS.

NOTE: Activating web applications will consume WAS licenses. You should activate only the required applications.

Additional Information

Required Permissions

Entity Type

Permissions

Vulnerability Findings

read:vulnerabilities

API Endpoints

Name

Endpoint

Example

Authorization API

https://<domain>.checkmarx.net/auth/realms/
<tenantId>
/protocol/openid-connect/token

Grant Type: client_credentials

Fetch Environment

https://<domain>.checkmarx.net/api/dast
/scans/environments/

Example Domain: deu.ast

Fetch Scans

https://<domain>.checkmarx.net/api/dast
/scans/scans?environmentId=<environmentId>

Example Environment ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Fetch Scan Details

https://<domain>.checkmarx.net/api/dast/mfe-results/results/<scanId>

Example Scan ID: xxxxxxxx-xxxx-xxxx-xxxx-
xxxxxxxxxxxx

Checkmarx One - DAST Data Model Map

Vulnerability Mapping    

Source Field Target Field

url

webAppUrl

domain

webAppName

scanResults_Id

externalFindingId

scanResults_Name

findingName

scanResults_severity

 INFO | LOW | MEDIUM | HIGH | CRITICAL

findingSeverity

 1 | 2 | 3 | 4 | 5

scanResults_status

New | Recurrent | Fixed | Resurfaced | Active 

findingStatus

 NEW | ACTIVE | FIXED | REOPENED | ACTIVE

scanResults_description

findingDescription

scanResults_solution

recommendation

scanResults_cweId

cweId

scanResults_owasp

owaspTop10Name

scanResults_url

sourceFindingURL

scanResults_scanType

detectectionMethod