--- title: Prepare your instance for GlideEncrypter deprecation description: Use an instance scan script to find and remove GlideEncrypter API calls on your instance. Removing these calls is a necessary step in deprecating 3DES encryption on your instance. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/platform-encryption/check-3des.html release: australia product: Platform Encryption classification: platform-encryption topic_type: task last_updated: "2026-03-12" reading_time_minutes: 1 breadcrumb: [Key Management Framework, Encryption] --- # Prepare your instance for GlideEncrypter deprecation Use an instance scan script to find and remove GlideEncrypter API calls on your instance. Removing these calls is a necessary step in deprecating 3DES encryption on your instance. ## Before you begin Role required: admin The GlideEncrypter API is planned for deprecation as of the Zurich release of ServiceNow. Removing GlideEncrypter calls from your script is also a necessary step before deprecating 3DES encryption on your instance. ## Procedure 1. Navigate to **All** > **Instance Scan** > **Suites**. 2. In the **Suites** list, select **GlideEncrypter** to identify the records with GlideEncrypter usages. 3. In the **Suites** record, select **Execute Suite Scan**. 4. In the **Scan Suites Now** window, select **Full Instance**, then select **Execute Scan**. The suite scan executes. During the scan execution a **Execute Test Scan**, a window displays the progress of the scan.\[Omitted image "scan-progress.png"\] Alt text: Scan progress window **Note:** This scan checks only records that have been created or modified by the customer. 5. When the scan is complete, select **Go to Result** to view the **Scan Result** record. \[Omitted image "scan-progress-2.png"\] Alt text: Completed scan with one finding 6. In the **Scan Result** record, select the **Count** field on the **Scan Findings** list to navigate to a record. \[Omitted image "scan-progress-3.png"\] Alt text: Completed scan 7. Modify any scripts in the record that uses the **GlideEncrypter** API. For details on alternatives to **GlideEncrypter**, see [Alternatives to deprecated GlideEncrypter APIs](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1320986). **Note:** You do not need to modify base system \(out-of-box\) records if you have not made any changes to them. These records are handled by ServiceNow. 8. After removing **GlideEncrypter** calls from your scripts, run the scan again to ensure that there are no remaining calls to the API. ## What to do next [Deprecate GlideEncrypter usage of 3DES for password2 fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/platform-encryption/password2-3des-deprecation.md) - **[GlideEncrypter deprecation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/platform-encryption/glideencrypter-deprecation.md)** Learn how to remove the use legacy GlideEncrypter calls from the scripts on your instance. - **[Deprecate GlideEncrypter usage of 3DES for password2 fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/platform-encryption/password2-3des-deprecation.md)** Deprecate GlideEncrypter usage of 3DES encryption standard on your instance ensure that your instance uses the more secure Advanced Encryption Standard \(AES\) exclusively for the encryption and decryption of your Password2 data. **Parent Topic:**[Key Management Framework](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/encryption.md)