Skip to main content

Wazuh Cloud getting started guide

Sharon Burton
  • Updated

Tip

This article was accurate at the time of writing, but changes happen. If you find the instructions are outdated, leave a description in the comment field below and let us know!

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.

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 getting started guide.

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.

  1. Go to Open Distro for Elasticsearch > Security > Roles > Create > Role.

    mceclip0.png

  2. Create a role with these options:

    mceclip1.png
    mceclip2.png

    • 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.

    mceclip3.png

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

    mceclip4.png

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

    mceclip5.png

  6. Select the newly created user and click Save.

    mceclip6.png

  7. Go to Wazuh > Security > Roles mapping.

    mceclip7.png

  8. Create a new Role mapping with these options:

    mceclip8.png

    • 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 access and noted the credentials, we can integrate Wazuh with Workbench.

  1. In a new browser tab, log into https://workbench.expel.io.

  2. On the console page, navigate to Settings and click Security Devices.

  3. At the top of the page, click Add Security Device.

  4. Find and select your technology.

    mceclip10.png

  5. Type these details:

    mceclip9.png

    • Name: Friendly 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 enter the Elastic API address.

    • Is this a Wazuh cloud Instance?: y

  6. Click Save.

After a few minutes, refresh the Security Devices page and you see your device status reporting as Healthy, or if there is an issue, you see details of what the issue may be.

To check if alerts are coming through, navigate to Alerts on the console page. Click the icon in the upper right to switch to grid view, then check the list for device alerts.

Related articles

Comments

0 comments

Article is closed for comments.