--- title: Exploring High Security Settings description: High Security Settings refer to several security options available in your instance. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-security/exploring-high-security-settings.html release: australia topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 11 breadcrumb: [High Security Settings] --- # Exploring High Security Settings High Security Settings refer to several security options available in your instance. The High Security Settings module is activated with the High Security Settings plugin, which is active by default on new instances. If High Security Settings are not active on your instance, see [Requesting High Security Settings activation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/t_ActivateHighSecuritySettings.md). To learn more about this plugin, see [Enable High Security Plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-high-security-plugin.md) in Instance Security Hardening Settings. Properties for these types of high security settings are available: - Default property values: To harden security on your platform by centralizing all critical security settings to one location for management and auditing. - Default deny property: Provides a security manager property to control the default security behavior for table access. - Security Administrator role: Provides a role to prevent modification of key security settings and resources. The Security Administrator role is not inherited by the admin role and must be explicitly assigned. - Elevated privileges: Allows users with the security admin role to operate in the context of a normal user and elevate to higher security role when needed. - Property access controls: Allows security administrators to set the roles required to read and write properties. - System logs: Are read only. - Access control rules: Control what data users can access and how they can access it. **Note:** - High Security Settings also automatically activates the Contextual Security plugin, if it is not already active. In addition, Platform Security Settings - High delivers settings and features in the context of increasing the security of your instance. - The Instance Security Hardening Settings content contains detailed descriptions, and compliance values, for the security-related system properties and plugins in the ServiceNow AI Platform. - To learn more about each of these properties, see [Hardening settings](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/security-hardening-settings.md). There are two ways to set or change High Security Settings properties. - Navigate to **System Security** > **High Security Settings**. Options on the High Security Properties page are **Yes** or **No**. - Navigate to the **sys\_properties.list** and search for the property you want to set or change. Options in the System Properties table \[sys\_properties.list\] are **true** or **false**. ## Property access control Two additional columns are created in the Properties \[sys\_properties\] table when High Security Settings are active: - **read\_roles**: A comma-separated list of role names that are allowed to read all fields of this property. - **write\_roles**: A comma-separated list of role names that are allowed to write/modify all fields of this property. Properties listed in the Properties table have **read\_roles** of admin, and **write\_roles** of security\_admin. Users with the admin role can view and read the property values, but must elevate to the security\_admin role to modify them. ## Notifications Activation of high security settings also activates security warning messages. The following is an example of a message that appears after an approval. \[Omitted image "Highsecuritywarning.png"\] Alt text: Security Warning notification ## High Security Settings properties
Property Description Default Value Instance Security Hardening Settings
glide.ui.escape\_text Escape XML values at the parser level for the user interface. Prevents reflected and stored cross-site scripting attacks. This property is not applicable in Service Portal. **Note:** This property is set to **true** by default in Vancouver and later releases, and can't be changed by administrators. For a use case where the property has to be changed, contact customer support. Yes [Escape XML markup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-security/instance-security-hardening-settings/sc-escape-xml.md)
glide.ui.escape\_all\_script Forces all expressions within Jelly JavaScript `