PAVINDAS / Blue Team Engineering
Loading... reads All Articles

Building a Home SOC Lab with Wazuh & Shuffle

A hands-on architecture guide to constructing a Security Operations Center laboratory in VirtualBox. Simulating real-world attacks, monitoring telemetry with Wazuh SIEM, and executing automated remediation pipelines with Shuffle SOAR and OPNsense.

Section 01 // Blueprint

Introduction & Operational Workflow

In this guide, I’ll walk you through the process of creating a home lab for a Security Operations Center (SOC) using Oracle VirtualBox. The goal is to detect malicious activity, improve incident response, and automate actions to cut down response time and reduce manual work.

Diagram // Home SOC Lab Topology Click to expand
Home SOC Lab Architecture Diagram
Figure 1: Complete architecture: Kali Linux Attacker, OPNsense Firewall, Windows 10 Host with Sysmon, and Ubuntu Defense Node connected to Wazuh and Shuffle.

Environment Components & Workflow

  • Kali Linux: Attacker machine located outside the firewall.
  • Windows 10 Host: Client machine equipped with Microsoft Sysmon for granular endpoint telemetry.
  • Ubuntu Machine: Defense and server host within the internal subnet.
  • OPNsense Firewall: Gateway filtering traffic between bridged WAN and the internal network.
  • Wazuh (SIEM): Aggregates and correlates logs from network and endpoints.
  • Shuffle (SOAR): Receives webhooks on critical alerts to trigger automated containment and ticketing.
Automated Detection & Containment Cycle

1. Wazuh agents forward real-time logs to Wazuh Cloud.
2. Rule correlations detect malicious activity (e.g., brute-force attacks).
3. An alert triggers a webhook payload directly into Shuffle SOAR.
4. Shuffle checks cache to eliminate duplicate alerts and logs a Jira incident ticket.
5. The offending IP is automatically dispatched to OPNsense to block traffic.

Section 02 // Virtualization

Virtual Environment Provisioning

1. Kali Linux (Attacker Machine)

  • OS Type: Linux, Debian (64-bit)
  • RAM: 2 GB to 4 GB
  • Network: Bridged Adapter
Kali Linux Setup
Kali Linux VM Settings

2. OPNsense (Firewall Appliance)

  • Type: BSD / FreeBSD (64-bit), 3 GB RAM, 10–20 GB Disk
  • Adapter 1: Bridged (WAN)
  • Adapter 2: Internal Network (LAN, named intnet)
OPNsense Firewall Setup
OPNsense VM Settings

3. Windows 10 Host & Sysmon

Internal network adapter connected to intnet.

Windows 10 VM Configuration
Windows 10 VM Settings
Sysmon Installation (PowerShell Admin)
Sysmon64.exe -i
Sysmon Active Telemetry
Sysmon service running in PowerShell

4. Ubuntu (Defense Node)

Ubuntu VM Setup
Ubuntu VM Settings
Section 03 // SIEM Ingestion

Wazuh Cloud SIEM & Agent Deployment

We utilize the Wazuh Cloud Console to establish a centralized analytics and log repository:

Wazuh Console Creation
Wazuh Console creation
Environment Activation
Creating new environment
Dashboard Dashboard Launch
Opening Wazuh Dashboard

Deploying the Wazuh Agent on Windows:

Windows Agent Deployment
Choosing Windows Agent
PowerShell Deployment Command
Running agent installer script in PowerShell
Start Wazuh Agent Service
NET START WazuhSvc
Section 04 // Detection Logic

Configuring Custom Alerting Rules in Wazuh

In Wazuh → Alerting, create a custom monitor to detect repeated authentication failures:

  • Monitor Name: Failed Login Monitor
  • Type: Per query monitor (Frequency: 1 minute)
  • Index: wazuh-alerts
  • Query Filter: rule.id = 60122
  • Trigger Condition: Count IS ABOVE 5
Alert Monitor Configuration
Configuring monitor
Threshold Trigger Definition
Setting trigger threshold
Section 05 // SOAR Pipeline

Automated Orchestration with Shuffle SOAR

Sign in to Shuffle Cloud and create an incident response workflow:

Shuffle Workflow Setup
Shuffle workflow console

Automated Workflow Pipeline

  • Webhook Trigger: Ingests the JSON alert payload from Wazuh.
  • Data Parser: Extracts timestamps, attacker IP, and target host.
  • Cache Deduplication: Verifies alert IDs to prevent duplicate alerts.
  • Ticketing Dispatch: Automatically creates an issue in Jira.
Shuffle Automation Graph
Shuffle workflow graph
Section 06 // ITSM Integration

Incident Tracking via Jira Cloud

Authenticate Jira Cloud within Shuffle using an API token to generate structured tickets automatically upon verified attack alerts:

Jira Integration Parameters
Jira app configuration in Shuffle
Section 07 // Retrospective

Conclusion & Learning Takeaways

Setting up and analyzing this environment demonstrates how security operations function in practice: bridging telemetry collection, automated detection, threat containment, and cross-team incident tracking.

Author's Note

This lab provides a realistic sandbox for practicing detection engineering and SIEM/SOAR integration. Keep experimenting, test new Sigma/YARA rules, and continue expanding your blue team defense capabilities!

01. Architecture Overview • 0%
Lab Blueprint