Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Data transformation for the Veracode Vulnerability Integration

After you identify the data that you want to import, the data is retrieved from the Veracode application, processed through a set of data sources, and transformed in your instance.

Veracode Application Vulnerable Item Integration

The data from the API is first loaded into the Veracode AppVul Item Import [sn_vul_veracode_appvul_item_import] table, and the Veracode AppVul Item Transform is used to transform the imported information.

To access this transform map, navigate to System Import Sets > Transform Maps and search for Veracode AppVul Item Transform. The following table lists the transform map fields by integration.

Source fieldTarget fieldDescription
app_idsource_app_idApplication ID.
issueidsource_avit_idAVIT ID.
app_nameapp_nameApplication name.
versionapp_versionApplication version.
build_idsource_scan_idBuild ID of the application.
account_idaccount_idAccount ID.
sandbox_idsandbox_idSandbox ID.
last_update_timelast_scan_dateLast updated time.
app_name + last_scan_datescan_summary_nameScan summary.
life_cycle_stagesource_sdlc_statusSource SDLC status.
levelsource_severitySource severity.
category_namecategoryCategory.
source_severitysource_severitySource severity.
category_id + " CWE-" + cweIdsource_entry_idSource entry ID.
source_vulnerability_summarysource_vulnerability_summarySource vulnerability summary.
source_recommendationsource_recommendationSource recommendation.
descriptiondescriptionDescription from the source.
descriptionsource_vulnerability_explanationSource vulnerability explanation.
mitigation_status_descsource_mitigation_statusSource mitigation status.
remediation_statussource_remediation_statusSource remediation status.
lineline_numberLine on which the flaw is found.
moduleapplication_moduleApplication module.
sourcefilesource_notesSource notes.
affects_policy_compliancecomplies_with_policyValues can be Yes or No based on the source information being true or false.
Sourcefilepath + sourcefilelocationLocation mapping in case of a static flaw.
urllocationLocation mapping in case of a dynamic flaw.
scope, type, exploitLevelsource_additional_infoName value field populated with the values from source in case of static flaws.

The following transform scripts are run during the transformation process.

Veracode transform map script timing and purpose

When the script is runPurpose
onComplete (when an import set has completed transformation)Script that is used to process the data source and update the count of AVITs created, updated or unchanged, and the ones imported as part of this integration from Veracode. This script is for internal use and should not be modified or deleted.