0
30.2.2
Australia, Zurich, Yokohama Patch 6, Yokohama, Xanadu Patch 9, Xanadu
Standalone Application
Note:
This app version is intended for Unified Security Exposure Management (USEM), a significant architectural upgrade to the Vulnerability Response applications.
If you are currently using Vulnerability Response and upgrading to USEM for the first time, you must use the Migration assistant for Unified Security Exposure Management to ensure a safe and successful upgrade. For full details, please refer to the KB2556844 and documentation before proceeding.
If you do not intend to upgrade to USEM, please select a version below 30.x when installing or upgrading.
Import vulnerabilities detected by Prisma Cloud Compute in deployed container images into ServiceNow and enable remediation workflow involving security and application development teams.
Import vulnerabilities detected by Prisma Cloud Compute in deployed container images into ServiceNow and enable remediation workflow involving security and application development teams to prioritize and remediate the most critical vulnerabilities in your container images.
This integration includes the following key feature:
- Data import - The Prisma Cloud Compute Vulnerability Integration executes scheduled jobs that import findings, vulnerable items, and related container images.
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.
- The following Security Operations plugins must be installed and activated:
- com.snc.security_support.vul
- com.snc.secops.orchestration
- The following applications must be installed and activated. These applications are available from the Servicenow Store:
- Vulnerability Response application and its dependent plugins
- Vulnerability Response and Configuration Compliance for Containers
- For more information on Vulnerability Response application compatibility, see Vulnerability Response Compatibility Matrix and Release Schema Changes in the Supporting Links and Docs section on this page.
- Permissions and roles:
- System Admin (admin) for installation, and
- Container Vulnerability Admin (sn_vul_container.vulnerability_admin) or admin for configuration