Visualize Veracode application scan results and findings, map findings to a code repo or project, and monitor changes and CWEs through queries and alerts.
- Installation guide
- Veracode data model
This integration requires a configured API ID and Secret Key from Veracode. This can be acquired
Depending on your Veracode account configuration, you may need to create an API Service account to generate your credentials. See Veracode's documentation for more information.
Configuration in JupiterOne
To install the Veracode integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Veracode. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Veracode account in JupiterOne. Ingested entities will have this value stored in
AccountNametoggle is enabled.
Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration.
Your Veracode API ID and Secret Key.
Click Create once all values are provided to finalize the integration.
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
The following entities are created:
The following relationships are created:
The following mapped relationships are created: