Wazuh provides a pre-built virtual machine image (OVA) that you can directly import using VirtualBox (where installed) and other OVA compatible virtualization systems.
This VM only runs on 64-bit systems and is not recommended for use in production environments. It can be a useful tool for proofs of concept and labs. Distributed architectures and multi-node Elastic Stack clusters are usually a better fit for production environments where higher performance is required.
- This virtual appliance, available here, contains the following components:
- CentOS 7
- Wazuh 3.9.5
- Wazuh API 3.9.5
- Elasticsearch 7.3.0
- Filebeat 7.3.0
- Kibana 7.3.0
- Wazuh app 3.9.5-7.3.0
Import the OVA in your virtualization platform and run the virtual machine. The root password is “wazuh” and the username/password for the Wazuh API is “foo/bar”.
Although you don’t need to change any Elastic Stack configuration settings, feel free to explore the options. You can find Elasticsearch installed in
/usr/share/elasticsearch. Similarly, Filebeat is installed in
/usr/share/filebeatand its configuration file is found in
The Wazuh Manager and the Elastic Stack included in this virtual image are configured to work out of the box. The next step of the process is to deploy the Wazuh agents on the systems you intend to monitor. Once installed, connect them to your virtual appliance. More documentation can be found at:
Before connecting any of the Wazuh agents, change the VM’s network interface type from NAT (the factory default) to bridge for communication with your network. By default, the VM will try to get an IP address from your network’s DHCP server. Alternatively, you can set a static IP address by configuring the proper network files on the CentOS operating system that the virtual machine is based on.
You can start and stop wazuh-manager, wazuh-api, elasticsearch, filebeat, and kibana with the ‘systemctl’ command. For example:
# systemctl restart wazuh-manager # systemctl restart wazuh-api # systemctl stop elasticsearch # systemctl start filebeat # systemctl status kibana
In order to connect to the Kibana web user interface, login with https://OVA_IP_ADDRESS (where
OVA_IP_ADDRESSis your system IP).
If you need to update your OVA virtual machine, you can check out this article. We also recommend updating the repositories using the