Important

Exabeam is currently migrating all users from Exabeam Fusion SIEM to Exabeam Fusion New-Scale SIEM.

For the New-Scale SIEM version of this article, refer to Exabeam Fusion New-Scale SIEM setup for Workbench.

This article explains how to connect Exabeam Fusion SIEM to Workbench.

 

In this article

Step 1: Enable console access

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 requires a dedicated user account, which allows us to respond to security alerts and leverage the data available in Exabeam Fusion SIEM.

 

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.

Note

Expel secures all login information our SOC analysts need about your devices in an MFA password product. Access to this login information is protected using our internal MFA processes. To learn more about the IP addresses all Expel traffic comes from, go here.

  1. At the bottom of the homepage, navigate to Exabeam Admin Operations.

  2. Under the Exabeam User Management section select Users.

  3.  

    Click Add User.

  4. Type the following information for the fields:

    Field Name

    What to put in it

    User Type

    Local

    Username

    Expel

    Full Name

    Expel SOC

    Email

    This optional field can be left blank.

    Password

    Type a password. Save the password to enter later in the Workbench.

  5. For Role, select Tier 3 Analyst. If a custom role is preferred, complete the next 2 steps. Note the permission requirements. If you don't need a custom role, skip to Step 2 below.

  6. For a custom role, type Expel for Role Name and Expel Custom Role for Description.

  7. Select Advanced Analytics, and choose 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

 

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.

  1. Navigate to Settings > Admin Operations > Cluster Authentication Token.

  2. On the Cluster Authentication Token menu, click + to add a new token.

  3. In the Setup Token dialog box, fill in the Token Name, set Expiry Date to Permanent, and set the Permission Level(s) as Tier 3 Analyst.

  4.  

    Click Save.

  5. Copy the generated token for use in the next step.

Step 3: Configure the technology in Workbench

 

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

  1. Go to https://workbench.expel.io/settings/security-devices?setupIntegration=exabeam_fusion_siem.

  2. Complete all fields using the credentials and information you collected in Steps 1 and 2:

    ExabeamFusionSIEM_AddSecDev.png
    • (On-prem only) Select an Assembler from the list. If you have an assembler, select the assembler you set up in Getting Connected to Workbench.

    • Type Name (give your Exabeam a name).

    • Type the city or site where your Exabeam is located for Location.

    • Under Connection Settings, for Token type the token you generated in Step 2 and for Server Address type the IP address for Exabeam.

    • For Username and Password, use the information you created in Step 1.

  3.  

    Click Save.

  4. You can provide console access now or set it up later. Use the instructions below to set it up later.

 

You can see if the device is healthy on the Security Devices page. It may take a few minutes to see the device listed as healthy.

To check if alerts are coming through, navigate to the Alerts Analysis page. Scroll to the device you want to check and click View alerts. Switch to grid view, then check the list for device alerts. It can take 36 to 72 hours for alerts to appear after setup, as we tune your device.

 

Step 4: Edit the device to add console access

 

Expel needs console access to your device to allow our SOC analysts to dig deeper during incident investigations. Additionally, our engineering teams use this access to investigate potential health issues, including proper alert ingestion.

Note

Expel secures all login information our SOC analysts need about your devices in an MFA password product. Access to this login information is protected using our internal MFA processes. To learn more about the IP addresses all Expel traffic comes from, go here.

  1. Open Workbench. Go to Organization Settings > Security Devices. Next to the device you just connected, click the down arrow and click Edit.

  2. In the Console Login area, type these details:

    • Console URL: type the console URL from the Server address in the Connection Settings area above. At the end of the URL, type /login.

    • Username: type the user name you created above.

    • Password: type the password you created above.

    • 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 engagement manager or to support.

  3.  

    Click Save.

Tip

This page was accurate at the time of writing, but changes happen. If you find the instructions are outdated, let us know via your engagement manager or account representative.