SN System Properties Reference
Property reference

glide.security.sandbox_no_logging

The glide.security.sandbox_no_logging property determines if logging methods are blocked when executing scripts in the sandbox environment. Admins should care about this setting to prevent sensitive information from being logged during script execution.

Default
true
Type
boolean
Application
Global

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.

Documentation excerpt View supporting context
Context preview Snippet 1
... sandbox These methods aren’t supported in client-generated scripts in the script sandbox. Note: The GlideSystem (gs) methods log(), logError(), and logWarning() can be enabled with script sandboxing 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() • ...
Documentation excerpt View supporting context
Context preview Snippet 2
... <blank> ◦(New‎ This could allow information disclosure in the event that stale accounts are compromised. Disable logger for low privilege users in script sandbox • Description ◦(Old‎ <blank> ◦(New‎ 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.multisso.check_table_exists_for_clone This property enables a check for the existence of the sso_properties table during cloning operations between glide.security.password_reset.uri It defines the URI for the password reset functionality within the ServiceNow platform, impacting how users ac 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.scripting_role.auto_provisioning This property determines if auto provisioning is active for Scripting Governance, facilitating automatic role glide.security.scripting_role.provisioning_job_running This property is a boolean that shows if the initial provisioning job for Scripting Governance is running, imp

All 45 properties in glide.security →