---
sourceDocument: australia Combined Product Files
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - australia Combined Product Files

ft:clusterId :

    - delta3ay

bundleId :

    - delta3ay


---

# Combined Container Vulnerability Response release notes for upgrades from Yokohama to Australia

# Combined Container Vulnerability Response release notes for upgrades from Yokohama to Australia {#ariaid-title1}

Release version: Australia  
Updated October 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 15 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 Yokohama to Australia

This consolidated release notes document provides ServiceNow customers with essential information for upgrading Container Vulnerability Response from Yokohama through Zurich to Australia releases.
It highlights new features, changes, deprecations, activation steps, and important upgrade tasks to ensure a smooth transition and enhanced container vulnerability management.
Show full answer Show less  
The document also covers integration updates with third-party scanners and AWS/Microsoft security services, and clarifies support and compatibility considerations for customers choosing to upgrade or maintain existing versions.

## Important Upgrade Information

* **Pre- and post-upgrade tasks:** Customers must review and complete specified tasks before and after upgrading to Australia to ensure system stability and feature accessibility.
* **Deprecations:** Now Assist for Vulnerability Response is being deprecated starting Australia Patch 5; it will be hidden on new instances but remains supported.
* **Wiz Integration changes:** The Missing Assets table is deprecated; users must backdate existing Wiz primary integrations by three days and rerun them after upgrading to v1.1.
* **Upgrade paths:** Customers not migrating to Unified Security Exposure Management (USEM) should install Container Vulnerability Response versions below v30.x for continued support and integration compatibility.

## New Features and Enhancements

* **Workspace improvements:** Unassign workflow support for container vulnerable items (CVITs) and remediation tasks, enabling better assignment management and approval workflows.
* **Manual remediation task creation:** Roles with appropriate permissions can create manual container remediation tasks in both Vulnerability Manager and IT Remediation workspaces, grouping CVITs based on selected criteria.
* **Granularity configuration:** Ability to configure CVIT granularity using Registry and data source information, supporting image or Kubernetes data views.
* **Enhanced data visibility:** Additional timestamp columns for CVITs and optional risk score change tracking in Work Notes improve auditability and triage accuracy.
* **Wiz integration upgrades:** Improved mapping of UUIDs, source IDs, and repository formatting; full imports necessary post-upgrade to view enriched container vulnerability data.
* **Australia release specific:** AWS Integration supports AWS Inspector and AWS Security Hub for automated import of host/container vulnerabilities and misconfigurations.
* **Microsoft Defender integration:** Consolidation of Defender plugins into a unified Security Exposure Management plugin with container image vulnerability ingestion and guided migration.
* **Container image vulnerability key configuration:** Customizable keys in the AI Platform to drive CVIT creation, supporting AWS ECS and EKS environments with scanner and discovery data sources.
* **Improved import support:** Namespace and cluster hierarchy data now imported and populated, enabling more precise vulnerability tracking.

## Changes and Deprecations

* **Related list row limits:** System property added to limit rows in related lists for improved performance and readability.
* **Path column relocation:** For Prisma Cloud Compute and Wiz integrations, path tracking moved from the Container Image Package to Container Image Finding table to enhance image association accuracy.
* **Deprecated tables:** The Missing Assets table for Wiz backfill integrations is deprecated and requires integration backdating and rerunning post-upgrade.

## Activation and Compatibility

* Container Vulnerability Response and related third-party integrations must be installed via the ServiceNow Store.
* Compatibility matrices and release schema changes are available to verify supported versions and integrations across releases.
* Customers upgrading to USEM should consult the Unified Security Exposure Management release notes for migration guidance.

## Practical Takeaways for ServiceNow Customers

