Error handling and logging
reference brazil Updated Sep 10, 2026 2 min read sc-error-handling-logging.md
The error handling and logging category addresses the quality and verbosity of logged information exposed to stakeholders.
This includes ensuring logs and error messages do not collect sensitive information, correctly protect data according to classification and have an appropriate lifetime. Additionally, this category relates to appropriate error handling and not revealing sensitive errors to end users, such as verbose stack traces for unhandled exceptions with security implications.
- Disable logger for low privilege users in script sandbox
Manage Glide System's ability to log scripts being executed in the sandbox environment. - Disable secure cookie debugging
Manage the log messages related to cookies in your instance. - Disable SQL error messages
Use the glide.db.loguser property to disable SQL error messages from rendering in a browser. - Enable Identity and Access Audit tool
Use Identity and Access Audit to track changes to user accounts, groups, and roles. - Enable MID audit log
The MID Server command audit log records details such as the command name, command hash, name of credential used, and execution status. - Enable protected tables plugin
Use the com.glide.security.protected_table.enabled property to prevent higher privilege users from tampering with log tables. - Log all outbound http request fields [Removed in Security Center v1.3.2]
Configure the glide.outbound_http.security.log.allow.all.fields property to false to prevent sensitive Outbound HTTP fields from being logged in plain text. - Log html sanitization [Removed in Security Center 2.0]
Configure glide.html_sanitize.discarded_log.enable property to determine if HTML sanitization events will be logged in your instance. - Log Impersonation History
Enable impersonation history logging using a system property. - Log session audit events
Use a system property to enable creations of session audit events - Log user impersonation
Configure glide.sys.log_impersonation to control if user-impersonating events are logged in your instance. - Prevent verbose HTTP request logging
Help prevent access to sensitive information by reducing verbose HTTP request logging. - Restrict exposure of validation error details to end users
Configure the platform to return generic error messages instead of detailed validation error text to end users in conversational AI interfaces when skill validation fails. - Restrict vault code signing audit exclusion to defaults
Manage which tables are excluded from Vault Code Signing audit tracking to maintain visibility into changes on protected code artifacts. - Track Impersonation Events
Enable impersonation event tracking using a system property. - Turn off verbose SQL error messages for import processor
Configure this property to control whether verbose SQL error messages are displayed.
Parent Topic:Hardening settings
56 lines · 6.5 KB
--- title: Error handling and logging description: The error handling and logging category addresses the quality and verbosity of logged information exposed to stakeholders. locale: en-US canonical_url: https://www.servicenow.com/docs/r/platform-security/instance-security-hardening-settings/sc-error-handling-logging.html release: brazil product: Instance Security Hardening Settings classification: instance-security-hardening-settings topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Hardening settings, Platform Security] --- # Error handling and logging The error handling and logging category addresses the quality and verbosity of logged information exposed to stakeholders. This includes ensuring logs and error messages do not collect sensitive information, correctly protect data according to classification and have an appropriate lifetime. Additionally, this category relates to appropriate error handling and not revealing sensitive errors to end users, such as verbose stack traces for unhandled exceptions with security implications. - **[Disable logger for low privilege users in script sandbox](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-glide-security-logger-no-loggining-for-sandbox.md)** Manage Glide System's ability to log scripts being executed in the sandbox environment. - **[Disable secure cookie debugging](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-disable-secure-cookie-debugging.md)** Manage the log messages related to cookies in your instance. - **[Disable SQL error messages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-disabling-sql-error-messages.md)** Use the **glide.db.loguser** property to disable SQL error messages from rendering in a browser. - **[Enable Identity and Access Audit tool](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-enable-identity-and-access-audit-tool.md)** Use Identity and Access Audit to track changes to user accounts, groups, and roles. - **[Enable MID audit log](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-enable-mid-audit-log-plugin-applicability-mid-server.md)** The MID Server command audit log records details such as the command name, command hash, name of credential used, and execution status. - **[Enable protected tables plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-enable-protected-tables-plugin.md)** Use the **com.glide.security.protected\_table.enabled** property to prevent higher privilege users from tampering with log tables. - **[Log all outbound http request fields \[Removed in Security Center v1.3.2\]](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-log-all-outbound-http-request-fields.md)** Configure the **glide.outbound\_http.security.log.allow.all.fields** property to false to prevent sensitive Outbound HTTP fields from being logged in plain text. - **[Log html sanitization \[Removed in Security Center 2.0\]](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-log-html-sanitization.md)** Configure **glide.html\_sanitize.discarded\_log.enable** property to determine if HTML sanitization events will be logged in your instance. - **[Log Impersonation History](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-log-impersonation-history.md)** Enable impersonation history logging using a system property. - **[Log session audit events](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-log-session-audit-events.md)** Use a system property to enable creations of session audit events - **[Log user impersonation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-log-user-impersonation.md)** Configure **glide.sys.log\_impersonation** to control if user-impersonating events are logged in your instance. - **[Prevent verbose HTTP request logging](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-prevent-verbose-http-request-logging.md)** Help prevent access to sensitive information by reducing verbose HTTP request logging. - **[Restrict exposure of validation error details to end users](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-restrict-exposure-of-validation-error-details-to-end-users.md)** Configure the platform to return generic error messages instead of detailed validation error text to end users in conversational AI interfaces when skill validation fails. - **[Restrict vault code signing audit exclusion to defaults](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-restrict-vault-code-signing-audit-exclusion-list-to-default-tables.md)** Manage which tables are excluded from Vault Code Signing audit tracking to maintain visibility into changes on protected code artifacts. - **[Track Impersonation Events](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-track-impersonation-events.md)** Enable impersonation event tracking using a system property. - **[Turn off verbose SQL error messages for import processor](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/sc-turn-off-verbose-sql-error-messages-for-import-processor.md)** Configure this property to control whether verbose SQL error messages are displayed. **Parent Topic:**[Hardening settings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-security/instance-security-hardening-settings/security-hardening-settings.md)
| title | Error handling and logging |
| description | The error handling and logging category addresses the quality and verbosity of logged information exposed to stakeholders. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/platform-security/instance-security-hardening-settings/sc-error-handling-logging.html |
| release | brazil |
| product | Instance Security Hardening Settings |
| classification | instance-security-hardening-settings |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | Hardening settingsPlatform Security |