Quick Links

Integrating with Okta

Overview

Okta provides secure identity management with single sign-on, multi-factor authentication, lifecycle management and more. You can send Okta logs to Blumira in two ways:

Both methods for integrating with Okta are covered in this article. Use one method for each Okta organization to avoid duplicate logs.

Integrating with Okta using a Cloud Connector

Before you begin

Blumira's Okta Cloud Connector uses an Okta API Services app that signs in with a key pair, so Blumira never stores a long-lived API token.

Create an Okta app that is specifically for Blumira. Do not reuse an app that another tool already uses. You must be an Okta Super Administrator to create the app and assign it an admin role.

You will also need your Okta org domain, such as acme.okta.com.

Create an API Services app in Okta

  1. In the Okta Admin Console, go to Applications > Applications.

  2. Click Create App Integration, select API Services, and click Next.

  3. Name the app (for example, Blumira) and click Save.
  4. On the app's General tab, copy the Client ID. You'll enter it in Blumira later.

Add a key pair

  1. On the General tab, in Client Credentials, click Edit.

  2. Set Client authentication to Public key / Private key.
  3. Under public key configuration, keep Save keys in Okta and click Add key.
  4. Click Generate new key. Okta shows the private key as JSON. Switch the view to PEM, then copy the key.

  5. Click Done, then click Save.

Note: Keep exactly one active key on this app. If the app has more than one active key, Blumira cannot connect and shows "This Okta app has more than one active key." To change keys later, see Rotating the key below.

Turn off DPoP

Blumira does not support DPoP, so complete these steps to turn it off:

  1. On the General tab, in General Settings, click Edit.

  2. Clear Require Demonstrating Proof of Possession (DPoP) header in token requests.
    Note: New API Services apps require DPoP by default, but Blumira does not support DPoP.

  3. Click Save.

Grant the log scope and admin role

The app needs both of these.

  1. Click the Okta API Scopes tab. Next to okta.logs.read, click Grant.

  2. Click the Admin roles tab, then click Edit assignments.

  3. Select the Read-Only Administrator role and click Save Changes.

Note: Role changes can take a minute to apply in Okta. If Blumira says the app is missing the Read-Only Administrator role right after you assign it, wait a minute and try again.

Configuring the Okta Cloud Connector in Blumira

To configure the Okta Cloud Connector, do the following:

  1. In Blumira, navigate to Ingestion > Cloud Connectors.

  2. Click + Add Cloud Connector.

  3. In the Available Cloud Connectors window, select Okta.

  4. In Cloud Connector Name, type a name that will help you identify the integration.

  5. Complete the following fields:

    • Okta Domain: enter the domain you sign in to, for example acme.okta.com. Do not use the admin console domain (acme-admin.okta.com). If you paste a full URL, Blumira removes the https:// and any path for you.
    • Client ID: the Client ID from Step 1.
    • Private Key (PEM): the full private key from Step 2, including the BEGIN and END lines.
  6. Click Connect.

Blumira tests the connection with Okta before saving. If something isn't set up correctly, Blumira shows a message telling you which setting to fix.

After you connect, Blumira collects up to the last 90 days of Okta events, then continuously checks for new events.

Rotating the key

Complete these steps in one sitting. Between steps 1 and 3, Blumira pauses collecting Okta events. When you finish, it catches up automatically and no events are lost.

  1. In Okta, open the app's General tab, click Add key > Generate new key, switch to PEM, and copy the new private key. Click Done, then click Save.
  2. In Blumira, edit the Okta Cloud Connector, replace Private Key (PEM) with the new key, and save.

  3. In Okta, set the old key to Inactive, then delete it. Only the new key should be active.

Integrating with Okta using a Blumira sensor module

Before you begin

Blumira's sensor module utilizes the Okta System Log API which provides a stream of event data that are correlated to Blumira detections.

The sensor-based integration requires a Blumira sensor to be installed before you can complete the steps below. Ensure that you complete the steps in Building a Blumira sensor with Ubuntu before you continue.

Generating an Okta SSWS Token

To gather your Okta token, do the following:

  1. Sign into your Okta Admin Panel with administrator privileges.
  2. Select the Security Menu > API > Tokens.
  3. Click Create Token.
  4. Name your token and click Create Token.
  5. Record the Token Value to use when configuring the Blumira module below.

Configuring Blumira

Set up the Okta Module within Blumira by doing the following:

  1. In Blumira, navigate to Ingestion > Sensors.
  2. Click on the sensor you want to use.
  3. Scroll down the page to the Modules section, and click on the Add Module button.
  4. In the Module drop-down, select Okta API Module.
  5. In the Module Configuration form, complete the following:
    • In Okta account name, type the subdomain of the URL you use to log in to Okta. For example, if you log in to “mycompany.okta.com,” then this value should be “mycompany.”
    • In Okta SSWS Token, paste the API token you obtained in the previous section.
    • (Optional) In Log Source Name, type a name to identify the Okta log source.
  6. Click Install.

Within minutes of completing these steps, the module will be operational and will ingest Okta logs from the last 90 days into the Blumira platform. The module will continuously monitor the Okta service for the latest available logs.