---
sourceDocument: Australia Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Viewing imported data

# Viewing imported data for the Vulnerability Response Integration with Palo Alto Prisma AIRS {#ariaid-title1}

Release version: Australia  
Updated October 2, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Viewing imported data for the Vulnerability Response Integration with Palo Alto Prisma AIRS

This guide explains how ServiceNow customers can view and interact with data imported from the Vulnerability Response Integration with Palo Alto Prisma AIRS within their ServiceNow AI Platform instance.
It describes the relevant data tables, roles required, navigation paths, and troubleshooting tips to ensure smooth integration and data visibility for vulnerability management.
Show full answer Show less  

## Key Features

* **Roles Required:** Access to imported data requires either the `snvulprismaairs.read` or `snvulprismaairs.admin` roles.
* **Data Tables:** Imported data is organized into several tables categorized by type:
  * **AI Security Exposure data:** Includes tables for scan summaries, individual vulnerability findings, discovered AI assets, detailed vulnerability entries, and model file metadata.
  * **Model validation data:** Contains validation findings, specific threat prompts tested against models, and detected attack signatures with mappings to MITRE ATT\&CK and NIST AI standards.
  * **Guardrail data:** Captures guardrail policies applied during Red Team scans including policy details and configurations.
* **Navigation:** View imported data via the Security Exposure Management workspace under AI Security Exposure Management \> AI Vulnerabilities. Users can select scan metrics, validation findings, and posture findings cards to drill down into detailed data.
* **Dashboard Insights:** Access metrics such as open vulnerabilities, models scanned, validation status, mitigated findings, active guardrails, and threat types.

## Troubleshooting

* **Integration Not Running:** Check API credentials, network connectivity, and system logs for errors.
* **No Data Displayed:** Confirm scans/validations exist in Prisma AIRS and contain severity findings, verify transform maps are active, and ensure the integration only fetches scans with issues.
* **Authentication Errors:** Validate Client ID, Client Secret, TSG ID, API URL, AUTH URL, and Prisma AIRS subscription status.

## Best Practices

* Manually run integrations initially to verify data import accuracy before scheduling automated syncs.
* Adjust Scan Limit and Validation Limit parameters to match data volume and avoid system overload.
* Monitor import set processing regularly to catch and resolve errors promptly.
* Schedule automated synchronizations during off-peak hours to minimize performance impact.
* Use ServiceNow reporting capabilities to monitor AI security trends continuously for proactive vulnerability management.  
View and work with imported data from the Vulnerability Response Integration with Palo Alto Prisma AIRS integration on records and dashboards in your ServiceNow AI Platform instance.

## AI Security Exposure data tables {#view-prisma-airs-data__data-tables}

Roles required: sn_vul_prisma_airs.read or sn_vul_prisma_airs.admin.

After the integration runs, data is organized into the following tables by data type.
{#view-prisma-airs-data__data-tables__entry__2}

| Table name | Description |
|-|-|
| AI Scan Summary (sn_sec_ai_scan_summary) | Overview of all vulnerability scans, including scan status, findings by severity (Critical, High, Medium, Low), and total findings count. |
| AI Vulnerability Finding (sn_sec_ai_scan_finding) | Individual vulnerabilities found, including vulnerability ID, description, category, and severity level. |
| Discovered AI Assets (sn_sec_ai_src_ci) | AI models and files discovered during scans. |
| AI Vulnerability Entry (sn_sec_ai_vul_entry) | Detailed vulnerability information. |
| Model File (sn_sec_ai_file) | File metadata including file name, file path, file size, file format, and last scanned timestamp. |
[Table 1. Tables and data description]

{#view-prisma-airs-data__data-tables__entry__14}

| Table name | Description |
|-|-|
| AI Validation Findings (sn_sec_ai_validation_finding) | Validation job results including status, attack counts, and outcomes. |
| AI Validation Threat (sn_sec_ai_validation_threat) | Specific threat prompts tested against the model, including attack prompt, model response, attack result status (FAILED, SUCCESS), and severity level. |
| AI Threat Signature (sn_sec_ai_threat_signature) | Attack patterns detected, including attack category (for example, CYBERBULLYING, HARASSMENT), attack technique (for example, keyboard_augmenter), MITRE ATT\&CK mappings, and NIST AI standards mappings. |
[Table 2. Model validation tables and data]

{#view-prisma-airs-data__data-tables__entry__22}

| Table name | Description |
|-|-|
| Prisma AIRS Red Team Scan Guardrails (sn_vul_prisma_airs_red_team_scan_guardrails) | Guardrail policies applied during Red Team scans, including policy ID, policy name, and policy configuration. |
[Table 3. Guardrail tables and data]

See [Viewing AI Exposures](https://www.servicenow.com/docs/P8GUyl9Gm5LN36RikAsmpg "Access the entire attack surface across various types of findings on the AI Security Exposure Management dashboard with the AI Exposures module. AI Security Exposure Management is a dedicated module of the Security Exposure Management workspace.") for more information about the finding types and the data displayed on the AI Security Exposure Management dashboard.  
1. Navigate to AllSecurity Exposure Management workspaceAI Security Exposure ManagementAI Vulnerabilities. The scan metrics are displayed.
2. Select a scan metrics card to open it.
   * Open Vulnerabilities
   * Models scanned
   * Model files scanned
   {#view-prisma-airs-data__ul_gmx_dfc_nkc}
3. Select the AI validation findings tab.
4. Select a validation metrics card to open it.
   * Open validation findings
   * Mitigated findings
   * Active guardrails
   * Models tested
   * Number of attacks
   {#view-prisma-airs-data__ul_dn3_ysc_nkc}
5. Select the AI posture findings tab.
6. Select a Posture metrics card to open it.
   * Open posture findings
   * Agents with findings
   * Tools with findings
   * System prompts with findings
   * MCP servers with findings
   {#view-prisma-airs-data__ul_j1v_dtc_nkc}
{#view-prisma-airs-data__ol_rr1_mxc_nkc}

## Troubleshooting {#view-prisma-airs-data__troubleshooting}

{#view-prisma-airs-data__troubleshooting__entry__2}

| Issue | Resolution |
|-|-|
| Integration not running | * Verify API credentials are correct. * Check network connectivity to Prisma AIRS. * Review system logs for error messages. |
| No data appearing | * Verify scans or validations exist in Prisma AIRS. * Check that scans have severity findings. The integration only fetches scans with issues. * Verify transform maps are active. |
| Authentication errors | * Confirm Client ID, Client Secret, and TSG ID are valid. * Check that the API URL is correct. * Check that the AUTH URL is correct. * Verify your Prisma AIRS subscription is active. |
[ ]

## Best practices {#view-prisma-airs-data__best-practices}

Start with manual runs
:   Test each integration manually before scheduling to confirm data is importing correctly.

Set appropriate limits
:   Adjust the Scan Limit and Validation Limit parameters based on your data volume to avoid overloading the instance.

Monitor import sets
:   Regularly check import set processing for errors after each run.

Schedule during off-peak hours
:   Run automated syncs when system load is low to minimize performance impact.

Review data regularly
:   Use ServiceNow reporting to track AI security trends over time.

*[\>]: and then