>touch home_lab
This post will be the first in a series where I discuss building a home lab to study offensive and defensive cybersecurity. Building a home lab has been the best decision I have made to help improve my technical skills. I have learned how to build and break Linux machines, become comfortable using the command line interface, and watched packets fly back and forth across my network.
When people begin researching a home lab, they may find sites like Reddit’s r/homelab. Some of the more impressive setups use enterprise servers and networking gear that could support a medium-sized office. A lab of that nature would undoubtedly be awesome to own and operate. However, all you need is a computer with some unused compute cycles as a beginner. For anyone reading this on a low-end laptop with no resources to get a better rig, there are a ton of free online resources as well. I will do another post on those resources soon. For now, check out the tools_resources page for some ideas.
The two primary types of home lab I will focus on are computer-based and networking-based. There are many other types of labs designed to support various other interests. Radio labs and hardware labs are common as well.
Computer labs support many objectives, such as testing new code or websites. They can be used as sandboxes to study malware. They can act as actual home servers to provide services such as email, media streaming, git repositories, data storage, or a myriad of other services. I currently run a few home services, but the primary focus of my home lab posts will be for offensive and defensive cybersecurity.