About The Device
OKTA Identity Engine:
Okta is an on-demand identity and access management service that enables enterprises to accelerate the secure adoption of their web-based applications, both in the cloud and behind the firewall. With Okta, IT can manage an employee's access to any application or device.
OKTA Advanced Server Access (ASA):
Okta Advanced Server Access provides Zero Trust identity and access management for cloud and on-premises infrastructure. Advanced Server Access extends secure privileged access to users, automates lifecycle management for server accounts, and eliminates the need for credential management.
Device Information
Entity | Particulars |
---|---|
Vendor Name | Okta |
Product Name | Identity Engine (Previously known as SSO) |
Type of Device | Cloud |
Collection Method
Log Type | Ingestion label | Preferred Logging Protocol | Log Collection Method | Data Source |
---|---|---|---|---|
Okta | OKTA | JSON | C2C | https://cloud.google.com/chronicle/docs/reference/feed-management-api#okta |
Device Configuration
Read-Only Admin User creation:
Login to OKTA SSO Admin Console with an Admin user.
Create a standard user or if you already have a user you want to make read-only admin go to next section.
Navigate to Security > Administrators
Click Add Administrator
Grant administrator role to the user you previously created and in Administrator roles select Read Only Administrator
Logout from a current admin account.
To Get API key
Sign in to the OKTA SSO Admin console with the Read-only admin user created above
Click Security, and select API
Click Create Token
Give the token a name and click Create Token
A token value will be generated, this is the API key. Copy the API key, which is required when you configure the Chronicle feed.
Click OK, got it.
We get only one chance to copy the token when creating it, after that it gets stored in encrypted format.
The token will remain valid as long as the user who created it exists and has the same privileges. Any change to this user or its privileges may lead to token not functioning and hence broken integration.
If the token is revoked or gets expired because of not being used, log collection will stop and a new token will be required when you configure the Chronicle feed.
Log Collection steps for Okta Advanced Server Access (ASA) -
Okta Advanced Server Access (ASA) audit events can be fetched through Okta System Log API. To enable this, Okta ASA Audit events integration should be done with Okta System Log.
This is an Early Access Feature as of now. To enable it, customer needs to connect with OKTA support. Please follow this link for your reference.
https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/audit-events-with-okta-syslog.ht
Integration Parameters
Parameters required from customer for Integration.
Property | Default Value | Description | |
---|---|---|---|
AUTHENTICATION HTTP HEADERS | N/A | The HTTP header used to authenticate Okta in key-value format. E.g. - Authorization:<API Key> | |
API HOSTNAME | N/A | The fully qualified domain name of your Okta instance. E.g. - xxxx.okta.com |