Building a Home Lab

The objective of this module is not "install some virtual machines." By the end, you should have an environment containing a virtualisation platform, Windows Server, Active Directory, DNS, DHCP, Windows clients, Linux servers, a firewall/router, multiple network segments, a database server, Docker containers, centralised logging, Splunk, Microsoft Sentinel, security monitoring, Kali Linux, deliberately vulnerable applications, backup and recovery capability, administrative accounts, service accounts, certificates, remote administration, basic automation, and documentation with network diagrams.

Many junior candidates have theoretical knowledge — they know DNS converts names to IP addresses, that Active Directory stores users and computers, that Kerberos performs authentication. Employers frequently want candidates who understand what these technologies look like when they actually interact. Building a lab develops exactly that kind of thinking.

Learning Objectives

By the end of this module, you should be able to:

• Design a segmented network with a firewall, server VLAN, client VLAN and security VLAN.
• Build a multi-DC Active Directory domain with OUs, RBAC groups, DNS, DHCP and Group Policy.
• Run Linux servers, SSH, a web server, PKI/certificates, and SQL or Oracle databases with least-privilege access.
• Deploy Docker containers and understand how VMs, containers and legacy servers differ.
• Centralise logging with Splunk and Microsoft Sentinel, and write basic SPL and KQL queries.
• Run Kali Linux and deliberately vulnerable applications inside an isolated security network.
• Segment further with a DMZ, reverse proxy, service accounts, and privileged/standard account separation.
• Back up and restore systems, patch and change-manage responsibly, and deliberately break and repair the lab.
• Document the environment, automate parts of it with PowerShell and shell scripting, and publish it as a portfolio project.
• Complete a capstone build-and-incident exercise you can describe concretely in an interview.

The lab does not need to be huge. It needs to demonstrate that you understand how modern and legacy enterprise technologies fit together, how to troubleshoot and secure them, and — most importantly — that you can explain what you built and why.

This Module's Lessons

Work through these in order — each lesson's build depends on infrastructure from the last. Every lesson has its own "Mark lesson complete" button; your progress across all six is tracked below.