ServiceNow Integration with Grip Security - Posture (SSPM)

  • Updated on Nov 19, 2025
  • 2 minute(s) read
  • nT
 Prev Next

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 outlines the required permissions and workflows for integrating ServiceNow with Grip's SSPM module.

Prerequisites

  • To set up a new connected app, you will need ServiceNow permissions and a username and password with access to the tables below.

  • Ensure the following tables, sys_properties, v_plugin, and sys_plugins have read permission + the admin who created the integration “User role.”

  • If field-level read ACL exists for one or more tables, ensure the  “User role" is added as well.

Refer to the instructions below for guidance on adding the permissions.

How to view and add SNOW table permissions.

Viewing and adding a user role

From the main menu, go to All » Access Control ACL.

  • Search for the required permissions sys_properties (1) v_plugin, (2) and sys_plugins (3)

  • Click the name and, under Definition, verify that the User role exists; if not, add it as needed.

Check the field-level user role.

Field-level ACL is indicated by the dot and asterisk. If you see this type of permission, click on it and verify that it also includes the User role (number 4) under the Definitions section.

Add Read and Allow access permissions.

  • Go to Tables, and find the following permissions: sys_properties, v_plugin, and sys_plugins.

  • Ensure that the  Read and Allow access to this table via web services boxes are checked.

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 and the “Refresh Token Lifespan” to 8,640,000 (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

Note: Do not include 'service-now.com' in the Tenant ID name.

  • Enter the admin-level 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.  

Related articles