Skip to content
AS
02 / Detection Engineering2026

Home SOC Lab

A segmented, instrumented SOC you can attack on purpose: pfSense, Security Onion, Suricata and Zeek with five documented scenarios.

pfSenseSecurity OnionSuricataZeek
Case file
Role
Solo build — research, engineering, documentation, release
Status
v2.0.0 · blueprint
Year
2026
Position
02 of 13
Case 02 / home-soc-labArchitecture · Evidence · Signal

01 — Context

The problem worth solving.

A SIEM with default rules proves nothing. Real detection work needs a controlled network, telemetry you trust, and attacks you can replay on demand.

02 — Approach

How it was built.

  1. 01

    Architect a flat home network into segmented VLANs with pfSense as the policy edge.

  2. 02

    Deploy Security Onion for ingest and search, Suricata for signatures, Zeek for protocol truth.

  3. 03

    Write seven custom detections for C2 beaconing, lateral movement and data staging.

  4. 04

    Run five attack scenarios end to end, capture the alerts, and document each incident.

03 — Architecture

The shape of the system.

01Edge

pfSense firewall with VLAN segmentation and explicit allow paths.

02Sensors

Suricata IDS and Zeek network security monitoring on the mirrored segment.

03Platform

Security Onion for ingest, hunt and alert triage.

04Rules

Seven custom detections tuned to the lab traffic baseline.

05Scenarios

Five attacks with incident write-ups and topology diagrams.

04 — Evidence

Receipts, not adjectives.

5attack scenarios
7custom rules
24/7lab telemetry

05 — Hiring signal

“Detection engineering is an architecture problem before it is a rules problem. This lab documents both halves, with evidence attached.”

Ships working systemsDocuments the methodExplains the trade-offsKeeps evidence attached

06 — What's next

Still being built.

Ingest into Wazuh and ELK, expand to ten detections, publish one full incident walkthrough.