Checkmarx integration with DevOps Change Velocity

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 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

    The integration of Checkmarx with DevOps Change Velocity enables ServiceNow customers to retrieve security scan results from their Checkmarx instances linked with CI/CD pipelines, allowing for assessment of code vulnerabilities. It supports Checkmarx scans configured on various platforms, including GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness pipelines.

    Show full answer Show less

    Key Features

    • Integration with two Checkmarx tools: Checkmarx One and Checkmarx SAST.
    • Requires specific user roles in Checkmarx for accessing project and scan results.
    • Allows configuration of Checkmarx scans at any stage of the CI/CD pipeline.
    • Results are viewable in ServiceNow through Change Requests, Task Execution, or Pipeline UI.
    • Use of scan results for defining change policies and automation conditions.

    Key Outcomes

    To successfully onboard Checkmarx, customers need to install the relevant DevOps Vulnerability Integration plugins. They can connect to Checkmarx through the DevOps Change Workspace, Service Catalog, or Classic experience. This integration aids in improving code security and streamlining change management processes in ServiceNow.

    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 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 Opt in to the ServiceNow Store products.

    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.