Property reference

`glide.security.sandbox_no_logging`

Blocks log(), logError(), and logWarning() calls in scripts running in the sandbox. With the default value of true, sandboxed scripts cannot use these logging methods; setting it to false enables them, including for low-privileged users.

Default: true
Type: boolean
Application: Global
Category: Security & Access Control

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	This property controls the availability of log(), logError(), and logWarning() methods in the sandbox, enhancing security by limiting logging capabilities.
What area does it affect?	Script execution security
What does the default mean?	The default value is "true", which means this behavior is enabled by default.
When should you review it?	Review this property when configuring sandbox environments or addressing security concerns related to script logging.

Out of the box property record

Raw metadata from the property record.

Property name	`glide.security.sandbox_no_logging`
Sys ID	`aab7d301970130008e00958e3b297575`
Type	boolean
Application	Global
Default value	`true`
Description	Specifies whether to block the log(), logError(), and logWarning() methods when running script from the sandbox
Updated	2024-05-25 04:03:33

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs Script sandbox evaluator ↗

Context preview Snippet 1

... these methods fail to execute in the sandbox. Note: The GlideSystem (gs) methods log(), logError(), and logWarning() can be enabled for use with the script sandbox evaluator by setting the glide.security.sandbox_no_logging system property to false. Restricted methods Class Method GlideRecord • deleteMultiple() • deleteRecord() • getRowCount() • insert() • update() • updateMultiple() GlideSystem (gs) • addErrorMessage() • addInfoMessage() • addMessage() • ...

Brazil docs Disable logger for low privilege users in script sandbox ↗

Context preview Snippet 2

... in the United States and/or other countries. Other company names, product names, and logos may be trademarks of the respective companies with which they are associated. 261 Documentation Updates If "glide.security.sandbox_no_logging" is set to "false", then logging will be available for low-privileged users using sandboxed scripts. This property controls Glide System's ability to log scripts being executed in the sandbox environment. ...

Additional source link Another external reference for this property

Open reference

More in `glide.security`

Other properties in the same namespace.

glide.security.password_reset.uri It defines the URI for the password reset functionality within the ServiceNow platform, impacting how users ac glide.security.response.authenticate.header.auth_profile.first_scheme_on This property configures the behavior of the authentication response header for REST APIs, allowing either a s glide.security.restrict.get.login This property determines whether GET login requests are restricted, enhancing security by limiting potential a glide.security.restrict.get.portal.login This boolean property determines whether access to portal login is restricted, enhancing security by limiting glide.security.scoped_administration This property restricts admin access to scoped applications, enhancing security by limiting visibility to only glide.security.scoped_administration.honor_global_acl This property enables or disables the honoring of Global ACLs for specific tables defined in sys_scoped_admin_ glide.security.script.include.name.case.insensitive.list This property configures a list of script includes for case-insensitive matching in authentication processes, glide.security.scripting_governance.enabled This property restricts script authorship to authorized users, ensuring that only those with the script-writer

All 64 properties in glide.security →