Veracode integration with DevOps Change Velocity

  • Release version: Xanadu
  • 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

    ServiceNow’s DevOps Change Velocity integrates with Veracode to retrieve security scan results from your CI/CD pipelines, enabling you to assess code vulnerabilities effectively. This integration supports Veracode scans configured in popular orchestration tools such as GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness pipelines.

    Show full answer Show less

    Integrating Veracode Scans

    • Veracode scans can be set up at any pipeline stage, with scan details retrieved automatically into DevOps Change Velocity.
    • For Azure DevOps and GitHub Actions, you must add custom action code in your pipeline to enable scan retrieval.
    • If using Jenkins, ensure the Veracode scan step includes waitForScan: true to allow result fetching; no additional custom action code is required.
    • GitLab users can either add Veracode scans using a generic Docker container image or follow specified integration steps.
    • Harness pipeline integration is supported only through the generic Docker container image method.

    Viewing and Using Security Scan Results

    Scan results are accessible within your ServiceNow instance in multiple locations:

    • Related list of a Change Request
    • Task Execution details of the pipeline
    • Pipeline UI

    You can also leverage these security results to define change policies and automate change management processes.

    Getting Started with Integration

    • Install the required plugins: DevOps Vulnerability Integrations (sndevopsvulints) and Vulnerability Response Integration with Veracode (snvulveracode).
    • Relevant roles are automatically assigned to the DevOps Tool Owner role upon plugin installation, enabling configuration and management.
    • There are three onboarding options to connect your Veracode instance with DevOps Change Velocity:
      • Workspace: Use the DevOps Change Workspace playbook for a guided setup.
      • Service Catalog: Connect via the ServiceNow Service Catalog interface.
      • Classic: Use the traditional method to link your Veracode instance and retrieve scan data.

    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 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.