---
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 Application Vulnerability Response release notes for upgrades from Yokohama to Zurich

# Combined Application 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) 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 Application Vulnerability Response Release Notes for Upgrades from Yokohama to Zurich

This document consolidates all release notes related to the Application Vulnerability Response (AVR) product upgrades from the Yokohama to Zurich releases.
It provides ServiceNow customers with essential information to prepare for and execute upgrades, highlighting new features, enhancements, changes, and activation details for the Zurich release.
Show full answer Show less  

## Important Upgrade Considerations

* Before upgrading to Zurich, review and complete pre- and post-upgrade tasks specific to Application Vulnerability Response.
* For customers not transitioning to Unified Security Exposure Management (USEM), install AVR versions below v30.x for compatibility with third-party integrations.
* Refer to the Vulnerability Response Compatibility Matrix and Release Schema Changes in the Now Support Knowledge Base for detailed compatibility information.

## Key Features and Enhancements

The Zurich release introduces multiple new capabilities and workflow improvements, including:

* **Unassign Workflow:** Supports unassigning application vulnerable items (AVITs) and remediation tasks (AVULs) with optional approval requests to streamline reassignment and triage accuracy.
* **SBOM Document Upload via GitHub Action:** Enables uploading Software Bill of Material (SBOM) documents directly to ServiceNow using GitHub Actions.
* **Manual Creation of Application Remediation Tasks:** Roles such as `snvul.appsecmanager` and `snvul.appsecuritychampion` can create remediation tasks manually in Vulnerability Manager and IT Remediation Workspaces by grouping selected AVIT records.
* **Manual Vulnerability Ingestion:** Import AVITs from external sources (CSV, Excel) to manage penetration test findings centrally.
* **Penetration Test Workspace:** Provides dashboards to monitor penetration test requests, findings, and team progress, emphasizing critical items and remediation status.
* **Expanded Penetration Test Assessment Types:** New assessment classifications such as Emergency Release, Bug Bounty Program, Release Approvals, One-off Reviews, and Executive Interest support diverse testing scenarios.
* **Change Request Creation:** Users with appropriate roles can create change requests directly from remediation tasks to expedite vulnerability investigations, with prepopulated data when the application is linked to a configuration item (CI).
* **Software Bill of Materials Workspace Enhancements:** Supports bulk deletion of BOM entities and automatically closes associated AVITs.
* **Risk Score Work Notes:** Optional system property enables detailed tracking of risk score changes in AVIT work notes.
* **Compensatory Controls Enhancements:** Newly ingested vulnerable items inherit reduced risk ratings from remediation tasks with approved compensatory controls.
* **Improved Vulnerability Assessment Workflows:** Includes CI filtering, business application population on AVITs, and priority roll-down from assessments to findings for consistent prioritization.
* **Remediation Task Rule Execution Modes:** Introduces "Match First" mode to assign each finding to only one remediation task, alongside the default "Match All" mode.
* **GitHub Application Vulnerability Integration:** Supports importing generic secrets with configurable ingestion controls and maps secrets to AVITs with appropriate scan types.
* **Tenable Web Application Scanning Integration:** Enables on-demand imports of applications, findings, and scan metadata with full integration run tracking.
* **Coral Theme:** Zurich sets Coral as the default user interface theme for portals, web, and mobile, including a dark mode option.
* **Related List Configuration:** System property to limit maximum rows displayed for better readability and performance.
* **Enhanced State Management:** Refined state roll-down and roll-up logic between remediation tasks and vulnerable items improves accuracy, including handling of mixed states and false positives.

## Activation and Installation

* Application Vulnerability Response is available through the ServiceNow Store as part of Vulnerability Response; Software Bill of Materials requires separate subscription.
* Zurich release customers should request installation of Vulnerability Response and compatible third-party integrations via the ServiceNow Store.
* For change request support, ensure discovered applications are associated with configuration items by disabling the Product Model system property (`snvul.useproductmodel` set to False).

## Changes, Removals, and Deprecations

There are no removals or deprecations reported between Yokohama and Zurich releases for Application Vulnerability Response. Some feature refinements and workflow improvements are introduced to enhance usability and accuracy.

