Deprecated Glideencrypter API Scanning Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2025 01:52 AM
Hello everyone,
I hope you are doing well.
I’m currently facing an issue related to the Security Centre in our instance. In Security Centre, we have a customer action for “End of Support: Glide encrypted API.” Since the Glide encrypted API is deprecated, we are required to remove all usages of it from our scripts.
I have updated the script accordingly in workflow and removed all references to the Glide Encrypted API. However, after running the Suite Scan again, the results still show the same findings as before, as if the changes were not detected.
I have attached a article for your reference KB1320986 .
Has anyone experienced this issue before, or could you please provide guidance on what else I should check or do to ensure the Suite Scan recognizes the updates?
Any suggestions or insights would be greatly appreciated.
Thank you in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I have the same issue.
KR Mario
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
You’re not alone my freind—this happens fairly often with ServiceNow Suite Scan.
Even when the code is fixed, Suite Scan can lag behind because results are cached and pattern-based. Double-check that the workflow was republished, there are no other hidden references (script includes, older activities, inactive versions), and give the platform time to refresh before scanning again. If it still shows up, it’s often the scan engine catching an old pattern rather than your current code.
Thumbs up if helpful!
