1. Expel Help Center
  2. Connect Your Technology
  3. Endpoint Integrations
  4. Wazuh

Wazuh Cloud Setup for Workbench

By following these steps, you create a user account for Expel which keeps Expel activity separate from other activity on the Wazuh console.

Note
This guide is for cloud installations of Wazuh. For on-premises installations, see the Wazuh on-prem article.

In this article

Step 1: Get the Elastic API

  1. Ask Wazuh support (cloud@wazuh.com) to expose the Elastic API and allow list these 6 IPs:

    • 34.75.13.114

    • 34.75.152.7

    • 35.243.190.98

    • 104.196.158.205

    • 34.75.81.28

    • 34.75.210.18

  2. Write down the exposed Elastic API. Your API URL should be similar to https://<cloud_instance>.cloud.wazuh.com/api/elastic/. Notify your engagement manager if your URL doesn't end with the suffix /api/elastic.

Step 2: Create an account in Elastic

This step configures a user with a read-only role for Expel to access this API.

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. Go to Open Distro for Elasticsearch > Security > Roles > Create > Role.

  2. Create a role with these options:

    • Cluster Permissions: cluster_all.

    • Index Permissions: Add the index - * , with index permissions - search, get, read.

    • Tenant permissions: global_tenant with Read only.

  3. Go to the Mapped Users tab and select Create Internal User.

  4. Type a username and password for the new user and write them down.

  5. Go back to the Roles screen and click Map users.

  6. Select the newly created user and click Save.

  7. Go to Wazuh > Security > Roles mapping.

  8. Create a new Role mapping with these options:

    • Roles: readonly.

    • Internal users: select the newly created user from the list.

Step 3: Setup the archives index

This step sets up the Wazuh-archives index.

  1. Go to Wazuh > Management > Configuration > Edit Configuration.

  2. Change the logall_json setting to yes.

    <ossec_config>
  <ossec_config>
    <global>
      <jsonout_output>yes</jsonout_output>
      <alerts_log>yes</alerts_log>
      <logall>no</logall>
      <logall_json>yes</logall_json>
    </global>

  3. After you configure the archive, the archive file goes to cold storage. For investigative purposes, we want to query this index in real-time. The next step is to reach out to your Wazuh support team to change this index to hot storage. This is a change to the filebeat.yml file which must be done by the Wazuh cloud support team.

Step 4. 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. In a new browser tab, log into https://workbench.expel.io/settings/security-devices?setupIntegration=wazuh. You may be asked to log into Workbench.

  2. Fill out the form like this:

    mceclip9.png

    • Where is your device? Cloud.

    • Name: any name for the integration.

    • Location: Cloud.

    • Username: Username for the newly created user.

    • Password: Password for the newly created user.

    • Server address: type the Wazuh cloud server address.

      Note
      Do not type the Elastic API address.

    • Is this a Wazuh cloud Instance?: select Yes.

  3. Click Save.

  4. You can set up console access now or 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 5: 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.

  • Was this article helpful?

  • 0 out of 0 found this helpful

Related articles