--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/delta-xanadu-zurich Release : - zurich ft:locale : - en-US ft:publication_title : - zurich Combined Product Files ft:clusterId : - delta3zx bundleId : - delta3zx --- # Combined Container Vulnerability Response release notes for upgrades from Xanadu to Zurich # Combined Container Vulnerability Response release notes for upgrades from Xanadu to Zurich {#ariaid-title1} Release version: Zurich Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 13 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 Combined Container Vulnerability Response Release Notes for Upgrades from Xanadu to Zurich This consolidated release notes document summarizes key updates, new features, changes, and important upgrade information for ServiceNow Container Vulnerability Response customers upgrading from the Xanadu release family through Yokohama to Zurich. It is designed to help you understand what enhancements have been introduced, deprecated, or removed, and details critical upgrade tasks necessary for a smooth transition. Show full answer Show less The Container Vulnerability Response application integrates container security findings, enabling efficient vulnerability management and remediation within ServiceNow's Security Operations. Zurich is the latest release with significant improvements relevant for customers managing container vulnerabilities, remediation workflows, and integrations such as with Wiz scanner data. ## Important Upgrade Information * Before upgrading to Zurich, complete pre- and post-upgrade tasks, especially if using integrations like Vulnerability Response with Wiz. * The Missing Assets table used for Wiz backfill integrations is deprecated; after upgrading to version 1.1, backdate existing Wiz primary integrations by three days and rerun them to maintain data integrity. * For customers not upgrading to Unified Security Exposure Management (USEM), install Container Vulnerability Response versions below v30.x and compatible third-party integrations. * Refer to the Vulnerability Response Compatibility Matrix and Release Schema Changes article for full compatibility details. ## New Features and Enhancements * **Properties Module:** Introduced in Xanadu v2.11.3, enabling direct modification of system property values through a user-friendly interface. * **Auto-Close Rules:** Define advanced conditions to automatically close stale container vulnerability items (CVITs). * **Age Calculation Customization:** Configure how Age and Age Closed parameters are calculated (Created, Opened, or First Found dates). * **Workspace Improvements (v24.0.6):** Open search results in Vulnerability Manager or IT Remediation Workspace instead of Classic UI; role-based access to view container vulnerable items; navigation enhancements; option to hide record counts; automatic dashboard refresh. * **Remediation Property Reevaluation:** Reevaluate remediation assignments, tasks, target dates, exceptions, and risk scores for all or selected CVITs from the Vulnerability Manager Workspace. * **Performance:** Scheduled jobs for rolling up container vulnerabilities now use multithreading for faster processing. * **Prisma Registry Integration:** Import static image findings from Prisma registry scans into Container Vulnerability Response. * **Manual Remediation Task Creation:** Roles with appropriate privileges can manually create remediation tasks in both Vulnerability Manager and IT Remediation Workspaces. * **Granularity Configuration:** Set CVIT granularity using Registry and data source information to view image or Kubernetes data. * **Additional CVIT Data:** Display precise discovery, opening, and resolution timestamps, including time zone awareness. * **Risk Score Change Tracking:** Optionally log changes in risk scores to Work Notes for audit and visibility. * **Zurich-Specific Enhancements:** * Remediation task rule execution mode: Choose between 'Match First' (first matching rule applies) or default 'Match All' mode during ingestion. * Wiz Integration updates: Improved mapping of detection keys, container image repository naming, and import enhancements requiring full import post-upgrade. * Enhanced scanner data support, including namespace and cluster hierarchy in discovered container images. * Dark theme support included with the Coral theme for improved accessibility and readability. ## Changes and Removals * Deletion of container vulnerable items is now restricted to users with the snvul.delete granular role; Admin role no longer has this privilege. * The Close button for remediation tasks has been removed across Classic UI, Vulnerability Manager Workspace, and IT Remediation Workspace. * System property introduced to configure the maximum number of rows displayed in related lists to improve performance and readability. ## Activation and Requirements * Container Vulnerability Response and related third-party integrations are available for installation via the ServiceNow Store. * Ensure to request the appropriate versions compatible with your Zurich upgrade. * There are no additional browser, localization, or accessibility requirements beyond the standard ServiceNow platform capabilities. ## Practical Guidance for ServiceNow Customers * Review and complete upgrade tasks to avoid integration issues, especially if using Wiz or planning to migrate to USEM. * Leverage new workspace enhancements to streamline vulnerability tracking, assignment, and remediation workflows. * Use the Properties module to efficiently manage system configurations related to container vulnerabilities. * Configure auto-close rules and remediation task assignment modes to optimize vulnerability lifecycle management. * After upgrading, run quick start tests to validate your Container Vulnerability Response functionality, especially if you have customizations. * Adopt the new dark theme option in Zurich for improved user experience during Consolidated page of all release notes for Container Vulnerability Response from Xanadu to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Container Vulnerability Response release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu to Zurich. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading Container Vulnerability Response to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-containervulnerabilityresponse-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | Upgrade information : If you are currently using Container Vulnerability Response, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Container Vulnerability Response and for upgrades to supported third-party integration applications. The Missing Assets \[sn_vul_wiz_missing_asset\] table used for storing assets imported by the backfill integrations for the [Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) is deprecated. If you are currently using the Vulnerability Response with Wiz integrations, after updating to version 1.1, you must backdate any of your existing Wiz primary integrations by three days and run them. Please review more information about the Wiz integration at [SecOps articles on the Security Operations Community](https://www.servicenow.com/community/secops-articles/announcement-wiz-integration-with-servicenow-secops/ta-p/3325055). For more information about the released versions of the Container Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Zurich release, see the [Vulnerability Response Compatibility Matrix and Release Schema Changes \[KB0856498\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0856498) article in the Now Support Knowledge Base. | [ ] ## New features Between your current release family and Zurich, new features were introduced for Container Vulnerability Response. {#dfrn3-containervulnerabilityresponse-summary__entry__10} | Release | Release notes | |-|-| | Xanadu | [New Properties module](https://www.servicenow.com/docs/access?context=installed-with-cvr-data&family=xanadu&ft:locale=en-US) : Starting with v2.11.3 of Container Vulnerability Response, a new Properties module has been added to the navigation menu under the Administration section. This module enables direct modification of the values, offering a user-friendly method to manage and update system properties directly from the interface. [Create auto-close rules for Container Vulnerability Response](https://www.servicenow.com/docs/access?context=cvr-create-auto-close-rules&family=xanadu&ft:locale=en-US) : Starting with v2.11.3 of Container Vulnerability Response, define auto-close rules with advanced conditions to automatically close older or stale CVITs based on defined filter criteria on container vulnerabilities. [Customize the calculation of Age and Age closed parameters of a container vulnerable item](https://www.servicenow.com/docs/access?context=container-vul-items-fields&family=xanadu&ft:locale=en-US) : Starting with v2.11.3 of Container Vulnerability Response, the Age and Age Closed durations of a Container Vulnerable Item can be configured to be calculated from the date in the Created, Opened, or First Found fields. Open the search results in the [Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-change-app-scope-search&family=xanadu&ft:locale=en-US) or [IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-change-app-scope-search&family=xanadu&ft:locale=en-US) rather than the Classic UI : Starting with v24.0.6 of Vulnerability Response, automatically open your search results in the Vulnerability Manager Workspace or IT Remediation Workspace rather than the Classic UI, by adjusting the application scope in the unified navigation bar to Vulnerability Manager Workspace or IT Remediation Workspace respectively. These application scopes are available to you based on your assigned role. [Vulnerability Manager Workspace access to the sn_vul_container.read_all role](https://www.servicenow.com/docs/access?context=roles-installed-cvr&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, as a user with the sn_vul_container.read_all role, you can view the container vulnerable items in the Vulnerability Manager Workspace. [IT Remediation Workspace access to the sn_vul_container.read_assigned role](https://www.servicenow.com/docs/access?context=roles-installed-cvr&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, as a user with the sn_vul_container.read_assigned role, you can view the container vulnerable items assigned to you and your assignment groups in the IT Remediation Workspace and remediate them. Navigate to the List page in the [Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-list-page&family=xanadu&ft:locale=en-US) or [IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-list-page&family=xanadu&ft:locale=en-US) by selecting the links from the All menu : Starting with v24.0.6 of Vulnerability Response, when you enable the 'sn_vul_cmn_ws.navigate_to_workspace' system property, selecting predefined filter links in the Container Vulnerability Response module from the 'All' menu will automatically open these links in the List page in the Vulnerability Manager Workspace or IT Remediation Workspace based on your role. Hide the record count on the lists in the [Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-list-page&family=xanadu&ft:locale=en-US) and [IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-list-page&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, you can hide the record count on the lists in the List page of the Vulnerability Manager Workspace and IT Remediation Workspace, by adding the table names to the glide.ui.list.seismic.omit.count system property. [Enable automatic refresh for the Home page dashboard in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-home-page-create-filter&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, when creating and editing filters on the Container Vulnerabilities tab on the Home page of the Vulnerability Manager Workspace, you can configure the widgets to automatically refresh. Otherwise, you can manually refresh the widgets by selecting the Refresh button on the Container Vulnerabilities tab. [Re-evaluating remediation properties for all records in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-reevaluate-remediation-parameters&family=xanadu&ft:locale=en-US) : Starting with v24.0.6 of Vulnerability Response, you can evaluate the remediation properties for all the Container Vulnerable Items from the Container Vulnerable Items list by selecting the All items in the Record selection field of the Re-evaluate remediation properties modal in the Vulnerability Manager Workspace. [Re-evaluate the remediation properties for container vulnerable items in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-reevaluate-remediation-parameters&family=xanadu&ft:locale=en-US) : Select the container vulnerable items conditionally for reevaluating the following remediation properties in Vulnerability Manager Workspace: * Assignments * Remediation tasks * Remediation target date * Exceptions (Vulnerability Response v24.0.6) * Risk score [Enhanced processing performance of scheduled job](https://www.servicenow.com/docs/access?context=scheduled-jobs-installed-cvr&family=xanadu&ft:locale=en-US) : The Rollup container vulnerable item values to vulnerability and group scheduled job is enhanced to create background jobs with multithreading capabilities. This upgrade involves segmenting the job into several smaller child jobs, which are executed either in parallel or concurrently. This modification enables processing of multiple records simultaneously, thus significantly speeding up the overall task. [for Container Vulnerability Response](https://www.servicenow.com/docs/access?context=quick-start-tests&family=xanadu&ft:locale=en-US) : After upgrades and deployments of new applications or integrations, run quick start tests to verify that Container Vulnerability Response works as expected. If you customized Container Vulnerability Response, copy the quick start tests and configure them for your customizations. [Vulnerability Response Prisma Registry Integration](https://www.servicenow.com/docs/access?context=pcc-integration&family=xanadu&ft:locale=en-US) : Now you can ingest the static image findings obtained from the Prisma registry scan into the ServiceNow Container Vulnerability Response. | | Yokohama | [Enhancements to the Vulnerability Manager and IT Remediation workspaces starting with version 2.13](https://www.servicenow.com/docs/access?context=unassigning-cvits&family=yokohama&ft:locale=en-US) : The Unassign workflow is supported for container vulnerable items (CVITs) and remediation tasks (CVULs). * Streamline vulnerability assignments in the workspaces with the Unassign UI action from the more actions menu on a CVIT. * Reassign incorrectly assigned CVITs, clarify ownership for reassessment, and maintain accurate triage records in workspace views. * You have the option to send unassign requests for approval prior to clearing the Assigned to and Assignment group fields on records. [\[Placeholder link text to key cvr-assignment-rules\]](https://www.servicenow.com/docs/access?context=cvr-assignment-rules&family=yokohama&ft:locale=en-US). You can use the following values imported from the Prisma Cloud Compute integration as conditions when you create or update your assignment rules to help you track ownership across your container environments. * Cloud account IDs * Image namespaces * Registry * Hosts * Labels * Status - Vendor status for a resolved (Fixed) vulnerability [Create container remediation tasks manually in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-create-remediation-task&family=yokohama&ft:locale=en-US) : With the sn_vul_container.vulnerability_analyst or sn_vul_container.vulnerability_admin role, you can create container remediation tasks manually by selecting some or all the records in the Container vulnerable items lists in the Vulnerability Manager Workspace. These records are grouped into one or more remediation tasks according to the grouping criteria selected while creating container remediation tasks. [Create container remediation tasks manually in the IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-create-remediation-task&family=yokohama&ft:locale=en-US) : With the role sn_vul_container.remediation_owner, you can create container remediation tasks manually by selecting some or all the records in the Container vulnerable items' lists in the IT Remediation Workspace. These records are grouped into one or more remediation tasks according to the grouping criteria selected while creating container remediation tasks. [Configure container vulnerable items (CVITs) granularity using Registry and data source](https://www.servicenow.com/docs/access?context=pcc-integration&family=yokohama&ft:locale=en-US) : Starting with v2.12.2 of Container Vulnerability Response, you can configure the granularity of container vulnerable items (CVITs) using Registry information and data sources. Depending on the chosen data source, you can view either image or kubernetes information related to a CVIT record. [Additional columns in the container vulnerable items (CVITs) table](https://www.servicenow.com/docs/access?context=container-vul-items-fields&family=yokohama&ft:locale=en-US) : Starting with v2.12.2 of Container Vulnerability Response, you can see the precise date and time when a CVIT was first discovered, last opened, resolved, and last found, ensuring clarity and accounting for different time zones. [View risk score details of a container vulnerable item in the Work Notes section](https://www.servicenow.com/docs/access?context=cvr-calculator-rules&family=yokohama&ft:locale=en-US) : Starting with v2.12.2 of Container Vulnerability Response, the system property sn_sec_cmn.risk_score_changes_add_worknotes is inactive by default. If you enable it, only then you can see all the changes related to the risk score of a container vulnerable item in the Work notes section. Additionally, the work notes are updated only if there's a change in the risk score. | | Zurich | [Remediation task rule execution mode](https://www.servicenow.com/docs/access?context=sem-grouping-multiple-findings-remediation-tasks-processing&family=zurich&ft:locale=en-US) : You can now choose how remediation task rules are evaluated during ingestion. The new Match First execution mode evaluates rules sequentially and applies only the first matching rule, assigning each finding to exactly one remediation task. The default Match All mode continues to evaluate all applicable rules. [Enhancements to the Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) : * The Universally Unique Identifier (UUID) that identifies detections for the Wiz Host Vulnerability integration will be mapped to a detection key. Note: This enhancement is supported for new customers only. For existing customers, the detection key for the Wiz Host Vulnerability integration is created using the combination of vulnerability, asset_id, and proof. * Added the source_id column to the Container Image Finding table (sn_vul_container_image_findings) and mapped the id attribute from the Wiz import to this field on findings records. Note: Perform a full import after upgrading to view the enhancement on container image findings, container image, and container image vulnerabilities records. * The image repository name format for new and existing discovered container images has been updated to align with the discovery format. The supported format is registry/repository. A separate finding is created for a repository present in each registry. * Appended all repositories that are associated with an image to the Repository field on the Discovered Container Image \[sn_vul_container_image\] table, which can help you see images from specific repositories. * The default integration instance parameter for configuring finding keys for the Container Vulnerability Integration includes src_ci, vulnerability, package, image_layer, and image_repository. [Enhancements to the Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) : The Missing Assets \[sn_vul_wiz_missing_asset\] is deprecated. After updating to version 1.1, you must backdate your existing primary Wiz integrations by three days and run them. The backfill integrations are activated by default. After you run them after updating to v1.1, the following backfill integrations are no longer required: * Host Vulnerability Backfill Integration * Test Results Backfill Integration * Host Test Results Backfill Integration * Issues Backfill Integration Data for resources that have the validated_at_runtime flag set to 'yes' is imported and populated on detections. The CMDB internet-facing field on the discovered item is mapped to Limited Internet Exposure on findings. Fix information that includes 'Fix available', 'Partial fix available', 'No fix available', and 'Fix version' from the \[fix_available\] and \[fix_version\] columns is rolled up to CVITs from findings. Note: If there are two or more findings on a CVIT, the fixed version might only apply to one. In that case, 'Partial fix available' is rolled up to the CVIT. The Wiz vendor severity attribute is mapped to the 'Source severity' column on findings records in the Container Image Findings \[sn_vul_container_image_findings\] table. The cluster and namespace is evaluated for all the following entity Types: DEPLOYMENT, DAEMON_SET, STATEFUL_SET, POD. [Import container vulnerability data with the Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) : Import configuration test results from Wiz to detect non-compliant cloud configurations. Findings are mapped to cloud test results (CTRs) in the Configuration Compliance application to help you enforce security policies and standards across your cloud environment. [Enhancements to imported scanner results](https://www.servicenow.com/docs/access?context=cvr-remediation-task-overview&family=zurich&ft:locale=en-US) : Enhancements support more scanner data on imports. Namespaces and hierarchy cluster are considered and populated in the discovered container image \[sn_vul_container_image\] table if this data is imported. | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing Container Vulnerability Response features. {#dfrn3-containervulnerabilityresponse-summary__entry__18} | Release | Release notes | |-|-| | Xanadu | [Deprecated the privilege to delete a container vulnerable item for the Admin role](https://www.servicenow.com/docs/access?context=installed-with-cvr-data&family=xanadu&ft:locale=en-US) : As an admin with the sn_vul.vulnerability_admin role, you can't delete a container vulnerable item. This privilege is now given to the sn_vul.delete granular role. | | Yokohama | No updates for this release. | | Zurich | [Configure maximum rows in related lists](https://www.servicenow.com/docs/access?context=vr-max-rows-rel-list&family=zurich&ft:locale=en-US) : To improve readability and performance, you can now limit the number of rows shown in related lists on forms by setting the system property sn_vul_cmn.related_list.set_max_row. | [ ] ## Removed Between your current release family and Zurich, some Container Vulnerability Response features or functionality were removed. {#dfrn3-containervulnerabilityresponse-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | The Close button has been removed for a remediation task in the classic UI, Vulnerability Manager Workspace, and IT Remediation Workspace. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Deprecations Between your current release family and Zurich, some Container Vulnerability Response features or functionality were deprecated. {#dfrn3-containervulnerabilityresponse-summary__entry__34} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Activation information Review information on how to activate Container Vulnerability Response. {#dfrn3-containervulnerabilityresponse-summary__entry__42} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | Activation information : Install Container Vulnerability Response by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US). Important: Container Vulnerability Response is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | | Zurich | Activation information : Install Container Vulnerability Response and third-party integrations by requesting them from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=zurich&ft:locale=en-US). Important: Container Vulnerability Response is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__50} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__58} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for Container Vulnerability Response, such as specific requirements or compliance levels. {#dfrn3-containervulnerabilityresponse-summary__entry__66} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. | [ ] ## Localization information If there are specific localization considerations for Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__74} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | | Zurich | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Container Vulnerability Response we have noted them here. {#dfrn3-containervulnerabilityresponse-summary__entry__82} | Release | Release notes | |-|-| | Xanadu | * Reevaluate the risk score, assignments, remediation target date, exceptions, and remediation task for a specific set of container vulnerable items in Vulnerability Manager Workspace. See [Container Vulnerability Response](https://www.servicenow.com/docs/access?context=cvr-landing&family=xanadu&ft:locale=en-US) for more information. | | Yokohama | * With the sn_vul_container.vulnerability_analyst or sn_vul_container.vulnerability_admin role, create container remediation tasks manually in the Vulnerability Manager Workspace. * With the role sn_vul_container.remediation_owner, create container remediation tasks manually in the IT Remediation Workspace. See [Container Vulnerability Response](https://www.servicenow.com/docs/access?context=cvr-landing&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * If you are currently using Container Vulnerability Response and you want to upgrade to Unified Security Exposure Management (USEM), see [Unified Security Exposure Management release notes](https://www.servicenow.com/docs/access?context=secops-sem-rn&family=zurich&ft:locale=en-US) for more information about USEM and the Unified Security Exposure Management migration. * Import container image vulnerability data from the Wiz scanners into container vulnerable items (CVITs) with the Vulnerability Response Integration with Wiz. * With the sn_vul_container.vulnerability_analyst or sn_vul_container.vulnerability_admin role, create container remediation tasks manually in the Vulnerability Manager Workspace. * With the role sn_vul_container.remediation_owner, create container remediation tasks manually in the IT Remediation Workspace. See [Container Vulnerability Response](https://www.servicenow.com/docs/access?context=cvr-landing&family=zurich&ft:locale=en-US) for more information. | [ ]