… Select " View ," >> Click on “ Manage Consumer Details ." Paste the verification code you received. Copy the “ Consumer Key ” and the “ Consumer Secret .” (10)  Connecting Salesforce to Grip SaaS Security Posture Management. From the Grip portal, go to “ Posture ” (1) >> “ Add Tenant ” (2) Click on “ Salesforce ” (3) Enter a “ Display Name ” The “ OAuth Endpoint ” is automatically populated, but if you want to test it in a “ Sandbox environment, ” replace the word “ login ” with “test.” Paste the “ Consumer key & secret” you copied in the previous step to the “ Consumer Key ” (4) and “Consumer Secret ” (5) fields.     You will receive a link to send to the Salesforce admin. The admin should navigate to the link and “Allow” the access. This should connect the integration. 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.

Overview Duo Single Sign-On (SSO) is a cloud-hosted identity provider (IdP) supporting SAML 2.0 and an OpenID Connect provider (OP). It enhances popular cloud services like Microsoft 365 and Amazon Web Services with two-factor authentication and access policy enforcement through SSO protocols. This article guides you through the process of integrating Duo SSO with Grip Security, by creating a new SAML application in Duo and configuring the necessary settings in Grip Security. Prerequisites Access to the Duo administration panel. Access to the Grip Security portal. Integrating Duo SSO with Grip Security From the   Duo Administration   page, select   Applications   on the left panel. On the   Applications   panel, select   Protect an Application .   Search for   custom , and in the row   Generic Service Provider, 2FA with SSO hosted by Duo (Single Sign-On) , click   Protect .   In Duo SSO, under   Service Provider , enter values for   Entity ID   and   Assertion Consumer Service …

… You are not required to check the other boxes. Write down the address of the group for future steps. Click Next . Click Create group . Click Edit group settings . On the right sidebar, go to the Members tab and click View and manage members . Click Add members , select all identities to be included in the scope, and click Add . Tip 💡 The identities included in the scope can always be changed later. Step 2 – Assign the policy Open a PowerShell terminal as Administrator and run the following script: $AppClientId = $SecurityGroupMail= $O365OrganizationAdminMail= Install-Module -Name ExchangeOnlineManagement Set-ExecutionPolicy Unrestricted $UserCredential = Get-Credential Connect-ExchangeOnline -UserPrincipalName $O365OrganizationAdminMail New-ApplicationAccessPolicy -AppId $AppClientId -PolicyScopeGroupId $SecurityGroupMail -AccessRight RestrictAccess -Description "Grip Access policy" Note Values marked with need to be filled-in with your specific values. Summary You have now created a scope for your Grip integration with a mail enabled security group. You can contact your …

… 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 portal, go to “ Posture ”   (1)   >> “ Add Tenant ” (2) Click on “ Okta ”   (3) In the “Tenant Details” section, enter your own “ Display Name ”   (4) . The “ Tenant ID (Domain) ” (5) field is populated automatically from the integration you connected. Click on “ Add Tenant ”   (6) . Note. If the integration isn’t connected via API or not connected at all, the tenant will not connect and will display a notification with instructions. 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. 

… to you. Integrating O365 with Grip Security We recommend reading the " Introduction to Posture Management " article to learn about posture at Grip. Process stages Create an application Grant Permissions Upload Certificate Configure integration with Grip Required Permissions To perform the discovery process, Grip requires several OAuth permissions from various Microsoft services, plus a given role. The required permissions are as follows: Product/Service Permissions  Graph API  Directory.Read.All  GroupMember.Read.All,      Organization.Read.All  Policy.Read.All,       RoleManagement.Read.Directory  User.Read.All          PrivilegedEligibilitySchedule.Read.AzureADGroup PrivilegedAccess.Read.AzureADGroup       RoleManagementPolicy.Read.AzureADGroup   SharePoint Online  Sites.FullControl.All   Exchange Online (O365) Exchange.ManageAsApp   Identity Roles  Global Reader  Defender for Office 365 Global Reader Microsoft Teams Global Reader Pay attention. The Sites.FullControl.All permission is the minimum required to read admin center configurations for SharePoint Online, as this is a limitation of the API provided by Microsoft. Grip does not …

… 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 ” and click on “ Add Tenant” Click on “ Zoom .” Enter a “ Display name ” Paste the data you copied in step 4: “Account ID , Client ID , and Client Secret.” Click on “ Add Tenant .” • Once connected, the tenant will be added to the “ Connected Tenants ” list under the “ Manage ” tab. • In the Tenant window, you can view and filter your policy statuses, evaluate your security posture, and start addressing it.  

… Used to gather sign-in logs for managed applications and social login applications within Entra ID domain Application.Read.All Used to gather the list of managed applications within the Entra ID environment Directory.Read.All Used for retrieving group, group alias, and member information to present identity and group-centric views into SaaS use Optional - Additional Graph permissions for O365 posture (SSPM) Permissions Product/Service Directory.Read.All GroupMember.Read.All, Organization.Read.All Policy.Read.All, RoleManagement.Read.Directory User.Read.All PrivilegedEligibilitySchedule.Read.AzureADGroup PrivilegedAccess.Read.AzureADGroup RoleManagementPolicy.Read.AzureADGroup Graph API Sites.FullControl.All SharePoint Online Exchange.ManageAsApp Exchange Online Global Reader Identity Roles Defender for Office 365 Global Reader Microsoft Teams Global Reader For OAuth Revocation Permissions Product/Service DelegatedPermissionGrant.ReadWrite.All Graph API Read more in this article How to Perform the Setup The process is comprised of the following steps: Step 1 - Create …

… 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 -  Users:read   (11) . User Token Scopes – admin.users:read & users:read   (12) Scroll up and click the “ Install to Organization ” button   (13). Click on “ Allow ”. Copy the “ User OAth Token ”, you will need it when connecting the SSPM integration.   Connecting Slack   to Grip SaaS Security Posture Management From the Grip portal, go to “ Posture ”   (1)   >> “ Add Tenant ” (2)     Click on “ Slack ”   (3) In the “Tenant Details” section, enter your own “ Display Name ”   (4) . in the “ User OAUTH Token ” field   (5) , paste the “ User OAuth Token ” from the previous step. Click on “ Add Tenant ”. 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.     

… 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.  

… 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: Field Name Description and Source Display Name Provide a friendly display name for the Tenant Tenant ID (Customer ID) Get the Customer ID from admin.google.com , under “ Account ” >> “ Account Settings ”>>״ Customer ID ”” Project ID console.cloud.google.com » Project selector > Copy the ID of the Grip Project Client Email & Client ID console.cloud.google.com » IAM & Admin » Service Account » Choose the discovery service account Copy the Email to Client Email Copy OAuth2 Client ID > Client ID Domain Admin The email address of the domain admin Click “ Add Tenant ”. The Tenant will be added to the “ Connected Tenants ” list Once the integration is connected, you will be able to see and filter your policy statuses, assess your security posture, and begin fixing it.

… 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   Client Email - The Service account email   Client ID and Domain Admin – Are the Email address of the Google Workspace administrator account   Click on “ Add Tenant ”.   The Tenant will be added to the “ Connected Tenants ” list   Once the integration is connected, you will be able to see and filter your policy statuses, assess your security posture, and begin fixing it.   Note. The policies will be synced and updated on a daily basis.  However, when first connecting the integration, we recommend clicking the “Sync Policies Status” button to perform an immediate sync (a few minutes).