For the complete documentation index, see llms.txt. This page is also available as Markdown.

Exabeam Fusion New-Scale SIEM Collector Setup for Workbench

Step 1: Create an API key

  1. Log in to the Exabeam web console.

  2. Navigate to Settings > API Keys

  3. Create a new API Key with the Search, Analyze and Export permission set.

    The Key Name is Search API and the Permissions are set to the Search, Analyze, and Support permission.
  4. When the new key is generated, copy the KEY ID and KEY SECRET.

  5. Reference the Exabeam documentation to determine your Exabeam API base URL.

Step 2: Add Exabeam Fusion New-Scale SIEM Collector as a Security Device in Workbench

Now that you have the correct access configured and noted the credentials, you can integrate your tech with Workbench.

  1. Log in to Workbench.

  2. In the side menu, navigate to Organization Settings > Security Devices.

  3. Select Add Security Device.

  4. In the search box, type “Exabeam” and then select the Exabeam Fusion New-Scale SIEM Collector integration.

  5. A configuration pane displays. Complete the fields as follows:

    • Name - enter a name that might help you more easily identify this integration, such as “CompanyName Exabeam Collector”; this name will display in Workbench under the Name column, and is a text string that you can filter on.

    • Location - enter the location of your integration, for example “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.

    • Server address - enter the API base URL from the Exabeam documentation.

    • Key ID and Key secret - enter the values generated in Step 1.

Exabeam Fusion New-Scale SIEM Collector security device configuration page.

Your device should be created successfully within a few seconds.

Collector integrations do not support health checks, so an appearance of little or no activity is expected. The (via Collector) integrations are what‌ present data – the Collector itself just facilitates passing the query to the integration receiving the information.

Last updated

Was this helpful?