Data transformation for the Vulnerability Response Integration with Black Duck
reference brazil Updated Sep 10, 2026 2 min read blackduck-data-transformref.md
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 field | Target field | Description |
|---|---|---|
| app_id | source_app_id | Application ID. |
| issueid | source_avit_id | AVIT ID. |
| app_name | app_name | Application name. |
| version | app_version | Application version. |
| build_id | source_scan_id | Build ID of the application. |
| account_id | account_id | Account ID. |
| sandbox_id | sandbox_id | Sandbox ID. |
| last_update_time | last_scan_date | Last updated time. |
| app_name + last_scan_date | scan_summary_name | Scan summary. |
| life_cycle_stage | source_sdlc_status | Source SDLC status. |
| level | source_severity | Source severity. |
| category_name | category | Category. |
| source_severity | source_severity | Source severity. |
| category_id + " CWE-" + cweId | source_entry_id | Source entry ID. |
| source_vulnerability_summary | source_vulnerability_summary | Source vulnerability summary. |
| source_recommendation | source_recommendation | Source recommendation. |
| description | description | Description from the source. |
| description | source_vulnerability_explanation | Source vulnerability explanation. |
| mitigation_status_desc | source_mitigation_status | Source mitigation status. |
| remediation_status | source_remediation_status | Source remediation status. |
| line | line_number | Line on which the flaw is found. |
| module | application_module | Application module. |
| sourcefile | source_notes | Source notes. |
| affects_policy_compliance | complies_with_policy | Values can be Yes or No based on the source information being true or false. |
| Sourcefilepath + sourcefile | location | Location mapping a static flaw. |
| url | location | Location mapping for a dynamic flaw. |
| scope, type, exploitLevel | source_additional_info | Name 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 run | Purpose |
|---|---|
| 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 states | Description of source states | Target state in the ServiceNow AI Platform |
|---|---|---|
| New | Vulnerability affects this component version. | Open |
| Needs Review | Can't be determined if a vulnerability affects this component version. | Open |
| Remediation Required | Remediation is required for this version. | Open |
| Remediation Complete | Remediation for this vulnerability is complete. | Closed |
| Mitigated | Vulnerability has been mitigated. | Closed |
| Patched | Vulnerability has been patched. | Closed |
| Ignored | Vulnerability has been ignored. | Closed |
78 lines · 4.9 KB
--- title: Data transformation for the Vulnerability Response Integration with Black Duck description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/security-management/application-vulnerability-response/blackduck-data-transformref.html release: brazil product: Application Vulnerability Response classification: application-vulnerability-response topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Vulnerability Response Integration with Black Duck, Integrate, Application Vulnerability Response, Unified Security Exposure Management, Security Operations] --- # 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 field|Target field|Description| |------------|------------|-----------| |app\_id|source\_app\_id|Application ID.| |issueid|source\_avit\_id|AVIT ID.| |app\_name|app\_name|Application name.| |version|app\_version|Application version.| |build\_id|source\_scan\_id|Build ID of the application.| |account\_id|account\_id|Account ID.| |sandbox\_id|sandbox\_id|Sandbox ID.| |last\_update\_time|last\_scan\_date|Last updated time.| |app\_name + last\_scan\_date|scan\_summary\_name|Scan summary.| |life\_cycle\_stage|source\_sdlc\_status|Source SDLC status.| |level|source\_severity|Source severity.| |category\_name|category|Category.| |source\_severity|source\_severity|Source severity.| |category\_id + " CWE-" + cweId|source\_entry\_id|Source entry ID.| |source\_vulnerability\_summary|source\_vulnerability\_summary|Source vulnerability summary.| |source\_recommendation|source\_recommendation|Source recommendation.| |description|description|Description from the source.| |description|source\_vulnerability\_explanation|Source vulnerability explanation.| |mitigation\_status\_desc|source\_mitigation\_status|Source mitigation status.| |remediation\_status|source\_remediation\_status|Source remediation status.| |line|line\_number|Line on which the flaw is found.| |module|application\_module|Application module.| |sourcefile|source\_notes|Source notes.| |affects\_policy\_compliance|complies\_with\_policy|Values can be Yes or No based on the source information being true or false.| |Sourcefilepath + sourcefile|location|Location mapping a static flaw.| |url|location|Location mapping for a dynamic flaw.| |scope, type, exploitLevel|source\_additional\_info|Name 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 run|Purpose| |----------------------|-------| |**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 states|Description of source states|Target state in the ServiceNow AI Platform| |------------------------|----------------------------|------------------------------------------| |New|Vulnerability affects this component version.|Open| |Needs Review|Can't be determined if a vulnerability affects this component version.|Open| |Remediation Required|Remediation is required for this version.|Open| |Remediation Complete|Remediation for this vulnerability is complete.|Closed| |Mitigated|Vulnerability has been mitigated.|Closed| |Patched|Vulnerability has been patched.|Closed| |Ignored|Vulnerability has been ignored.|Closed|
| title | Data transformation for the Vulnerability Response Integration with Black Duck |
| description | 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. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/security-management/application-vulnerability-response/blackduck-data-transformref.html |
| release | brazil |
| product | Application Vulnerability Response |
| classification | application-vulnerability-response |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | Vulnerability Response Integration with Black DuckIntegrateApplication Vulnerability ResponseUnified Security Exposure ManagementSecurity Operations |