A 90-Day Security+ Study Plan That Fits Around a Full-Time Job
6 min read6 views
Super Admin
Most people who sit CompTIA Security+ are not full-time students. They have a job, a commute and a life, and they study in the gaps. This plan is built for exactly that situation: roughly seven to nine hours a week over thirteen weeks, with the heaviest exam domains getting the most time and a full fortnight reserved for practice and review.
It is a template, not a contract. If you already work in a security operations role you may move faster through some weeks; if networking is new to you, add a buffer week early rather than cramming at the end.
Know the shape of the exam before you plan
The current exam is SY0-701. It has a maximum of 90 questions in 90 minutes, mixing multiple-choice items with performance-based questions, and the passing score is 750 on a scale of 100 to 900. Fees, retake rules and voucher options change from time to time, so check the details on the official CompTIA Security+ page before you book.
The exam objectives divide the content into five domains. The weights matter because they tell you where marks come from, and therefore where your hours should go.
| Domain | Weight | What it feels like in practice |
|---|---|---|
| 1. General Security Concepts | 12% | Vocabulary and foundations: controls, CIA, change management, cryptography basics |
| 2. Threats, Vulnerabilities and Mitigations | 22% | Threat actors, attack types, indicators and how to blunt them |
| 3. Security Architecture | 18% | Network and cloud design, segmentation, resilience and data protection |
| 4. Security Operations | 28% | Day-to-day defence: hardening, monitoring, identity, incident response |
| 5. Security Program Management and Oversight | 20% | Governance, risk, third parties, compliance and awareness |
Two observations follow. Security Operations alone is more than a quarter of the exam, so it deserves the longest block. And General Security Concepts, although the smallest domain, is the language every other domain is written in, so it goes first.
The weekly rhythm
A plan survives a full-time job when each week has the same shape. A pattern that works for many people looks like this:
- Two weekday evenings (about 60 minutes each): new material from a course or study guide.
- One weekday evening (about 45 minutes): flashcards and a short quiz on the week's topics.
- Weekend block (two to three hours): a lab or hands-on exercise, then a timed practice set and a review of every wrong answer.
- Daily micro-sessions (10 minutes): flashcards on your phone during a commute or lunch break.
Tip: protect the weekend review more than any other session. Reading feels productive, but reviewing why you got a question wrong is where the score actually moves. If a busy week forces a cut, cut new reading, not the review.
The 13-week schedule
The table below maps the domains onto thirteen weeks. Hours are approximate and assume a learner with some general IT background.
| Week | Focus | Hours | Milestone |
|---|---|---|---|
| 1 | Exam objectives, baseline diagnostic, Domain 1 controls and CIA | 7 | Baseline score recorded |
| 2 | Domain 1: cryptography, PKI, change management | 8 | Can explain symmetric vs asymmetric in your own words |
| 3 | Domain 2: threat actors, vectors, social engineering | 8 | First 30-question timed set |
| 4 | Domain 2: application, network and malware attacks | 8 | Indicator-to-attack flashcard deck complete |
| 5 | Domain 2: vulnerabilities and mitigation techniques | 8 | Domain 2 checkpoint quiz |
| 6 | Domain 3: network architecture, segmentation, cloud models | 8 | Draw a segmented network from memory |
| 7 | Domain 3: data protection, resilience and recovery | 8 | Domain 3 checkpoint quiz |
| 8 | Domain 4: hardening, asset management, vulnerability management | 9 | First performance-based practice item |
| 9 | Domain 4: monitoring, identity and access management | 9 | Log-reading exercise done |
| 10 | Domain 4: incident response, forensics, automation | 9 | Domain 4 checkpoint quiz |
| 11 | Domain 5: governance, risk, third parties, compliance, audits | 8 | Domain 5 checkpoint quiz |
| 12 | Full-length timed practice exam, then targeted review | 9 | First full mock completed |
| 13 | Second full mock, weak-area drills, light final review | 7 | Exam day |
Why Domain 4 gets three weeks
Security Operations is the largest domain and also the most practical. Questions often describe a situation, such as an alert, a log excerpt or a misconfigured account, and ask what you would do next. That kind of judgement comes from repetition, so it gets the most weeks and the most hours per week.
Why the last two weeks are not new material
By week 12 you have seen everything once. What remains is the gap between recognising a topic and answering under time pressure. Full mocks expose that gap, and the days after each mock are for closing it.
Using practice questions well
Practice questions are a measuring instrument, not a reading list. Three habits make them far more useful.
- Time every set. The exam gives you about a minute per question on average, and performance-based items take longer. Practising untimed hides the problem you will meet on the day.
- Write a one-line reason for every miss. "Did not know the term", "misread the question" and "two options looked right" are different problems with different fixes.
- Track scores by domain, not just overall. An overall 78% can hide a weak Domain 5 that costs you the pass.
Handling performance-based questions
Performance-based items ask you to do something: match controls to scenarios, order steps, or interpret a configuration. Many candidates find it useful to skim them first and decide whether to answer them immediately or flag them for later, so that one difficult simulation does not consume time meant for twenty multiple-choice questions. Whatever approach you choose, rehearse it during your mocks rather than inventing it on the day.
When life gets in the way
Ninety days is long enough that something will interrupt it: a project deadline, an illness, a family event. Plan for that now.
- Keep one floating buffer week you can insert anywhere without moving the exam date.
- If you miss more than a week, restart with a short quiz on the last domain before moving on.
- Book the exam around week 6 or 7. A fixed date turns "I'll study later" into "I have seven weeks left".
- Tell the people around you about the plan. A weekend block is easier to protect when others know it exists.
Final-week checklist
The last week is about confidence and logistics, not cramming. Work through this list:
- Your last full mock is at or above your target score in every domain, not only overall.
- You have reviewed every flagged flashcard at least twice.
- You know the exam format: question count, time limit and how performance-based items appear.
- You have confirmed the test centre or online-proctoring requirements in your booking confirmation.
- Your identification matches the name on your booking exactly.
- For an online exam, you have run the system check on the computer and network you will use.
- You have planned a light final day and a normal night's sleep.
Conclusion
A full-time job does not prevent you from passing Security+; an unstructured plan does. Give the heavy domains the most time, measure progress with timed practice, review every mistake, and keep the last fortnight for full mocks. Thirteen steady weeks beat four frantic ones, and the habits you build along the way are the same ones you will use on the job.
Security+
1,877 practice questions
How ready are you for Security+?
Take the entry assessment and see exactly which domains need work.
Take the assessment24 questions · about 15 minutes · no account needed
Security+
Discussion (0)
No discussion here yet — be the first to comment.
Please sign in to join the discussion.