Overview Slack integration with Grip’s SSPM module allows Grip to assess critical security configurations in your Slack Enterprise Organization. Prerequisites A “ Slack Enterprise Grid ” is required A Grip user with Slack owner permissions We recommend reading the “ Introduction to Posture Management ” article to learn about posture at Grip. Configuration in Slack Create a new app From the Slack admin panel, go to   “Configure apps ”   (1)   >> click on Build   (2) . Click on”   Create New App ”   (3)   and select the” From   scratch ” option   (4) . Give your App a name – (Recommended to include the SSPM in the name)  (5) and select the workspace to develop your app in   (6) . Click the “Org Level Apps” in the side menu   (7)   >> “Enable Org-Readiness button ” (8) . Check the “ I understand. ..” checkbox >> “Yes, Enable” button   (9) . Add scopes From the side menu, click on   OAuth & Permissions   (10)   and add the following scopes: Bot Token Scopes …

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 …

Overview Zoom integration with Grip’s SSPM module allows Grip to assess critical security configurations around AI, external user governance, meeting encryption and more, in your Zoom Enterprise Organization. Prerequisites “ Zoom Admin ” permissions Zoom Pro or Business account Zoom Configuration Create a new app From Zoom “ App Marketplace ,” go to “ Develop >> Build App ” (1) Select the “ Server to Server OAuth App ” (2) and click on “ Create ” Give the new app a name (3) and click " Create ." In the “App Credentials ” section, copy and save the “ Account ID, Client ID, and Client Secret .” (4) Click “ Continue .” In the “ Basic Information ” section, enter the “ Company Name ” and the “ Developer contact information .” (5) Click “ Continue ” (6) in the “ Token ” section. Click “ Add Scopes ” (7) Search for " account:read:admin " and click on " Select All Account Permissions " (8) Click on “ Done >> Continue ” Click on “ Activate your app .” (9) Connect Grip integration. Go to “ Posture …

Overview The Salesforce integration with Grip’s SSPM module lets Grip pull account data from a single Salesforce organization and provide configuration insights around Session Settings, Password Policies, Certificate and Key Management, File Sharing Security, and Access Controls. This article covers the required permissions and flow to integrate Salesforce with Grip's SSPM module. Prerequisites A Salesforce System Administrator permission to configure a new connected app. Salesforce setup. From Salesforce, go to Setup (1) >> Apps >> App Manager (2) >> New Connected App (3) . Select the “Created a Connected App” option (4) and click “ Continue .” Enter the connected app “ Basic Information ” (5) . In the “ API (Enable OAuth Settings) ”, fill in the following details: Check the “ Enable OAuth Settings ” checkbox. In the “ Callback URL ” (6) enter the following URL. https://central-prod.dep.grip.security/central/v1/integrations/salesforce/auth/callback Add the following Oath scopes (7) : Manage user data via APIs (api …

Overview This guide outlines the integration of Snowflake with Grip Security, enabling Grip Security to deliver insights on Session Settings, Passwords, Authentication, User Provisioning, Role Management, and Network. Prerequisites You need to provide Grip with Snowflake’s Account ID , username, password , and the Warehouse ID . To get the above, you will need a Snowflake administrator role. Get Snowflake Information Account ID (Identifier) Open your user options on the bottom left (1), go to the account name (2) >> “ View account details ” (3) >> Copy the “ Account Identifier ”. Warehouse ID Go to “ Projects >> Worksheets ” (5) Select a warehouse worksheet that can run queries or create a new one using the plus+ icon (6) and copy the following code: USE ROLE orgadmin; SELECT CURRENT_WAREHOUSE(); Click the worksheet and copy the Warehouse ID (7) . Connecting Snowflake to Grip SaaS Security Posture Management. From the Grip portal, go to “Posture >> “ Add Tenant ” (1) . Click on …

Overview Okta’s integration with Grip’s SSPM module allows Grip to pull account data from a single Okta tenant and provide configuration insights around Authentication, Access Control, Password management, Session Security and threat Notifications. This guide describes, step-by-step, how to set up the integration. This article also covers the required permissions and flow to integrate Okta with Grip's SSPM module. Prerequisites We recommend reading the " Introduction to Posture Management " article to learn about posture at Grip. If your setup is “ Okta Setup (OAuth Based) ” please add to the existing permissions the following scopes: okta.policies.read okta.threatInsights.read okta.roles.read Note. When connecting to Okta for Posture insights using OAuth scopes, some of the policies curated by Grip security will be prone to manual review due to a limitation with Okta's API Connecting Okta to Grip SaaS Security Posture Management From the Grip …

