- 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
- Anomali Context Tables
- Prerequisites to Onboard an Anomali Context Table
- Create an Anomali Context Table
- View and Interact with an Anomali Context Table
- View the Details Panel for an Anomali Context Table
- Edit the Configuration of an Anomali Context Table
- Default IP Attribute Mapping for Anomali
- Default Domain Attribute Mapping for Anomali
- 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
- Recorded Future Context Tables
- Prerequisites to Onboard a Recorded Future Context Table
- Create a Recorded Future Context Table
- View and Interact with a Recorded Future Context Table
- View the Details Panel for a Recorded Future Context Table
- Edit the Configuration of a Recorded Future Context Table
- Default IP Attribute Mapping for Recorded Future
- Default Domain Attribute Mapping for Recorded Future
- STIX/TAXII Context Tables
- Prerequisites to Onboard a STIX/TAXII Context Table
- Create a STIX/TAXII Context Table
- View and Interact with a STIX/TAXII Context Table
- View the Details Panel for a STIX/TAXII Context Table
- Edit the Configuration of a STIX/TAXII Context Table
- Default IP Attribute Mapping for STIX/TAXII
- Default Domain Attribute Mapping for STIX/TAXII
- 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
Troubleshooting Context Management
The following table identifies some possible issues, their likely causes, and suggested resolutions.
Issue Description | Likely Cause | Resolution |
|---|---|---|
The following error occurs while uploading a CSV file:
| The uploaded CSV file is larger than 300 MB. | Compress the file into a ZIP file and upload the ZIP. NoteThe ZIP file must contain only one CSV file. Alternately, split the file into multiple smaller CSV files. Upload them sequentially using the Append option. For more information, see Add Data to a Context Table by Uploading a CSV File. |
The following error occurs while uploading data:
| The uploaded file is not in a supported format. | In order to upload data, create a CSV file, or a CSV file compressed as a ZIP file. CSV and ZIP are the only supported file formats. NoteIf you upload a ZIP file, it must contain only one CSV file. |
During file upload, the progress bar does not complete. | The file upload is stuck in pending status. | Submit an Exabeam support ticket. Include a |
A context table displays fewer rows than the uploaded CSV file. | The CSV file included duplicate keys. | Check the mapping of CSV columns to context table attributes. Warning messages during preview will highlight when duplicate keys are being removed. |
Data ordering in the context table UI is different from the uploaded file. | Data rows are automatically ordered in ascending order by key attribute string values. | Currently, data ordering cannot be modified. |