ERROR DEXby Akshay kumar
STUDY MODE / TOOLS / WAZUH
DEFENSIVE · HIDS / XDR

Wazuh

Wazuh watches every endpoint: file changes, logins, processes, registry keys, vulnerabilities. It is an open-source HIDS/XDR that turns "something changed on that server" into an alert with a rule ID.

File Integrity Monitoring is the core: it hashes watched paths and alerts when they change — the fastest way to catch a webshell.
Rule IDs tell the story. 550/553 = authentication, 1002 = unknown process, 510 = rootkit. Learn the common ones.
It is host-based. It sees inside the machine, not the network — pair it with Suricata for the wire.
HOW TO USE IT → WHY IT MATTERSCOMMANDS HOW IT WORKSMISTAKES
LICENCEOpen source (GPLv2)
PLATFORMLinux · Windows · macOS · containers
ARCHITECTUREAgent + Manager + Indexer
DATAFIM · logs · SCA · vulnerabilities

What it is

Wazuh is a host-based intrusion detection system that grew into an extended detection and response platform. An agent runs on each endpoint, collecting log data, file hashes, running processes and configuration state. The manager receives that data, decodes it, and applies decoders and rules. The indexer (OpenSearch) stores it and the dashboard visualises it.

Three capabilities matter most in practice: FIM (file integrity monitoring) alerts on changes to files you care about, log analysis applies rules to syslog, Windows events and application logs, and SCA (security configuration assessment) scores the host against CIS benchmarks.

WALKTHROUGH

How to use Wazuh

Follow it exactly as you would in a real session — every command, every line of output, and what each result actually tells you. This is a interface walkthrough.

01

Confirm the agent is actually reporting

WAZUH DASHBOARD · AGENTS
AgentsFIMSecurity eventsSCA
001 web-01 · Active · v4.9.0
002 db-01 · Disconnected · last seen 3h ago
WHAT THIS MEANSA disconnected agent is a blind spot — you are not monitoring that host, you just think you are. Alert on agents that stop reporting before you trust any "no alerts" dashboard.
02

Configure file integrity monitoring on what matters

AGENT CONFIG · ossec.conf
syscheck /var/www/html · check_all=yes · realtime
syscheck /etc · check_all=yes
syscheck /root/.ssh · check_all=yes
frequency 300 seconds
WHAT THIS MEANSWatch specific paths, not the whole filesystem. Web roots catch webshells, /etc catches configuration tampering, /root/.ssh catches persistence.
03

Read a real FIM alert

ALERT · RULE 550 · LEVEL 7
File /var/www/html/uploads/shell.php
Change new file · size 132 bytes
MD5 9f2c1a7b3e5d4c6a8b0e1f2d3c4b5a69
Mode realtime
WHAT THIS MEANSA new PHP file in an uploads directory, in realtime, is a webshell until proven otherwise. This single alert type catches the most common web compromise path.
04

Search across agents for the same file

THREAT HUNTING · DASHBOARD SEARCH
Query rule.id:550 AND syscheck.path:*uploads*
Hits 3 agents · web-01, web-02, staging
WHAT THIS MEANSOne alert becomes a hunt: if the same file appeared on three web servers, this was not a one-off upload — it was a campaign. That is what turns host monitoring into incident response.

Flags & options

FLAGWHAT IT DOES
rule.level >= 10Start with high-severity alerts only.
rule.id:550File integrity: checksum changed.
rule.id:553File integrity: file deleted.
rule.id:5712SSH brute force detected.
syscheck.pathFilter by watched path.
data.srcipFilter by source IP.
agent.nameFilter by host.
Active responseAutomatic block or isolate — test in a lab first.
SCACIS benchmark scoring per host.

Why it matters

Network sensors miss what happens inside an encrypted connection. Wazuh sees the host: a new file in /var/www/html, a user added to sudoers, a service restarted at 3 AM. For a small team without a commercial EDR, it is the highest-value defensive deployment available — and it is free.

How it works

Each agent collects three kinds of data: log lines, file hashes for watched paths, and system state. It ships them to the manager, which runs decoders to pull fields out and rules to decide whether the event matters. Each alert carries a rule ID and a severity level.

File integrity monitoring works by hashing every watched file on a schedule (and in real time where supported). When a hash changes, the manager compares it against the baseline and raises rule 550 with the old and new checksums.

ENDPOINT AGENTFIM · logsENDPOINT AGENTWindowsENDPOINT AGENTcontainersMANAGERdecoders + rulesINDEXEROpenSearchALERTSrule id · levelDASHBOARDvisualiseACTIVE RESPONSEblock · isolate
Agents collect → manager decodes and applies rules → indexer stores → dashboard and active response act

Commands & syntax

FIM CONFIGURATION
# /var/ossec/etc/ossec.conf on the agent — watch what matters
<syscheck>
  <directories check_all="yes" report_changes="yes">/var/www/html</directories>
  <directories check_all="yes">/etc</directories>
  <directories check_all="yes">/root/.ssh</directories>
  <frequency>300</frequency>
</syscheck>
SEARCH THE ALERTS
# in the dashboard, or directly in the indexer
rule.level >= 10

# authentication failures
rule.id: (550 OR 553) AND data.srcip: *

# file added in the web root
rule.id: 550 AND syscheck.path: /var/www/html/*
AGENT MANAGEMENT
# on the manager
/var/ossec/bin/agent_control -l
/var/ossec/bin/agent_control -i 001

# on the agent
/var/ossec/bin/wazuh-control status
ACTIVE RESPONSE (LAB FIRST)
# block an IP for 10 minutes after repeated auth failures
<active-response>
  <command>firewall-drop</command>
  <location>local</location>
  <rules_id>5712</rules_id>
  <timeout>600</timeout>
</active-response>
KALI LINUX
root@wazuh-manager:~# grep -i "integrity" /var/ossec/logs/alerts/alerts.log | tail -6

** Alert 1775000001.88123: - ossec,syscheck,
2026-11-14T09:41:02+05:30  (manager) 10.0.0.5->syscheck
Rule: 550 (level 7) - Integrity checksum changed.
File: /var/www/html/uploads/shell.php
New size: 132
Old md5sum: d41d8cd98f00b204e9800998ecf8427e
New md5sum: 9f2c1a7b3e5d4c6a8b0e1f2d3c4b5a69
Mode: realtime

# A new PHP file appeared in the uploads directory.
# uploads/ + .php + realtime = webshell until proven otherwise.
# This is the alert that matters most in a typical web compromise.

Common mistakes

Watching the entire filesystem

You will generate thousands of alerts a day and stop reading them. Watch specific paths.

Alerting at every level

Start at level 10+, tune down once you have a baseline.

Deploying active response without testing

Auto-blocking can lock out administrators or break applications.

Treating Wazuh as a network sensor

It sees the host. Use Suricata or Zeek for traffic.

Ignoring agent health

A disconnected agent is a blind spot. Alert on agents that stop reporting.

No baseline period

Without knowing normal, every alert looks like an incident.

Practice safely

Deploy the Wazuh OVA or the all-in-one installer in a VM, add a second VM as an agent, and trigger your own alerts: change a watched file, fail an SSH login five times, and watch the rule IDs appear. TryHackMe has a Wazuh room.

Legal note. Only use Wazuh on systems you own or have explicit written permission to test. In India, unauthorised access is punishable under sections 43 and 66 of the IT Act, 2000. Every example on this page assumes a lab environment.

Related