Wazuh SIEM is an open-source security tool that collects logs and security events from many servers and puts them in one place. It helps teams see what is happening across their systems, spot suspicious activity, and get alerts when something looks wrong. This tutorial from PerLod Hosting will show you how to configure Wazuh SEIM for VPS Infrastructure.
Wazuh is useful because a VPS setup often has many small servers that are easy to miss if checked one by one. With Wazuh, each VPS can send key data like system logs, login activity, and important file changes to a central server, so problems can be found faster and handled sooner.
Prerequisites To Configure Wazuh SEIM for VPS Infrastructure
This guide shows you how to install Wazuh on a VPS, add other VPS servers as agents, and enable key security features like file integrity monitoring and vulnerability scanning.
Before starting the Wazuh SEIM setup, ensure you have the following requirements.
Hardware Requirements
For an all-in-one Wazuh deployment monitoring up to 100 VPS servers:
Minimum: 4 vCPU, 8 GB RAM, 50 GB disk space.
Recommended: 8 vCPU, 8 GB RAM, 100-200 GB disk space (SSD is recommended).
Operating System
One VPS for the Wazuh SIEM server running:
Ubuntu 16.04, 18.04, 20.04, 22.04, or 24.04
Or CentOS Stream 10, RHEL 7-10
In this guide, we use Ubuntu 24.04 to show you the steps.
Access Requirements
Root or sudo access on all servers.
SSH access to all VPS instances.
Basic familiarity with the Linux command line.
For this tutorial, the Wazuh SIEM server and all monitored nodes are deployed on PerLod VPS Hosting.
1. Install Wazuh SIEM Server (All-in-One)
We want to install Wazuh all-in-one, including server, indexer, and dashboard. To do this, you must run the system update and upgrade to install the latest security updates and patches on your system:
Bash
sudoaptupdate&&sudoaptupgrade-y
Then, use the curl command to download the official Wazuh installation script:
Now that you have set up Wazuh SEIM and configured the network access, you can access the dashboard. To do this, open your desired web browser and navigate to:
HTML/XML
https://YOUR_WAZUH_SERVER_IP:443
Replace YOUR_WAZUH_SERVER_IP with your VPS public IP address.
Warning: Your browser will show a security warning because Wazuh uses a self-signed SSL certificate. Safely click Advanced and proceed to the site.
You will see the login screen, enter the credentials you got from the Wazuh installation:
Username: admin
Password: password shown during installation.
If you lost the password, you can use the command below to get it:
In this step, you must install the Wazuh agents on the VPS servers you want to monitor. On each VPS you want to monitor, you must add the Wazuh repository.
In Ubuntu and Debian systems, you can use the following command to download Wazuh's GPG signing key:
Run the system update and install the Wazuh Agent package:
Bash
sudoaptupdatesudoaptinstallwazuh-agent-y
This downloads and installs the Wazuh agent software, which will monitor this VPS and send security events to the Wazuh manager.
Configure Wazuh Agent to Connect to Manager
After Wazuh agent installation, you must configure it to connect to the Wazuh manager or server. To do this, open the Wazuh agent main config file with the command below:
Bash
sudonano/var/ossec/etc/ossec.conf
In the file, find the client section and update the address field with your Wazuh manager IP:
You should see an alert showing that the new file was detected.
6. Enable Vulnerability Detection in Wazuh Manager
Vulnerability detection scans installed software packages on agents and compares them against CVE databases to identify known security flaws. To enable this option, follow the steps below.
On the Wazuh manager VPS, edit the following file:
Bash
sudonano/var/ossec/etc/ossec.conf
Find the vulnerability-detection section and ensure it is enabled:
This loads the new configuration and begins vulnerability scanning. After 10-15 minutes, check the dashboard:
Navigate to Threat detection and response, Vulnerabilities.
Select an agent from the list.
View detected vulnerabilities categorized by severity, such as Critical, High, Medium, and Low.
Verification and Troubleshooting Wazuh SEIM
At this point, you can confirm that each agent is connected to the manager, confirm the network path is open on the required ports, and then use logs to quickly identify the exact error.
To list all added agents with their ID, name, IP address, and status, you can run the command below from the Wazuh manager:
Bash
sudo/var/ossec/bin/agent_control-l
Also, you can check the agent status on the agent itself:
Firewall rules on both the manager and the agent VPS.
Security group rules if using a cloud VPS.
Network routing between VPS instances.
To review logs for errors, you can use the commands below:
Bash
#On the Wazuh manager:sudotail-50/var/ossec/logs/ossec.log#On agents:sudotail-50/var/ossec/logs/ossec.log
Security Best Practices: Wazuh SEIM VPS Setup
This step focuses on running Wazuh safely and smoothly in a real VPS environment, where public IP exposure, limited resources, and fast growth can create security and stability risks. The goal is to reduce attack surface, keep agent traffic private when possible, and make sure updates and backups are planned.
Security Recommendations:
1. Restrict dashboard access: Only allow access from admin IPs.
Bash
sudoufwallowfromYOUR_ADMIN_IPtoanyport443
2. Use private networking: If your VPS provider supports private networks, configure agents to connect via private IPs to avoid exposing agent traffic on the public internet.
3. Regular updates: Schedule maintenance windows to update Wazuh components following the official upgrade guide.
4. Backup configuration: Regularly back up /var/ossec/etc/ directory and the wazuh-install-files.tar file.
Performance Tuning: For larger VPS (100+ agents), consider:
Increase manager resources: 8+ vCPU, 16 GB RAM.
Separate components: Deploy indexer, server, and dashboard on separate VPS instances.
Adjust agent reporting interval: Reduce frequency for less critical systems.
1. Monitor disk usage: Wazuh indexes consume disk space over time.
Bash
df-h/var/ossec
2. Set up index rotation: Configure automatic deletion of old indices in the dashboard settings.
3. Configure email alerts: Set up SMTP integration to receive critical alerts via email.
4. Create custom rules: Set up Wazuh rules for your specific VPS applications and threats.
Conclusion
At this point, you have a fully functional Wazuh SIEM deployment monitoring your VPS infrastructure. This setup provides:
Centralized log aggregation from all monitored VPS servers.
Real-time threat detection through rule-based analysis.
File integrity monitoring to detect unauthorized changes.
Vulnerability scanning to identify CVE exposures.
Compliance monitoring for regulatory frameworks.
Security dashboards for visualization and reporting.
We hope you enjoy this guide on Configuring Wazuh SEIM for VPS Infrastructure. Subscribe to our X and Facebook channels to get the latest updates and articles.
For monitoring up to 100 agents, you need at least 4 vCPU, 8 GB RAM, and 50 GB disk space. For better performance, use 8 vCPU, 8 GB RAM, and 100-200 GB SSD storage.
You need to open port 1514 (TCP) for agent communication, port 1515 (TCP) for agent registration, port 443 (TCP) for dashboard access, and optionally port 55000 (TCP) for the Wazuh API.
Common causes include a firewall blocking ports 1514/1515, an incorrect manager IP in the agent's ossec.conf file, network routing issues, or security group rules blocking traffic. Use nc -zv MANAGER_IP 1514 to test connectivity.
We use cookies to run PerLod and to understand how the site is used. You can accept everything, or open Manage to turn individual categories off. Cookie policy.