For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XDR

Okta connector

Use Okta data in Cortex XDR.

Secure identity configurations, monitor identity risks, and respond to threats across your Okta environment.

This connector includes the following capabilities and sub-capabilities (if applicable):

  • Log Collection: Collects Okta System Log events. This capability is available with any Cortex XSIAM, Cloud Runtime Security with Data Collection add-on, Cloud Posture, Cortex XDR with Data Collection add-on, or Data Security license.

    Note

    To ingest Okta Advanced Server Access (ASA) events, use the Okta Automation and Collection connector.

To configure this connector for your specific capabilities, follow the steps outlined in the configuration wizard.

Log Collection

Prerequisite

How to configure the Okta connector

Task 1. Get the Okta domain URL in Okta

  1. From the Okta Dashboard, click the down arrow under your name in the top-right corner.

  2. Copy the Org URL (for example, https://example.okta.com) and save it for the Okta Domain field in Cortex XDR.

Task 2. Create an API token in Okta

  1. Identify the Okta administrator account that you will use to create your API token. The API token inherits the permissions of the administrator who creates it. For read and write access, create the token as a Super Administrator. For read-only access, create the token as a read-only administrator.

  2. Using the administrator account that you identified, log in to your Okta administrator console.

  3. Identify your administrator instance URL, which appears in the browser's address bar. Your administrator instance URL is your subdomain plus -admin.okta.com (format: https://<subdomain>-admin.okta.com). Before you continue to the next step, make note of your administrator instance URL. You will provide this information to Cortex Cloud during the onboarding process.

  4. In the left navigation pane, select Security → API.

  5. On the API page, select the Tokens tab.

  6. Click Create token. A dialog opens prompting you to name your token.

  7. Specify a name for your token and click Create token. Okta generates and displays your token.

  8. Copy the generated token and paste it into a text file. Do not continue to the next step unless you have copied the API token. You will provide this token to Cortex Cloud during the onboarding process.

Task 3. Configure egress in Cortex Gateway

An Account Admin or Instance Administrator must configure egress settings in the Cortex Gateway to allow communication with your Okta domain URL. For more information, see Egress Configurations.

  1. Log in to the Cortex Gateway with Account Admin or Instance Administrator permissions and click Permission Management.

  2. From the side menu, select Egress Configurations.

  3. In the TENANT dropdown, select the tenant where you are configuring the Okta instance.

  4. Click +Path to initiate a new path request.

  5. In the New Path dialog box, configure the following:

    • Requester: In the dropdown, select the requester from the list of users.

    • Flow: In the dropdown, select the appropriate data service option for a generic webhook/host out (or Okta if it is explicitly listed).

    • Path: Enter the domain name or host of your Okta instance (for example, your-company.okta.com).

      Note

      Do not include https:// or trailing slashes. The domain must match the standard Okta domain format.

  6. Click Add to create the path. Once the status of the path shows as Approved in the Egress Configuration table, Cortex XDR can successfully authenticate and execute commands against your Okta environment.

Task 4. Configure the Okta connector in Cortex XDR

  1. Navigate to Settings → Data Sources & Integrations.

  2. Click + Add new.

  3. In the Add Data Sources or Integrations page, search for Okta.

  4. Under Recommended, hover over the new Okta integration and click Add Instance to launch the configuration wizard.

  5. Set up your Okta instance by following the wizard steps in the following tabs.

    Capabilities tab

    1. Instance name: Enter a unique name for your instance. Ensure this domain is unique and not already in use by another instance.

    2. Select capabilities: Choose the required instance functionality:

      • Log Collection (selected by default): Collect Okta System Log events for investigation and detection.

    3. Click Next.

    Connection tab Enter credentials to securely authorize the connection.

    1. Instance URL: Enter your Okta domain obtained in Task 1. This must be identical to the domain URL defined in the Cortex Gateway egress configuration. You must click Apply to proceed.

    2. API Token: Enter a generated character string that identifies an Okta administrator to the Okta API and click Save. This authentication and authorization approach gives SSPM access to your app instance through an API token that you create. The token will inherit the permissions of the administrator who creates the token.

      • The Default option is to enter an API Token: The token is a generated character string that identifies an Okta administrator to the Okta API and click Save.

      • Optionally choose Select from vault to select a stored secret Credential. You can configure and store secrets under Settings→Configurations→Integrations→Vault Manager.

    Configuration tab

    • Under Log Collection:

      • Event Filter: Define an Okta API filter expression for collecting data. The default is filter=eventType eq "user.session.start". For Okta information to be weaved into authentication stories, user.authentication.sso events must be collected.

    Summary tab

    Confirm the summary and click Create instance.

Security Posture

How to configure the Okta connector

To access Okta, Cortex XSIAM requires the following information, which you will specify during the connection process.

  • API Token: A generated character string that identifies an Okta administrator to the Okta API. SaaS Security requires this API token to authenticate to the API. The token inherits the permissions of the administrator who creates it. Required permissions: For read and write access, the API token must be created by a Super Administrator. For read-only access, the API token can be created by a read-only administrator.

  • Admin Instance URL: The URL for your administrator console.

Task 1: Create an Okta API Token

  1. Identify the Okta administrator account that you will use to create your API token. The API token inherits the permissions of the administrator who creates it. For read and write access, create the token as a Super Administrator. For read-only access, create the token as a read-only administrator.

  2. Using the administrator account that you identified, log in to your Okta administrator console.

  3. Identify your administrator instance URL, which appears in the browser's address bar. Your administrator instance URL is your subdomain plus -admin.okta.com (format: https://<subdomain>-admin.okta.com). Before you continue to the next step, make note of your administrator instance URL. You will provide this information to Cortex XSIAM during the onboarding process.

  4. In the left navigation pane, select Security > API.

  5. On the API page, select the Tokens tab.

  6. Click Create token. A dialog opens prompting you to name your token.

  7. Specify a name for your token and click Create token. Okta generates and displays your token.

  8. Copy the generated token and paste it into a text file. Do not continue to the next step unless you have copied the API token. You will provide this token to Cortex XSIAM during the onboarding process.

Task 2: Connect Okta to Cortex XSIAM

  1. In Cortex XSIAM, navigate to Settings → Data Sources & Integrations.

  2. Click + Add new.

  3. In the Add Data Sources or Integrations page, search for Okta.

  4. Under Recommended, hover over the new Okta integration and click Add Instance to launch the configuration wizard.

  5. Under the Capabilities tab, Enter a Name for your application.

  6. Select Security Posture under Default Capabilities.

  7. Click Next.

  8. Under Connection, enter the API key and personal access token details.

  9. Under Configuration tab, select a Sync Interval. Choose a meaningful Tag to distinguish between various applications in different environments.

  10. A confirmation message indicates that Okta is successfully connected. Confirm the Summary details and click Save instance.

Last updated

Was this helpful?