ServiceNow security

Oomnitza uses several mechanisms for protecting integrations with external systems. These mechanisms allow Oomnitza to protect customer data from unauthorized access and from malicious or accidental changes.

Authentication

The Oomnitza plugin for ServiceNow utilizes SSO (and basic authentication, if enabled) over HTTPS. To use the plugin, the service desk user is required to have an authenticated session with Oomnitza and provide valid credentials in the plugin window.

ServiceNow User Authentication

Following authentication, Oomnitza creates and supports a standard user session. The session time is restricted according to Oomnitza instance session configuration, which is typically set to 20 minutes. The plugin receives the authorization headers Cookie and Oomnitza-session, which are stored in the browser.

Authorization

The authenticated Oomnitza ServiceNow plugin has the same level of permissions as the corresponding Oomnitza user and sends authorization headers with each request. The plugin does not update the information in ServiceNow, only in Oomnitza.

Connections

The plugin communicates with Oomnitza securely via HTTPS. This connection allows a seamless integration between user incidents and assets. In other words, this connection allows the plugin to send comments and fields from ServiceNow to Oomnitza if the corresponding mappings are configured. The following table describes the protocols used to host communication between ServiceNow, Oomnitza, and the Oomnitza for ServiceNow plugin: 

Direction	Protocol	Authentication
Oomnitza to ServiceNow	*443: HTTPS GET  requests	Basic authentication
ServiceNow to Oomnitza	*443: HTTPS POST/GET  requests	Cookie and Oomnitza-session

* The Oomnitza application has security built into its design. Connections between the Oomnitza application, Oomnitza ServiceNow plugin, and ServiceNow take place only over Secure Sockets Layer (SSL) using the latest Transport Layer Security (TLS) version the operating system is capable of using.