Skip to main content
Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor’s documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.
Veracode is an automated security platform that identifies and remediates vulnerabilities in software applications. DAST, SAST, and SCA are supported. Integrating Veracode with Cortex allows you to:

​
How to configure Veracode with Cortex

​
Prerequisite

Before getting started:
  • Create an API ID in Veracode.
    • If using XML, configure the ID with the following permissions:
      • get Detailed report
      • get Build list
      • get sandbox list
      • get application list
    • If using REST, configure the ID with the following permissions:
      • get application
      • get findings
  • Create a secret key in Veracode with the following roles:
    • Creator or Security Lead
    • Reviewer or Security Lead
    • Results API
If you’re using a self-hosted instance of Veracode, you’ll need to verify that your Cortex instance is able to reach the Veracode instance. We route our requests through a static IP address. Reach out to support at help@cortex.io to receive details about our static IP. If you’re unable to directly allowlist our static IP, you can route requests through a secondary proxy in your network that has this IP allowlisted and have that proxy route traffic to your Veracode instance.

​
Configure the integration in Cortex

  1. In Cortex, navigate to the Veracode settings page:
    1. Click Integrations from the main nav. Search for and select Veracode.
  2. Click Add configuration.
  3. Configure the Veracode integration form:
    • Key ID: Enter your Veracode API ID.
    • Secret key: Enter the secret key associated with your API ID.
    • Region: Enter your Veracode instance region.
  4. Click Save.

​
Advanced configuration

If you’re unable to expose your Veracode instance to be reachable by Cortex, you can set up a custom integration webhook.

​
How to connect Cortex entities to Veracode

​
Editing the entity descriptor

The YAML examples on this page show only the x-cortex-* block. When you add one to an entity descriptor, nest it inside the info section. Blocks at the root level of the file are ignored without an error. For a full example, see Defining entities with YAML.
You can set up the Veracode integration for an entity by specifying its Veracode application names or sandboxes in the x-cortex-static-analysis section of the entity descriptor. For example:
The application and sandbox names must appear exactly as they are in Veracode.

​
Using the Veracode integration

​
View Veracode data on entity pages

On an entity details page overview, Veracode findings will appear the Code and Security block. When viewing an entity, click Code & security > Veracode to see the DAST findings count, SAST findings count, SCA findings count, and a list of findings that can be filtered by severity and source. The data syncs automatically every hour, or you can click Sync findings in the upper right side of the entity’s Veracode page to trigger a sync.

​
Scorecards and CQL

With the Veracode integration, you can create Scorecard rules and write CQL queries based on Veracode findings. See more examples in the CQL Explorer in Cortex.
Check if entity has Veracode application or sandbox specified in its entity descriptor.Definition: veracode (==/!= null): BooleanExampleIn a Scorecard, you can write a rule to verify that an entity has a Veracode application or sandbox specified:
List of findings, filterable on risk, source, and status.Definition: veracode.findings(): ListExampleIn a Scorecard, you can write a rule to verify that an entity has fewer than 10 Veracode findings from two of the sources:
You can write a rule to verify that an entity has fewer than 3 findings with a risk level of 0 or 2:
You can write a rule to verify that an entity has fewer than 5 findings with a status of “OPEN”:

​
View integration logs

This feature is available in Cortex cloud.
While viewing an integration’s settings page, select the Error logs tab to view errors from the last 7 days. You can filter the logs list by configuration and by operation (for example, you could filter to view errors surfaced only via Scorecards).
The 'Logs' tab on an integration's settings page shows error information over the past 7 days.
Click into a row to get more information, including time stamp, status code, full error, and request path.

​
Background sync

Cortex conducts an entity sync for Veracode every hour.

​
Still need help?

The following options are available to get assistance from the Cortex Customer Engineering team:
  • Email: help@cortex.io, or open a support ticket in the in app Resource Center
  • Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a :ticket: reaction to a question in Slack, and the team will respond directly.
Don’t have a Slack channel? Talk with your Customer Success Manager.
Last modified on October 21, 2026