---
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


---

# Enable script sandbox \[Updated in Security Center 1.3\]

# Enable script sandbox \[Updated in Security Center 1.3\] {#ariaid-title1}

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

Use the glide.script.use.sandbox property to enable script
sandboxing.
Prevent unauthorized or unauthenticated users from executing privileged script on your instance by enabling the script sandbox feature. The script sandbox is used to execute client-generated scripts, such as query conditions and
GlideAjax expressions, in a "sandbox" environment that has restricted rights.

Without the script sandbox, unauthorized/unauthenticated users can execute privileged script on an instance. This can impact security across all areas, including, but not limited to potentially malicious access to all data on
the instance.

Enable the script sandbox feature on your instance by setting the glide.script.use.sandbox system property to true.  
Warnung:  
This is a safe harbor property, meaning the value can't be altered once it's changed. It is non-revertible.  
There are two cases in the ServiceNow AI Platform that enable the client to send scripts to the server for evaluation:

Filters or queries
:   It is legal to send a filter to the server such as `assigned_to=JavaScript:getMyGroups()`.

System API
:   API call enables the client to run arbitrary scripts on the server and receive a response.
If you enable the script sandbox, the script being evaluated at either of these two entry points runs in a sandbox with reduced rights, with the following characteristics:

* Only those business rules marked Client callable are available within the sandbox.
* Only script includes marked Sandbox enabled are available within the sandbox.
* Certain API calls (largely, but not entirely, limited to ones dealing with direct DB access are not allowed.)
* You can't insert, update, or delete data from within the sandbox. For example, any calls to `current.update()`, are ignored. If you run the ServiceNow AI Platform without enabling script sandboxing, none of these restrictions apply.

{#sc-client-generated-scripts-sandbox__ul_ty4_zgk_jkb}  
Hinweis:  
Beginning with the Xanadu release, script includes marked as Glide AJAX enabled (previously named Client callable) aren't accessible within the sandbox. Only those marked Sandbox enabled are available within the sandbox. When upgrading to the Australia release from the Washington DC release or earlier, any script includes marked as Client callable are also marked as Sandbox enabled.

## More information {#sc-client-generated-scripts-sandbox__section_more_information}

{#sc-client-generated-scripts-sandbox__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Property name | glide.script.use.sandbox |
| Configuration type | System Properties (/sys_properties_list.do) |
| Category | [Validation, sanitization, and encoding](https://servicenow-prod.fluidtopics.net/F1nREUr0FIKK6cga6jbKwg "Validation, sanitization, and encoding addresses input validation to prevent against vulnerabilities like Cross-Site Scripting (XSS), SQL injection and other attacks.") |
| Purpose | Enforces validation for the client-side JavaScript queries that are launched against the platform |
| Recommended value | true |
| Default value | true |
| Security risk rating | 10 |
| Functional impact | This remediation enforces validation for the client-side JavaScript queries that are launched against the ServiceNow AI Platform. There is a potential impact if customer has customizations that include hard-coded JavaScript queries to perform CRUD operations. |
| Security risk | (Critical) The ServiceNow AI Platform provides wide variety of features and functionality through JavaScript queries. However, without appropriate authorization and validation, there is a potential for an attacker to perform unauthorized operations against the platform. |
| References | [Configuring Script sandbox property](https://servicenow-prod.fluidtopics.net/eqcfon4_JCUoRyzCe9rGtg "Enable the script sandbox property (glide.script.use.sandbox) to run client-generated scripts inside a sandbox that has restricted rights.") glide.script.use.sandbox belongs to the same family of properties that secure and restrict execution of scripts originating from the client: * glide.script.allow.ajaxevaluate: See [Disable AJAXEvaluate](https://servicenow-prod.fluidtopics.net/oF4JD9yBCmjSuJHfy6sPxQ "Use the glide.script.allow.ajaxevaluate to protect the system API from vulnerabilities of Client script execution through AJAX calls."). * glide.script.secure.ajaxgliderecord: See [Require AJAXGlideRecord ACL checking \[Updated in Security Center 1.3\]](eqDY710a7RVDCnZmLnUuDw "Use the glide.script.secure.ajaxgliderecord property to perform access control rule (ACL) validation when server-side records, such as tables, are accessed using GlideAjax APIs within a client script."). {#sc-client-generated-scripts-sandbox__ul_bpq_vvq_nkb} |
[ ]

{#sc-client-generated-scripts-sandbox__table_ajc_b43_3kb}

To learn more about adding or creating a system
property, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US).