## Additional Notes

* No new browser, accessibility, localization, or additional requirements changes were introduced in Zurich.
* Customers upgrading to USEM should review Unified Security Exposure Management release notes and migration guidance separately.

## Summary of Benefits for ServiceNow Customers

Upgrading to the Zurich release of Application Vulnerability Response enables customers to:

* Streamline vulnerability  
Consolidated page of all release notes for Application Vulnerability Response from Yokohama to Zurich.

## How to use this page

To help you prepare for your upgrade, we have combined the cross-family Application 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 Application Vulnerability Response to Zurich

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

| Release | Release notes |
|-|-|
| Yokohama | Upgrade information : * For information about the new features of Vulnerability Response, see [Vulnerability Response release notes](https://www.servicenow.com/docs/access?context=secops-vuln-resp-rn&family=yokohama&ft:locale=en-US). * For more information about the released versions of the Application Vulnerability Response application as well as the third-party and ServiceNow applications that are compatible with the Xanadu 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. |
| Zurich | Upgrade information : * If you are currently using Application Vulnerability Response, and you do not intend to upgrade to Unified Security Exposure Management (USEM), install a version below v30.x of Application Vulnerability Response and for upgrades to supported third-party integration applications. * For information about the new features of Vulnerability Response, see the [Vulnerability Response release notes](https://www.servicenow.com/docs/access?context=secops-vuln-resp-rn&family=zurich&ft:locale=en-US). * For more information about the released versions of the Application 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 Application Vulnerability Response.  
{#dfrn3-applicationvulnerabilityresponse-summary__entry__8}

| Release | Release notes |
|-|-|
| Yokohama | [Enhancements to Application Vulnerability Response](https://www.servicenow.com/docs/access?context=Unassigning_vis&family=yokohama&ft:locale=en-US) :   The Unassign workflow is supported for application vulnerable items (AVITs) and remediation tasks (AVULs). * Streamline application vulnerability assignments with the Unassign UI action from the more actions menu on an AVIT. * Reassign incorrectly assigned AVITs, 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. [SBOM document upload via Github Action](https://www.servicenow.com/docs/access?context=vr-sbom-supported-apps&family=yokohama&ft:locale=en-US) :   Upload valid Software Bill of Material (SBOM) documents to ServiceNow platform with the help of GitHub Action. [Create application 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.app_sec_manager role, you can create application remediation tasks manually by selecting some or all the records in the Application 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 application remediation tasks. [Create application 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.app_security_champion role, you can create application remediation tasks manually by selecting desired records in the Application 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 application remediation tasks. [Manual Ingestion of vulnerabilities for application vulnerability response](https://www.servicenow.com/docs/access?context=manual-ingestion-of-vulnerabilities-for-application-vulnerability-response&family=yokohama&ft:locale=en-US) :   Import AVITs from external sources via a standardised template (e.g., CSV, Excel) and manage Penetration test findings lifecycle. Now, you can ingest vulnerability data, including details such as affected application, vulnerability description, severity, remediation recommendations, including other necessary details. This enhancement allows you to simplifies the process of consolidating vulnerability data from diverse sources into a centralised Penetration test workspace. [Penetration Test Workspace](https://www.servicenow.com/docs/access?context=penetration-testing-dashboard&family=yokohama&ft:locale=en-US) :   Monitor your penetration test requests and findings as well as your team's overall progress in the Penetration Test Workspace. Prioritize tests that need your attention, track findings, and view assignments with the following data visualizations on the dashboard: * Important items. * Penetration test requests that are critical and by state. * Reported findings. * Overall remediation progress based on assignment. [Enhancements to Penetration Test Assessment Requests](https://www.servicenow.com/docs/access?context=pen_test_dashboard_components&family=yokohama&ft:locale=en-US) :   Along with Full Penetration, Focused, and Re-test, the following assessment types are included for Penetration Test Assessment Requests forms in the Penetration Test Workspace: * Emergency Release - Supports emergency releases that are required for rapid software updates to address critical issues like security vulnerabilities. * Bug Bounty Program - Rewards ethical hackers to find and report security vulnerabilities. * Release Approvals - Ensure that all necessary checks are completed before deploying new software. * One-off reviews - Assess specific projects outside regular development and release cycles to evaluate performance and implement improvements. * Executive Interest - Report on senior management's engagement and support for critical projects within the organization. Enhancements to the Release Approval and Release Notes fields help you ensure quality and security for your pen test findings. The following states have been added to the Release approval field: * Not Applicable (Default). * Approved. * Denied. You can add details to justify your release approvals in the Release notes field. [Associate CWEs for manual AVIT creation from Penetration Test Assessment Requests](https://www.servicenow.com/docs/access?context=penetration-testing-dashboard&family=yokohama&ft:locale=en-US) :   On the Penetration test findings tab on Penetration Test Assessment Requests, you have the option to associate Common Weakness Enumerations (CWE)s or Common Vulnerabilities and Exposures (CVE)s in the Vulnerability field for manually created AVITs. Create change requests in Application Vulnerability Response :   Users with the sn_vul.app_sec_manager and sn_vul.app_sec_champion roles as well as users with the sn_vul.app_developer role who have the ITIL role can create change requests from remediation tasks in the Application Vulnerability Response application. Create change requests to expedite your investigation for application vulnerabilities (AVIT)s that require manual intervention. * Create change requests with prepopulated information for scanned applications that are classified as configuration items (CI)s. * The change request workflow in Application Vulnerability Response is similar to the workflow supported in Vulnerability Response. For more information about the Vulnerability Response change request workflow, see [Change management for Vulnerability Response](https://www.servicenow.com/docs/access?context=vuln-change_mgmnt_ovrvw&family=yokohama&ft:locale=en-US). Note: Change requests are supported for Application Vulnerability Response only if the discovered application is associated with a configuration item (CI). You must set Product model to False in the Use Product Model \[sn_vul.use_product_model\] system property to associate a discovered application with a CI. [Enhancements to the Software Bill of Materials Workspace](https://www.servicenow.com/docs/access?context=sbom-landing&family=yokohama&ft:locale=en-US) : * You can delete multiple BOM entity records and their related components with bulk edit from the Software Bill of Materials SBOM SBOM Workspace. * Any Application Vulnerable Items (AVIT)s that are associated with deleted BOM entities automatically transition to Closed. [View risk score details of a vulnerable items in the Work notes section](https://www.servicenow.com/docs/access?context=avm-calculators-rules&family=yokohama&ft:locale=en-US) :   Starting with v25.0.3 of Application 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 an application vulnerable item in the Work notes section. Additionally, the work notes are updated only if there's a change in the risk score. |
| Zurich | [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. [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. [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. [GitHub Application Vulnerability Integration -- Generic secrets support](https://www.servicenow.com/docs/access?context=github-vuln-integration&family=zurich&ft:locale=en-US) :   The GitHub Secret Scanning Integration now imports generic secrets in addition to standard secrets from your GitHub repositories. A new Manage generic secrets in ServiceNow configuration option lets you control whether generic secrets are ingested. Imported secrets are mapped to Application Vulnerable Items (AVIs) with the scan type Secret, while generic secrets are mapped with the scan type Generic Secret. [Enhancements to Application Vulnerability Response](https://www.servicenow.com/docs/access?context=Unassigning_vis&family=zurich&ft:locale=en-US) :   The Unassign workflow is supported for application vulnerable items (AVITs) and remediation tasks (AVULs). * Streamline application vulnerability assignments with the Unassign UI action from the more actions menu on an AVIT. * Reassign incorrectly assigned AVITs, 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. [SBOM document upload via Github Action](https://www.servicenow.com/docs/access?context=vr-sbom-supported-apps&family=zurich&ft:locale=en-US) :   Upload valid Software Bill of Material (SBOM) documents to ServiceNow platform with the help of GitHub Action. [Create application remediation tasks manually in the Vulnerability Manager Workspace](https://www.servicenow.com/docs/access?context=vmws-create-remediation-task&family=zurich&ft:locale=en-US) :   With the sn_vul.app_sec_manager role, you can create application remediation tasks manually by selecting some or all the records in the Application 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 application remediation tasks. [Create application remediation tasks manually in the IT Remediation Workspace](https://www.servicenow.com/docs/access?context=itr-ws-create-remediation-task&family=zurich&ft:locale=en-US) :   With the sn_vul.app_security_champion role, you can create application remediation tasks manually by selecting desired records in the Application 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 application remediation tasks. [Tenable Web Application Scanning Vulnerability Response Integration](https://www.servicenow.com/docs/access?context=tenable-was-integration&family=zurich&ft:locale=en-US) :   The Tenable.was integration now supports on‑demand execution of both application and vulnerability imports, allowing you to quickly ingest web applications, findings, and scan metadata into ServiceNow. Imported data automatically populates Discovered Applications, Vulnerability Entries, Scan Summaries, and AVITs, with full visibility through integration run tracking. [Manual Ingestion of Vulnerabilities for Application Vulnerability Integration](https://www.servicenow.com/docs/access?context=manual-ingestion-of-vulnerabilities-for-application-vulnerability-response&family=zurich&ft:locale=en-US) :   Import AVITs from external sources via a standardised template (e.g., CSV, Excel) and manage Penetration test findings lifecycle. Now, you can ingest vulnerability data, including details such as affected application, vulnerability description, severity, remediation recommendations, including other necessary details. This enhancement allows you to simplifies the process of consolidating vulnerability data from diverse sources into a centralised Penetration test workspace. [Penetration Test Workspace](https://www.servicenow.com/docs/access?context=penetration-testing-dashboard&family=zurich&ft:locale=en-US) :   Monitor your penetration test requests and findings as well as your team's overall progress in the Penetration Test Workspace. Prioritize tests that need your attention, track findings, and view assignments with the following data visualizations on the dashboard: * Important items. * Penetration test requests that are critical and by state. * Reported findings. * Overall remediation progress based on assignment. [Enhancements to Penetration Test Assessment Requests](https://www.servicenow.com/docs/access?context=pen_test_dashboard_components&family=zurich&ft:locale=en-US) :   Along with Full Penetration, Focused, and Re-test, the following assessment types are included for Penetration Test Assessment Requests forms in the Penetration Test Workspace: * Emergency Release - Supports emergency releases that are required for rapid software updates to address critical issues like security vulnerabilities. * Bug Bounty Program - Rewards ethical hackers to find and report security vulnerabilities. * Release Approvals - Ensure that all necessary checks are completed before deploying new software. * One-off reviews - Assess specific projects outside regular development and release cycles to evaluate performance and implement improvements. * Executive Interest - Report on senior management's engagement and support for critical projects within the organization. Enhancements to the Release Approval and Release Notes fields help you ensure quality and security for your pen test findings. The following states have been added to the Release approval field: * Not Applicable (Default). * Approved. * Denied. You can add details to justify your release approvals in the Release notes field. [Associate CWEs for manual AVIT creation from Penetration Test Assessment Requests](https://www.servicenow.com/docs/access?context=penetration-testing-dashboard&family=zurich&ft:locale=en-US) :   On the Penetration test findings tab on Penetration Test Assessment Requests, you have the option to associate Common Weakness Enumerations (CWE)s or Common Vulnerabilities and Exposures (CVE)s in the Vulnerability field for manually created AVITs. Create change requests in Application Vulnerability Response :   Users with the sn_vul.app_sec_manager and sn_vul.app_sec_champion roles as well as users with the sn_vul.app_developer role who have the ITIL role can create change requests from remediation tasks in the Application Vulnerability Response application. Create change requests to expedite your investigation for application vulnerabilities (AVIT)s that require manual intervention. * Create change requests with prepopulated information for scanned applications that are classified as configuration items (CI)s. * The change request workflow in Application Vulnerability Response is similar to the workflow supported in Vulnerability Response. For more information about the Vulnerability Response change request workflow, see [Change management for Vulnerability Response](https://www.servicenow.com/docs/access?context=vuln-change_mgmnt_ovrvw&family=zurich&ft:locale=en-US). Note: Change requests are supported for Application Vulnerability Response only if the discovered application is associated with a configuration item (CI). You must set Product model to False in the Use Product Model \[sn_vul.use_product_model\] system property to associate a discovered application with a CI. [Enhancements to the Software Bill of Materials Workspace](https://www.servicenow.com/docs/access?context=sbom-landing&family=zurich&ft:locale=en-US) : * You can delete multiple BOM entity records and their related components with bulk edit from the Software Bill of Materials SBOM SBOM Workspace. * Any Application Vulnerable Items (AVIT)s that are associated with deleted BOM entities automatically transition to Closed. [View risk score details of a vulnerable items in the Work notes section](https://www.servicenow.com/docs/access?context=avm-calculators-rules&family=zurich&ft:locale=en-US) :   Starting with v25.0.3 of Application 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 an application vulnerable item in the Work notes section. Additionally, the work notes are updated only if there's a change in the risk score. |
[ ]

## Changes

Between your current release family and Zurich, some changes were made to existing Application Vulnerability Response features.  
{#dfrn3-applicationvulnerabilityresponse-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. [Configure maximum rows in related lists](https://www.servicenow.com/docs/access?context=avm-configuring&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. [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. |
[ ]

## Removed

Between your current release family and Zurich, some Application Vulnerability Response features or functionality were removed.  
{#dfrn3-applicationvulnerabilityresponse-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 Application Vulnerability Response features or functionality were deprecated.  
{#dfrn3-applicationvulnerabilityresponse-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 Application Vulnerability Response.  
{#dfrn3-applicationvulnerabilityresponse-summary__entry__32}

| Release | Release notes |
|-|-|
| Yokohama | Activation information :   Install Application Vulnerability Response by requesting it from the ServiceNow Store. Application Vulnerability Response is included as a part of the Vulnerability Response application. The Software Bill of Materials applications require a separate subscription. 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: Application 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: Application 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 Application Vulnerability Response we have noted them here.  
{#dfrn3-applicationvulnerabilityresponse-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 Application Vulnerability Response we have noted them here.  
{#dfrn3-applicationvulnerabilityresponse-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 Application Vulnerability Response, such as specific requirements or compliance levels.  
{#dfrn3-applicationvulnerabilityresponse-summary__entry__50}

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

## Localization information

If there are specific localization considerations for Application Vulnerability Response we have noted them here.  
{#dfrn3-applicationvulnerabilityresponse-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 Application Vulnerability Response we have noted them here.  
{#dfrn3-applicationvulnerabilityresponse-summary__entry__62}

| Release | Release notes |
|-|-|
| Yokohama | * Monitor your penetration test requests and findings, as well as your team's overall progress in the Penetration Test Workspace. * Reevaluate the risk score, assignments, remediation target date, exceptions, and remediation task for a specific set of application vulnerable items in the Vulnerability Manager Workspace. * Integrate with supported third-party scanners to import vulnerability data. * Compare application vulnerability-related data and determine if application vulnerabilities are found in an application. * Prioritize, remediate, and manage application vulnerable items (AVIT)s. Each application vulnerability represents a vulnerability entry in the Common Weakness Enumeration (CWE) or third-party libraries. * With the sn_vul.app_sec_manager role, create application remediation tasks manually in the Vulnerability Manager Workspace. * With the sn_vul.app_security_champion role, create application remediation tasks manually in the IT Remediation Workspace. See [Application Vulnerability Response](https://www.servicenow.com/docs/access?context=avr-landing&family=yokohama&ft:locale=en-US) for more information. |
| Zurich | * If you are currently using Application 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. * Monitor your penetration test requests and findings, as well as your team's overall progress in the Penetration Test Workspace. * Reevaluate the risk score, assignments, remediation target date, exceptions, and remediation task for a specific set of application vulnerable items in the Vulnerability Manager Workspace. * Integrate with supported third-party scanners to import vulnerability data. * Compare application vulnerability-related data and determine if application vulnerabilities are found in an application. * Prioritize, remediate, and manage application vulnerable items (AVIT)s. Each application vulnerability represents a vulnerability entry in the Common Weakness Enumeration (CWE) or third-party libraries. * With the sn_vul.app_sec_manager role, create application remediation tasks manually in the Vulnerability Manager Workspace. See [Application Vulnerability Response](https://www.servicenow.com/docs/access?context=avr-landing&family=zurich&ft:locale=en-US) for more information. |
[ ]