Overview This article covers the additional permissions required to integrate Google Workspace Posture SSPM into Grip. Prerequisites Administrator account for the Google Workspace tenant undergoing integration. Follow the Google Workspace Setup article steps We recommend reading the " Introduction to Posture Management " article to learn about posture at Grip. Required permissions Add permissions: Under   Project >>   Service Account   >> Project change the permissions to the below: https://www.googleapis.com/auth/cloud-platform.read-only,https://www.googleapis.com/auth/gmail.readonly,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.user.security,https://www.googleapis.com/auth/admin.reports.audit.readonly,https://www.googleapis.com/auth/admin.directory.group.readonly,https://www.googleapis.com/auth/admin.directory.domain.readonly,https://www.googleapis.com/auth/admin.directory.orgunit.readonly,https://www.googleapis.com/auth/apps.groups.settings,https://www.googleapis.com/auth/cloud-identity.policies.readonly …

… added to the list.  Sometimes, there will be an extra permission at the beginning –  User.Read . This is OK.  Click the ”Grant admin consent for ” tab  (18)  and select "Yes"  in the confirmation popup. Step 5 – Assign user role.  Go to Microsoft Entra roles and administrators in your   Entra ID admin panel . Search for Global Reader and select the entry. Click " + Add assignments " Search for the full name you assigned for your app ( Grip Security – SSPM ), select it, and click " Add "  Step 6 –   Upload certificate .  On the left sidebar, select " Certificates & secrets " (19).  Select the " Certificates " tab   (20) .  Click " Upload certificate "   (21) .  On the new right sidebar, upload the certificate you received from Grip .  Enter a description for internal use (optional).   Click " Add "   (22) .    Final Step –   Configure Integration with Grip. On Grip Platform, go to the “ Posture ” tab >> and click on “ Add Tenant .” Select a “ Display name ”   (3)   for this …

Grip Security – SSPM ), select it, and click " Add " Step 3 – Upload certificate On the left sidebar select Certificates & secrets . Select the Certificates tab. Click Upload certificate . On the new right sidebar, upload the certificate you received from Grip. Enter a description for internal use (optional). Click Add . What next? - Post completion requirements Send Grip the fields you saved in the Create the application step: Application (client) ID Directory (tenant) ID Summary You have now created your part of the integration. After sending the relevant identifiers to Grip the discovery process will begin. You can get a time estimation from your Grip representative.

Overview This guide provides detailed instructions on integrating Okta with Grip using an API key. The integration allows Grip to leverage Okta's identity management capabilities, enhancing security by efficiently managing user access and permissions. Note. If you haven't completed the Okta Setup (API Key Based) step during Grip's historical discovery (sales) cycle, the initial set-up might be delayed during the live Okta SSPM deployment session with the Grip team. There are 2 options for creating an API token: Option A- As a Regular User (Faster) Share this article and ask the users to follow it as Okta admins , with their API Token Key and Okta domain . Only then, perform the Okta SSPM live deployment. Option B- As a Read-Only Service Account (Slower, Less Privileges) Creating an API token using a read-only service account is a more secure but slower process. This method involves additional …

… To use the Google API’s domain-wide delegation feature, Grip requires the email address of the administrator who provided those delegated permissions for the domain. What’s next?  Securely send Grip the details you wrote down while setting up the integration: Key ID Project ID Service account email OAuth2 Client ID / Unique ID Email address of the GW administrator account (Required for domain-wide delegated scopes in Google Workspace API) Appendix for Google Workspace SSPM integration   Additionally, to complete the Google Workspace posture SSPM integration with Grip, you will need to get the Customer ID .   Get the Customer ID from admin.google.com , under “ Account ” >> “ Account Settings ”   Connecting Grip portal    From the Grip portal, go to “ Posture ” >> “ Add Tenant ”>> “ Google Workspace ” >> “ Add Tenant ”   Populate the required fields:   Display name – Provide a friendly display name for the Tenant   Tenant ID - Grip customer ID   Project ID – Copied from the previous steps …