Skip to main content

CollectorsCloud Collectors Administration Guide

Configure the Okta Cloud Collector

Set up the Okta Cloud Collector to continuously ingest events from Okta.

  1. Before you configure the Okta Cloud Collector, ensure that you complete the Prerequisites to Configure the Okta Cloud Collector.

  2. Log in to the Exabeam Security Operations Platform with your registered credentials as an administrator.

  3. Navigate to Collectors > Cloud Collectors.

  4. Click New Collector.

    Okta_Home_page.png

  5. Click Okta.

  6. Enter the following information for the cloud collector:

    Okta_1.png

    • Name – Specify a name for the Cloud Collector instance.

    • Account – Select the Okta account you want to use with this Cloud Collector. If you have not yet created an Okta account, click New Account. For instructions, see Add Accounts for Okta Cloud Collectors .

  7. (Optional) SITE – Select an existing site or to create a new site with a unique ID, click manage your sites. Adding a site name helps you to ensure efficient management of environments with overlapping IP addresses.

    By entering a site name, you associate the logs with a specific independent site. A sitename metadata field is automatically added to all the events that are going to be ingested via this collector. For more information about Site Management, see Define a Unique Site Name.

  8. (Optional) TIMEZONE – Select a time zone applicable to you for accurate detections and event monitoring.

    By entering a time zone, you override the default log time zone. A timezone metadata field is automatically added to all events ingested through this collector.

    Timezone_sitename_site_management_1.png

  9. To confirm that the Exabeam Security Operations Platform communicates with the service, click Test Connection.

  10. Click Install.

    AWS_S3_2.png

    A confirmation message informs you that the new Cloud Collector is created.

Troubleshoot 429 Too Many Requests Error

The Okta Cloud Collector collects up to 1000 log events per API call. If there are more than 1000 log events that need to be collected in one API request, the collector displays an error because of the Okta API rate limits. In the next API request, the collector collects events from the point where it stopped, with no data loss. The collector shows 429 Too Many Requests Error when the collector gets high volume of data to fetch within a minute. To eliminate this error, ensure that you increase the Okta API limit for the Logs endpoint. For more information, see API rate limit categories and cumulative rate limits in the Okta documentation.