Service Now Integration with Grip Security - Posture (SSPM)

Overview

The ServiceNow integration with Grip’s SSPM module allows Grip to pull configuration and security data from a single ServiceNow instance and provide actionable insights into Access Control, Session Security, Code Protection, Data and network Restrictions, and Threat Monitoring, along with detailed reports and guidance.

This article covers the required permissions and flows to integrate ServiceNow with Grip's SSPM module.

Prerequisites

A ServiceNow System Administrator permission to configure a new connected app.

How to configure SSPM In ServiceNow

From ServiceNow, go to All >> Application Registry (1)

Under the “System OAuth” >> go to the “Application Registries” window and click on “New” (2).

From “OAuth application,” select “Create an OAuth API endpoint for external clients” (3).

Create a new Application registry

• Give the registry a “Name.”

• Note that the “Client ID” is automatically populated when a name is entered (4).

• Ensure the “Active” checkbox is checked (5).

• Increase the “Access Token Lifespan” to 6000 (6)

• Click on “Submit” (7).

After clicking “Submit,” go to your new Grip SSPM App registry, copy, and save the “Client ID” and “Client Secret,” as you will need it to connect Grip integration to ServiceNow.

Connecting ServiceNow to Grip SaaS Security Posture Management. 

From the Grip portal, go to “Posture” (1) >> “Add Tenant”(2)  

Click on “ServiceNow” (3)  

Enter the “Display Name” (4) and the “Tenant ID” (5) from the ServiceNow URL

Enter your ServiceNow “Username & Password” (6)

Enter the “Client ID & Client Secret” you copied in the previous steps.

Once connected, the Tenant will be added to the “Connected Tenants” list   

Click the tenant to see and filter your policy statuses, assess your security posture, and begin fixing it.