--- sourceDocument: yokohama Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/delta-xanadu-yokohama Release : - yokohama ft:locale : - en-US ft:publication_title : - yokohama Combined Product Files ft:clusterId : - delta3yx bundleId : - delta3yx --- # Combined Operational Resilience release notes for upgrades from Xanadu to Yokohama # Combined Operational Resilience release notes for upgrades from Xanadu to Yokohama {#ariaid-title1} Release version: Yokohama Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 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 Operational Resilience Release Notes for Upgrades from Xanadu to Yokohama This consolidated release notes document guides ServiceNow customers through the key updates, new features, changes, and activation details when upgrading Operational Resilience from the Xanadu release family to Yokohama. It provides essential information to help prepare for the upgrade, highlighting improvements in reporting, digital resilience compliance, and integration with the Common Service Data Model (CSDM). Show full answer Show less ## New Features * **Managing Operational Vulnerabilities:** Introduced in Xanadu, users can report, assess, and manage operational vulnerabilities via the Operational Resilience Workspace and Employee Center. * **Maintaining Digital Resilience Third-Party Registers:** Supports compliance with the Digital Operational Resilience Act (DORA) by managing contractual arrangements and ICT service provider records. Includes bulk import/export in Microsoft Excel to facilitate EU auditing requirements. * **Yokohama Enhancements:** * Integration with the CSDM model to define entity types and pillars, generate entities, and establish relationships among CSDM objects such as business services and application services. * Configurable main node settings allow importing CMDB data for resilience metrics reporting, with weekly updates for CSDM dependencies and daily red flag calculations. * Ability to specify the **primary origin** of operational vulnerabilities, automatically including upstream dependencies to view impacts comprehensively. * Digital resilience incident reporting module integrated with Incident Management and Security Incident Response enables classification, regulator notification, and automated report generation within regulatory timeframes. ## Changes * Operational vulnerability related lists were added to multiple assessment and self-attestation modules. * New Operational Resilience Workspace modules for **Services, Business Services, Service Offerings, Business Processes, Entity Types, and Pillars** to centrally manage these elements for reporting and resilience tracking. * The **Primary Origin tab** was introduced in operational vulnerability records for identifying main sources and reporting upstream impacted entities. * Expanded assessment, scenario analysis, and self-attestation forms now include Business Service and Offering classes for more comprehensive risk evaluation. * The Digital resilience incident reporting module enhances ICT-related incident reporting to regulators. ## Activation and Requirements * Operational Resilience continues to be available via the **ServiceNow Store**. Customers should request installation through the store and refer to the ServiceNow Store version history for cumulative release details. * **Browser Support:** Business Continuity Management within Operational Resilience supports Google Chrome, Firefox (including ESR), Microsoft Edge Chromium, and Safari 12.0 or later. * **Accessibility:** Xanadu introduced improved screen reader and translation support with ARIA labels and tooltips; no further updates in Yokohama. ## Key Outcomes * **Enhanced Compliance:** Streamlined management of third-party ICT service providers aligned with DORA regulatory requirements, facilitating audits and regulator reporting. * **Improved Visibility:** Leveraging the CSDM model and primary origin tagging provides a holistic view of operational vulnerabilities and their impact across business services and applications. * **Automated Incident Reporting:** Integration with core incident management processes enables timely and automated reporting of major incidents to regulators, meeting strict deadlines. * **Centralized Management:** New modules in Operational Resilience Workspace empower managers to efficiently maintain services, processes, and entity configurations supporting operational risk and resilience assessments. Consolidated page of all release notes for Operational Resilience from Xanadu to Yokohama. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Operational Resilience release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Xanadu to Yokohama. 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 Operational Resilience to Yokohama Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-operationalresilience-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## New features Between your current release family and Yokohama, new features were introduced for Operational Resilience. {#dfrn3-operationalresilience-summary__entry__8} | Release | Release notes | |-|-| | Xanadu | [Managing Operational vulnerability](https://www.servicenow.com/docs/access?context=operational-vulnerability&family=xanadu&ft:locale=en-US) : Address operational vulnerabilities through reporting, assessing impact, evaluating criticality, managing issues, and planning treatments in Operational Resilience Workspace. Report operational vulnerabilities by using either Employee Center or Operational Resilience Workspace. [Maintaining Digital resilience third-party registers](https://www.servicenow.com/docs/access?context=digi-resi-third-party-registers&family=xanadu&ft:locale=en-US) : Comply with Digital Operational Resilience Act (DORA) regulation requirements by creating contractual arrangements between the financial entities and the ICT service providers in Digital resilience third-party registers. The ICT third-party service provider records are maintained in Digital resilience third-party registers for DORA compliance. Add or modify the records in bulk or individually for assessments, branches, contracts, functions, legal entities, supply chains, third parties, or third-party engagements. Export the records to Microsoft Excel format for the European Union to streamline the auditing process as per the regulation. You have the option to import the records from external sources into the Digital resilience third-party registers application. | | Yokohama | [Measure resilience metrics using the CSDM model](https://www.servicenow.com/docs/access?context=using-csdm-v5&family=yokohama&ft:locale=en-US) : Define the entity types and pillars in Operational Resilience and generate the entities. Establish relationships between CSDM objects, including business services, service offerings, business processes, and application services. Specify the type of main node configuration that you want to use by setting the sn_oper_res.opres_csdm_main_node_config property. After generating the entities and setting up the main node configurations, you can import CMDB data into Operational Resilience for reporting. CSDM and their dependencies are updated weekly while the red flags data is calculated daily. The outcome is displayed on the Homepage or in the related list of the CSDM objects. [Specify the primary origin of an operational vulnerability](https://www.servicenow.com/docs/access?context=add-impacted-area-to-vul&family=yokohama&ft:locale=en-US) : Identify the primary origin of an operational vulnerability in its record. Once the primary origin is specified, its upstream dependencies are automatically included in the impacted areas, enabling you to view the operational vulnerability from all affected perspectives. [Using Digital resilience incident reporting](https://www.servicenow.com/docs/access?context=drir-module&family=yokohama&ft:locale=en-US) : Assess whether any critical services are affected and classify the reported incident as a major incident if necessary. Notify regulators of major incidents, categorized by their severity and security ratings. The Digital resilience incident reporting module, accessible from the Operational Resilience Workspace, is integrated with Incident Management and Security Incident Response to generate and share reports in the format that is specified by the regulators. You can generate an initial report within 24 hours, an intermediate report within 72 hours, and a final report within 1 month. All of these reports are automatically triggered by the application from the time that the incident is classified as a major incident. | [ ] ## Changes Between your current release family and Yokohama, some changes were made to existing Operational Resilience features. {#dfrn3-operationalresilience-summary__entry__14} | Release | Release notes | |-|-| | Xanadu | [Reporting Operational vulnerability](https://www.servicenow.com/docs/access?context=reporting-operational-vul&family=xanadu&ft:locale=en-US) : The Operational vulnerability related list has been added to the following modules in the List view: * Importance and impact tolerance assessment * Scenario analyses * Self attestations * Services | | Yokohama | [Business services dashboard](https://www.servicenow.com/docs/access?context=opres-ws-homepage-overview&family=yokohama&ft:locale=en-US) : The Business services dashboard has been added to display business services data. [New modules for services and processes](https://www.servicenow.com/docs/access?context=using-csdm-v5&family=yokohama&ft:locale=en-US) : The Services, Business Services, Service Offerings, and Business Processes modules have been added to the Operational Resilience Workspace. Operational Resilience managers use these modules to manage the services, business services, service offerings, and business processes used in Operational Resilience reporting. [Entity Types and Pillars modules](https://www.servicenow.com/docs/access?context=manage-entity-types-pillars-from-ws&family=yokohama&ft:locale=en-US) : The Entity Types and Pillars modules have been added to the Operational Resilience Workspace. These modules enable Operational Resilience managers to update the entity types and pillars directly from the Workspace. [Primary origin tab](https://www.servicenow.com/docs/access?context=add-impacted-area-to-vul&family=yokohama&ft:locale=en-US) : The Primary origin tab has been added to the Operational vulnerability record to identify the main source and report the upstream entities of the vulnerability. [Addition of classes to the assessment form](https://www.servicenow.com/docs/access?context=submit-an-assessment-in-ws&family=yokohama&ft:locale=en-US) : The Business Service and Offering classes have been added to the Scope tab of the assessment form, enabling you to assess the business services and service offerings alongside services. Once the assessment is complete, the importance and impact tolerance of these items are displayed in the Importance and Impact Tolerance columns on the Scope tab. [Addition of classes to the scenario analysis form](https://www.servicenow.com/docs/access?context=scenario-analysis-in-ws&family=yokohama&ft:locale=en-US) : The Business Service and Offering classes have been added to the Scope tab of the scenario analysis form, enabling you to analyze the business services and service offerings alongside services. [Addition of classes to the self-attestation form](https://www.servicenow.com/docs/access?context=self-attestation-in-ws&family=yokohama&ft:locale=en-US) : The Business Service and Offering classes have been added to the Scope tab of the self-attestation form, enabling you to self-attest the business services and service offerings alongside services. [Digital resilience incident reporting module](https://www.servicenow.com/docs/access?context=drir-module&family=yokohama&ft:locale=en-US) : The Digital resilience incident reporting module is used to report the Information and Communication Technology (ICT) related incidents to the regulators. | [ ] ## Removed Between your current release family and Yokohama, some Operational Resilience features or functionality were removed. {#dfrn3-operationalresilience-summary__entry__20} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Deprecations Between your current release family and Yokohama, some Operational Resilience features or functionality were deprecated. {#dfrn3-operationalresilience-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Activation information Review information on how to activate Operational Resilience. {#dfrn3-operationalresilience-summary__entry__32} | Release | Release notes | |-|-| | Xanadu | Install Operational Resilience 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=xanadu&ft:locale=en-US). | | Yokohama | Activation information : Install Operational Resilience 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: Operational Resilience 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 Operational Resilience we have noted them here. {#dfrn3-operationalresilience-summary__entry__38} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for Operational Resilience we have noted them here. {#dfrn3-operationalresilience-summary__entry__44} | Release | Release notes | |-|-| | Xanadu | Business Continuity Management requires the following browsers: * Google Chrome * Firefox and Firefox Extended Support Release (ESR) * Microsoft Edge Chromium * Safari 12.0 and later versions | | Yokohama | Browser requirements : Business Continuity Management requires the following browsers: * Google Chrome * Firefox and Firefox Extended Support Release (ESR) * Microsoft Edge Chromium * Safari 12.0 and later versions | [ ] ## Accessibility information Review details on accessibility information for Operational Resilience, such as specific requirements or compliance levels. {#dfrn3-operationalresilience-summary__entry__50} | Release | Release notes | |-|-| | Xanadu | Improved screen reader and translation support by adding ARIA button labels, tooltips, and alt text to the Operational Resilience Workspace. This support provides an explanation for button actions and identifies tooltip text to be translated. | | Yokohama | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for Operational Resilience we have noted them here. {#dfrn3-operationalresilience-summary__entry__56} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for Operational Resilience we have noted them here. {#dfrn3-operationalresilience-summary__entry__62} | Release | Release notes | |-|-| | Xanadu | * Monitor business service resiliency from start to finish, with a focus on operational risk and compliance. * Identify and report operational vulnerabilities from Employee Center or Operational Resilience Workspace. Address these vulnerabilities through procedures such as reporting, assessing impact, evaluating criticality, managing issues, and planning treatments. * Use the Digital resilience third-party registers application to establish, update, and manage contractual arrangements between the financial entities and Information and Communication Technology (ICT) service providers. * Export the records for regulators and auditors in Microsoft Excel format by using the Microsoft Excel upload capability in Digital resilience third-party registers. Similarly, you can import the records from external sources by using the Microsoft Excel download functionality. See [Managing Operational vulnerability](https://www.servicenow.com/docs/access?context=operational-vulnerability&family=xanadu&ft:locale=en-US) and [Maintaining Digital resilience third-party registers](https://www.servicenow.com/docs/access?context=digi-resi-third-party-registers&family=xanadu&ft:locale=en-US) for more information. | | Yokohama | * Align with the CSDM model to set up configurable main node configurations, which are used to retrieve CSDM and their dependency data. * Add the primary origin to an operational vulnerability, and the impacted areas are automatically included. The vulnerability can then be viewed from any impacted area. * All CSDM objects, dependencies, and their red flags can be rolled up based on the entity hierarchy. * Use Smart Assessment for evaluating an Operational vulnerability. See [Operational Resilience](https://www.servicenow.com/docs/access?context=grc-opres-landing-page&family=yokohama&ft:locale=en-US) for more information. | [ ]