Ctrlk
Go to Workbench
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Okta Workforce Identity Setup for Workbench

Step 1: Enable Console Access

Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech. For more information, see Why Expel Asks for Console Access.

  1. Log in to the Okta Admin Console.

  2. Select Directory > People.

  3. Under People, select Add person and configure as follows:

    • User type - enter "User".

    • First name - enter "Expel".

    • Last name - enter "SOC".

    • Username - Enter "soc+<Your_Organization_Name>@expel.io".

      • For example, if your organization were Acme Corp, the format would be "soc+acme_corp@expel.io".

    • Primary email - use the same email address you just entered for "Username".

    • Password - select Set by user.

    • Select Send user activation email now.

  4. Select Save.

Expel will receive the email invitation and complete console access configuration in Workbench on your behalf.

Additional permissions will be required if you would like to set up and use the auto remediation actions for which you are licensed. Locate your auto remediations setup guide for more information.

Step 2: Generate API Credentials

To integrate the technology with Workbench, you need to create secure credentials to the API.

  1. Sign into your Okta organization as a user with Read-Only Admin privileges. API tokens have the same permissions as the user who creates them, and if the user permissions change, the API token permissions also change.

  2. Open the API page.

    • If you use the Developer Console, select Tokens from the API menu.

    • If you use the Administrator Console (Classic UI), select API from the Security menu, and then select Tokens.

  3. Click Create Token.

  4. Name your token "ExpelAPI" and click Create Token. Be sure to make note of your API token in a safe location, as it will only be shown one time.

  5. Collect your Okta URL (also called an Okta domain).

    • Sign in to your Okta organization with your administrator account.

    • Look for the Okta domain in the upper right corner of the dashboard.

Step 3: Enable Okta Behavior Detection

Expel provides coverage on geo-location, geo-impossible, and proxy login activity by leveraging the behavior indicators provided by Okta’s Adaptive MFA. This feature allows Okta to evaluate sign-in behavior such as device, location, IP, and velocity patterns that deviates from past activity. While this feature is intended to configure sign-on policies that respond to changes in behavior, this also provides behavioral indicators in Okta events. To enhance our detection coverage for anomalous activity, enable Okta Behavior Detection using the default Okta evaluation settings.

To enable Okta Behavior Detection:

  1. In the Okta Admin Console, navigate to Security > Behavior Detection.

  2. Select Add behavior and configure the behavior types listed below. Okta's default behavior detection evaluation settings provide a balanced baseline for most environments.

    • Location (New City, New State, New Country, New Geo-Location)

    • Device

    • IP

    • Velocity

For detailed guidance and information on how behavior detection works, refer to the official Okta documentation:

Step 4: Add Okta Workforce Identity as a Security Device in Workbench

Now that you have the correct access configured and noted the credentials, you can integrate your tech with Workbench.

  1. Log in to Workbench.

  2. Navigate to Settings > Security Devices.

  3. At the top of the page, select Add New Device.

  4. Search for and select Okta Workforce Identity.

  5. Configure the fields as follows:

    Okta Workforce Identity Add a Security device screen.

    • Name - enter a name that might help you more easily identify this integration, such as “CompanyName Okta”; this name will display in Workbench under the Name column, and is a text string that you can filter on.

    • Location - enter the location of your integration, for example “cloud;” this is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.

    • URL - enter your organization's Okta URL.

    • API token - enter the API token you created in Step 2.

  6. Select Save.

Your device should be created successfully within a few seconds. A few reminders:

  • After your connection is healthy, it will take some time for your device to begin polling and receiving data.

  • To check on the status, select the downward arrow for your device in the first column and choose View details.

  • Polling will happen first; data will be received after that. You must refresh the page to see updates.

  • If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, contact our support team for help.

  • To check if alerts are coming through, navigate to Dashboards > Alert Analysis. Scroll to the device you want to check, and select the Expel Alerts tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we tune your device.

Last updated

Was this helpful?