--- 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 Encryption Key Management release notes for upgrades from Yokohama to Zurich # Combined Encryption Key Management 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) 5 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 Encryption Key Management Release Notes for Upgrades from Yokohama to Zurich This consolidated guide assists ServiceNow customers in preparing for and understanding the Encryption Key Management changes and enhancements when upgrading from Yokohama to Zurich. It covers important upgrade considerations, new features, key changes, activation details, and deprecations related to encryption key management throughout this upgrade path. Show full answer Show less ## Important Upgrade Information * **3DES Deprecation:** Both Yokohama and Zurich releases address the deprecation of the GlideEncrypter API's three-key Triple Data Encryption Standard (3DES), which NIST recommends against using post-2023. * Yokohama: New instances no longer use GlideEncrypter with 3DES; existing instances can disable 3DES via system property. * Zurich: New instances cannot use GlideEncrypter with 3DES; upgraded instances use GlideEncrypter updated to AES256-GCM through the Key Management Framework. Disabling GlideEncrypter is controlled by the `glide.security.glideencrypter.allow` system property, editable only on upgraded instances. ## New Features * **Field Encryption Rebranding:** Column Level Encryption has been renamed and redesigned as Field Encryption Starter (FES) and Field Encryption Enterprise (FEE). * **Access Observer:** A new tool to monitor and understand who accesses data, aiding in planning and troubleshooting Field Encryption implementations. * **Improved Migration Process:** Enhanced workflow to migrate data from Edge Encryption to Field Encryption without leaving data unencrypted during transition. * **Audit Logging (Zurich):** Changes to Field Encryption and Key Management configuration records are now logged in the Sys Audits \[sysaudit\] table, improving traceability. ## Changes * **Coral Theme (Zurich):** New default branding theme for portals and mobile experiences, including a dark mode option. * **GlideEncrypter Updates (Zurich):** GlideEncrypter now uses AES256-GCM encryption. Legacy 3DES usage requires ServiceNow support to enable and can be disabled via system property. ## Deprecations and Removals There are no new deprecations or removals specific to Encryption Key Management in either Yokohama or Zurich beyond the planned 3DES deprecation. ## Activation Information * The Platform Encryption subscription bundle remains consistent from Yokohama to Zurich, including Field Encryption Enterprise and Cloud Encryption. * Activation requires enabling the `com.glide.now.platform.encryption` plugin. ## Additional Notes * No changes were reported for browser requirements, accessibility, localization, or additional requirements related to Encryption Key Management between Yokohama and Zurich. ## Practical Takeaways for ServiceNow Customers * Plan upgrades with attention to the 3DES deprecation and consider disabling legacy encryption to align with NIST standards. * Leverage Access Observer for better visibility into data access patterns and security compliance. * Use the improved migration process to transition securely from Edge Encryption to Field Encryption without data exposure risks. * Monitor encryption and key management configuration changes via audit logs for enhanced governance. * Be aware of UI updates like the Coral theme that may impact user experience post-upgrade. Consolidated page of all release notes for Encryption Key Management from Yokohama to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Encryption Key Management 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 Encryption Key Management to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-encryptionkeymanagement-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | Upgrade information : * The GlideEncrypter API uses the three-key Triple Data Encryption Standard (3DES) encryption standard which [NIST 800-131A Rev 2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar2.pdf) has recommended against using after 2023. The following changes are taking place in the Yokohama release in preparation for a full deprecation of GlideEncrypter/3DES in the future. * New Yokohama instances can't use GlideEncrypter. All base system scripts have been changed to use alternative encryption processes. * if you're upgrading your Yokohama instances, you can still use 3DES, but you can also disable 3DES usage with a system property. * Learn more about 3DES deprecation in [KB1704481](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704481). | | Zurich | Upgrade information : * In previous releases, the GlideEncrypter API used the three-key Triple Data Encryption Standard (3DES) encryption standard, which [NIST 800-131A Rev 2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-131Ar2.pdf) has recommended against using after 2023. The following changes are taking place in the Zurich release in preparation for a full deprecation of GlideEncrypter/3DES in the future: * New Zurich instances can't use GlideEncrypter. All base system scripts have been changed to use alternative encryption processes. * if you're upgrading your Zurich instances, you can still GlideEncrypter, which has been updated to use AES256-GCM encryption via the Key Management Framework. * Learn more about 3DES deprecation in [KB1704481](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704481). | [ ] ## New features Between your current release family and Zurich, new features were introduced for Encryption Key Management. {#dfrn3-encryptionkeymanagement-summary__entry__8} | Release | Release notes | |-|-| | Yokohama | [Column Level Encryption is now Field Encryption](https://www.servicenow.com/docs/access?context=column-level-encryption-landing&family=yokohama&ft:locale=en-US) : Column Level Encryption has been rebranded to Field Encryption Starter (FES), while Column Level Encryption Enterprise is now Field Encryption Enterprise (FEE). [Access observer](https://www.servicenow.com/docs/access?context=access-observer&family=yokohama&ft:locale=en-US) : Use access observer to understand the people and processes that access data on your instance. [Improved migration process from Edge Encryption to Field Encryption](https://www.servicenow.com/docs/access?context=column-level-encryption-landing&family=yokohama&ft:locale=en-US) : Use the new process for migration from Edge Encryption to Field Encryption (formerly Column Level Encryption). This improved workflow ensures that your data migrates from Edge Encryption to Field encryption without spending time in an unencrypted state. | | Zurich | [Keep track of Field Encryption and Key Management changes](https://www.servicenow.com/docs/access?context=c_UnderstandingTheSysAuditTable&family=zurich&ft:locale=en-US) : By default, the changes to the records on these tables are now logged to the Sys Audits \[sys_audit\] table: * Encrypted Field Configurations \[sys_platform_encryption_configuration\] * Module Access Policies \[sys_kmf_crypto_caller_policy\] * Cryptographic Modules \[sys_kmf_crypto_module\] For details on accessing the Sys Audits \[sys_audit\] table, see [Review](https://www.servicenow.com/docs/access?context=c_UnderstandingTheSysAuditTable&family=zurich&ft:locale=en-US). | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing Encryption Key Management features. {#dfrn3-encryptionkeymanagement-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. [Updates to GlideEncrypter functionality](https://www.servicenow.com/docs/access?context=glideencrypter-deprecation&family=zurich&ft:locale=en-US) : The GlideEncrypter API has been updated to use AES256-GCM encryption via the Key Management Framework. If needed, your instance can be changed to use legacy 3DES encryption, but this task can only be done by ServiceNow support. [Disable GlideEncrypter on your instance](https://www.servicenow.com/docs/access?context=check-3des&family=zurich&ft:locale=en-US) : GlideEncrypter can be enabled or turned off using the glide.security.glideencrypter.allow system property. This property is unavailable on new Zurich instances, but administrators with the security_admin role can edit this property in upgraded instances. When this system property is set to false, users see this error when attempting to run GlideEncrypter. Unsupported call to GlideEncrypter. Details: GlideEncrypter is deprecated and now returns null, please refer KB1320986 | [ ] ## Removed Between your current release family and Zurich, some Encryption Key Management features or functionality were removed. {#dfrn3-encryptionkeymanagement-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 Encryption Key Management features or functionality were deprecated. {#dfrn3-encryptionkeymanagement-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 Encryption Key Management. {#dfrn3-encryptionkeymanagement-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | Activation information : The Platform Encryption subscription bundle is a group commercial entitlement that includes Field Encryption Enterprise and Cloud Encryption. Field Encryption Enterprise is the unlimited license of Field Encryption. The Enterprise plugin is available with the activation of the com.glide.now.platform.encryption plugin. For details, see [Encryption and Key Management subscription bundle](https://www.servicenow.com/docs/access?context=encryption-sku&family=yokohama&ft:locale=en-US). | | Zurich | Activation information : The Platform Encryption subscription bundle is a group commercial entitlement that includes Field Encryption Enterprise and Cloud Encryption. Field Encryption Enterprise is the unlimited license of Field Encryption. The Enterprise plugin is available with the activation of the com.glide.now.platform.encryption plugin. For details, see [Encryption and Key Management subscription bundle](https://www.servicenow.com/docs/access?context=encryption-sku&family=zurich&ft:locale=en-US). | [ ] ## Additional requirements If any additional requirements were introduced or changed for Encryption Key Management we have noted them here. {#dfrn3-encryptionkeymanagement-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 Encryption Key Management we have noted them here. {#dfrn3-encryptionkeymanagement-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 Encryption Key Management, such as specific requirements or compliance levels. {#dfrn3-encryptionkeymanagement-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 Encryption Key Management we have noted them here. {#dfrn3-encryptionkeymanagement-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 Encryption Key Management we have noted them here. {#dfrn3-encryptionkeymanagement-summary__entry__62} | Release | Release notes | |-|-| | Yokohama | * Column Level Encryption has been rebranded and redesigned to now be called Field Encryption. * Use Access Observer to help plan for and troubleshoot Field Encryption implementations. * Edge Encryption administrators can use the new process to migrate from Edge Encryption to Field Encryption. See [Key Management Framework](https://www.servicenow.com/docs/access?context=encryption&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * See the changes to the Key Management and Field Encryption records that are now logged on the Sys Audits \[sys_audit\] table. * The GlideEncrypter API has been updated and now uses AES256-GCM encryption via the Key Management Framework. * Enable or disable GlideEncrypter by using the glide.security.glideencrypter.allow system property. See [Key Management Framework](https://www.servicenow.com/docs/access?context=encryption&family=zurich&ft:locale=en-US) for more information. | [ ]