Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

High Security Settings

Log in to subscribe to topics and get notified when content changes.

High Security Settings

High Security Settings refer to several security options available in your instance.

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.

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.

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.
  • Transaction and 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.

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.


Activation of high security settings also activates security warning messages. The following is an example of a message that appears after an approval.

Figure 1. Security Warning notification
Security Warning notification

High Security Settings properties

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.
  • Default: Yes
Forces all expressions within Jelly JavaScript <script type="text/javascript"> tags to be escaped by default. Enforces escaping only if the type attribute in the <script> tag is empty, or if the value is text/javascript, text/ecmascript, application/javascript, application/ecmascript, or application/x-javascript.
  • Default: Yes in new instances
Rotate HTTP session identifiers to reduce security vulnerabilities. See:
  • Default: Yes
If you are using the SAML 2.0 plugin for Single Sign-on authentication, set this property to No. Otherwise, it interferes with the session information sharing that takes place between the instance and the Identity Provider.
Enable secure session cookies: Enable additional cookie security. If Yes, strict session cookie validation is enforced.
  • Default: Yes
For mobile Password Reset, URL that the user is taken to when the user clicks the Forgot password? button.
Double-check security on inbound transactions during form submission (rights are always checked on form generation).
  • Default: Yes
Check conditions on UI actions before execution. Normally conditions are checked only during form rendering.
  • Default: Yes
Enable usage of a secure token to identify and validate incoming requests. This token is used to prevent cross-site request forgery attacks.
  • Default: Yes
Escape HTML for HTML fields in a list view.
  • Default: Yes
Escape JavaScript tags in HTML fields.
  • Default: Yes
Remove the Remember me check box from the login page.
  • Default: Yes
Authenticate with the SMTP server by the user name and password properties.
  • Default: Yes
Run client-generated scripts (AJAXEvaluate and query conditions) inside a reduced-rights sandbox. If Yes, only those business rules and script includes with the Client callable check box set to Yes are available, and certain back-end API calls are disallowed. For more information, see The script sandbox property.
  • Default: Yes
Enforce strict security on incoming SOAP requests. Requires incoming SOAP requests to go through the security manager for table and field access and checks SOAP users for the correct roles for using the web service.
  • Default: Yes
Require authorization for incoming WSDL requests.
  • Default: Yes
Note: If you choose not to require authorization for incoming WSDL requests, you must modify the Access Control (ACL) rules to allow guest users to access the WSDL content.
Require basic authorization for incoming CSV requests.
  • Default: Yes
Require basic authorization for incoming Excel requests.
  • Default: Yes
Require basic authorization for incoming import requests.
  • Default: Yes
Require basic authorization for incoming PDF requests.
  • Default: Yes
Require basic authorization for incoming RSS requests.
  • Default: Yes
Require basic authorization for incoming script requests.
  • Default: Yes
Require basic authorization for incoming SOAP requests.
  • Default: Yes
Require basic authorization for incoming unload requests.
  • Default: Yes
Require basic authorization for incoming XML requests.
  • Default: Yes
Require basic authorization for incoming XSD requests.
  • Default: Yes
Enforce relative links from the URI parameter on /ess/ If Yes, only relative URLs are permitted through the /ess/ page using the uri parameter. If No, all URLs are permitted, which may permit linking to external unauthorized content.
  • Default: Yes
Enable this property to set the X-Frame-Options response header to SAMEORIGIN for all UI pages. The X-Frame-Options HTTP response header can be used to indicate whether a browser should be allowed to render a page in a <frame> or <iframe>. Sites can use this property to avoid clickjacking attacks by ensuring that their content is not embedded into other sites.
  • Default: Yes
A list of comma-separated attachment mime types that do not render inline in the browser. Prevents cross-site scripting attacks. For example, text/html forces HTML files to be downloaded to the client as attachments rather than viewed inline in the browser.
  • Default: text/html,image/svg,image/svg+xml
When this property is enabled, ACL checks for GroupBy operations are performed for the group names based on the actual data from the groups.
  • Default: Yes
If Yes, only the admin user or user from allowed IP address can access,, and
  • Default: No
Allow embedded HTML (using [code] tags) to contain JavaScript tags.
  • Default: Yes
Enable the AJAXEvaluate processor. The AJAXEvaluate API call allows the client to send and execute arbitrary scripts on the server.
  • Default: No
Allow browsers to use auto-complete on password fields on login forms.
  • Default: No

The following properties are defined in the sys_properties table, but are not visible on the High Security Settings page.

Verify the hostname and certificate chain presented by remote SSL hosts. Protect against Man-In-The-Middle (MITM) attacks.
  • Default: true
Note: This property overrides the com.glide.communications.trustmanager_trust_all property.
Require basic authentication for inbound table schema requests.
  • Default: true
Allow usage of an expired secure token to identify and validate incoming requests. This token is used to prevent cross-site request forgery attacks.
  • Default: false
Time in seconds for a secure token to expire. Allows control over the length of time that the previous CSRF token is valid. When the user session expires, the secure token expires with it unless the property is enabled and it is within the timeframe described by this property. This token is used to prevent cross-site request forgery attacks.
  • Default: 86400 seconds or 1 day
Enforces strict validation on CSRF tokens so that users cannot resubmit a request if the CSRF token does not match.
  • Default: false