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

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - zurich Combined Product Files

ft:clusterId :

    - delta3zy

bundleId :

    - delta3zy


---

# Combined Vulnerability Response release notes for upgrades from Yokohama to Zurich

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

Release version: Zurich  
Updated October 8, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 21 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 Vulnerability Response Release Notes for Upgrades from Yokohama to Zurich

This consolidated guide details the key updates, new features, enhancements, changes, and important upgrade information for ServiceNow Vulnerability Response from the Yokohama release through to Zurich.
It is designed to help ServiceNow customers prepare effectively for upgrading their instances and to understand functionality improvements impacting vulnerability management workflows.
Show full answer Show less  
The Zurich release introduces significant enhancements including new integrations, improved remediation workflows, UI refinements, and performance optimizations. It also prepares customers for future deprecations and migration paths toward Unified Security Exposure Management (USEM).

## Important Upgrade Information

* Now Assist for Vulnerability Response is deprecated starting with Zurich Patch 12; new instances will no longer have it installed, but existing support continues.
* Customers not moving to USEM should install Vulnerability Response versions below v30.x for compatibility with third-party integrations.
* The Wiz Missing Assets table used in integrations is deprecated; users must backdate and rerun Wiz integrations post-upgrade.
* Review the Vulnerability Response Compatibility Matrix and Release Schema Changes Knowledge Base article for supported versions and integrations.

## New Features and Enhancements

* **Wiz Integration Enhancements:** Configure resource types for import, activate backfill integrations for missing assets, and map new detection keys for improved vulnerability ingestion.
* **Manual Remediation Task Creation:** Vulnerability analysts and remediation owners can manually create host remediation tasks in both Vulnerability Manager and IT Remediation Workspaces with flexible grouping criteria.
* **Exception Management with Smart Assessment:** Advanced questionnaires can be configured to enforce mandatory exception justifications, improving collaboration and decision-making.
* **Lookup Rules and Background Jobs:** Enhanced performance by excluding inactive discovered items older than 90 days from lookup and licensing considerations, plus improved job status visibility.
* **Tenable.cs Integration:** Direct ingestion of cloud and container vulnerabilities from Tenable.cs, with setup assistance and scheduled import jobs to streamline remediation workflows.
* **Vulnerability Exposure Assessment by Publisher:** Assess and prioritize vulnerabilities by vendor, such as Microsoft or Red Hat, focusing remediation efforts on critical threats.
* **Risk Score Visibility:** Optionally view risk score changes in the work notes section of vulnerable items for better auditability.
* **Exception Rule Handling:** Nightly reevaluation of exception rules improves accuracy by unlinking vulnerable items that no longer meet criteria and reopening deferred items as needed.
* **Microsoft Defender Integration:** Unified plugin consolidates Defender for Cloud and Threat \& Vulnerability Management integrations, adding container image vulnerability ingestion and a guided migration path.
* **Qualys Integration Upgrades:** Support for newer API versions and additional data fields enhances visibility into vulnerability and compliance data.
* **Improved Remediation Target Date Management:** Dynamic recalculation of remediation target dates based on risk rating changes helps maintain accurate SLA tracking.
* **UI and Workflow Enhancements:** Coral theme with dark mode improves user experience; refined state management reduces manual effort and clarifies task ownership; confirmation messaging aids reassignment visibility.
* **Additional Integrations:** Support for Tenable endpoint scanning metadata, out-of-the-box vendor advisories via CSAF (e.g., Red Hat, Suse), and enhanced Wiz integration resource filtering.

## Changes and Removed Features

* Coral theme is now default for portals and workspaces, with a dark mode option.
* State management improvements provide better handling of mixed remediation task states and false positive transitions.
* Manual cancellation of exposure assessment background jobs is now available to reduce downtime.
* No significant removals or deprecations affecting core Vulnerability Response functionality as of Zurich.

## Activation and Additional Considerations

* Vulnerability Response and third-party integrations are available via the ServiceNow Store; customers must request installation there.
* Quick start tests are recommended post-upgrade to verify functionality, especially if customizations exist.
* Accessibility improvements include the new dark theme option to aid readability and reduce eye strain.
* No changes to browser requirements or localization were introduced in this release cycle.

## What ServiceNow Customers Can Expect

