glide.security.sandbox_no_loggingThe 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.
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. |
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 |