* Review and perform required pre- and post-upgrade tasks to maintain integration functionality and data integrity.
* Plan for deprecated features like Now Assist for Vulnerability Response and update workflows accordingly.
* After upgrading, run a full import to enable new enriched container vulnerability data views and features.
* Utilize enhanced workspace features for better vulnerability assignment and remediation task management.
* Leverage improved integrations with AWS and Microsoft Defender to expand vulnerability coverage and automate import processes.
* Configure vulnerability keys and granularity settings to tailor vulnerability detection to your container environments, including AWS ECS and EKS.
* Ensure understanding of deprecations, especially in Wiz integrations, to avoid data gaps and maintain accurate vulnerability tracking.  
Consolidated page of all release notes for Container Vulnerability Response from Yokohama to Australia.

## 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 Yokohama to Australia.  
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 Australia

Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed.  
{#dfrn3-containervulnerabilityresponse-summary__entry__2}

| Release | Release notes |
|-|-|
| 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. |
| Australia | Upgrade information :   Starting with Australia Patch 5, Now Assist for Vulnerability Response is being prepared for future deprecation. It will be hidden and no longer installed on new instances but will continue to be supported. For details, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base. ServiceNow Otto® is the new AI experience brand. This change is reflected in the name of ServiceNow products, including the Now Assist for Vulnerability Response product name, which will be replaced with ServiceNow Otto for Unified Security Exposure Management. Your product entitlements remain unchanged. Check your entitlements to determine your access to specific features. Enhancements to Container Vulnerability Response permit you to see enriched container vulnerability data on data imports from your third-party scanners. After you upgrade, perform a full import to view the features on discovered container image, container image finding, and container vulnerable item records that are described in the following New in the Australia release section. If you're 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. 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 Australia 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 Australia, new features were introduced for Container Vulnerability Response.  
{#dfrn3-containervulnerabilityresponse-summary__entry__10}

| Release | Release notes |
|-|-|
| 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. |
| Australia | [Activate the Wiz Asset Integration and identify resource types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=australia&ft:locale=en-US) :   Enhancements to the Wiz integration include: * A link lets you navigate from the Wiz configuration module directly to the Configure VI Granularity module where you can configure the keys that generate Container Vulnerability Response findings. * Starting with version 32.1 (USEM) and version 4.1 (non-USEM), the Asset integration is deactivated by default and is not a mandatory prerequisite for the other Wiz integration imports. If you choose to activate it, the Asset integration will retrieve assets for all resource types if you don't specify the ones you want on the Asset Integration Configuration tab. To avoid importing vulnerability data you don't need, identify only the resources (assets) that you want to import with this integration. * Resource Type is no longer a mandatory field for configuring the Vulnerability Response Integration with Wiz. You can now save Wiz configurations for the integrations without specifying a Resource Type, simplifying setup for use cases where specifying a Resource Type isn't appropriate. [Configure Image Vulnerability keys for Container Vulnerability Response CVIT creation](https://www.servicenow.com/docs/access?context=cvr-configuring-findings-key-granularity&family=australia&ft:locale=en-US) :   Configure records on the Configure Image Vulnerability Keys \[sn_vul_container_image_vulnerability_keys\] table in your ServiceNow AI Platform® instance for the Image Vulnerability Keys that create container vulnerable items (CVIT)s. * The Universally Unique Identifier (UUID) provided by Wiz is now mapped as the detection key for the Wiz Host Vulnerability integration. * AWS ECS (Elastic Container Service) and AWS EKS (Elastic Kubernetes Service) environments are supported. * Cluster and Service are supported for AWS ECS environments. * Namespace, Registry, and Service are supported for AWS EKS environments. * Choose either Scanner (third-party scanners) or Discovery (Configuration Management Database (CMDB)) as sources for data import for AWS ECS and AWS EKS. Note: If you choose Discovery as the data source, the Populate image relationships scheduled job runs daily to pre-import cluster and service details, and you should schedule your third-party integration runs at least 4 hours after this scheduled job is completed to verify that the pre-import data is available. This job is activated by default, but you must set the schedule so it runs before your scheduled third-party integration runs. For new customers only: The system property, sn_vul_container.image_relationship_mapping_months sets the number of previous months (1-12) that you want your third-party integration to look for container image updates when processing relationship mappings. This data is used to filter images by the sys_updated_on field. The default setting is three months. After you configure the integration run, relationship mapping is created for images which have been scanned in the last 90 days and present in discovered container images. * Column labels on the Container Vulnerable item \[sn_vul_container_image_vulnerable_item\] table are updated to support the scanner and discovery options, depending on your choice on the Configure Image Vulnerability Keys configuration page: * Cluster (Scanner) Namespace (scanner), and Service (scanner) for scanner data * Cluster (Discovery), Namespace (Discovery) and Service (Discovery) for Discovery [AWS Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=aws-integration-for-security-exposure-management-overview&family=australia&ft:locale=en-US) :   The AWS Integration for Security Exposure Management supports integrations with the following AWS services: * AWS Inspector is an automated vulnerability management service that continuously scans EC2 instances, ECR container images, and Lambda functions for software vulnerabilities (CVEs) and unintended network exposure. The Vulnerability Response integration with AWS Inspector imports host and container vulnerability findings from AWS Inspector. * AWS Security Hub is a security service that is used to centralize and update security checks across AWS accounts. It provides a unified view of security alerts and compliance status by integrating with various AWS services. The Vulnerability Response integration with AWS Security Hub imports host, container vulnerabilities, and misconfigurations from AWS Security Hub. [Unified Microsoft Defender Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=ms-defender-sem&family=australia&ft:locale=en-US) :   The Microsoft Defender for Cloud and Microsoft Defender Threat and Vulnerability Management (MS TVM) plugins are now consolidated into a single plugin: Microsoft Defender Integration for Security Exposure Management. This consolidation deprecates the standalone Microsoft Defender for Cloud plugin. The unified plugin also introduces container image vulnerability ingestion from Microsoft Defender for Cloud, creating Container Vulnerable Items on your instance. A guided migration path is available to transfer existing data from the deprecated applications to the unified plugin. |
[ ]

## Changes

Between your current release family and Australia, some changes were made to existing Container Vulnerability Response features.  
{#dfrn3-containervulnerabilityresponse-summary__entry__18}

| Release | Release notes |
|-|-|
| 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. |
| Australia | No updates for this release. |
[ ]

## Removed

Between your current release family and Australia, some Container Vulnerability Response features or functionality were removed.  
{#dfrn3-containervulnerabilityresponse-summary__entry__26}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | No updates for this release. |
[ ]

## Deprecations

Between your current release family and Australia, some Container Vulnerability Response features or functionality were deprecated.  
{#dfrn3-containervulnerabilityresponse-summary__entry__34}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | * The Path Column in the Container Image Package \[sn_vul_container_image_package\] table for the Vulnerability Response Integration with Palo Alto Networks Prisma Cloud Compute and [Vulnerability Response Integration with Wiz](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=australia&ft:locale=en-US) third-party integrations. Path tracking has been moved to the Path Column on the Container Image Finding \[sn_vul_container_image_findings\] table to support accurate and consistent path and image association. If you use these integrations you must refer to the Path column available on the Container Image Finding \[sn_vul_container_image_findings\] table. * 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=australia&ft:locale=en-US) is deprecated. If you're 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. See 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). |
[ ]

## Activation information

Review information on how to activate Container Vulnerability Response.  
{#dfrn3-containervulnerabilityresponse-summary__entry__42}

| Release | Release notes |
|-|-|
| 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. |
| Australia | 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) 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=australia&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 |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | 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 |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | 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 |
|-|-|
| 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. |
| Australia | No updates for this release. |
[ ]

## 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 |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | No updates for this release. |
| Australia | 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 |
|-|-|
| 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. |
| Australia | * The AWS Integration for Security Exposure Management supports integrations with AWS Inspector and AWS Security Hub. * If you're currently using Container Vulnerability Response and you want to upgrade to Unified Security Exposure Management (USEM), see [Unified Security Exposure Management (USEM) release notes](https://www.servicenow.com/docs/access?context=secops-sem-rn&family=australia&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=australia&ft:locale=en-US) for more information. |
[ ]