(Latest wazuh_branch="4.14.4")
This project demonstrates the deployment of a Wazuh SIEM (Security Information and Event Management) system in a lab environment.
The lab simulates a real-world security monitoring setup where:
- Logs are generated on an endpoint
- Collected by an agent
- Sent to a SIEM
- Analyzed and visualized in a dashboard
Wazuh is an open-source security platform that provides:
- Log Analysis
- Host-based Intrusion Detection System (HIDS)
- File Integrity Monitoring (FIM)
- Malware Detection
- Compliance Monitoring
| Component | Role |
|---|---|
| Kali Purple | Wazuh SIEM Server |
| Kali Linux | Endpoint (Victim System) |
| Wazuh Manager | Log analysis |
| Wazuh Agent | Log collection |
| Wazuh Indexer | Data storage |
| Wazuh Dashboard | Visualization |
| Resource | Minimum | Recommended |
|---|---|---|
| Disk | 50 GB | 100+ GB |
| RAM | 8 GB | 16 GB |
| CPU | 2 vCPU | 4 vCPU |
This lab using 16GB and 4 processors for kali purple & 8GB and 2 processors for kali linux
Take VM snapshots before starting to allow rollback.
sudo apt update && sudo apt upgrade -yOn Kali Purple:
sudo hostnamectl set-hostname wazuh-siem
# also change old host name in editor: sudo nano /etc/hosts -> then change old host name to new.On Kali Linux:
sudo hostnamectl set-hostname victim-endpoint
# also change old host name in editor: sudo nano /etc/hosts -> then change old host name to new.Verify:
hostnameping <target_ip>Both systems must communicate successfully.
sudo apt install -y curl apt-transport-https lsb-release gnupg2
sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
sudo apt install -y chrony
sudo systemctl enable chrony
sudo systemctl start chrony
##Verify-
timedatectl
#- Install UFW if not present (ufw is a simple firewall manager)
sudo apt install -y ufw
sudo ufw allow 1514/tcp
sudo ufw allow 1515/tcp
sudo ufw allow 443/tcp
sudo ufw allow 55000/tcp
sudo ufw enable
Download Installer (check for latest branch [https://documentation.wazuh.com/current/quickstart.html])
curl -sO https://packages.wazuh.com/4.14/wazuh-install.sh
chmod +x wazuh-install.shsudo ./wazuh-install.sh -a
# Installation time: ~10β20 minutes, depending on system specs.
--At the end of the successful installation, the terminal will give a dashboard URL, including username and password to access the Wazuh dashboard. Save the credentials in a text file (or) in a nano text file.--
- nano wazuh-creds.txt
sudo systemctl status wazuh-manager
sudo systemctl status wazuh-indexer
sudo systemctl status wazuh-dashboardAll services should be active and running.
https://<YOUR_IP>
Login using generated credentials.
Navigate in dashboard:
1. Agents Management β Deploy New Agent
2. Select Operating System and pakage
To check the system specs of linux based system:
- Check Distribution pakage: cat /etc/os-release
- Check Architecture: uname -m
3. Enter Agent name (Example: victim-endpoint)
4. Copy the Generated Command
5. Paste and Run the Command on Kali linux (Victim system) to install the agent.
Agent Deployment Page
Running generated command on kali linux
sudo systemctl daemon-reload
sudo systemctl enable wazuh-agent
sudo systemctl start wazuh-agentsudo systemctl status wazuh-agent
Confirm agent appears in dashboard.
#(Troubleshooting notes)
https://github.com/siddhesh-001/Wazuh-SIEM-Lab/blob/main/Project%20Notes%20(troubleshooting_steps_ssh_alerts_hidden)
#(Test Results)
https://github.com/siddhesh-001/Wazuh-SIEM-Lab/blob/main/Test_Results_WAZUH/ssh-brute-force.mdWazuh rates every alert from Level 0 to Level 15
Open the dashboard β go to Security Events Click on any alert to expand it
| Level Range | Severity | Example Event |
|---|---|---|
| 0β3 | Informational | System startup, successful login |
| 4β7 | Low | Single failed login attempt |
| 8β11 | Medium | Multiple failed login attempts |
| 12β14 | High | Brute-force attack detected |
| 15 | Critical | Rootkit or system takeover |
This project demonstrates:
- SIEM deployment and configuration
- Log collection and analysis pipeline
- Endpoint monitoring using agents
- Security event detection workflow
- SOC-style investigation process