Security best practices (instance security hardening)
In addition to security configurations, some extra manual effort is required to further
secure ServiceNow AI Platform applications on a day-to-day basis. This section contains
security tasks that an administrator should perform periodically, within a certain interval of
time.
Auto set Content Type options [Removed in Security Center 1.3.3] X-Content-Type-Options response HTTP header is used by the server to indicate that the MIME (Multipurpose Internet Mail Extensions) enters advertised in the Content-Type headers should be followed.Cache-Control HTTP header value (instance security hardening) Use the glide.http.cache_control property to set the default cache-control value in the HTTP response headers that the ServiceNow AI Platform sends when requesting static content data for a page. Examples of static content include images, CSS, and JavaScript rendered from within, for a page.Enforce security on reports Deactivate this property to prevent the user from publishing or accessing reports. This property disables the published reports feature in reporting.High security plugin (instance security hardening) When you activate the High Security plugin, it creates or updates hundreds of different configurations to control the level of security on your instance. These configurations mitigate many of the top OWASP attacks by enabling strict access control, input validation, and output encoding.Individual login IDs (instance security hardening) Ensure that all users have individual user IDs, which enables auditing of all user activities.Mobile UI obfuscation (instance security hardening) Use the glide.ui.m.blur_ui_when_backgrounded property to obfuscate all fields from the snapshot as the image is saved during the backgrounding process. to obfuscate.Patches and updates (instance security hardening) Ensure that the instance is running the most current patch level. Security fixes are routinely released for the ServiceNow AI Platform within many of the patches and hot fixes that accompany product feature updates. Upgrading when new patches and hot fixes are available reduces the risk of potential vulnerabilities.Remove demo data (instance security hardening) Demo data, particularly demo accounts, are typically included when an instance is created. If so, all demo data should be removed prior to using the instance in non-production or production.