Freddy Flores

show wazuh-lab

Wazuh SOC Home Lab

I built a Wazuh monitoring lab, created a custom process-detection rule, and verified alerts for failed logons and file changes on Windows.

Completed learning project
Technologies
Wazuh, Sysmon, Windows Event Logs, Ubuntu Server, KVM/QEMU, File integrity monitoring
Source code
View on GitHub

Explore the full project on GitHub ↗Setup notes, lab journal, and original evidence.

Wazuh SOC Home Lab — completed security monitoring learning project.

What I built

I built a local monitoring environment with an Ubuntu Wazuh server and a Windows 11 endpoint on KVM/QEMU. I followed harmless, controlled activity from Windows logs into Wazuh, investigated the alerts, and documented what the evidence actually showed.

The defined learning project is complete: Windows monitoring, custom process detection, failed-logon investigation, and file integrity monitoring.

Key results

  • Custom detection: connected Sysmon, wrote Wazuh rule 100100 for whoami.exe, and verified a live alert with the executable, user, and parent process.
  • Authentication investigation: traced three deliberate failed logons through Windows event 4625 and Wazuh rule 60122. I confirmed expected local test activity rather than assuming an attack.
  • File integrity monitoring: configured a lab folder for real-time monitoring and verified alerts for file creation, modification, and deletion, including changed hashes.
  • Clock troubleshooting: corrected a three-hour Windows clock discrepancy using NTP and verified a fresh event against the dashboard after timezone conversion.

What I learned as an analyst

I learned to separate an event from what it proves. I traced a PowerShell alert to the Wazuh agent’s assessment activity and investigated why a locally recorded process did not appear in my alert search. My custom rule then verified the collection-to-alert path in a fresh test.

Earlier service-change records identified BITS and UCPD, not the Wazuh service I initially suspected. Their cause remains unconfirmed. Checking parent processes, event fields, and timestamps helped me test assumptions before reaching a conclusion.

Scope and full documentation

These were controlled tests in my own VMs, not production SOC work or real attack response. The exercises do not establish complete telemetry coverage or comprehensive hardening. Scheduled-task testing and automated response were outside the completed scope.

For the commands, configuration, troubleshooting, and full evidence:

Key results in five snapshots

Select an image to take a closer look.

Read the full documentation on GitHub ↗Follow the documented steps, findings, and current limitations.

Selected lab screenshot

Open full size ↗