Cybersecurity
Wazuh SIEM: An Open-Source Security Monitoring Guide
Published on 22 September 2026 | 10 min read
Commercial SIEM platforms can be powerful, but their licence costs put them out of reach for many Malaysian SMEs, universities and smaller agencies. That is a big part of why Wazuh has become one of the most widely deployed open-source security monitoring platforms.
This guide explains what Wazuh is, how its architecture fits together, what it can monitor, how it compares with commercial options, and what a realistic implementation looks like. If you are new to the concept of SIEM itself, start with our complete guide to SIEM.
What is Wazuh SIEM?
Wazuh is a free, open-source security platform that combines SIEM capabilities (log collection, analysis, correlation and alerting) with endpoint security features such as file integrity monitoring, vulnerability detection and configuration assessment. The project describes itself as a unified XDR and SIEM platform.
The software is released under the GPLv2 licence, so there is no licence fee to download, install or run it. Wazuh Inc. also offers a paid hosted version (Wazuh Cloud) and commercial support for organisations that prefer not to run the infrastructure themselves.
Understanding Wazuh architecture
A Wazuh deployment has four main components.
Wazuh agent
A lightweight agent installed on the systems you want to monitor. Agents are available for Windows, Linux and macOS, along with several Unix platforms. The agent collects logs and system data, runs local checks such as file integrity and configuration assessment, and sends events securely to the server.
Wazuh server
The server receives data from agents and other sources, decodes it, and evaluates it against detection rules. When a rule matches, the server generates an alert. The server also manages agent enrolment and configuration, and can trigger automated responses.
Wazuh indexer
The indexer stores and indexes alerts and events so they can be searched quickly. It is a full-text search and analytics engine designed to scale across multiple nodes.
Wazuh dashboard
The web interface for searching events, investigating alerts, viewing dashboards and managing the deployment.
For small environments, all four components can run on a single server. As data volume and the number of agents grow, the server and indexer are typically split across multiple nodes for performance and resilience.
Key security features of Wazuh
Log collection and analysis
Wazuh collects operating system logs, application logs and syslog from network devices, then decodes and analyses them against a large built-in rule set. Custom decoders and rules handle formats the defaults do not.
File integrity monitoring
File integrity monitoring (FIM) watches selected files and directories and alerts when they are created, modified or deleted. Typical targets include system binaries, configuration files, and web application directories where an unexpected new PHP file can be a sign of a web shell.
Vulnerability detection
Wazuh inventories installed packages on monitored systems and compares them against vulnerability data to flag software with known CVEs.
Security configuration assessment
Security configuration assessment (SCA) checks systems against hardening policies, for example CIS benchmarks, and reports where configuration falls short.
Threat detection
Rules cover common attack patterns such as brute-force logins, privilege escalation and suspicious processes, with many rules mapped to MITRE ATT&CK techniques. Active response can take automated actions, such as blocking an IP address after repeated authentication failures.
Security dashboards and reporting
The dashboard includes views for security events, integrity monitoring, vulnerabilities and configuration assessment, plus modules that map alerts to frameworks such as PCI DSS and NIST 800-53 to support (not replace) audit work.
Wazuh SIEM architecture for Malaysian organisations
A typical deployment follows this flow:
- Endpoints, servers and applications generate events.
- Wazuh agents and log integrations (syslog, cloud APIs) collect them.
- The Wazuh server decodes events and evaluates rules.
- The Wazuh indexer stores alerts and events for search.
- The Wazuh dashboard presents them to analysts.
- Security analysts or IT administrators investigate and respond.
When designing this, a few practical points matter more than the diagram:
- Secure transport. Agent traffic is encrypted, but you still need firewall rules that only allow agents to reach the server on the required ports, and TLS for the dashboard.
- Access control. Limit who can log in to the dashboard, use individual accounts, and restrict administrative roles.
- Storage sizing. Estimate events per day and retention period up front. Storage is usually the component that grows fastest.
- Backup. Back up configuration, custom rules and decoders, and decide whether indexed data itself needs backup or can be rebuilt.
- High availability. For critical environments, plan multi-node indexer and server clusters so a single failure does not stop monitoring.
Deploying Wazuh on-premises vs cloud
| Factor | On-premises | Cloud (self-managed VMs or Wazuh Cloud) |
|---|---|---|
| Infrastructure ownership | You own and operate the servers | Cloud provider or Wazuh hosts the infrastructure |
| Operational responsibility | Full: OS, upgrades, storage, backups | Shared; less with Wazuh Cloud |
| Scalability | Limited by hardware you buy | Scale up or out more easily |
| Data residency | Data stays in your data centre | Depends on the region chosen; confirm it meets your policy |
| Maintenance | Your team patches and upgrades | Reduced with a managed service |
| Cost considerations | Up-front hardware, then staff time | Ongoing subscription or VM and storage charges |
For government agencies and organisations with strict data-residency policies, on-premises or a Malaysian cloud region is often the starting point. Smaller organisations without spare infrastructure staff may prefer a managed option.
Integrating Wazuh with Laravel applications
Many Malaysian organisations run business systems built in Laravel. Those applications know things the operating system does not: which user logged in, who changed a role, who exported a report. Getting that into Wazuh makes monitoring far more useful.
Laravel authentication logs
Log successful and failed logins, password resets and MFA events from the
application. Laravel fires authentication events such as Login, Failed
and PasswordReset that a listener can write to a dedicated security log.
Nginx security logs
Wazuh decodes common web server access and error logs, so it can detect patterns like scanning, repeated 404s on admin paths, or SQL injection attempts in query strings.
Linux server monitoring
The agent on the application server covers SSH logins, sudo usage, package
changes, and integrity monitoring of the application directory and .env
file.
Administrative activity monitoring
Role changes, permission grants, user deletion, bulk exports and configuration changes inside the application are high-value events. They should be logged deliberately, with the acting user, target and IP address.
Custom Wazuh detection rules
The cleanest approach is to write security events as one JSON object per
line to a separate log file, for example storage/logs/security.log, and
configure the Wazuh agent to read it with log_format set to json. Wazuh
can then decode the fields directly, and custom rules in local_rules.xml
can match on them, for example alerting at high severity when event is
role.granted and role is admin.
This does require work on both sides: the application must log the right events in a consistent format, and the rules must be written and tested. Wazuh will not understand custom application events on its own.
Wazuh vs commercial SIEM platforms
| Area | Wazuh | Typical commercial SIEM |
|---|---|---|
| Licence | Free and open source | Licence or subscription, often based on data volume |
| Endpoint features | FIM, vulnerability detection, SCA included | Varies; often separate EDR products |
| Analytics | Rule-based correlation, good search | Often more advanced analytics and UEBA |
| Support | Community, or paid from Wazuh | Vendor support included |
| Effort to run | Higher: you tune and maintain it | Lower for SaaS, still needs tuning |
Wazuh is not “the same thing for free”. You trade licence cost for engineering effort. For many organisations that is a good trade; for others, a managed commercial service makes more sense.
Wazuh implementation challenges
Alert noise
Default rules generate many low-severity alerts. Without tuning, analysts drown in noise and stop looking.
Storage and retention
Indexed data grows every day. Retention policies and index lifecycle management need to be configured, not left to fill the disk.
Rule tuning
Rules need adjusting to your environment so normal behaviour does not trigger alerts and important behaviour does.
Monitoring coverage
Agents must be deployed and kept running on every system that matters, and log sources must be confirmed as actually arriving.
Operational staffing
Someone must review alerts, maintain the platform and apply upgrades. Our article on SIEM vs SOC covers how organisations structure that work.
Recommended Wazuh implementation phases
- Infrastructure assessment. Inventory systems, estimate log volume and retention needs, confirm data-residency requirements.
- Architecture design. Choose single-node or clustered deployment, sizing, network placement and access control.
- Pilot deployment. Install the platform and connect a small set of critical servers.
- Agent and log integration. Roll out agents, syslog sources and application logs in waves.
- Detection rule configuration. Tune default rules and add custom rules for your applications.
- Dashboard implementation. Build views that match what your team and management need to see.
- Testing and handover. Simulate key scenarios, confirm alerts fire, document procedures and train the team.
Frequently asked questions
Is Wazuh free?
The software is free and open source. You still pay for the servers or cloud resources it runs on, the storage it uses, and the people who operate it. Wazuh Cloud and commercial support are paid options.
Is Wazuh a SIEM or XDR?
Both, in practice. It provides SIEM functions (log analysis, correlation, alerting) and endpoint capabilities associated with XDR (integrity monitoring, vulnerability detection, active response).
Can Wazuh monitor Windows and Linux?
Yes. Agents are available for Windows, Linux and macOS, and network devices can send logs via syslog.
Can Wazuh monitor Laravel applications?
Yes, if the application logs the right security events and Wazuh is configured to read them. Structured JSON logs and custom rules give the best results.
Does Wazuh require a dedicated server?
For anything beyond a test, yes. The indexer in particular needs adequate memory and fast storage. Size it based on the number of agents and your expected event volume.
Is Wazuh suitable for universities?
It is a common choice in education because of the licence model, but universities face specific challenges such as decentralised IT and many campuses. We cover that in SIEM for universities.
Conclusion
Wazuh gives Malaysian organisations a capable, licence-free route into security monitoring, with endpoint features that many commercial SIEMs sell separately. The trade-off is that you own the engineering: sizing, tuning, integrations and day-to-day operation. Organisations that plan for that work, start with a focused pilot, and invest in good application logging tend to get real value from it. For budgeting, see our guide to SIEM implementation cost.
Exploring Wazuh for your organisation?
Tarsoft builds Laravel systems and manages the Linux servers they run on, so we understand both sides of application security logging. If you are planning a Wazuh deployment, or need an existing system to log security events Wazuh can use, talk to our team. Government agencies can request a quotation directly.
References
- Wazuh documentation: documentation.wazuh.com
- MITRE ATT&CK: attack.mitre.org
- CIS Benchmarks: cisecurity.org
- OWASP Logging Cheat Sheet: cheatsheetseries.owasp.org
- #Wazuh
- #SIEM
- #Cybersecurity
- #Security Monitoring
- #Malaysia