Back to Secure Cloud Academy

Secure Cloud Academy · Free learning resource

Your career-changer’s roadmap into cybersecurity.

You don’t need to plan your entire career tonight. Choose your starting point, build a study routine, and finish one small piece of work you can explain.

This is a four-week orientation plan, not a promise of exam readiness or employment. Adjust the pace to your background. Free to read—no purchase or sign-up required.

To keep a copy, use your browser’s Print option and choose “Save as PDF.” Checkboxes are for this visit and are not saved after a refresh.

1. Find a useful starting point

Computer fundamentals still feel unfamiliar?

Start with files, operating systems, installing trusted software, and basic troubleshooting. Practice finding system information and explaining a problem clearly before adding a certification schedule.

Comfortable using a computer, but unsure how networks work?

Begin with Network+ topics. Learn what an IP address, router, DNS server, and port do. They give security concepts something concrete to connect to.

Already work in IT or understand the networking basics?

Review Security+ objectives and identify gaps. Pair concepts with scenarios. Add Linux practice to become more comfortable investigating and managing systems.

The certification path is Network+ → Security+. It is a suggested learning route, not an official prerequisite chain. Basic Linux skills are useful alongside it; a dedicated free introductory Linux resource is planned separately. Later offerings will focus on certifications for mid-to-senior practitioners, with the specific certifications and release dates still undecided.

2. Make a routine small enough to repeat

Start with three 45-minute study blocks and one 30-minute review each week. That is a suggested 2 hours 45 minutes, not an exam-completion estimate. If that is too much, shorten the blocks and extend the plan.

Put your next block on the calendar: Day __________ Time __________ Topic __________

3. Your first four weeks

Week 1 · Understand a connection

Learn: Device, local network, router, IP address, and DNS.

Practice: Sketch how your own laptop or phone reaches a website. Label the device, router, internet connection, DNS lookup, and destination. On Windows, run ipconfig; on Linux, run ip address. Identify your own device’s address and explain its role.

Keep: A labeled sketch and a short explanation of what a router and DNS server do. Keep personal network details in your private notes.

Check: Can you explain why having Wi-Fi does not always mean a website will load?

Week 2 · Work through a troubleshooting question

Learn: The difference between a connection problem, a name-resolution problem, and an application problem.

Practice: On your own computer, use nslookup example.com to inspect a DNS answer. Write down what the command asks and what the answer tells you. If the tool is unavailable, use the scenario below as a paper exercise.

Scenario: A colleague says “the internet is broken,” but only one website fails. List three questions you would ask before changing any settings.

Keep: A troubleshooting note with the symptom, evidence, possible explanations, and next check. A DNS response alone does not prove that a website is available.

Week 3 · Make a security decision

Learn: Authentication, authorization, least privilege, and multifactor authentication.

Practice: Imagine a new employee needs access to one shared project folder. Specify what they should be able to read or change, who approves it, and when access should be reviewed. Explain why administrator access is unnecessary.

Keep: A one-page access recommendation: the need, the minimum permission, the risk, and the review step.

Check: Explain the difference between proving who you are and deciding what you may access.

Week 4 · Get familiar with Linux and explain your work

Learn: Users, directories, file permissions, and the purpose of system logs.

Practice: In a Linux practice environment you own or are authorized to use, try pwd, ls -l, and id. Explain what each command displays. These commands inspect information; they do not change permissions or files.

No Linux environment yet? Sketch a small directory tree and explain how owner, group, and other permissions work. Note environment setup as your next learning task.

Keep: A short walkthrough of what you learned. Finish with a 60-second spoken explanation of one exercise from the month.

4. Keep evidence, not just completed lessons

Copy this template into a private note. Later, use a cleaned-up version to describe your practice in a portfolio or interview. Describe it as a learning exercise, not professional experience.

Date and topic: What I was trying to understand: My practice environment or scenario: What I did: What I observed: One mistake or uncertainty: How I would explain this to someone else: My next step:

Example resume wording, only after doing the exercise: “Created a sample access-control recommendation for a project folder and documented a least-privilege rationale.” Make your own wording accurate to your work.

5. Connect study to actual opportunities

Read five current job listings in your target location. Include IT support and junior operations roles as well as security roles. Record the skills, experience, and certifications they request. Compare recurring requirements with your skills log.

Your first role may be in IT support or networking. A route through adjacent work can help you gain experience relevant to security. A certification alone does not guarantee a job or a particular salary.

6. Before paying for an exam or course

Training budget: __________ Exam budget: __________ Weekly study time: __________

Use CompTIA’s current certification pages for official requirements and exam information: Network+ and Security+.

Your next move

Choose one 45-minute block. Pick one topic. Finish with a note you can explain in your own words. That is a useful first step.

Compare Network+ and Security+ study packages