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