EN PL

Wazuh in practice - from detection to response

Wazuh SIEM Dashboard - Security monitoring in a test environment

Tests in a private lab

In my private lab, I tested brute-force detection, file change monitoring and automated response using VirusTotal. The tests informed my thinking about deploying tools and preparing people to use them.

Tags: Wazuh / SIEM / FIM / VirusTotal Published: Updated: 4 min read

Project purpose and scope

I wanted to explore Wazuh as an open-source security monitoring solution. I was interested in which rules respond to simulated events and how detection can trigger an automated action. I used scenarios from the official documentation to test these mechanisms in my own environment.

Wazuh runs in an LXC container on Proxmox. The monitored environment includes two Windows systems and a Debian virtual machine. This is a private lab for learning and testing.

Wazuh running in an LXC container in Proxmox

Wazuh in an LXC container in my private Proxmox lab.

Three scenarios I tested

Detecting brute-force attempts

I performed brute-force attempts using Hydra, following the Wazuh scenario. The system detected the events and generated the corresponding alerts. This let me examine how failed authentication attempts appear in the system and which rules respond to them.

File integrity monitoring

I tested FIM by modifying a text file in a specified location. Wazuh detected the changes as configured. This simple, controlled test allowed me to connect my own action with the information reported by the system.

VirusTotal integration and automated response

I enabled VirusTotal integration and reproduced the documented scenario for detecting and automatically removing an EICAR test file. I checked the complete sequence: FIM detecting the file, obtaining a result from VirusTotal and the configured Active Response mechanism removing the file. The scenario worked in my environment.

The public VirusTotal API was sufficient for my lab tests. Business use, however, requires consideration of request limits, permitted uses and the cost of an appropriate integration plan.

Visibility of the monitored environment

The agent dashboard let me check which hosts were reporting to the system. This matters when interpreting results: an absence of events should not be assessed without checking whether data from that host is actually arriving.

Wazuh agents dashboard

Wazuh agent dashboard in the test environment.

Wazuh also displayed vulnerability findings. I treat these as a starting point for validation and analysis in the context of the asset. A vulnerability finding alone is not evidence of exploitation or an incident.

Wazuh vulnerability detection logs

Vulnerability findings as a starting point for further validation.

Results and limitations

I confirmed that three selected scenarios worked: brute-force detection, file change detection and VirusTotal integration with automated removal of a test file. I used existing scenarios from the documentation and verified their operation in my own configuration.

These tests do not measure overall detection effectiveness or establish production readiness. Their value was in tracing specific mechanisms from an event to an alert and, in one scenario, to an automated response.

Application to business

I also apply the lessons from this project to deploying other tools in an organisation. Selecting and installing a solution is the starting point. It then needs to be configured for its intended purpose, tested against expected scenarios, and supported by staff who are prepared to operate it and respond appropriately.

A successful deployment requires preparation of both technology and people. Beyond configuration and testing, this means a clear objective, time to learn the solution, access to knowledge and support. Training should prepare staff for the actual tasks and decisions they will face.

Staff should understand the information they receive, their responsibilities and how to proceed: when to act and when to escalate. Responsibility for deployment also includes providing the conditions needed to develop these skills.

Summary

For me, a successful deployment means that a solution works as intended and people can use it in their daily work. The lab allowed me to test selected technical mechanisms. In an organisation, these must be combined with staff competence and an agreed way of working.

Sources and documentation

Q&A: Wazuh

Does FIM remove files on its own?

FIM detects file changes. In this scenario, a separate Active Response mechanism removed the file after a result was obtained from VirusTotal.

Does this test prove effectiveness against every threat?

No. I confirmed that selected scenarios worked in my configuration. I did not measure detection across all threats or the false-positive rate.

Was this project useful?