Skip to content
Commitpedia
Log in Join & edit

Wazuh: an open source security platform with agents, SIEM and XDR

Wazuh installs a small agent on each server and sends its logs, file changes and package lists to a central manager that detects intrusions, checks configurations and reports vulnerabilities.

Drafted with AI from official documentation. Scripts were run in a test environment and repository links verified. Awaiting a human check. Did it work for you? Last edited Outdated?

Edit history of Wazuh: an open source security platform with agents, SIEM and XDR: 1 recorded edit
Edit history · 1 edit
Type
Repo
Edits
1
Editors
1
First issued
15 Oct 2026
Last edit
15 Oct 2026
Source
wazuh/wazuh

wazuh/wazuh

Stars
17.3k
Forks
2.5k
Language
C++
Licence
NOASSERTION
Last push
15 Oct 2026

On GitHub: Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.

Open on GitHub

Wazuh (about 17,000 stars on GitHub) is a free, open source security platform that combines host based intrusion detection, log analysis, file integrity monitoring, vulnerability detection and configuration assessment in one product. It began in 2015 as a fork of the older OSSEC project and is developed by Wazuh, Inc., a company that sells cloud hosting and support around the open source core. The main repository holds the agent and the manager written mostly in C and Python; the dashboard, indexer and installation packages live in sibling repositories under the same organisation.

What it does

The platform has three parts. A lightweight agent runs on each Linux, Windows or macOS machine and collects system logs, watches directories for file changes, lists installed packages and runs configuration checks. A central manager receives that data, matches it against several thousand built in rules, compares package versions with public vulnerability feeds and raises alerts. An indexer and dashboard, based on OpenSearch, store the events and present them in a web interface with views for security events, compliance standards such as PCI DSS and GDPR, and the MITRE ATT&CK catalogue of attacker techniques. Together this makes Wazuh both a host based intrusion detection system (HIDS) and a small SIEM, and the project describes the combination as XDR, extended detection and response.

Who it is for

  • Small and medium teams that want a complete security monitoring stack without a licence fee.
  • Administrators who already centralise logs and want detection rules, file integrity checks and vulnerability reports on top.
  • Organisations that need audit evidence for a compliance standard and want a tool that maps alerts to its controls.
  • People migrating from OSSEC who want an actively maintained successor with a web interface.

How to install it

The project publishes an all in one installer script that sets up the manager, indexer and dashboard on a single Linux server, plus packages and container images for larger deployments. The documentation also covers Docker Compose, Kubernetes and cloud marketplace images. A single server with four gigabytes of memory is enough to try it:

Check before you run this

  • Runs with administrator rights. Make sure you understand every line.
curl -sO https://packages.wazuh.com/4.x/wazuh-install.sh
sudo bash ./wazuh-install.sh -a

Agents are then installed from the dashboard, which generates the exact package command for each operating system. Read the quickstart before running the installer on a machine you care about, and plan for disk space, since the indexer keeps every event.

Credit

Wazuh is developed by Wazuh, Inc. and a community of contributors, and builds on the earlier OSSEC project by Daniel Cid. The code is released under the GNU General Public License version 2 with an OpenSSL exception; see the LICENSE file in the repository for the exact terms.

Did this work for you?

No votes yet. Be the first.

If it did not work, the report form below tells the editors what went wrong.

See also

  • 0193 Linux logs reference: journalctl, journald storage, logrotate and centralized logging Read and filter systemd journal logs, keep their disk use in check, rotate classic log files with logrotate, and understand when to… Intermediate · Cheat sheet · Linux Article Linux administration · Logs 15 Oct 2026
  • 0291 What is a log? A log is a running record of what a program did and when, written to a file so you can look back… Beginner · Explains an idea · Any system Article Logs 15 Oct 2026
  • 0323 Fix: Failed to start service, how to read systemctl status and journalctl Job for x.service failed tells you only that the service did not start. The real reason is in systemctl status and journalctl… Beginner · Fixes an error · Linux Article Logs · Services & systemd 15 Oct 2026
  • 0371 Where are the logs? journalctl, /var/log and container logs A practical map of where Linux programs write their logs and the commands to read them: journalctl filters, the classic files under… Beginner · Step by step · Linux Article Logs 15 Oct 2026
  • 0373 Loki: ship and search logs Run Loki, Grafana Alloy and Grafana with Docker Compose, collect the systemd journal and /var/log files with a short Alloy configuration, and… Intermediate · Step by step · Linux Article Logs 15 Oct 2026
  • 0432 Try Sigma rules against your own logs Install the sigma-cli converter, take a rule from the public SigmaHQ library, convert it into a query for a log tool you… Intermediate · Step by step · Linux, macOS Article Logs · Security resources & detection 15 Oct 2026

History

Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.

  1. Dominik +2,859 chars

Report a problem

Something wrong, unsafe or copied? Tell the editors.
What is wrong?