Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute integration
Summarize
Summary of Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute
The Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute allows you to scan hosts for vulnerabilities and import vulnerability data into your ServiceNow instance. Starting with version 24.02.0, this integration utilizes the Prisma Host APIs for comprehensive vulnerability information and regular synchronization between Prisma and ServiceNow.
Show less
Key Features
- Vulnerability Detection: Scans and retrieves vulnerabilities from running hosts.
- MID Server Requirement: Necessary for invoking Prisma APIs if ServiceNow and Prisma are not in the same environment.
- Integration Viewing: Access integrations via All > Prisma Cloud Compute Integration > Integrations.
- Configuration Options: Adjust the granularity of Vulnerability Item Types (VITs) based on key components such as image repository and tag.
- CVE Check Process: Checks for Common Vulnerability and Exposure (CVE) in the National Vulnerability Database (NVD) and manages placeholder records when necessary.
Key Outcomes
By utilizing this integration, ServiceNow customers can efficiently manage and remediate vulnerabilities within their cloud environments. The ability to view vulnerability reports and prioritize them enhances incident response capabilities. Customizable fields for NVD entries ensure relevant information is populated based on Prisma data, improving overall vulnerability management processes.
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 .
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. |
Configure CVR based VI granularity
To configure the granularity of VITs, navigate to and specify the key combinations. By default, a CVIT is created for a combination of image repository, image tag, and vulnerability. You can add additional components to the key for further granularity. For example, you can create a CVIT for a combination of image repository, image tag, vulnerability, and cluster.
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.