--- 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 release notes for upgrades from Yokohama to Zurich # Combined Encryption 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) 3 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 release notes for upgrades from Yokohama to Zurich This consolidated release note page provides essential information for ServiceNow customers upgrading their Encryption features from the Yokohama release to Zurich. It highlights new features, changes, deprecations, and activation details relevant to Encryption in the Zurich release, helping you prepare for and manage the upgrade effectively. Show full answer Show less ## Important upgrade information * **3DES Deprecation:** The GlideEncrypter API no longer supports Triple Data Encryption Standard (3DES), following NIST 800-131A Rev 2 recommendations. Zurich removes 3DES encryption for GlideEncrypter, defaulting to the Advanced Encryption Standard (AES) via the Key Management Framework (KMF) for upgraded instances only. Instances created with Zurich or later do not support GlideEncrypter. * **Column Level Encryption Upgrade:** Column Level Encryption is upgraded to use Key Management Framework Column Level Encryption (KMF-CLE) due to platform-wide 3DES deprecation. * **Encrypted string keys in 3DES format:** No longer supported; KMF is now the required format. ## New features * **Row Conditions for Field Encryption:** Define encryption rules dynamically within specific columns by using row conditions. This enables more granular and context-sensitive encryption. ## Changes to existing features * **Field Encryption Enterprise API:** All three Encryption APIs now support encrypting attachments without restricting to any single API, offering greater flexibility. ## Deprecations and removals * **GlideEncrypter 3DES support:** Deprecated and removed in Zurich, requiring preparation for migration to KMF-based encryption. * No other Encryption features or functionality were removed between Yokohama and Zurich. ## Activation and licensing * The Platform Encryption subscription bundle includes Field Encryption Enterprise and Cloud Encryption. * Field Encryption Enterprise offers unlimited Field Encryption licenses. * Activation requires enabling the `com.glide.now.platform.encryption` plugin. ## Additional notes * No changes in browser requirements, accessibility, localization, or additional requirements for Encryption were introduced between Yokohama and Zurich. * For detailed guidance, refer to related knowledge base articles on 3DES deprecation and the KMF-CLE upgrade. This upgrade ensures enhanced security compliance by adopting AES encryption standards and improves encryption flexibility through row conditions and API enhancements. ServiceNow customers should review these changes carefully to prepare their instances for the Zurich release. Consolidated page of all release notes for Encryption from Yokohama to Zurich. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family Encryption 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 to Zurich Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-encryption-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | Upgrade information : For the GlideEncrypter API, NIST 800-131A Rev 2 has recommended against using the Triple Data Encryption Standard (3DES) encryption. The following changes are taking place in the Zurich release with the official removal of 3DES encryption for GlideEncrypter. * The GlideEncrypter API defaults to using the Key Management Framework (KMF) based algorithm, Advanced Encryption Standard (AES), for encryption and decryption operations for upgraded instances only. * For instances created with the Zurich release or later, this API isn't supported. * Learn more about 3DES deprecation in [KB1704481](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1704481). In the Zurich release, Column Level Encryption has received a required upgrade to Key Management Framework Column Level Encryption (KMF-CLE) due to the platform-wide deprecation of 3DES. For more information about this upgrade, see KB1700704. | [ ] ## New features Between your current release family and Zurich, new features were introduced for Encryption. {#dfrn3-encryption-summary__entry__8} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | [Encrypt data using Row Conditions](https://www.servicenow.com/docs/access?context=encrypt-data-using-row-conditions&family=zurich&ft:locale=en-US) : Use row conditions for Field Encryption to define encryption rules for rows within a specific column, based on dynamic conditions. | [ ] ## Changes Between your current release family and Zurich, some changes were made to existing Encryption features. {#dfrn3-encryption-summary__entry__14} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | [Field Encryption Enterprise](https://www.servicenow.com/docs/access?context=now-platform-encryption&family=zurich&ft:locale=en-US) API : Use all three Encryption APIs to encrypt on attachments, without needing to use any one specific API. | [ ] ## Removed Between your current release family and Zurich, some Encryption features or functionality were removed. {#dfrn3-encryption-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 features or functionality were deprecated. {#dfrn3-encryption-summary__entry__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | [Prepare your instance for GlideEncrypter deprecation](https://www.servicenow.com/docs/access?context=check-3des&family=zurich&ft:locale=en-US) : Encrypted string keys 3DES format is no longer supported. Key Management Framework (KMF) is the supported format. | [ ] ## Activation information Review information on how to activate Encryption. {#dfrn3-encryption-summary__entry__32} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | 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 the [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 we have noted them here. {#dfrn3-encryption-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 we have noted them here. {#dfrn3-encryption-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, such as specific requirements or compliance levels. {#dfrn3-encryption-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 we have noted them here. {#dfrn3-encryption-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 we have noted them here. {#dfrn3-encryption-summary__entry__62} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | * Use row conditions for Field Encryption to define encryption rules for rows within a specific column, based on dynamic conditions. * Use any of the three Field Encryption APIs to encrypt attachments. See [Encryption](https://www.servicenow.com/docs/access?context=encryption-landing&family=zurich&ft:locale=en-US) for more information. | [ ]