Objective Lab goal

This lab introduces centralized log collection and analysis using a lightweight SIEM platform. You’ll deploy a SIEM VM, configure log sources from DC01, WIN10‑LAB, and OPNsense, and validate ingestion and dashboard visibility.

  • Outcome 1: SIEM VM deployed and operational.
  • Outcome 2: Logs collected from Windows and OPNsense.
  • Outcome 3: Dashboards and alerts visible in SIEM console.
  • Outcome 4: Foundation for alert tuning and incident response.
Lab 6: SIEM Deployment & Log Collection
Lab 6: Deploying a lightweight SIEM and integrating log sources from DC01, WIN10‑LAB, and OPNsense.

Deliverables End‑of‑lab checklist

  • DL6.1: SIEM VM deployed and reachable.
  • DL6.2: Log sources configured (DC01, WIN10‑LAB, OPNsense).
  • DL6.3: Dashboards populated with event data.
  • DL6.4: Basic alert rules created and tested.
  • DL6.5: Documentation of SIEM configuration.

Lab Steps Step‑by‑step instructions

Step 1 – Deploy SIEM VM

~30 minutes
  1. Download your preferred SIEM ISO or installer (Wazuh, Security Onion, or Splunk Free).
  2. In Proxmox, create a new VM named SIEM01.
  3. Assign:
    • CPU: 4 vCPUs
    • RAM: 8 GB
    • Disk: 100 GB
    • Network: vmbr10 (Lab LAN)
  4. Install the SIEM OS and verify network connectivity.

Step 2 – Configure Log Sources

~45 minutes
  1. On DC01, enable Windows Event Forwarding (WEF) subscription for Security and System logs.
  2. On WIN10‑LAB, confirm WEF client configuration:
    wecutil es /enum-subscription
  3. On OPNsense, enable remote syslog under System → Settings → Logging / Targets.
  4. Point all sources to SIEM01 (10.10.10.x).

Step 3 – Validate Log Ingestion

~30 minutes
  1. Log in to SIEM web console.
  2. Check incoming data streams for Windows and syslog sources.
  3. Verify event types appear in dashboards (Security, System, Firewall).
  4. Run a test logon event on WIN10‑LAB and confirm visibility in SIEM.

Step 4 – Create Basic Alerts and Dashboards

~45 minutes
  1. Create alerts for:
    • Failed logons (Windows Event ID 4625)
    • Policy changes (Event ID 4739)
    • Firewall blocks (OPNsense syslog)
  2. Design a dashboard showing:
    • Authentication events by host
    • Top alerts by severity
    • Event volume over time

Step 5 – Document Configuration and Results

~20 minutes
  1. Record SIEM version, log sources, and alert rules in your documentation folder.
  2. Save screenshots of dashboards and alert tests.
  3. Save screenshots of dashboards and alert tests.
  4. Export SIEM configuration summary for future reference.

Reflection What you should understand now

  • Visibility: How centralized logging reveals system and network activity across your homelab.
  • Detection: How SIEM tools correlate events and generate alerts for suspicious behavior.
  • Integration: How Windows Event Forwarding and syslog connect heterogeneous systems into a single monitoring plane.

Your homelab now has a fully operational SIEM collecting logs from multiple sources. In Week 7, you’ll focus on alert tuning and dashboard design to refine signal‑to‑noise ratio and visualize key security metrics.