Okta

Okta + JupiterOne Integration Benefits

• Visualize Okta users, groups, devices, applications, and services in the JupiterOne graph.
• Map Okta users to employees in your JupiterOne account.
• Monitor changes to Okta users and access management data using JupiterOne alerts.
• Create an employee entity that is used to map users across your organization to an employee via a matching email property.

How it Works

• JupiterOne periodically fetches Okta users, groups, and access management data to update the graph.
• Write JupiterOne queries to review and monitor updates to the graph.
• Configure alerts to take action when the JupiterOne graph changes.

Requirements

• JupiterOne requires the organization URL and an API key used to authenticate with Okta.
• You must have permission in JupiterOne to install new integrations.

Support

If you need help with this integration, please contact JupiterOne Support.

Integration Walkthrough

In Okta

Create an Okta API Token with Read-Only Admin permission.

In JupiterOne

1. From the configuration Gear Icon, select Integrations.
2. Scroll to the Okta integration tile and click it.
3. Click the Add Configuration button and configure the following settings:

• Enter the Account Name by which you'd like to identify this Okta account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when Tag with Account Name is checked.
• Enter a Description that will further assist your team when identifying the integration instance.
• Select a Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.
• Enter the Organization URL unique to your Okta organization.
• Enter the API Key used to authenticate with Okta.

1. Click Create Configuration once all values are provided.

How to Uninstall

1. From the configuration Gear Icon, select Integrations.
2. Scroll to the Okta integration tile and click it.
3. Identify and click the integration to delete.
4. Click the trash can icon.
5. Click the Remove button to delete the integration.

Data Model

Entities

The following entity resources are ingested when the integration runs:

Note: the Service entities can later be connected to security policy procedures as control providers. This mapping establishes evidence that your organization security policies, procedures and controls are fully implemented, monitored, and managed.

Relationships

The following relationships are created/mapped:

Tips

All Okta users are automatically mapped to a Person entity as an employee. If you have service accounts or generic users in Okta, set their userType attribute to generic or service or bot in Okta user profile to skip this mapping.

This allows you to find non-interactive users with a query like

Find User that !is Person

Okta API Rate Limits

Okta API rate limits are sophisticated, depending on a number of factors including the particular endpoint, organization-wide limits, and subscription level. Responses include a few headers to guide a system into conformance, and will deliver 429 responses that indicate a backoff delay when the rate limits are exceeded. The integration is implemented to respect these 429 response directives by leveraging the API client provided by Okta. However, there is more work to be done to make the integration more proactive by using the headers of every response.

The Okta integration currently ingests users, groups, applications, and MFA devices. The number of calls works out to be:

• ((numUsers / 200) * listUsers) + (numUsers * (listFactors(user) + listGroups(user)))
• listApplications + (numApplications * (listApplicationGroupAssignments(app) + listApplicationUsers(app)))