Homelab

Index of my study infrastructure.

PT-BR

Deployed Environment

🖥️ Host Environment

• VS Code IDE: VSCode setup for C, Python and SQLite development, extending CS50's workflow.
• Tails Amnesic Incognito System: Personal setup and operational notes for an amnesic security environment on a USB drive.

🌐 Homelab Infrastructure

• pfSense: Default gateway for the virtual lab network, handling routing and firewall rules.

🔵 Blue Team / Detection

• SOC Lab: Security Operations Center lab for hands-on practice with SIEM, log analysis, threat detection, and incident response workflows.

🔴 Red Team / Analysis

• Kali Linux: Analyst virtual machine for security analysis of the homelab environment and CTF challenges on online study platforms.

🎯 Attack Surface (Vulnerable Targets)

Vulnerable Systems:

• Metasploitable: Intentionally vulnerable virtual machines for penetration testing practice and security training across multiple versions.

Web Applications:

• DVWA (Damn Vulnerable Web Application) — In documentation process.

Roadmap

Completed:

• Host Machine: VS Code IDE + Oracle VirtualBox;
• Tails Amnesic Incognito System (Bootable USB);
• pfSense VM (Firewall/Router);
• Kali Linux VM (Security Analysis);
• Metasploitable VMs (versions 1 and 2);
• Debian + DVWA;
• SOC Lab (in progress);

🎯 Attack Surface (Vulnerable Targets)

Web Applications:

• OWASP Juice Shop;
• DVWA (Damn Vulnerable Web Application);

Vulnerable Systems:

• Metasploitable3-ub1404 (Ubuntu);
• Metasploitable3-win2k8 (Windows);

🪟 Windows Environment

Active Directory Lab:

• Windows Server 2025 + Active Directory;

Workstations:

• Windows 11 (Production);
• Windows 10;

Legacy Systems (EOL):

• Windows 7;
• Windows Vista;
• Windows XP;

Malware Analysis (Isolated):

• Windows 11 - Malware Analysis Lab (Snapshot)
  • Tools: Wireshark, IDA, x32dbg, x64dbg, ProcMon, ProcExp, Ghidra, DIE, HxD

🐧 Linux Environment

• Debian VM:
  • Snapshot: OWASP Juice Shop
  • Snapshot: DVWA

Troubleshooting

Common issues and their solutions.

Full Troubleshooting Guide

Driver name clash (VERR_PDM_USB_NAME_CLASH)

• Problem: Corrupted/duplicated USB drivers after reinstall or update.
• Solution: Reinstall VirtualBox cleanly:
  1. Uninstall VirtualBox (accept removal of all network/USB components);
  2. Delete C:\Program Files\Oracle\VirtualBox and C:\Windows\System32\drivers\VBox*;
  3. Reboot;
  4. Reinstall from virtualbox.org.