---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Prepare your instance for GlideEncrypter deprecation

# Prepare your instance for GlideEncrypter deprecation {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

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.

## Vorbereitungen

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.

## Prozedur

1. Navigate to AllInstance ScanSuites.
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.  
   Hinweis:  
   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.  
6. In the Scan Result record, select the Count field on the Scan Findings list to navigate to a record.  
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).  
   Hinweis:  
   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.

## Nächste Maßnahme

[Deprecate GlideEncrypter usage of 3DES for password2 fields](https://servicenow-prod.fluidtopics.net/Ye7VdUVLltRotNW6Q6Up2g "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.")
* **[GlideEncrypter deprecation](https://servicenow-prod.fluidtopics.net/X52bL~BeokXtitH9AYd6rw)**   
  Learn how to remove the use legacy GlideEncrypter calls from the scripts on your instance.
* **[Deprecate GlideEncrypter usage of 3DES for password2 fields](https://servicenow-prod.fluidtopics.net/Ye7VdUVLltRotNW6Q6Up2g)**   
  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.