Okta

Prerequisites

• Okta Administrator Account with API token generation privileges.

Steps to Send Okta Logs to Cribl for Monitoring

1. Generate Okta API Token

1. Log in to Okta Admin Console:
2. Go to your Okta Admin Console.
3. Navigate to Security > API.
4. Click on Tokens and then Create Token.
5. Name your token and click Create Token.
6. Save the token securely as it will only be shown once.

After completing the initial steps to set up API access in Okta, please provide the following information to our support team to configure Cribl for receiving and processing Okta logs:

API Access Details

API Token: The API token generated for accessing the Okta REST API. This token is required for authentication when fetching logs.

Okta Server Information

Okta Domain: The base URL of your Okta instance (e.g., https://YOUR_OKTA_DOMAIN).

Log Data Information

Log Types: Specify the types of logs being sent (e.g., security events, authentication logs, system logs).

Log Format: The format of the logs being sent (e.g., JSON).

Additional Configuration Details

Log Fetching Frequency: The desired frequency for fetching logs from Okta (e.g., every 5 minutes, hourly).

Any Specific Filters or Parameters: Any specific filters or parameters to apply when fetching logs (e.g., specific time ranges, event types).

Please send the above details to our support team via an "Onboard Log source request in your SecurIST platform

Getting Help

If you encounter any issues or need assistance during this process, our support team is here to help. You can reach out to us through:

Support Portal: Submit a ticket via our support portal for detailed assistance. Documentation: Refer to our extensive documentation library for troubleshooting and additional guides.

By providing these details, we will be able to configure SecurIST to accept and process Bitdefender logs for your SIEM service.