- 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 User Attribute Mapping for Active Directory
- Default Device Attribute Mapping for Active Directory
- CrowdStrike Context Tables
- 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 User Attribute Mapping for Microsoft Entra ID
- Default Device Attribute Mapping for Microsoft Entra ID
- 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
Active Directory Context Tables
The Active Directory option is designed to streamline the process of creating a new Active Directory context table. When an Active Directory context table is onboarded, it processes either user or device attributes that a site collector has pulled from a Microsoft Active Directory server. In the Active Directory context table, these attributes can be mapped to Exabeam target attributes.
By default, Active Directory tables map a set of specific user or device attributes that are compliant with the Exabeam common user information model. This model defines standardized user or device objects for security content across Exabeam products. You can also manually map additional raw data, fetched by an Active Directory site collector, either to an Exabeam target attribute or to a custom field.
The Active Directory user and device options are available on the Context Library tab. To create an Active Directory context table, you must first have both a site collector instance and an Active Directory site collector configured and running in the Exabeam Site Collectors service. Then you can create an Active Directory context table in the Context Management service and it can begin processing the data sent from the site collector.
For more information, see the following sections:
Note
License Requirement for Device Context Tables
Currently, device context data can only be accessed if you have the New-Scale Analytics license. Access to device data will be available to other licenses in the near future.