---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Security scan results

# Security scan results {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Security scan results display scan details from security scans configured on your GitHub Actions, Jenkins, Azure DevOps, GitLab, or Harness pipelines.
You can configure security scans in your GitHub Actions, Jenkins, Azure DevOps, GitLab, and Harness pipelines to retrieve the scan results in DevOps Change Velocity. Security inbound events will be created in ServiceNow from the corresponding pipeline run that are then processed to store the scan results. You can view the scan results for each scan that was part of your build or release pipeline executions.  
Note:  
If you want to configure Veracode for the GitLab tool, you can either use the generic Docker container image to add the Veracode security step or perform the steps specified in the [Integrate security tools with GitLab](https://www.servicenow.com/docs/_Ei_m2ZDQ12JaIrx4Nm5eQ "Configure security tool for GitLab which is not supported in the base system.") topic.

The retrieved scan summaries are stored in the following tables:
{#security-tool-framework__table_zjl_jll_cyb__entry__2}

| Column name | Description |
|-|-|
| Source | Source application vulnerability scanner for this application record. |
| Detected Flaw Count | Total number of new detected flaws in the scan. |
| Last scan date | Date of the most recent scan. |
| Last scan rating | Rating assigned by the scanner based on the detected items of the most recent scans. |
| Last static scan date | Date of the most recent static scan. |
| Last static scan rating | Rating assigned by the scanner based on the detected items of the most recent static scan. |
| Last dynamic scan date | Date of the most recent dynamic scan. |
| Last dynamic scan rating | Rating assigned by the scanner based on the detected items of the most recent dynamic scan. |
| Last interactive scan date | Date of the most recent interactive scan. |
| Last interactive scan rating | Rating assigned by the scanner based on the detected items of the most recent interactive scan. |
[Table 1. Application Vulnerability Scan Summary (sn_vul_app_vul_scan_summary)]

{#security-tool-framework__table_zjl_jll_cyb} {#security-tool-framework__table_rtm_mml_cyb__entry__2}

| Column name | Description |
|-|-|
| Category name | Name of the vulnerability category. |
| Severity | Severity of the flaws in the scan report. |
| Count | Number of flaws in the category for a severity. |
[Table 2. Application Vulnerability Scan Summary Details (sn_vul_app_vul_scan_summary_details)]

{#security-tool-framework__table_rtm_mml_cyb}