Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute integration

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 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 Integration

    The Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute allows ServiceNow customers to scan hosts for vulnerabilities and import vulnerability data into their ServiceNow instance. This integration is available starting from version 24.02.0 and utilizes Prisma Host APIs for comprehensive vulnerability information retrieval and synchronization.

    Show full answer Show less

    Key Features

    • Host Vulnerability Scanning: Automatically detect vulnerabilities on running hosts.
    • Regular Synchronization: Maintains updated vulnerability data between Prisma and ServiceNow through the use of a MID Server, especially if the environments are separate.
    • Integration Dashboard: View and manage vulnerabilities through the Vulnerability Response dashboards, allowing for prioritization and remediation.
    • Daily Integration Schedule: Retrieves host vulnerabilities daily and creates Vulnerability Item Tickets (VITs) along with detections and discovered items.

    Key Outcomes

    By implementing this integration, customers can expect enhanced visibility into their host vulnerabilities, timely updates on CVEs from the National Vulnerability Database (NVD), and customizable fields in NVD entries based on information from Prisma. This aids in efficient vulnerability management and remediation efforts within the ServiceNow platform.

    The Prisma Cloud Compute integration enables you to scan hosts to detect vulnerabilities.

    Starting with version 24.02.0 of the Vulnerability Response, you can use the Prisma Cloud Compute Integration to import vulnerabilities on the running hosts. The Prisma Host APIs enable retrieval of comprehensive vulnerability information for a specific host and also provides a snapshot of the host vulnerabilities at a specific time. This API enables regular synchronization between Prisma and ServiceNow instance. As Prisma is offered both as software as a service (SaaS) and on-prem solution, using a MID Server is necessary to invoke Prisma APIs from the ServiceNow instance. In addition, you’re required to use a MID Server if the Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute product and your ServiceNow AI Platform instance aren’t in the same environment. For more information, see MID Server system requirements.

    You can also view reports on vulnerabilities and vulnerable items on the Vulnerability Response dashboards. These vulnerabilities can then be prioritized and remediated.

    Viewing the integrations

    You can view the integrations that are part of the Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute. To view the integrations, navigate to All > Prisma Cloud Compute Integration > Integrations.

    The following integrations are available.

    Run Sequence Schedule Integration Description
    1 Daily Prisma Cloud Compute Hosts Integration

    Retrieves hosts vulnerabilities and creates VITs, detections, and discovered items for hosts.

    Note:
    If Container Vulnerability Response plugin is installed, you can also view Container Vulnerability Response related integrations.

    Prisma integration process

    When the Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute is run, it checks if a Common Vulnerability and Exposure (CVE) exists in the National Vulnerability Database (NVD) table. If it’s already present, the existing information is used. However, if the CVE isn’t found, placeholder records are generated in the NVD table. When creating these placeholder NVD records, initially only the CVE and its name is populated. Other details aren’t populated with the assumption that the NVD integration fills in these details later. If the integration instance parameter update_nvd is set to true, it updates the placeholder NVD records. By default, the instance parameter is set to false. However, at least until the NVD integration runs and populates these details, some understanding of the CVE, such as its severity or some basic information about the issue is needed. To meet this requirement, the fields Exploit exists and Remediation notes are populated with the details obtained from Prisma. Additionally, this configuration is made customizable, enabling you to specify any other fields you want to populate in the NVD entry based on the information provided by Prisma.