Checkmarx integration with DevOps Change Velocity

  • Release version: Yokohama
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Checkmarx integration with DevOps Change Velocity

    This integration enables ServiceNow customers to connect their Checkmarx security scanning tools with DevOps Change Velocity, allowing them to retrieve security scan results directly from their CI/CD pipelines. It supports Checkmarx scans configured on platforms such as GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness, helping teams assess the vulnerability of their code efficiently.

    Show full answer Show less

    Two Checkmarx tools are supported:

    • Checkmarx One (retrieves only Static Application Security Testing (SAST) scans)
    • Checkmarx SAST

    Note that Software Composition Analysis (SCA) scans are not available through this integration.

    Key Features

    • Supports integration with multiple pipeline orchestration tools: GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness.
    • Allows configuring Checkmarx scans at any pipeline stage, with scan details automatically retrieved into DevOps Change Velocity.
    • Custom action code requirements depend on the orchestration tool and Checkmarx product used:
      • Azure DevOps and GitHub Actions require adding custom action code in the pipeline.
      • Jenkins pipelines with existing Checkmarx One scan steps do not require adding custom action code; however, for Checkmarx SAST, adding custom action code is still necessary.
      • GitLab integration can be done via a generic Docker container image or specific configuration steps.
      • For Harness pipelines, Checkmarx scans are configured using a generic Docker container image only.
    • Security scan results are accessible in multiple places within ServiceNow: linked to Change Requests, visible in Task Execution of pipelines, or within the Pipeline UI.
    • Scan results can be utilized to define change policies and conditions for change automation, enhancing governance and security workflows.
    • User roles and permissions must be configured appropriately in Checkmarx:
      • Checkmarx SAST users need roles with permissions to read Project and Scan Results.
      • Checkmarx One users require create-scan and manage-project roles for scan summary access.

    Getting Started

    • Install the required ServiceNow plugins before integration:
      • DevOps Vulnerability Integrations (sndevopsvulints)
      • Checkmarx One Vulnerability Integration (xchec3chexone) or Checkmarx CxSAST Vulnerability Integration (xchec3cxsast)
    • Note that installing the DevOps Vulnerability Integrations plugin automatically adds the snvul.appsecmanager role to the DevOps Tool Owner role.
    • Choose from multiple onboarding methods to connect your Checkmarx instance:
      • Workspace: Use the DevOps Change Workspace playbook for a guided onboarding experience.
      • Service Catalog: Connect via the ServiceNow Service Catalog.
      • Classic: Use the Classic experience for manual connection and retrieval of scan results.

    Connect to your Checkmarx instance that is integrated with your CI/CD pipelines to retrieve security scan results. This helps you determine how vulnerable your code is.

    Checkmarx integration overview

    Checkmarx scans that are configured on GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness pipelines are supported in DevOps Change Velocity.

    Two Checkmarx tools can be integrated with DevOps Change Velocity, which are Checkmarx One and Checkmarx SAST. For more information, see Checkmarx One and Checkmarx SAST documentation.

    Ensure that your Checkmarx SAST user has a role that has permissions to read Project and Scan Results to get summary details. For more information, see Checkmarx documentation. Ensure that your Checkmarx One user has the create-scan and manage-project roles to access Scan summary details. For more information, see Checkmarx documentation.

    Note:
    If you are integrating with Checkmarx One, you can retrieve only Static Application Security Testing (SAST) scans but not Software Composition Analysis (SCA) scans.

    You can configure Checkmarx scans on any stage of the pipeline and the scan details are retrieved from the corresponding stage to DevOps Change Velocity. If you’re using Azure DevOps or GitHub Actions orchestration tools, then you must add the custom action code in your pipeline always. If you’re using Jenkins, and your pipeline already has a Checkmarx One security scan (checkmarxASTScanner) step, you don’t have to add the custom action code in your pipeline. For Checkmarx SAST, the custom action code must be added in your pipeline even if it has the security scan step (checkmarxASTScanner).

    If you want to configure Checkmarx for the GitLab tool, you can either use the generic Docker container image to add the Checkmarx security step or perform the steps specified in the Integrate security tools with GitLab topic.

    For Harness pipelines, you can configure Checkmarx scans only through the generic Docker Container Image. For more information, see Implement custom actions for pipelines using a generic Docker container image.

    You can view the security scan results either in the related list of a Change Request, or the Task Execution of the pipeline, or in the Pipeline UI in your ServiceNow instance. You can also use security results in defining change policies and conditions for change automation.

    Get started

    You must install the DevOps Vulnerability Integrations (sn_devops_vul_ints) and Checkmarx One Vulnerability Integration (x_chec3_chexone) or Checkmarx CxSAST Vulnerability Integration (x_chec3_cxsast) plugins before connecting your Checkmarx instance to ServiceNow. For more information on activating a plugin, see Install a ServiceNow Store application.

    Note:
    The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.

    For more information on the scan results captured in ServiceNow, see Security scan results.

    Use one of the following options to onboard Checkmarx. For a guided experience, use the workspace to onboard a tool. Alternatively, you can use the Service Catalog or Classic experience.