Upgrading to Zurich provides customers with enhanced integration capabilities, improved remediation workflows, and greater control over vulnerability management processes. The new features enable more granular tracking, better exception handling, and optimized performance. Customers benefit from streamlined UI experiences and expanded support for cloud and container vulnerability sources. Additionally, the upgrade prepares customers for future migrations to Unified Security Exposure Management, ensuring a path forward for comprehensive security posture management.

By carefully following the pre- and post-upgrade tasks and leveraging the new functionalities, ServiceNow customers can expect to improve their vulnerability prioritization, remediation efficiency, and overall security operations effectiveness.  
Consolidated page of all release notes for Vulnerability Response from Yokohama to Zurich.

## How to use this page

To help you prepare for your upgrade, we have combined the cross-family Vulnerability Response release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama 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 Vulnerability Response to Zurich

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

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | Upgrade information :   Starting with Zurich, Patch 12, 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. The change is reflected in the name of ServiceNow® products, including Now Assist for Vulnerability Response which is called ServiceNow Otto for Unified Security Exposure Management with these enhancements for the new AI experience. See [ServiceNow Otto for Unified Security Exposure Management](https://www.servicenow.com/docs/access?context=now-assist-for-usem-landing-ties&family=zurich&ft:locale=en-US) for more information. If you're currently using Vulnerability Response, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of 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're currently using the Vulnerability Response with Wiz integrations, after updating to new version 1.1, backdate any of your existing Wiz primary integrations by three days and run them. 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 Vulnerability Response application and 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 Vulnerability Response.  
{#dfrn3-vulnerabilityresponse-summary__entry__8}

| Release | Release notes |
|-|-|
| Yokohama | [Identify Wiz Resource Types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=yokohama&ft:locale=en-US) :   Identify the Resource Types (assets) that are reported by Wiz that you want to import with the Wiz Integration Resource Type configuration page in your ServiceNow AI Platform instance. The Resource Types that you select apply to all the primary Wiz vulnerability and compliance integrations except the Wiz Container Vulnerability Integration. See the [Wiz Vulnerability Response Integrations](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=yokohama&ft:locale=en-US) for more information about the vulnerability and compliance integrations. [Wiz Backfill Integrations](https://www.servicenow.com/docs/access?context=wiz-backfill&family=yokohama&ft:locale=en-US) :   Retrieve and process data stored on the Wiz Missing Assets \[sn_vul_wiz_missing_asset\] table for assets that were not processed by the primary Host Vulnerability Integration with a specialized Wiz Backfill Integration. The Host Vulnerability Backfill Integration is activated by default. Note: The Wiz Asset Integration and the Wiz Container Vulnerability Integration do not have backfill integrations. The Wiz Asset Integration can discover assets and create and update discovered item records on the Discovered item \[sn_sec_cmn_src_ci\] table. The Wiz Container Vulnerability Integration imports and processes discovered container image records. [Create host 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.vulnerability_analyst or sn_vul.vulnerability_admin role, you can create host remediation tasks manually by selecting some or all the records in the Host 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 host remediation tasks. [Create host 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 sn_vul.remediation_owner role, you can create host remediation tasks manually by selecting desired records in the Host 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 host remediation tasks. [Questionnaire Support in Exception Management via Smart Assessment](https://www.servicenow.com/docs/access?context=vr-exception-management-smart-assessment&family=yokohama&ft:locale=en-US) :   Configure advanced questionnaires as part of the exception management process using Smart Assessment. This enhancement allows remediation owners to provide detailed context for exception requests and enables approvers to configure conditional questions to gather information for informed decision making. * Collaboration and streamlined approval: Facilitate collaboration between your vulnerability management and remediation teams by streamlining the approval process with clear and complete exception justifications. * Mandatory questionnaires: Block the submission of exception requests until mandatory questionnaires are completed. If a questionnaire is marked as mandatory, the test results and its associated remediation tasks remain in the 'Open' state until the questionnaire is completed and submitted. * If the questionnaire is incomplete, the state change approval record is saved as 'Draft'. Only after completing the questionnaire can the user submit the exception request, which will then move the test results or remediation tasks to the 'In Review' state. [Lookup rules enhancements](https://www.servicenow.com/docs/access?context=working-unmatched-cis&family=yokohama&ft:locale=en-US) :   When you reapply Lookup rules, Discovered items (DIs) that have been inactive for more than 90 days are ignored. These Discovered items (DIs) are also excluded from licensing considerations. Removing them from the lookup logic can improve performance and reduce processing time. * Background job enhancements: New fields have been added to help you view successfully evaluate records, the time taken for processing, the time remaining, and an estimated number of records. * Improved accuracy for non-CSDM Vulnerability Response users: A system property (sn_sec_cmn.ci_lifecycle_status_source) has been introduced to help users who do not follow Common Service Data Model (CSDM) standards. This property ensures that Discovered items (DIs) and associated VITs are properly marked as Decommissioned and are excluded from the CI Lookup. Additionally, the Retired Configuration Items PA indicator has been updated to accurately reflect CIs based on the decommissioning flags. * The scheduled job to create reconcile unmatched discovered items feature is deprecated. You can "Reapply Look up Rules" for selected or filtered items in the discovered items table view. [Tenable.cs integrations with the Vulnerability Response and Container Vulnerability Response application](https://www.servicenow.com/docs/access?context=tenable-cs-integrations-list&family=yokohama&ft:locale=en-US) :   The Vulnerability Response Integration with Tenable application now supports data ingestion from Tenable.cs, enabling you to bring in cloud and container vulnerabilities directly into ServiceNow. This integration enhances your ability to prioritize and remediate vulnerabilities identified in Tenable cloud resources and container images. Key capabilities are: * Importing vulnerabilities discovered by Tenable.cs in cloud hosts and container images into ServiceNow automatically. * Enabling remediation workflows to triage, assign, and resolve the most critical vulnerabilities across cloud-native and containerized environments. * Using the Setup Assistant to easily configure credentials and integration parameters---get started with minimal manual setup. * Scheduling jobs to run periodically to import findings from Tenable.cs, create vulnerable items (for cloud hosts), create container vulnerable items and associate them with the relevant cloud resources and container image records. [Assess vulnerability exposure by publisher](https://www.servicenow.com/docs/access?context=vr-ws-exposure-publisher&family=yokohama&ft:locale=en-US) :   Starting with v5.0 of Vulnerability Exposure Assessment, a publisher-based assessment is introduced that enables you to assess the vulnerability impact by vendor. For example, Microsoft, and Red Hat. By focusing on recently disclosed vulnerabilities from critical vendors, you can prioritize remediation and proactively address threats, improving your overall security posture. [View risk score details of a vulnerable item in the Work notes section](https://www.servicenow.com/docs/access?context=vuln-calculators-rules&family=yokohama&ft:locale=en-US) :   Starting with v25.0.3 of 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 vulnerable item in the Work notes section. Additionally, the work notes are updated only if there's a change in the risk score. [Quick Start Tests for Vulnerability Response](https://www.servicenow.com/docs/access?context=available-quick-start-tests&family=yokohama&ft:locale=en-US) :   After upgrades and deployments of new applications or integrations, run quick start tests to verify that Vulnerability Response works as expected. If you customized Vulnerability Response, copy the quick start tests and configure them for your customizations. [Enhancements to exception rules handling](https://www.servicenow.com/docs/access?context=direct-deferral-of-vits-by-exception-rules-without-remediation-task-creation&family=yokohama&ft:locale=en-US) : * Exception rules are reevaluated with nightly scheduled jobs. * Vulnerable items that no longer match exception rule conditions are unlinked from remediation tasks. * A deferred vulnerable item (VIT) is reopened if it doesn't match any active exception rules. * Exception rules don't create remediation tasks. VITs are deferred directly and aren't associated with a remediation task. [Tenable's endpoint scanning integration](https://www.servicenow.com/docs/access?context=tenable-io-integrations-list&family=yokohama&ft:locale=en-US) :   Support for Tenable's endpoint scanning integration to retrieve scan metadata. The integration fetches scan details using the last_schedule_id from existing asset data in Tenable.io. Reopened Count field on vulnerable items :   Added the Reopened Count field on vulnerable items to track the number of times their states change from 'Closed' to 'Open' or to 'Active'. [Out-of-the-box vendor advisories via Common Security Advisory Framework (CSAF) integration](https://www.servicenow.com/docs/access?context=vuln-solution-mgmt&family=yokohama&ft:locale=en-US) :   The following vendor advisories are configured out-of-the-box and are automatically activated when the Solution Management plugin is enabled: Redhat and Suse. |
| 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. [Unified Microsoft Defender Integration for Security Exposure Management](https://www.servicenow.com/docs/access?context=mstvm-integration&family=zurich&ft:locale=en-US) :   The Microsoft Defender for Cloud and Microsoft Threat and Vulnerability Management (MS TVM) integrations are now consolidated into a single plugin, Microsoft Defender Integration for Security Exposure Management. the standalone Microsoft Defender for Cloud Integration application is deprecated. The unified plugin also introduces container image vulnerability ingestion from Microsoft Defender for Cloud, creating Container Vulnerable items on your instance. The deprecated application are supported through a guided migration path to transfer existing data to the unified plugin. [Optimized Tenable.io Compliance Results ingestion](https://www.servicenow.com/docs/access?context=tenable-io-integrations-list&family=zurich&ft:locale=en-US) :   Starting with v 6.1.3, the Tenable.io Compliance Results Integration is replaced by the Tenable.io Fixed Compliance Results Integration and Tenable.io Open Compliance Results Integration. Compliance results are now imported based on their status, optimizing ingestion performance and scalability for environments with large volumes of compliance data while keeping remediation and compliance tracking aligned with the current state of findings. [Improved vulnerability assessment workflows](https://www.servicenow.com/docs/access?context=vr-ws-vuln-assessment&family=zurich&ft:locale=en-US) : * CI filtering for vulnerability assessments: You can now filter which configuration items are included in a vulnerability assessment using a condition builder. * Business Application population on AVITs: AVITs created from SBOM assessment results now include Business Application information, helping you understand application impact and prioritize remediation. * Priority roll‑down from vulnerability assessments: Updates to the priority of a vulnerability assessment now automatically roll down to associated VITs and AVITs, ensuring consistent prioritization based on the highest severity. [Enhanced Compensatory controls](https://www.servicenow.com/docs/access?context=requesting-approving-risk-reduction&family=zurich&ft:locale=en-US) :   When new vulnerable items are ingested and associated with a remediation task that already has an approved compensating control, the reduced risk rating is now automatically inherited by those new vulnerable items. [Qualys Integration -- API enhancements](https://www.servicenow.com/docs/access?context=qualys-rest-messages&family=zurich&ft:locale=en-US) :   Qualys Integration has been upgraded to support newer Qualys API versions across Host Detection, Host List, Knowledgebase, PC Controls, PC Policies, and PCRS integrations. The integrations now ingest additional data fields, including vulnerability detection source, authentication privilege status, active status for controls and policies, and cloud metadata, giving you better visibility into your vulnerability and compliance data. [Enhancements to the Wiz Vulnerability Response Integration](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. * You can configure the First parameter for the Wiz Asset Integration to help you resolve 504 errors. You can reduce the page size if you're having memory issues or generating errors. The default value is 500. [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 backdate and run your primary integrations, the following backfill integrations are no longer required: * Host Vulnerability Backfill Integration * Test Results Backfill Integration * Host Test Results Backfill Integration * Issues Backfill Integration Resource types filters are supported on the Host Vulnerability, Host Test Results, Test Results, and Issues tabs on the Wiz Configuration page. Additional attributes imported from Wiz that are not stored in the Discovered items \[sn_sec_cmn_src_ci\] table are stamped with Asset Attributes in this table. Test results from the Host misconfiguration integration are classified as result type 'host_misconfiguration'. Data for resources that have the validated_at_runtime flag set to 'yes' is imported and populated on detections. The is_ignored column is deprecated on the Host Test Results and Test Results Integrations. This column was replaced by the is_result_ignored column. The CMDB internet-facing field on the discovered item is mapped to Limited Internet Exposure on findings. Column length for the descriptions in the Host Vulnerability import table has been increased. [Improved remediation target date handling](https://www.servicenow.com/docs/access?context=sem-recalculate-rt-date&family=zurich&ft:locale=en-US) :   Remediation target (RT) dates now dynamically recalculate when a finding's risk rating changes. Administrators can configure how recalculation occurs to verify RT dates remain accurate and align with the latest risk updates, helping maintain consistent and reliable SLA tracking. [Identify Wiz Resource Types for import](https://www.servicenow.com/docs/access?context=wiz-assets-resources-tab&family=zurich&ft:locale=en-US) :   Identify the Resource Types (assets) that are reported by Wiz that you want to import with the Wiz Integration Resource Type configuration page in your ServiceNow AI Platform instance. The Resource Types that you select apply to all the primary Wiz vulnerability and compliance integrations except the Wiz Container Vulnerability Integration. See the [Wiz Vulnerability Response Integrations](https://www.servicenow.com/docs/access?context=vr-wiz-exploring-host-cf&family=zurich&ft:locale=en-US) for more information about the vulnerability and compliance integrations. [Wiz Backfill Integrations](https://www.servicenow.com/docs/access?context=wiz-backfill&family=zurich&ft:locale=en-US) :   Retrieve and process data stored on the Wiz Missing Assets \[sn_vul_wiz_missing_asset\] table for assets that were not processed by the primary Host Vulnerability Integration with a specialized Wiz Backfill Integration. The Host Vulnerability Backfill Integration is activated by default. Note: The Wiz Asset Integration and the Wiz Container Vulnerability Integration do not have backfill integrations. The Wiz Asset Integration can discover assets and create and update discovered item records on the Discovered item \[sn_sec_cmn_src_ci\] table. The Wiz Container Vulnerability Integration imports and processes discovered container image records. [Enhancements to Detection Key Configurations for Vulnerability Response](https://www.servicenow.com/docs/access?context=detection-key-configurations-for-vr&family=zurich&ft:locale=en-US) :   Introduced configurable detection keys that enable you to choose between Asset ID and Configuration Item, with validations, UI controls. Enhanced an existing schedule job to update existing detections. [Import host 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 host vulnerability findings related to virtual machines and serverless assets in your cloud environment with the Wiz Host Vulnerability Integration. These findings are mapped to Host Vulnerable Items (VITs) within the Vulnerability Response application to support remediation workflows. [Modify the severity for a CVE or TPE](https://www.servicenow.com/docs/access?context=vmws-modify-reset-severity&family=zurich&ft:locale=en-US) :   Vulnerability managers and vulnerability analysts can now adjust the severity of common vulnerabilities and exposures (CVEs) and third-party entries (TPEs) from the list view in the vulnerability manager workspace. The risk level of the associated vulnerabilities will be recalculated during the scheduled jobs based on the modified severity. You can also reset the severity to its original source value if required. [Questionnaire Support in Exception Management via Smart Assessment](https://www.servicenow.com/docs/access?context=vr-exception-management-smart-assessment&family=zurich&ft:locale=en-US) :   Configure advanced questionnaires as part of the exception management process using Smart Assessment. This enhancement enables remediation owners to provide detailed context for exception requests and enables approvers to configure conditional questions to gather information for informed decision making. * Collaboration and streamlined approval: Facilitate collaboration between your vulnerability management and remediation teams by streamlining the approval process with clear and complete exception justifications. * Mandatory questionnaires: Block the submission of exception requests until mandatory questionnaires are completed. If a questionnaire is marked as mandatory, the test results and its associated remediation tasks remain in the 'Open' state until the questionnaire is completed and submitted. * If the questionnaire is incomplete, the state change approval record is saved as 'Draft'. Only after completing the questionnaire can the user submit the exception request, which will then move the test results or remediation tasks to the 'In Review' state. [Lookup rules enhancements](https://www.servicenow.com/docs/access?context=working-unmatched-cis&family=zurich&ft:locale=en-US) :   When you reapply Lookup rules, Discovered items (DIs) that have been inactive for more than 90 days are ignored. These Discovered items (DIs) are also excluded from licensing considerations. Removing them from the lookup logic can improve performance and reduce processing time. * Background job enhancements: New fields have been added to help you view successfully evaluate records, the time taken for processing, the time remaining, and an estimated number of records. * Improved accuracy for non-CSDM Vulnerability Response users: A system property (sn_sec_cmn.ci_lifecycle_status_source) has been introduced to help users who do not follow Common Service Data Model (CSDM) standards. This property verifies that Discovered items (DIs) and associated VITs are properly marked as Decommissioned and are excluded from the CI Lookup. Additionally, the Retired Configuration Items PA indicator has been updated to accurately reflect CIs based on the decommissioning flags. * The scheduled job to create reconcile unmatched discovered items feature is deprecated. You can "Reapply Look up Rules" for selected or filtered items in the discovered items table view. [Tenable.cs integrations with the Vulnerability Response and Container Vulnerability Response application](https://www.servicenow.com/docs/access?context=tenable-cs-integrations-list&family=zurich&ft:locale=en-US) :   The Vulnerability Response Integration with Tenable application now supports data ingestion from Tenable.cs, enabling you to bring in cloud and container vulnerabilities directly into ServiceNow. This integration enhances your ability to prioritize and remediate vulnerabilities identified in Tenable cloud resources and container images. Key capabilities are: * Importing vulnerabilities discovered by Tenable.cs in cloud hosts and container images into ServiceNow automatically. * Enabling remediation workflows to triage, assign, and resolve the most critical vulnerabilities across cloud-native and containerized environments. * Using the Setup Assistant to easily configure credentials and integration parameters---get started with minimal manual setup. * Scheduling jobs to run periodically to import findings from Tenable.cs, create vulnerable items (for cloud hosts), create container vulnerable items and associate them with the relevant cloud resources and container image records. [Assess vulnerability exposure by publisher](https://www.servicenow.com/docs/access?context=vr-ws-exposure-publisher&family=zurich&ft:locale=en-US) :   Starting with v5.0 of Vulnerability Exposure Assessment, a publisher-based assessment is introduced that enables you to assess the vulnerability impact by vendor. For example, Microsoft, and Red Hat. By focusing on recently disclosed vulnerabilities from critical vendors, you can prioritize remediation and proactively address threats, improving your overall security posture. [View risk score details of a vulnerable item in the Work notes section](https://www.servicenow.com/docs/access?context=vuln-calculators-rules&family=zurich&ft:locale=en-US) :   Starting with v25.0.3 of 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 vulnerable item in the Work notes section. Additionally, the work notes are updated only if there's a change in the risk score. [Quick Start Tests for Vulnerability Response](https://www.servicenow.com/docs/access?context=available-quick-start-tests&family=zurich&ft:locale=en-US) :   After upgrades and deployments of new applications or integrations, run quick start tests to verify that Vulnerability Response works as expected. If you customized Vulnerability Response, copy the quick start tests and configure them for your customizations. [Enhancements to exception rules handling](https://www.servicenow.com/docs/access?context=direct-deferral-of-vits-by-exception-rules-without-remediation-task-creation&family=zurich&ft:locale=en-US) : * Exception rules are reevaluated with nightly scheduled jobs. * Vulnerable items that no longer match exception rule conditions are unlinked from remediation tasks. * A deferred vulnerable item (VIT) is reopened if it doesn't match any active exception rules. * Exception rules don't create remediation tasks. VITs are deferred directly and aren't associated with a remediation task. [Tenable's endpoint scanning integration](https://www.servicenow.com/docs/access?context=tenable-io-integrations-list&family=zurich&ft:locale=en-US) :   Support for Tenable's endpoint scanning integration to retrieve scan metadata. The integration fetches scan details using the last_schedule_id from existing asset data in Tenable.io. Reopened Count field on vulnerable items :   Added the Reopened Count field on vulnerable items to track the number of times their states change from 'Closed' to 'Open' or to 'Active'. [Out-of-the-box vendor advisories via Common Security Advisory Framework (CSAF) integration](https://www.servicenow.com/docs/access?context=vuln-solution-mgmt&family=zurich&ft:locale=en-US) :   The following vendor advisories are configured by default and are automatically activated when the Solution Management plugin is enabled: Redhat and Suse. |
[ ]

## Changes

Between your current release family and Zurich, some changes were made to existing Vulnerability Response features.  
{#dfrn3-vulnerabilityresponse-summary__entry__14}

| Release | Release notes |
|-|-|
| Yokohama | No updates for this release. |
| Zurich | Coral theme :   Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Enhanced UI experience in workspaces when reassigning vulnerable items](https://www.servicenow.com/docs/access?context=using-vulnerability-manager-workspace&family=zurich&ft:locale=en-US) :   When you reassign a record (VIT, AVIT, CVIT, or CTR) in workspace to a group you're not a member of, the system now confirms the reassignment and displays a clearer message explaining why the record is no longer visible. This helps you understand that access is now limited to the new assignment group, reducing confusion. [Granular VIT creation for Microsoft TVM recommendations](https://www.servicenow.com/docs/access?context=vr-configure-vi-key&family=zurich&ft:locale=en-US) :   You can now configure recommendation as a vulnerability item (VIT) key for Microsoft Threat \& Vulnerability Management (TVM). This enhancement enables each recommendation to generate a separate vulnerable item, offering more granular control for tracking, assigning, and managing remediation efforts, especially when different recommendations require actions from different teams. [Improved state management for remediation tasks and vulnerable items](https://www.servicenow.com/docs/access?context=vr-rt-states&family=zurich&ft:locale=en-US) :   State management logic for roll down of state from remediation tasks (RTs) to findings and roll up of state from findings to RTs has been refined across all modules. Updates improve accuracy by handling mixed item states (a combination of Deferred and Closed), supporting closure of tasks in sub-states like In-Review, and reopening tasks based on the Assigned To field. The update also improves handling of False Positive state transitions based on scanner results as source of truth. These enhancements reduce manual effort, clarify task ownership, and streamline remediation workflows. [Ability to manually cancel Exposure Assessment background jobs](https://www.servicenow.com/docs/access?context=vr-ws-exposure-assessment&family=zurich&ft:locale=en-US) :   Vulnerability Admins and Event Managers can now cancel Exposure Assessment background jobs that were triggered with incorrect parameters or are taking longer than expected. This enhancement reduces downtime by removing the need to wait for the job to complete. After the job is cancelled, the substate is immediately set to User cancelled, and the state updates to Complete after the job is fully terminated; giving you better control and flexibility. [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. [Qualys Integration -- Detection Splitting](https://www.servicenow.com/docs/access?context=split-qualys-detections&family=zurich&ft:locale=en-US) :   Use the Qualys Host Detection Integration to create a separate VIT for each vulnerability instance based on proof. This improves accuracy in vulnerability tracking and supports clearer team ownership during remediation. [Activate the QVS score integration](https://www.servicenow.com/docs/access?context=enable-qualys-qvs-score&family=zurich&ft:locale=en-US) :   Add risk context specific to Qualys to CVEs by importing QVS scores, helping you make more informed prioritization decisions. |
[ ]

## Removed

Between your current release family and Zurich, some Vulnerability Response features or functionality were removed.  
{#dfrn3-vulnerabilityresponse-summary__entry__20}

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

## Deprecations

Between your current release family and Zurich, some Vulnerability Response features or functionality were deprecated.  
{#dfrn3-vulnerabilityresponse-summary__entry__26}

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

## Activation information

Review information on how to activate Vulnerability Response.  
{#dfrn3-vulnerabilityresponse-summary__entry__32}

| Release | Release notes |
|-|-|
| Yokohama | Activation information :   Install 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: Vulnerability Response is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. |
| Zurich | Activation information :   Install 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: 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 Vulnerability Response we have noted them here.  
{#dfrn3-vulnerabilityresponse-summary__entry__38}

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

## Browser requirements

If any specific browser requirements were introduced or changed for Vulnerability Response we have noted them here.  
{#dfrn3-vulnerabilityresponse-summary__entry__44}

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

## Accessibility information

Review details on accessibility information for Vulnerability Response, such as specific requirements or compliance levels.  
{#dfrn3-vulnerabilityresponse-summary__entry__50}

| 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. |
[ ]

## Localization information

If there are specific localization considerations for Vulnerability Response we have noted them here.  
{#dfrn3-vulnerabilityresponse-summary__entry__56}

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

## Highlight information

If there are specific highlight considerations for Vulnerability Response we have noted them here.  
{#dfrn3-vulnerabilityresponse-summary__entry__62}

| Release | Release notes |
|-|-|
| Yokohama | * With the sn_vul.vulnerability_analyst or sn_vul.vulnerability_admin role, create host remediation tasks manually in the Vulnerability Manager Workspace. * With the sn_vul.remediation_owner role, create host remediation tasks manually in the IT Remediation Workspace. See [Vulnerability Response](https://www.servicenow.com/docs/access?context=vuln-landing-page&family=yokohama&ft:locale=en-US) for more information about the Vulnerability Response application. See the [Vulnerability Response Compatibility Matrix and Release Schema Changes](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0856498) Knowledge Base article for more information about released Security Operations applications and their version compatibility. |
| Zurich | * If you're currently using 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 host vulnerability data from the Wiz scanners into Vulnerability Response VITs to help vulnerability managers assess your over-all cloud security posture. * With the sn_vul.vulnerability_analyst or sn_vul.vulnerability_admin role, create host remediation tasks manually in the Vulnerability Manager Workspace. * With the sn_vul.remediation_owner role, create host remediation tasks manually in the IT Remediation Workspace. See [Vulnerability Response](https://www.servicenow.com/docs/access?context=vuln-landing-page&family=zurich&ft:locale=en-US) for more information. |
[ ]