explaingit

orevic21/wazuh-home-soc

Analysis updated 2026-05-18

0Audience · ops devopsComplexity · 4/5Setup · hard

TLDR

A home-lab security monitoring setup using Wazuh and Suricata that detects real exploits and brute-force attacks against a deliberately vulnerable legacy target, including a custom detection rule.

Mindmap

mindmap
  root((wazuh-home-soc))
    What it does
      Simulates real attacks
      Detects via network traffic
      Adds custom detection rule
    Tech stack
      Wazuh
      Suricata
      VirtualBox
    Use cases
      Practice detection engineering
      Monitor a legacy device via network
      Write custom SIEM rules
    Audience
      Security learners
      SOC analysts
    Setup
      Set up three VMs
      Configure Wazuh and Suricata
      Run attacks and review alerts

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Practice detecting network scans, exploits, and brute-force attacks in a safe home lab.

USE CASE 2

Learn how to monitor a legacy device that cannot run a monitoring agent directly.

USE CASE 3

Write and test a custom SIEM correlation rule to catch a gap in default IDS signatures.

What is it built with?

WazuhSuricataVirtualBoxKali Linux

How does it compare?

orevic21/wazuh-home-soc00kaku/gallery-slider-block04amanrajj/netwatch
Stars00
LanguageJavaScriptRust
Last pushed2021-05-19
MaintenanceDormant
Setup difficultyhardeasymoderate
Complexity4/52/53/5
Audienceops devopsgeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Requires setting up and networking three separate virtual machines with VirtualBox before any detections can run.

In plain English

This project is a home built security monitoring lab that demonstrates how to detect real cyberattacks, not just how to install security software. It sets up a small practice environment with three virtual computers: one acting as an attacker, one acting as a deliberately vulnerable, outdated target, and one running the security monitoring system that watches for suspicious activity. The interesting design choice is that the vulnerable target computer is running such an old operating system that it cannot run any modern monitoring software directly on it, similar to how old industrial equipment or forgotten devices on a real network often cannot be monitored the usual way. Instead of giving up on watching that machine, the project routes around the problem by watching the network traffic flowing to and from it using a separate network monitoring tool, so it can still catch attacks even though the target itself reports nothing. The lab then runs several real, well known attacks against the vulnerable target and shows how each one gets caught. A network scan gets flagged by built in detection rules within seconds. A well known backdoor vulnerability that gives an attacker full root access is caught because the security tool spots a giveaway phrase crossing the network at the moment the attacker gains that access. A slower attack that tries many passwords in a row against a file transfer login is captured too, but the author notes that the standard detection rules do not have a ready made alert for that kind of repeated password guessing, since it is a pattern of behavior rather than a single known bad signal. To close that gap, the author writes a custom detection rule from scratch. Throughout the write up, the author is honest about what worked, what did not, and what is still being debugged, including a custom rule that is not yet firing reliably. The lab requires virtualization software to run the three practice computers and is meant for people learning or practicing security monitoring and detection engineering skills, not for use on any real production system.

Copy-paste prompts

Prompt 1
Help me set up a three-VM Wazuh and Suricata lab like this one using VirtualBox.
Prompt 2
Explain why Suricata runs on the attacker box instead of a dedicated sensor VM here.
Prompt 3
Walk me through writing a custom Wazuh rule to detect FTP brute-force attempts.
Prompt 4
Explain how the vsftpd backdoor exploit gets detected at the network layer in this lab.

Frequently asked questions

What is wazuh-home-soc?

A home-lab security monitoring setup using Wazuh and Suricata that detects real exploits and brute-force attacks against a deliberately vulnerable legacy target, including a custom detection rule.

How hard is wazuh-home-soc to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is wazuh-home-soc for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.