- Introduction to Context Management
- Onboarding a Context Table
- Custom Context Tables
- Create a Custom Context Table by Importing a CSV File
- Create a Custom Context Table Using the Add Custom Option
- Working with Filtered Context Tables
- View and Interact with a Custom or Filtered Context Table
- View the Details Panel for a Custom or Filtered Context Table
- Edit the Configuration of Custom or Filtered Context Tables
- Active Directory Context Tables
- Prerequisites to Onboard an Active Directory Context Table
- Create an Active Directory Context Table
- View and Interact with an Active Directory Context Table
- View the Details Panel for an Active Directory Context Table
- Edit the Configuration of an Active Directory Context Table
- Default Active Directory Attribute Mapping
- Microsoft Entra ID Context Tables
- Prerequisites to Onboard a Microsoft Entra ID Context Table
- Create a Microsoft Entra ID Context Table
- View and Interact with a Microsoft Entra ID Context Table
- View the Details Panel for a Microsoft Entra ID Context Table
- Edit the Configuration of a Microsoft Entra ID Context Table
- Default Microsoft Entra ID Attribute Mapping
- Okta Context Tables
- Custom Context Tables
- Add Data to an Existing Context Table
- Using Context Data in Downstream Applications
- Pre-Built Context Tables
- Context Management APIs
- Troubleshooting Context Management
Okta Context Tables
The Okta option is designed to streamline the process of creating a new Okta context table. When an Okta context table is onboarded, it processes user attributes that an Okta context collector, in the Exabeam Cloud Collectors service, has pulled from an Okta application.
By default, Okta context tables map a set of specific user attributes that are compliant with the Exabeam common user information model. This model defines a standardized user object for security content across Exabeam products.
The Okta option is available on the Context Library tab. To create an Okta context table, you must first have an Okta cloud collector configured and running in the Exabeam Cloud Collectors service. Then you can create the Okta context table in the Context Management service and it can begin processing the data sent from the cloud collector.
For more information, see the following sections: