12 Cybersecurity Home Lab Projects for Beginners
Rule Zero: Only Touch Your Own Machines#
Before the ideas, one rule that protects your career. Scan, attack and probe only systems you own or have written permission to test. Every project below runs inside your own lab or on platforms built for practice. A recruiter who sees a story about scanning a random company website will not call you back, and in many countries that is a crime.
Now the good news. Entry level security hiring is mostly about whether you can investigate, explain and document. A tidy write-up of a small lab beats a list of tool names.
The twelve ideas below are a ladder. Each level builds on the last, so you can stop at any step and still have something to show. Hours are rough and assume you can already use a command line.
Get the next guide by email
New guides and fresh jobs in one short email. Free.
Level 1: Build the Lab (Weekend)#
Step 1. A virtual lab on one laptop. Install VirtualBox, then create one Linux machine and one Windows evaluation machine on a private network. Snapshot both. Publish a diagram and a one page build note. About 6 hours.
Resume bullet: "Built an isolated virtual lab with snapshots and documented network layout."
Step 2. Watch your own traffic. Capture your lab traffic with Wireshark, then explain what a DNS lookup, a TCP handshake and a TLS start look like. Publish an annotated screenshot set. About 5 hours.
Resume bullet: "Captured and annotated DNS, TCP and TLS traffic using Wireshark."
Level 2: Break Things Legally (Weeks 2 to 4)#
Step 3. Work through an intentionally vulnerable app. Run OWASP Juice Shop locally and solve ten challenges. Write one page per challenge on what the flaw was and how a developer would fix it. About 20 hours.
Resume bullet: "Exploited and documented 10 web vulnerabilities in OWASP Juice Shop with remediation advice."
Step 4. A scan of your own lab with a report. Use Nmap to map the lab, then OpenVAS or Nessus Essentials to scan the Windows machine. Rank the findings by risk and write them as a short report that a manager could act on. About 12 hours.
Resume bullet: "Ran authenticated vulnerability scans in a lab and delivered a prioritised remediation report."
Step 5. A weak password experiment. Create test accounts in your lab with different password policies, then use a tool such as Hashcat against your own hashes. Show how length and randomness change the time needed. About 8 hours.
Resume bullet: "Compared password policies by cracking lab hashes and recommended minimum length."
Level 3: Defend (Weeks 4 to 8)#
Step 6. Stand up a free SIEM. Install Wazuh or Security Onion and send logs from your lab machines. Then run Step 3 or Step 4 attacks and find them in the alerts. This is the single most valuable project on the list for SOC roles. About 30 hours.
Resume bullet: "Deployed Wazuh, forwarded endpoint logs and detected simulated attacks."
Step 7. Write three detection rules. Using Sigma rule format and the MITRE ATT&CK framework, write rules for three techniques you ran yourself, such as a new local admin account. Test each one for false positives. About 15 hours.
Resume bullet: "Authored 3 Sigma detections mapped to MITRE ATT&CK and tuned false positives."
Step 8. Investigate a packet capture. The site malware-traffic-analysis.net publishes training exercises with real capture files. Pick one, find the infected host and write the incident report in the same shape you would send to a manager. About 10 hours.
Resume bullet: "Investigated a malware packet capture and produced an incident timeline with indicators."
Level 4: Think Like a Practitioner (Weeks 8 to 12)#
Step 9. A phishing email teardown. Collect samples you receive or public ones, read the headers, check SPF, DKIM and DMARC results, and look up links in VirusTotal. Write a one page triage guide for non-technical staff. About 8 hours.
Resume bullet: "Wrote a phishing triage guide based on header analysis of 10 sample emails."
Step 10. Harden a server and prove it. Take a fresh Linux machine, apply a published benchmark such as CIS guidance, and re-scan before and after. Show the count of findings dropping. About 14 hours.
Resume bullet: "Hardened a Linux server against a CIS benchmark and cut scan findings from 41 to 9." Use your own counts.
Step 11. A small cloud security review. Using a free tier account you control, deploy a deliberately misconfigured environment from an open source project such as CloudGoat, then find and fix the issues. Remember to delete everything afterwards to avoid charges. About 20 hours.
Resume bullet: "Identified and remediated IAM and storage misconfigurations in a lab cloud account."
Step 12. A security policy for a made-up company. Write a two page acceptable use and incident response outline for a 20 person business, mapped loosely to NIST CSF. It sounds dull, but governance roles read these. About 8 hours.
Resume bullet: "Drafted an incident response outline aligned to NIST CSF functions."
Advertisement
What a Good Write-Up Contains#
Take Step 8, the packet capture investigation. A strong write-up has the same bones as a real incident report, and you can reuse this shape for every step:
- Summary. Two sentences: what happened, which host was affected and how you know.
- Timeline. A short table of times, events and the evidence for each one, such as a DNS request to a suspicious domain.
- Indicators. The domains, IP addresses and file hashes you found, labelled clearly as lab data.
- What you would do next. Contain the host, reset credentials, block the domain. Name the action and the owner.
- What you are unsure about. Every investigation has gaps. Naming them is a skill.
Notice that nothing in that list is a screenshot of a fancy dashboard. Screenshots support the story. They are not the story.
Tools You Will Touch Along the Way#
- VirtualBox: your lab, and the place snapshots save you from mistakes.
- Wireshark and Nmap: the two tools every analyst is expected to recognise.
- Wazuh or Security Onion: your first taste of a SIEM, which is the daily tool in many SOC jobs.
- Sigma and MITRE ATT&CK: a shared language for describing detections and attacker behaviour.
- VirusTotal and CyberChef: quick lookups and decoding for the investigation steps.
- TryHackMe, Hack The Box and OverTheWire: structured practice sites if you want guided exercises alongside your own lab. Check current free tier limits before you plan around them.
A Twelve Week Plan#
If you have about eight hours a week, here is a pace that works without burning out:
- Weeks 1 and 2: Steps 1 and 2. Get the lab running and learn to read a capture.
- Weeks 3 to 5: Steps 3 and 4. Break the vulnerable app, then scan your own machines.
- Weeks 6 to 8: Steps 6 and 7. Stand up the SIEM and write detections for what you did earlier.
- Weeks 9 and 10: Steps 8 and 9. Do the investigation and the phishing teardown.
- Weeks 11 and 12: Step 10 or 11, then spend the last week tidying the repo and writing your resume bullets.
You can skip Steps 5 and 12 if you are short on time. They are the lightest on the resume, and the rest hold together without them.
Questions Interviewers Ask About Lab Projects#
Be ready to answer these out loud about any step you list:
- What did you expect to see, and what did you actually see?
- What went wrong, and how did you find out?
- If this were a real company, who would you tell first?
- What would you automate if you had to do it every day?
If you can answer those without notes, the project has done its job, whatever the tool list says.
Mistakes Beginners Make#
- Collecting tools, not evidence. Twelve tools listed on a resume with no project behind them reads as a keyword list.
- Skipping the writing. The lab is half the work. If nobody can read what you did, it did not happen.
- Running something noisy outside the lab. Scanning a school network or a company you do not work for can break rules and laws. Stay inside your own environment.
- Copying walkthroughs line by line. It is fine to follow a guide once. Then change something, break it and explain why it behaved that way.
- Forgetting cleanup. Delete cloud resources, and keep passwords and keys out of your public repo.
Presenting It#
- One public repo or blog. One folder per step, each with a README that starts with the finding.
- Redact. No real IP addresses, passwords or emails from anyone but you.
- Name the limits. "This was a lab, not production" is honest and respected.
- Match the job post. A SOC analyst posting wants steps 6 to 8. A junior GRC or analyst role wants 9 and 12.
What About Certificates?#
They help get past filters, but they are not a substitute for steps like these. Whichever you pursue, run your resume through the free ATS checker against the posting. Then read the cybersecurity analyst interview questions and answers and, if you are still deciding on a direction, the guide on cybersecurity analyst or DevOps engineer.
Build Step 1 this weekend. A working lab is the hardest part to start and the easiest to keep going.
Advertisement
Send this to whoever has the interview this week.