Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute release notes

  • Release version: Store
  • Updated June 11, 2026
  • 5 minutes to read
    • Summarize
    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 Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute release notes

    The Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute application on the ServiceNow Store allows customers to import and manage container and host vulnerabilities detected by Prisma Cloud Compute within ServiceNow. This integration supports comprehensive vulnerability data ingestion, including detailed image and host findings, enabling assignment and remediation workflows that involve security and application development teams.

    Show full answer Show less

    Key Features and Updates

    • Granularity and Data Accuracy Improvements: Enhancements in handling cluster, namespace, and path granularity ensure accurate mapping and reporting of container vulnerabilities. Issues with empty or incorrect data fields affecting container vulnerability item (CVIT) population have been fixed to improve data synchronization.
    • Extended Vulnerability Coverage: Integration now includes scanning for vulnerabilities on running hosts through Prisma Cloud Compute Host APIs and registry scanning of Docker images, broadening the scope beyond container images.
    • Access Control Enhancements: Access Control Lists (ACLs) have been updated to meet internal security directives, controlling query access to Prisma-related repositories and enforcing report view permissions.
    • Data Integrity and Configuration Preservation: Upgrades no longer overwrite customer-configured vulnerability keys or granularity settings. Auto-closure and reopening of CVITs now respect namespace-level granularity to prevent incorrect reopening.
    • User Interface and Monitoring: Introduction of a Prisma Cloud Compute integration run status dashboard in the Next Experience UI aids in monitoring integration health and status.
    • Bug Fixes and Stability Improvements: Multiple fixes address data truncation, localization issues, error message improvements, and integration process failure handling to enhance reliability and user experience.
    • Support for Project Management: The Prisma Projects table has been deprecated and moved to a common security support scope to unify project management across container integrations.
    • New Data Fields: Addition of the Source severity column provides scanner-provided severity levels directly within vulnerability findings.

    Practical Benefits for ServiceNow Customers

    • Seamless ingestion and management of container and host vulnerabilities detected by Palo Alto Networks Prisma Cloud Compute within ServiceNow’s Vulnerability Response.
    • Improved accuracy in vulnerability data correlation through enhanced granularity configurations and cluster-to-namespace mappings.
    • Preservation of customized settings during upgrades ensures consistent integration behavior without loss of customer configurations.
    • Enhanced security and governance through refined access controls for vulnerability data and reports.
    • Expanded visibility and remediation capabilities for both container images and running hosts, supporting comprehensive security operations.
    • Improved user experience with dashboards and error handling for easier monitoring and troubleshooting of integration processes.

    What to Expect

    ServiceNow customers using this integration can expect a robust and secure method to synchronize and remediate vulnerabilities discovered by Prisma Cloud Compute. Upgrades deliver fixes for previously reported issues, better data fidelity, and additional features to cover host-level vulnerabilities and registry scanning. Access controls and UI enhancements provide better governance and usability. Customers should review configuration options related to granularity and ensure compatibility with their internal security policies as reflected in updated ACLs.

    Version history for the Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute application on the ServiceNow Store .

    Important:
    For details on system requirements and family compatibility, view the application listing on the ServiceNow Store website.

    Version history

    Version 30.3.1 - June 2026 (USEM)
    Changed: Updated Access Control Lists (ACLs) for the Palo Alto Networks Prisma Cloud Compute integration for queries on the app-vul-prisma repository to support internal security directives.
    Version 3.7.0 - June 2026
    Changed: Updated Access Control Lists (ACLs) for the Palo Alto Networks Prisma Cloud Compute integration for queries on the app-vul-prisma repository to support internal security directives.
    Version 30.2.2 - April 2026 (USEM)
    • Fixed:
      • The Image Clusters field on Container Vulnerable Items is now correctly populated from the Prisma Cloud Compute integration. The root cause was an empty data_source field in the Configure Image Vulnerability Keys (VI Granularity) record, which prevented the cluster data from being synced.
      • Prisma Cloud Compute integrations no longer log an erroneous "Loading import set table with error" message on import set runs. The Prisma API returns a final empty payload ({"results":null}) to signal completion. This payload no longer returns an error.
      • Upgrading the Prisma Cloud Compute integration no longer overwrites customer-configured VI Granularity (Configure Image Vulnerability Keys) settings. Previously, upgrading from v3.2.x to v3.3.x reset the Cluster and Namespace options to their default settings and discarded any customizations.
      • Container Vulnerable Items (CVITs) that were correctly auto-closed due to a namespace no longer reporting are no longer incorrectly reopened during subsequent integration runs. The post-integration job now considers namespace-level granularity when determining which CVITs to reopen.
    Version 3.6.2 - April 2026
    • Fixed:
      • The Image Clusters field on Container Vulnerable Items is now correctly populated from the Prisma Cloud Compute integration. The root cause was an empty data_source field in the Configure Image Vulnerability Keys (VI Granularity) record, which prevented the cluster data from being synced.
      • Prisma Cloud Compute integrations no longer log an erroneous "Loading import set table with error" message on import set runs. The Prisma API returns a final empty payload ({"results":null}) to signal completion. This payload no longer returns an error.
      • Upgrading the Prisma Cloud Compute integration no longer overwrites customer-configured VI Granularity (Configure Image Vulnerability Keys) settings. Previously, upgrading from v3.2.x to v3.3.x reset the Cluster and Namespace options to their default settings and discarded any customizations.
      • Container Vulnerable Items (CVITs) that were correctly auto-closed due to a namespace no longer reporting are no longer incorrectly reopened during subsequent integration runs. The post-integration job now considers namespace-level granularity when determining which CVITs to reopen.
    Version 3.5.0 - December 2025
    Fixed: Minor fixes for this release.
    Version 3.3.3 - August 2025
    Changed: Deprecated the Prisma Projects [sn_sec_cmn_projects] table in the Prisma Cloud Compute application scope and moved it to the security support common scope to support imported Projects for all container integrations.
    Version 3.2.2 - May 2025
    • Changed: A new column, Source severity, has been added to sn_vul_container_image_findings, which includes the severity level provided by the scanner.
    • Fixed: Prisma container counts integration is made active OOTB.Remediation Owner should not be able to reassign CVITs from list view.
    Version 3.1.4 - March 2025
    Fixed: As issue with validating the mapping between clusters and namespaces, when the granularity option is set to "cluster" and "namespace" in ServiceNow, CVITs are created based on the combination of the lists for namespaces and clusters. We are introducing a solution that uses the "host" field to accurately determine the cluster-to-namespace mappings, ensuring proper functionality for different CVIT granularity combinations.
    Version 3.0.4 - January 2025
    Fixed: Now, the 'First Found' field is populated for the Vulnerable Items and Detections from the Prisma Host scanners.
    Version 3.0.3 - November 2024
    • New:
      • Prisma Cloud Compute Host Integration can now scan vulnerabilities on the running hosts. The Prisma Host APIs enable retrieval of comprehensive vulnerability information for a specific host and enable assignment and remediation workflows.
      • Prisma Cloud Compute Registry Integration integrating with Palo Alto Prisma Registry scanning API will import vulnerabilities with comprehensive vulnerability information on the docker images in registry and enable assignment and remediation workflowsWith the integration of registry scanning, we are introducing an additional metering component.
    Version 2.8.2 - September 2024
    Changed: When you add path as granularity for findings in the integration instance parameter, the system includes path as one of the unique keys while creating the findings.
    Version 2.8.0 - August 2024
    Fixed: If projects are not configured in Prisma console and you select the Use projects flag on the Prisma configuration page, then an error message will be displayed.
    Version 2.7.10 - May 2024
    Fixed: Localization issues have been fixed.
    Version 2.7.4 - February 2024
    • Fixed:
      • ID request parameter is used instead of name in the registry API request.
      • Added null checks in PrismaVulnerabilitiesProcessor script include while processing findings.
    Version 2.7.3 - November 2023
    Minor fixes for this release.
    Version 2.7.2 - August 2023 (Vancouver)
    New:
    • The Prisma Cloud Compute integration run status dashboard is now available in the Next Experience UI.
    • The Vulnerability Response Integration with the Prisma Cloud Compute application adds or updates the exploit and remediation_notes information on the Common Vulnerabilities and Exposures (CVEs) that are created by it.
    Version 2.5.0 - May 2023
    Fixed: Container Vulnerable Items (CVIT)s are created as expected only for base images that are used to fetch registry scan data.
    Version 2.4.0 - February 2023
    • Fixed:
      • Create CVITs for an image without tags. A placeholder record with the name "No tags are defined for this container image" is created in cmdb_ci_container_repository_entry table to avoid downstream errors.
      • Along with the CVITs created from 'vulnerabilities' attribute under 'history' in the response payload, we now process the data with 'layerTime': '0' from 'vulnerabilities' attribute outside 'history'.
    Version 2.3.1 - November 2022
    • Fixed:
      • Resized the Image and Base Image attributes on the Prisma Vulnerabilities Import set table to avoid data truncation.
      • Fixed the Prisma Containers Count integration to use the same configuration as Prisma Vulnerabilities Import integration.
    Version 2.2.1 - August 2022
    • New: The report_view access control lists (ACLs) that govern who can see reports in dashboards and elsewhere are enabled by default in the Tokyo release.
    • Fixed: The handling of integration process failure in Prisma Cloud Compute.
    Version 2.1.0 - May 2022
    New: Added multiple data sources to the Prisma Vulnerabilities Integration and Prisma Base Images integration to enable parallel processing of the imported data.
    Version 2.0.4 - April 2022
    • Fixed:
      • Populate the Docker image labels in to the CMDB key value table.
      • Fixed the configuration page load issue in the Domain Separation enabled environment.
    Version 2.0.2 - March 2022
    Import vulnerabilities detected by Prisma Cloud Compute in deployed container images into ServiceNow platform and enable remediation workflow involving security and application development teams.