Restrict GlideRecord in Client Callable Script

Using GlideRecord in client-callable script includes can expose sensitive data to unauthorized users. Since client-callable scripts run on the client-side, directly querying the database with GlideRecord can lead to data leaks. Replacing GlideRecord with GlideRecordSecure ensures proper data access restrictions based on user roles and permissions.

Resolution Steps

1. Replace GlideRecord with GlideRecordSecure

   • GlideRecordSecure enforces Access Control Rules (ACLs) and restricts unauthorized data access.

2. Validate Data Access Permissions

   • Ensure that users with appropriate roles can still retrieve necessary data.

   • Test the script with different user roles to confirm expected behavior.

Before:

Using GlideRecord can pose a security threat in client callable scripts

After:

GlideRecordSecure enforces Access Control Rules (ACLs) and restricts unauthorized data access.

Replacing GlideRecord with GlideRecordSecure in client-callable script includes protects sensitive data and ensures compliance with role-based access controls. This practice enhances security and prevents unauthorized data exposure.

For more detailed guidance on resolving this issue, please contact us at support@dt-advisory.ch.