Veracode enables organizations to identify security issues in application code, assess the overall security of applications, and learn about security testing. For more information, refer to Veracode’s official documentation.

Integration Method: API

Tables: Vulnerability Finding (2002)

This integration supports the following events.

This integration supports the following versions.

Note:

Veracode is a continuously updated cloud service. As for this document preparation, the latest release was on Feb 19, 2025.

Prerequisites

• Access to the Veracode Platform.

• Access to the DataBee console.

Configuration Overview

1. Generate API credentials in the Veracode Platform.

2. Add the Veracode data feed in the DataBee console with the below parameters.

   DataBee Parameter	Veracode Parameter
   Integration Key	ID
   Secret Key	Secret Key

Veracode Configuration

Create API Credentials

1. Log in to the Veracode console.

2. Click on API Credentials button.
    

3. Click on Generate API Credentials.
    

4. Copy generated ID and Secret Key.
    

   Note:

   Make sure to copy and save the secrets. Additionally, users need to re-generate the credentials once they expire.

DataBee Configuration

1. Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.
    

2. Search for the Veracode and click it as shown below.
    

3. Click on the API Ingest option for collection method.
    

4. Enter feed contact information and click Next.
    

5. In the configuration page, confirm the following:

   • Authorization Method: HMAC Auth

   • API URL: this is the base URL that DataBee will interact with.

   • Integration key: paste ID generated earlier.

   • Secret Key: paste Secret Key generated earlier.

   • Event Types: preselected for all the event types that integration pulls.

   

6. Click Submit.

Troubleshooting Tips

• If you are facing an unauthorized (401) or forbidden (403) error, it might be due to incorrect credentials. Ensure that the ID and Secret Key are pasted correctly. Also, verify that the API credentials have not expired. If needed, generate new credentials. For more details, refer to the official documentation.