Veracode 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 Veracode integration with DevOps Change Velocity

    This integration enables ServiceNow customers to connect their Veracode security scanning tool with DevOps Change Velocity. It retrieves security scan results from Veracode instances integrated into CI/CD pipelines, helping teams assess the vulnerability of their code in real-time during the development lifecycle.

    Show full answer Show less

    Supported CI/CD orchestration platforms include GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness. The integration captures scan results configured at any pipeline stage and makes this data accessible within ServiceNow for enhanced security visibility and automation.

    Key Features

    • CI/CD Pipeline Support: Works with popular tools like GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness pipelines to collect Veracode scan data.
    • Flexible Pipeline Configuration: Veracode scans can be configured on any pipeline stage. Specific integration steps vary by orchestration tool:
      • Azure DevOps and GitHub Actions require adding custom action code in pipelines.
      • Jenkins requires the existing Veracode scan step to include waitForScan: true for scan result retrieval.
      • GitLab integration can use either a generic Docker container image or follow specific integration steps.
      • Harness pipelines support Veracode scans only via the generic Docker container image.
    • Security Results Access: Scan results are accessible in the Change Request related list, pipeline Task Execution, or Pipeline UI within ServiceNow.
    • Automation and Policy Use: Security scan results can be leveraged to define change policies and automate change processes based on vulnerability data.
    • Role and Plugin Requirements: Requires installation of the DevOps Vulnerability Integrations (sndevopsvulints) and Vulnerability Response Integration with Veracode (snvulveracode) plugins. Relevant security roles are automatically assigned to the DevOps Tool Owner role upon plugin installation.

    Getting Started

    To begin using the integration, install the necessary plugins and assign proper roles. Then, onboard your Veracode instance into DevOps Change Velocity using one of the following methods:

    • Workspace Playbook: A guided onboarding experience within the DevOps Change Workspace.
    • Service Catalog: Connect Veracode through the ServiceNow Service Catalog interface.
    • Classic Experience: Traditional method for connecting your Veracode instance to retrieve scan results.

    These options provide flexibility depending on your preferred setup process and user experience.

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

    Veracode integration overview

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

    Ensure that your Veracode credentials have the following API roles.
    • Upload and Scan
    • Results
    For more information, see Veracode documentation.

    You can configure Veracode 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 Veracode security scan step, you don’t have to add the custom action code in your pipeline. Ensure that your Veracode security scan step has waitForScan: true. This is required for the system to retrieve the scan information.

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

    For Harness pipelines, you can configure Veracode 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 Vulnerability Response Integration with Veracode (sn_vul_veracode) plugins before connecting your Veracode 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.
    • The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.

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

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