Skip to content
izaz.dev

Learning

90 days of cybersecurity, a plan you can actually follow

Most roadmaps are link lists. This one is a workout program: 90 daily tasks in 10 phases, one to two hours a day, every tool free, every day ending with something built, broken, or captured.

Muhammad Izaz Haider9 min read

Most roadmaps are link lists. This one is a workout program: networking before hacking, Linux before Python, web fundamentals before Burp, and a real vulnerable lab, not screenshots of one, when it is time to attack. Follow it in order and you will finish with skills you can demonstrate, not just videos you watched.

That is the idea behind 90 Days of Cyber, a 90-day hands-on study plan that takes you from zero to job-ready fundamentals. One to two hours a day, every tool free, every single day ends with something you built, broke, or captured yourself.

The 10 phases

DaysPhaseWhat you will be able to do
1-7Networking FundamentalsRead a network like a map, capture traffic with Wireshark, scan with nmap
8-14Security FoundationsThink in CIA triad terms, hash and crack, spot phishing on sight
15-28Linux Command LineLive in the terminal, script in bash, clear Bandit levels
29-42Python for SecurityWrite your own tools, parse logs, build a port scanner
43-56Web Hacking with the PenTrix VulnLabIntercept traffic with Burp Suite, exploit real vulnerabilities, earn 50 flags
57-63Git and GitHubVersion everything, publish your work, collaborate with pull requests
64-70SIEM and Blue Team BasicsHunt threats in logs with the Elastic Stack, write an incident note
71-77Cloud Security BasicsSecure AWS and Azure resources the way attackers see them
78-84Review and Guided PracticeSolve TryHackMe, HackTheBox, and picoCTF challenges against the clock
85-90Capstone: Prove Your SkillsFinish kill-chain scenarios, ship a project, write a professional writeup

After day 90 comes the career track, days 91 to 95: a one-page resume, a clean GitHub, and a real job search plan.

The 10 phases, in order

Ninety day plan, ten phases in orderA flow diagram of the ten phases of the ninety day cybersecurity plan in a snake layout, from networking fundamentals through to the capstone, followed by the career track.1. NetworkingDays 1-72. FoundationsDays 8-143. Linux CLIDays 15-284. PythonDays 29-425. Web HackingDays 43-566. Git and GitHubDays 57-637. SIEM / Blue TeamDays 64-708. Cloud SecurityDays 71-779. Review + PracticeDays 78-8410. CapstoneDays 85-90Days 91-95: Career trackone-page resume, clean GitHub, real job search planEach phase assumes the one before it. Go in order.Miss a week, pick up where you left off. The days are numbered, not dated.
Ten phases in a snake: left to right across the top row, then right to left across the bottom row, then the career track. Each phase assumes the one before it.

The rules of the plan

Budget 1 to 2 hours a day. Every day is scoped for that. Some days will take less, a few will take more, and that is fine.

Go in order. Each phase assumes the one before it. You cannot enjoy web hacking in phase 5 if you skipped the Linux terminal in phase 3. That order is the whole point: packets are the alphabet of everything in security, so the plan starts with networking, and the hacking comes only after the foundations can carry it.

Everything is free. Every tool, platform tier, and resource in the plan has a free option. If something asks for a card, there is a free tier or a free alternative named in the day's task. The cloud phase warns you before anything could cost money and ends with a cleanup day so the free tier stays free.

Track your progress. Each day ends with a checkbox. Check it only when the hands-on task is actually done. Fork the repo and check them off in your own copy, or print the progress list and pin it to your wall.

Build in public. From phase 6 onward you push your scripts, notes, and writeups to GitHub. Employers hire people who can show their work.

The labs are the plan, not an appendix

Reading about vulnerabilities does not teach exploitation. The labs are woven into the daily tasks, not parked in an appendix.

The plan's home lab for web hacking is the PenTrix VulnLab, an intentionally vulnerable web app with 201 challenges across 29 modules, each its own small website, running locally with docker compose. Flags are earned only by genuine exploitation. You meet it daily in phases 5 and 10, and the phase 5 milestone is 50 earned flags plus a written writeup of your favorite exploit. For an example of what a finished writeup looks like, see the CTF investigation writeup.

Other labs in the plan: TryHackMe guided rooms with a free tier, HackTheBox Starting Point machines with a free tier, picoCTF free challenges for timed practice, and OverTheWire Bandit, a Linux wargame over SSH, at the end of phase 3. For the scanning skills in phase 1, the network reconnaissance automation guide covers the same workflow in depth.

A command from phase 1, the first scan you run in the plan:

bash
nmap -sn 192.168.56.0/24

Illustrative output:

text
Nmap scan report for 192.168.56.10
Host is up.
Nmap scan report for 192.168.56.20
Host is up.

What if you fall behind

The days are numbered, not dated. Miss a week, pick up where you left off. Phase 9 exists specifically to repair weak spots: a review of your weakest days, and timed redos of labs you already solved.

Can you skip to the hacking part? You can, but you will be slower at it. Phases 1 through 4 are what make phase 5 fun instead of frustrating.

Either Windows or Mac works for the early phases. In phase 3 you install a Linux VM, and from then on most hands-on work happens in Linux.

What the plan does not promise

It gives you demonstrable fundamentals: a GitHub with real projects, labs you can talk through, and the vocabulary to survive a junior interview. Days 91 to 95 turn that into applications. No plan replaces persistence, but this one replaces wondering what to learn next.

Everything here targets your own machines, your own cloud accounts, or platforms built for practice. Never test systems you do not own or have written permission to test.

References

1625 words. Published 20 Oct 2026, updated 20 Nov 2026. Written by Muhammad Izaz Haider.

Was this helpful?

Spotted a mistake? Report an error on GitHub, the issue opens pre-filled with this article.

Your vote is stored only in this browser, so you can vote once per article. Nothing is sent anywhere.