Return Home

VirtualBox Home Lab Setup

Project VM SIEM Security Networking

Overview

Documenting the design and implementation of a home lab environment using Oracle VirtualBox. The lab features multiple VMs configured on an internal network, enabling safe penetration practice, exploit analysis, and network traffic monitoring with Security Onion and Elastic. This setup provides a cost-effective platform (free) for developing offensive and defensive skills without impacting public facing networks.

Objectives

The primary objectives:

  • Create a safe environment for security testing and exploit practice
  • Configure multiple VMs with static IP addresses for a consistent lab topology
  • Deploy Security Onion for network traffic monitoring, and exploit analysis
  • Learn Elastic Stack for centralized logging and analysis at home
  • Document the setup process for reproducibility and knowledge sharing

Environment Setup

The lab is comprised of four virtual machines on a VirtualBox internal network. Each VM serves a specific purpose in the lab environment.

Virtual Machine Inventory

VM/OS Purpose
Ubuntu 24.04.3 Desktop General purpose Linux platform for testing
Parrot OS (Parrot Security 6.4) Primary attack platform with pre-installed penetration testing toolkits
Metasploitable2 Linux 2.6.24-16-Server Deliberately vulnerable target for exploit practice
Security Onion 2.3.300 Network monitoring, exploit analysis, and traffic capture

Methodology

The lab was built systematically to ensure proper network functionality from the start.

Network Configuration

First I created an internal network in VirtualBox. DHCP was disabled on end devices in favor of static IP assignments for a more consistent lab topology. Each VM was configured with static networking using either Netplan (on modern Ubuntu/Parrot) or traditional interfaces file (Metasploitable2). Upon configuration of a single VM, I verified connectivity with other devices on the network.

VM Deployment Process

Each virtual machine was deployed with specific network adapter settings. The attack platform (Parrot OS) and target systems (Ubuntu and Metasploitable2) were configured with standard internal network adapters. Security Onion required special configuration with its monitoring interface set to promiscuous mode, allowing it to capture all traffic on the network segment for analysis, and it required another network adapter in bridged mode to access external resources, and access the SOC web interface.

Security Onion Configuration

Security Onion was configured with Elastic, Suricata IDS and Zeek for comprehensive network traffic analysis and SIEM. The promiscuous configuration allows the system to intercept all traffic on the network, not just traffic addressed to the monitoring device, enabling full visibility into attacks, exploits, and lateral movement attempts during penetration testing events.

Verification Testing

After configuration, I verified connectivity between all VMs and tested Security Onion's monitoring capabilities by performing basic port scans and exploit attempts. Security Onion successfully detected and logged the network activity, confirming proper network visibility and alerting functionality. In the future, I'd like to do a document both sides; successfully exploiting a service or protocol on Metasploitable2, and then uncover that exploit with Security Onion.

Future Improvements

Several enhancements are planned to expand the lab's capabilities:

  • Automated Snapshots: Implement snapshot management to quickly revert VMs to healthy states
  • Documentation: Document the Security Onion installation and configuration process
  • pfSense Router: Deploy a pfSense VM to add firewall rules, and inter-network routing capabilities
  • Vulnerable Web Apps: Deploy DVWA, OWASP Juice Shop, and others for web security practice
  • Enhanced SIEM: Customize Security Onion's Elastic stack for improved log visualization

References