Learning
90DaysOfCyberSecurity
A 90-day hands-on cybersecurity study plan in 10 phases plus a career track: one to two hours a day, every tool free, every day ending with something built, broken, or captured.
Problem
Most roadmaps are link lists. A beginner does not need more links, they need an order: what to learn first, how long it takes each day, and what to build so the learning sticks.
Approach
A workout program, not a link list. 90 daily tasks in 10 phases, in a deliberate order: networking before hacking, Linux before Python, web fundamentals before Burp, and a real vulnerable lab when it is time to attack. Each day is scoped for 1 to 2 hours and ends with a checkbox that is checked only when the hands-on task is actually done.
The phases run from Networking Fundamentals (days 1-7) through Security Foundations, Linux Command Line, Python for Security, Web Hacking with the PenTrix VulnLab (days 43-56, milestone 50 earned flags plus a written writeup), Git and GitHub, SIEM and Blue Team Basics, Cloud Security Basics, Review and Guided Practice, and a Capstone (days 85-90). A career track, days 91 to 95, turns the 90 days into a resume, a clean GitHub, and a job search plan.
Everything in the plan is free. Every tool, platform tier, and resource has a free option, and the cloud phase ends with a cleanup day so the free tier stays free. The labs are woven into the daily tasks: the PenTrix VulnLab, TryHackMe, HackTheBox, picoCTF, and OverTheWire Bandit.
Stack
Markdown phase files, a progress checklist, a curated resource list in learn.md, and an interactive site at https://mizazhaider-ceh.github.io/90DaysOfCyberSecurity/
Status
Complete. Exactly 90 daily tasks in 10 phases plus the career track.
Limits
The plan gives demonstrable fundamentals, a GitHub with real projects, labs you can talk through, and the vocabulary to survive a junior interview. It does not promise a job, and no plan replaces persistence. Everything 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.