1. Expel Help Center
  2. Connect Your Technology
  3. D-J Integrations

Elastic Security (SIEM) Setup for Workbench

This article helps you connect your Elastic Security (SIEM) installation with the Expel Workbench.

Quick Start

Step 1: Enable Console and API 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. For more information, see Why Expel Asks for Console Access.

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. 
  1. Open Kibana and use the User Creation Wizard to to create a user for Expel with a role that grants Read privileges to the Indices that host your security logs. For instructions, see: https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html#security-create-roles
  2. Make note of the Username and Password for later use.

Step 2: 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. Log in to Workbench.
  2. In the side menu, navigate to Organization Settings > Security Devices. If you have multiple organizations, you must select the appropriate organization name from the list.
  3. Select Add Security Device.
  4. In the search box, enter “Elastic” and then select the Elastic Security (SIEM) integration.
  5. For Where is your device? select Cloud or On-prem.
  6. Fill in the other fields like this:
    1. For Assembler, select your Assembler from the list. (On-prem only.)
    2. For Name and Location, type in a unique name and describe the general physical location of the server.
    3. For Username and Password, type in the credentials you created in Step 1.
    4. For Server address, copy/paste the Elastic Security endpoint. Be sure to use the Elastic Security endpoint and not the Kibana endpoint.
    5. For Index, enter: .alerts-security.alerts-default
  7. Click Save.
  8. 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 3: Edit the Device to Add Console Access

  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.

Related articles