Combined Operational Resilience release notes for upgrades from Vancouver 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 Vancouver 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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	Roles installed with Operational Resilience To track end-to-end business service resiliency from the continuity of operations perspective, use the new set of roles created for the Business Continuity Management (BCM) Professional users. To track end-to-end business service resiliency from the continuity of operations perspective, use the new set of roles created for the Integrated Risk Management (IRM) Professional users. [Placeholder link text to key bundle-grc.grc-operational-resilience-dashboard] Display reports according to the persona with different roles. Separate reports are displayed for the BCM Professional and IRM Professional users in the Operational Resilience application Home page. Fetching dependencies from the CMDB and BIA Auto-populate the dependency mappings for the business services based on the source-data relationships in the CMDB and BIA.
Xanadu	Managing Operational vulnerability 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 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 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 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 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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	Reporting Operational vulnerability 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	No updates for this release.

Removed

Between your current release family and Yokohama, some Operational Resilience features or functionality were removed.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Activation information

Review information on how to activate Operational Resilience.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	Install Operational Resilience by requesting it from the ServiceNow Store. Visit the ServiceNow Store 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.
Xanadu	Install Operational Resilience by requesting it from the ServiceNow Store. Visit the ServiceNow Store 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.
Yokohama	Install Operational Resilience by requesting it from the ServiceNow Store. Visit the ServiceNow Store 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.

Additional requirements

If any additional requirements were introduced or changed for Operational Resilience we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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	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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
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.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	Track end-to-end business service resiliency from the continuity of operations perspective. Track end-to-end business service resiliency from the operational risk and compliance perspective. Display reports according to the persona in the Operational Resilience application Home page. Auto-populate the dependency mappings for the business services based on the source-data relationships in the Configuration Management Database (CMDB). Auto-populate the dependency mappings for the business services based on the source-data relationships in the business impact assessment (BIA). See Operational Resilience for more information.
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 and Maintaining Digital resilience third-party registers 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 for more information.