--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ay bundleId : - delta3ay --- # Combined Encryption Key Management release notes for upgrades from Yokohama to Australia # Combined Encryption Key Management release notes for upgrades from Yokohama to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Australia This document consolidates the release notes for Encryption Key Management from the Yokohama through Australia ServiceNow releases, providing essential information to help customers prepare for and execute upgrades smoothly. It covers important upgrade considerations, feature updates, changes, removals, deprecations, activation details, and other relevant information across these releases. Show full answer Show less ## Important Upgrade Information * **Yokohama Release:** The GlideEncrypter API used the three-key Triple Data Encryption Standard (3DES), which NIST 800-131A Rev 2 recommends against using after 2023. Yokohama introduced restrictions where new instances cannot use GlideEncrypter with 3DES, and base system scripts were updated to alternative encryption. For existing Yokohama instances, 3DES can still be used but can be disabled via a system property. * **Zurich Release:** Enhanced GlideEncrypter to use AES256-GCM encryption through the Key Management Framework. New Zurich instances cannot use 3DES-based GlideEncrypter. Upgrading Zurich instances retain GlideEncrypter functionality with AES256-GCM. The glide.security.glideencrypter.allow system property controls GlideEncrypter usage. * **Australia Release:** No changes or updates to Encryption Key Management were introduced in this release. ## Feature Updates and Changes * No new features, changes, removals, or deprecations were introduced in Yokohama, Zurich, or Australia releases besides those related to GlideEncrypter and 3DES deprecation. * **Yokohama Highlight:** Column Level Encryption was rebranded and redesigned as Field Encryption. Tools such as Access Observer assist in planning and troubleshooting Field Encryption implementations. A migration process from Edge Encryption to Field Encryption is available. * **Zurich Highlight:** Audit logging enhancements for Key Management and Field Encryption records now use the Sys Audits table. ## Activation Information * Encryption Key Management is included in the Platform Encryption subscription bundle, which comprises Field Encryption Enterprise (the unlimited license version) and Cloud Encryption. * The Enterprise plugin is activated via the `com.glide.now.platform.encryption` plugin. * This applies consistently across Yokohama and Zurich releases; no updates were made in Australia. ## Additional Considerations * No updates or changes were noted regarding additional system requirements, browser compatibility, accessibility, or localization for Encryption Key Management across the releases. ## What This Means for ServiceNow Customers Customers upgrading from Yokohama through Australia should be aware of the planned deprecation of 3DES encryption and the transition to AES256-GCM for better security compliance. It is important to review system properties controlling GlideEncrypter usage and plan migrations accordingly. Field Encryption replaces Column Level Encryption with enhanced tools to support implementation and troubleshooting. Activation and licensing remain consistent, but customers should verify entitlement to the Platform Encryption bundle to ensure access to full Encryption Key Management capabilities. Consolidated page of all release notes for Encryption Key Management from Yokohama to Australia. ## 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 Australia. 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 Australia Before you upgrade to Australia, 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). | | Australia | No updates for this release. | [ ] ## New features Between your current release family and Australia, new features were introduced for Encryption Key Management. {#dfrn3-encryptionkeymanagement-summary__entry__10} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing Encryption Key Management features. {#dfrn3-encryptionkeymanagement-summary__entry__18} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Removed Between your current release family and Australia, some Encryption Key Management features or functionality were removed. {#dfrn3-encryptionkeymanagement-summary__entry__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some Encryption Key Management features or functionality were deprecated. {#dfrn3-encryptionkeymanagement-summary__entry__34} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate Encryption Key Management. {#dfrn3-encryptionkeymanagement-summary__entry__42} | 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). | | Australia | No updates for this release. | [ ] ## Additional requirements If any additional requirements were introduced or changed for Encryption Key Management we have noted them here. {#dfrn3-encryptionkeymanagement-summary__entry__50} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__58} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__66} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__74} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | 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__82} | 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. | | Australia | No updates for this release. | [ ]