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

Data transformation for the Vulnerability Response Integration with Black Duck

After you identify the data that you want to import, the data is retrieved from the Vulnerability Response Integration with Black Duck, processed through a set of data sources, and transformed in your instance.

Vulnerability Response Integration with Black Duck

The data from the API is first loaded into the Black Duck AppVul Item Import [sn_vul_blackduck_appvul_item_import] table, and the Black Duck 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 Black Duck 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 a static flaw.
urllocationLocation mapping for a dynamic flaw.
scope, type, exploitLevelsource_additional_infoName value field populated with the values from the source for static flaws.

The following table lists the transform scripts that are run during the transformation process.

Black Duck transform map script timing and purpose

When the script is runPurpose
onStart (when an import set has created transformation).Script that is used to process the record and updates the number of entities created, updated, or unchanged, and the ones that are imported as part of this integration. This script is for internal use and should not be modified or deleted.
onBefore (before an import set has completed transformation)Script that is used to define the behavior for records that are invalid and must be ignored. Also, used to define the global object for record processing. This script is for internal use and shouldn’t be modified or deleted.

Black Duck Integration state mapping

The following table shows the source states from the Black Duck Vulnerability Integration and their target states in your instance.

Black Duck source statesDescription of source statesTarget state in the ServiceNow AI Platform
NewVulnerability affects this component version.Open
Needs ReviewCan't be determined if a vulnerability affects this component version.Open
Remediation RequiredRemediation is required for this version.Open
Remediation CompleteRemediation for this vulnerability is complete.Closed
MitigatedVulnerability has been mitigated.Closed
PatchedVulnerability has been patched.Closed
IgnoredVulnerability has been ignored.Closed