Repository navigation
Wazuh Deployment Guide
Wireless monitoring integration: For a practical end-to-end Kismet WIDS โ Wazuh agent โ custom severity rules โ dashboards lab, see the Kismet + Wazuh Wireless IDS Lab. It includes example scripts, JSON log paths and correlation tests; a wired VM interface cannot directly capture Wi-Fi management frames. For a complementary nzyme wireless sensor with native webhook forwarding, custom Wazuh rules and shared dashboards, see nzyme + Wazuh Integration.
Deception sensor integration: OpenCanary/Cowrie/DIY โ Wazuh supplies native JSON log sources, custom severity rules and dashboard guidance. Includes Pi, Proxmox, and ESP32-S3 deployment options. Correlate with wireless Kismet/nzyme using independent AP/client evidence.
Wazuh SIEM and XDR deployment guide - covering Wazuh manager installation, agent deployment across Windows/Linux, built-in detection rules, vulnerability assessment, compliance modules, and integration with ELK/OpenSearch.
Covers: Wazuh all-in-one installation, agent enrollment, rule customization, active response configuration, vulnerability detection, file integrity monitoring (FIM), compliance dashboards (PCI-DSS, GDPR, HIPAA, CIS), and Wazuh + OpenSearch/Elasticsearch integration.
Deploy Wazuh as a unified SIEM/XDR platform that combines log management, endpoint detection, vulnerability assessment, and compliance monitoring in a single open-source solution.
- Building a comprehensive SIEM/XDR stack for a homelab or small organization
- Needing compliance monitoring (PCI-DSS, CIS, GDPR) alongside threat detection
- Setting up endpoint agent-based monitoring across mixed Windows/Linux environments
- Purple team exercises requiring EDR-style endpoint telemetry
Wazuh is an open-source security platform providing unified XDR (Extended Detection and Response) and SIEM (Security Information and Event Management) capabilities. It monitors endpoints, detects threats, identifies vulnerabilities, and ensures compliance across your infrastructure.
This guide covers deploying the Wazuh Manager using Docker and installing agents on Windows and Linux endpoints.
| Component | Minimum | Recommended |
|---|---|---|
| OS | Ubuntu 20.04/22.04 LTS | Ubuntu 22.04 LTS |
| RAM | 4 GB | 8 GB |
| CPU | 2 vCPUs | 4 vCPUs |
| Storage | 50 GB | 100 GB+ |
- Docker Engine 20.10+
- Docker Compose 1.29+
Ensure the following ports are accessible on your Wazuh Manager:
| Port | Protocol | Purpose |
|---|---|---|
| 443 | TCP | Wazuh Dashboard (HTTPS) |
| 1514 | TCP | Agent communication |
| 1515 | TCP | Agent enrollment |
| 55000 | TCP | Wazuh API |
sudo apt update && sudo apt upgrade -y# Install dependencies
sudo apt install -y apt-transport-https ca-certificates curl gnupg lsb-release
# Add Docker GPG key
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
# Add Docker repository
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
# Install Docker
sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin
# Add your user to the docker group
sudo usermod -aG docker $USERLog out and back in for group changes to take effect, or run newgrp docker.
docker --version
docker compose versionNote
This guide pins Wazuh 4.7.0 for a known-good, internally consistent config.
The current line is 4.14.x (with 5.0 in beta) โ check the
Wazuh releases and
wazuh-docker releases before
deploying, since version bumps can change the compose files and default
settings used below.
git clone https://github.com/wazuh/wazuh-docker.git -b v4.7.0
cd wazuh-docker/single-nodeNote: Check Wazuh releases for the latest stable version and adjust the branch tag accordingly.
The Wazuh Indexer (OpenSearch) requires increased virtual memory limits:
# Apply immediately
sudo sysctl -w vm.max_map_count=262144
# Make persistent across reboots
echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.confdocker compose -f generate-indexer-certs.yml run --rm generatorThis creates self-signed certificates in the config/wazuh_indexer_ssl_certs/ directory.
docker compose up -dMonitor the startup process:
docker compose logs -fWait 2-3 minutes for all services to initialize. You'll see health checks passing in the logs.
docker compose psExpected output shows three healthy containers:
single-node-wazuh.manager-1single-node-wazuh.indexer-1single-node-wazuh.dashboard-1
Open your browser and navigate to:
https://<SERVER-IP>
Default Credentials:
- Username:
admin - Password:
SecretPassword
โ ๏ธ Security Warning: Change the default password immediately after first login via Settings โ Security โ Internal Users.
sudo ufw allow 443/tcp comment "Wazuh Dashboard"
sudo ufw allow 1514/tcp comment "Wazuh Agent Communication"
sudo ufw allow 1515/tcp comment "Wazuh Agent Enrollment"
sudo ufw allow 55000/tcp comment "Wazuh API"
sudo ufw reload
sudo ufw statussudo firewall-cmd --permanent --add-port=443/tcp
sudo firewall-cmd --permanent --add-port=1514/tcp
sudo firewall-cmd --permanent --add-port=1515/tcp
sudo firewall-cmd --permanent --add-port=55000/tcp
sudo firewall-cmd --reload- Log into the Wazuh Dashboard
- Navigate to Agents โ Deploy new agent
- Select Windows as the operating system
- Enter your Wazuh Manager IP address
- Optionally assign an agent name and group
- Copy the generated PowerShell command
Download from an elevated PowerShell prompt:
Invoke-WebRequest -Uri https://packages.wazuh.com/4.x/windows/wazuh-agent-4.7.0-1.msi -OutFile $env:TEMP\wazuh-agent.msimsiexec.exe /i $env:TEMP\wazuh-agent.msi /q WAZUH_MANAGER="<MANAGER-IP>" WAZUH_REGISTRATION_SERVER="<MANAGER-IP>" WAZUH_AGENT_NAME="<HOSTNAME>"Replace:
-
<MANAGER-IP>with your Wazuh server's IP address -
<HOSTNAME>with a descriptive name for this endpoint
NET START WazuhSvcGet-Service WazuhSvc| Item | Path |
|---|---|
| Installation Directory | C:\Program Files (x86)\ossec-agent\ |
| Configuration File | C:\Program Files (x86)\ossec-agent\ossec.conf |
| Log File | C:\Program Files (x86)\ossec-agent\ossec.log |
Debian/Ubuntu:
curl -s https://packages.wazuh.com/key/GPG-KEY-WAZUH | gpg --no-default-keyring --keyring gnupg-ring:/usr/share/keyrings/wazuh.gpg --import && chmod 644 /usr/share/keyrings/wazuh.gpg
echo "deb [signed-by=/usr/share/keyrings/wazuh.gpg] https://packages.wazuh.com/4.x/apt/ stable main" | tee /etc/apt/sources.list.d/wazuh.list
apt updateRHEL/CentOS:
rpm --import https://packages.wazuh.com/key/GPG-KEY-WAZUH
cat > /etc/yum.repos.d/wazuh.repo << EOF
[wazuh]
gpgcheck=1
gpgkey=https://packages.wazuh.com/key/GPG-KEY-WAZUH
enabled=1
name=EL-\$releasever - Wazuh
baseurl=https://packages.wazuh.com/4.x/yum/
protect=1
EOFDebian/Ubuntu:
WAZUH_MANAGER="<MANAGER-IP>" apt install -y wazuh-agentRHEL/CentOS:
WAZUH_MANAGER="<MANAGER-IP>" yum install -y wazuh-agentsystemctl daemon-reload
systemctl enable wazuh-agent
systemctl start wazuh-agentsystemctl status wazuh-agent| Item | Path |
|---|---|
| Installation Directory | /var/ossec/ |
| Configuration File | /var/ossec/etc/ossec.conf |
| Log File | /var/ossec/logs/ossec.log |
- Log into the Wazuh Dashboard
- Navigate to Agents
- Verify your agent appears with status Active
On the Windows agent, trigger a test alert by creating a test file:
# This simulates suspicious activity that Wazuh will detect
echo "test" > C:\Users\Public\eicar-test.txtOn Linux:
# Simulate a failed SSH login attempt
logger -t sshd "Failed password for invalid user admin from 192.168.1.100 port 22 ssh2"Check the Security Events section in the dashboard for corresponding alerts.
- Navigate to Settings โ Security โ Internal Users
- Select the
adminuser - Click Edit and set a new password
Groups allow you to apply specific configurations to sets of agents:
- Navigate to Management โ Groups
- Click Add new group
- Name the group (e.g.,
windows-servers,linux-workstations) - Assign agents to groups during deployment or via the dashboard
Edit the ossec.conf file on the agent to customize:
- Log collection sources
- File integrity monitoring paths
- Active response settings
After changes, restart the agent service.
Check agent logs:
Windows:
Get-Content "C:\Program Files (x86)\ossec-agent\ossec.log" -Tail 50Linux:
tail -n 50 /var/ossec/logs/ossec.logCommon issues:
- Firewall blocking ports 1514/1515
- Incorrect manager IP in agent configuration
- Certificate/enrollment issues
- Verify network connectivity:
ping <MANAGER-IP> - Test port accessibility:
nc -zv <MANAGER-IP> 1514 - Restart the agent service
- Check manager logs:
docker compose logs wazuh.manager
# Check container status
docker compose ps
# View dashboard logs
docker compose logs wazuh.dashboard
# Restart the stack if needed
docker compose restartIf an agent needs to be re-enrolled:
Windows:
NET STOP WazuhSvc
Remove-Item "C:\Program Files (x86)\ossec-agent\client.keys" -Force
# Re-run the enrollment command
NET START WazuhSvcLinux:
systemctl stop wazuh-agent
rm /var/ossec/etc/client.keys
# Re-run the enrollment
systemctl start wazuh-agentUpdate passwords for all internal users:
adminkibanaserverkibanaro
For production, replace self-signed certificates with certificates from a trusted CA or your internal PKI.
Edit the Wazuh API configuration to limit access by IP address or require client certificates.
Keep Wazuh components updated:
cd wazuh-docker/single-node
docker compose pull
docker compose up -d- Wazuh Documentation
- Wazuh GitHub Repository
-
Wazuh Ruleset (the standalone
wazuh-rulesetrepo is archived; rules now ship in the main repo) - Wazuh Slack Community
| Command | Purpose |
|---|---|
docker compose up -d |
Start the stack |
docker compose down |
Stop the stack |
docker compose restart |
Restart all containers |
docker compose logs -f |
Follow all logs |
docker compose ps |
Show container status |
| OS | Start | Stop | Status |
|---|---|---|---|
| Windows | NET START WazuhSvc |
NET STOP WazuhSvc |
Get-Service WazuhSvc |
| Linux | systemctl start wazuh-agent |
systemctl stop wazuh-agent |
systemctl status wazuh-agent |
Part of the Incident Response & Log Aggregation Branch
- ../README.md - IncidentResponse section index
- elk_stack.md - ELK Stack backend for Wazuh indexer
- splunk.md - Splunk as Wazuh SIEM alternative
- graylog.md - Graylog alternative
- ../Endpoint-Visibility/Windows/sysmon.md - Sysmon data source for Wazuh agents
๐ Source: IncidentResponse/SIEM/wazuh.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Incident Response
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics