Exabeam Fusion XDR Setup for Workbench

Step 1: Enable Console Access

Having read-only access to the interface of your technology allows Expel to dig deeper during incident investigations. Our device health team uses this access to investigate potential health issues with your tech.

The Exabeam Security Management Platform uniquely combines a data lake for unlimited data collection, machine learning for advanced analytics, and automated incident response into an integrated set of products. The SOC analysts require a dedicated user account, which allows us to respond to security alerts and leverage the data available in Exabeam. Learn more about why Expel asks for console access.

1. Log in to the Exabeam portal and select Settings.
2. In the Team section of the submenu, select Users.
3. In the upper right portion of the Users page, select + New User. Enter the following information for the fields:

Field name	What to enter
User Type	Local
Username	expel
Full Name	Expel SOC
Email	Optional field - can be left blank
Password	Enter a password. Save the password to enter later in Workbench.

1. For Role, select Tier 3 Analyst. If a custom role is preferred, expand to view and complete the steps below, being sure to note the permission requirements. If you do not need a custom role, skip to Step 2.

Configure Custom Role

1. At the bottom of the left-hand context menu, select Settings.
2. In the Team section of the settings submenu, select Roles.
3. In the upper right portion of the Users page, select + New Role.

   • Role Name - enter "Expel".
   • Description - enter "Expel Custom Role".
4. Select Advanced Analytics, and then select the following permissions:

   View
   View Activities	Required
   View Executive Info	Required
   View Global Insights	Required
   View Infographics	Required
   View Insights	Required
   View Rules	Required
   Edit and Approve
   Approve Lockouts	Optional but recommended
   Accept Sessions	Optional but recommended
   Manage Rules	Optional but recommended
   Manage Watchlist	Optional but recommended
   Search
   Manage Search Library	Optional but recommended
   Basic Search	Required
   Threat Hunting	Required
   View Search Library	Required

Step 2: Generate API credentials

1. Navigate to Advanced Analytics > Core > Cluster Authorization Token.
2. In the Cluster Authentication Token menu, select + to add a new token.
3. In the Setup Token dialog box:

   • Token Name - enter a name for the token.
   • Expiry Date - select Permanent.
   • Permission Level - select Tier 3 Analyst.
4. Select Save.
5. Copy the generated token for use in the next step.

Step 3: Add Exabeam Fusion XDR 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. Complete the fields using the credentials and information you collected in previous steps.

   • (On-prem only) Select an Assembler from the list. If you have an assembler, select the assembler you set up in Add a New Assembler.
   • Name - enter a name that might help you more easily identify this integration, such as “CompanyName Exabeam Fusion XDR”; 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.
   • Token - enter the token you generated in Step 2.
   • Username - enter the username you created in Step 1.
   • Password - enter the username you created in Step 1.
   • Server Address - enter the IP address for Exabeam.

   
3. Click Save.
4. On the console access screen, select Set up now. Expel requires console access to allow analysts to perform investigation and triage. Without this additional level of information, alerts cannot be verified by our analysts and an investigation cannot be initiated. For more information, see Why Expel Asks for Console Access.
5. In the Console Login area, provide these details:

   • Console URL - enter the console URL from the Server address in the Connection Settings area above. At the end of the URL, type /login.
   • Username - enter the username you created previously.
   • Password - enter the password you created previously.
   • Two-factor secret key (32-character code) - depending on how your organization enforces log-ins, this field may not apply to you. In these cases, you can leave it blank. This field is optional and if you have questions or concerns, reach out to your Customer Success Manager (CSM) or to support.
6. Click Save.

Your device should be created successfully within a few seconds. A few reminders:

• After your connection is healthy, it will take some time for your device to begin polling and receiving data.
• To check on the status, select the downward arrow for your device in the first column and choose View details.
• Polling will happen first; data will be received after that. You must refresh the page to see updates.
• If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, contact our support team for help.
• To check if alerts are coming through, navigate to Dashboards > Alert Analysis. Scroll to the device you want to check, and select the Expel Alerts tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we tune your device.