My 2027 Learning Plan: Certifications, Labs and Goals

At the start of every year, I sit down and plan what I want to learn. Not a vague resolution like "get better at security," but a specific plan with goals, timelines and ways to prove progress.

Cybersecurity and networking change quickly. New attack techniques appear, tools evolve and employer expectations shift. Without a plan, it's easy to spend a year bouncing between tutorials and finish with little to show for it.

This article shares my plan for 2027 and the framework behind it. I'm sharing it publicly for two reasons: writing it down makes me accountable, and I hope it helps others build their own.

Step 1: Start from the destination

A learning plan should start with the roles you want, not the courses that look interesting.

My background combines hands-on IT support for a 1,200-user manufacturing site, network support at an internet service provider, a BEng in Computer Network and Security, postgraduate studies in Cybersecurity and Threat Management and in IT Project Management, and the Certified Ethical Hacker (CEH) credential.

The roles I'm focused on build directly on that foundation:

• Security operations, such as a SOC analyst role, monitoring, investigating and responding to threats.
• Network administration, with a strong security focus.
• Systems and network support roles with growing security responsibility.

So my plan prioritizes skills that appear again and again in job postings for those roles.

Step 2: Read the job postings

Before choosing what to learn, I collected job postings for my target roles in the Toronto area and noted the skills and certifications that came up repeatedly. Common themes included:

• Security monitoring and SIEM tools.
• Incident triage and response processes.
• Windows and Active Directory administration.
• Cloud identity and Microsoft 365 security.
• Firewalls, routing and switching.
• Vulnerability management.
• Scripting for automation.
• Certifications such as CompTIA Security+ for security roles and Cisco CCNA for networking roles.

That list became the backbone of my plan. If you do one thing from this article, do this exercise. Job postings are the clearest guide to what employers need right now.

Step 3: One certification at a time

Certifications can help get your resume through screening and give structure to your study. But chasing several at once usually leads to finishing none.

My plan for 2027 is to focus on one major certification at a time, chosen to match the roles above. Security+ covers broad security fundamentals and operations and is widely requested for entry and intermediate security roles. CCNA covers networking in depth and is a strong signal for network administration roles. Both build on knowledge I already have from my degree, my CEH studies and my work experience, which should make study more efficient.

For each one, my approach is:

1. Book the exam date early, so there's a real deadline.
2. Study in short, regular sessions rather than occasional marathons.
3. Pair every topic with hands-on lab practice.
4. Use practice exams to find gaps, then go back to the material.
5. Write a short summary of what I learned for LinkedIn after passing.

Step 4: Grow the home lab with purpose

My current home lab is an Ubuntu server running Docker, with Pi-hole for DNS filtering and WireGuard for secure remote access. It has taught me a lot, but it's mostly a network services lab. In 2027, I want it to look more like a small business environment, with security monitoring built in.

My lab goals:

• Add log collection and a SIEM. Collect logs from the server, containers and network devices, and practise writing detection rules. Free and open-source options make this possible on modest hardware.
• Build a small Windows domain. Practise Active Directory administration, group policy and identity security, which are central to many corporate environments.
• Add a dedicated firewall. Set up network segmentation, firewall rules and VPN access the way a business would.
• Run attack and detect exercises. Use the techniques from my CEH studies against my own lab, then check whether my monitoring catches them. Every missed detection becomes a lesson.
• Document everything. Each lab project becomes a write-up and, where appropriate, a LinkedIn article.

Step 5: Strengthen scripting

I built Forensic Raptor, my Android forensics tool, in Python, and I want to keep that skill sharp. Automation is increasingly expected in security and networking roles.

My goals:

• Write small Python scripts to automate lab tasks, such as parsing logs, checking configurations and generating reports.
• Learn enough PowerShell to automate common Windows and Active Directory tasks.
• Keep scripts in a public GitHub repository with clear documentation.

Step 6: Write and share consistently

This article series is part of my learning plan. Writing forces me to understand topics well enough to explain them, and sharing builds connections with people in the field.

My goal is to keep publishing regularly, covering lab projects, lessons from study and practical guides, and to engage with other professionals' posts rather than only sharing my own.

Step 7: Learn from people, not just material

Some of the most valuable learning happens in conversation. In 2027, I want to:

• Attend local security and networking meetups and events in Toronto.
• Have regular informational conversations with people working in the roles I'm targeting.
• Join an online community where I can ask questions and help others.

What I'm deliberately not doing

A good plan is as much about what you leave out as what you include. In 2027, I'm choosing not to:

• Chase several certifications at once. Splitting attention across multiple exams usually means slower progress on all of them.
• Learn every tool. There are hundreds of security tools. I'll focus on the categories that appear in job postings, such as SIEM, endpoint protection, firewalls and identity, and learn one good example of each well.
• Collect courses I never finish. Before starting a new course, I'll finish or drop the current one.
• Study only theory. If a topic doesn't come with a lab exercise, I'll create one.
• Learn in isolation. Progress is faster with feedback, so I'll share work and ask questions publicly.

Saying no to good options is what makes room for the important ones.

Making time and budget work

Learning takes time and money, and both are limited. A few things help me stay realistic.

Time. I plan for consistent, modest blocks: a few focused hours on weekday evenings and a longer lab session at the weekend. That's sustainable alongside work, and steady progress adds up over a year.

Budget. Exams cost money, so I plan for them in advance. Before paying for training, I use free and low-cost resources first: vendor documentation, free practice labs, open-source tools, community study groups and library resources. Home lab hardware doesn't need to be new. Older desktops and laptops run Linux, Docker and small virtual labs perfectly well.

Energy. Burnout is a real risk for anyone working and studying at the same time. I build in rest weeks and treat them as part of the plan, not a failure of it.

How I'll track progress

A plan without tracking is just a wish. I keep a simple tracker with:

• Quarterly goals: one certification milestone, one lab project and a set number of articles.
• Weekly check-ins: fifteen minutes on Sunday to review what I did and plan the week ahead.
• Evidence: a link to something tangible for every goal, such as an exam result, a lab write-up, a GitHub repository or a published article.

If a goal no longer makes sense, I change it. The plan serves my career, not the other way around.

A framework you can use

If you want to build your own plan, here's the short version:

1. Pick your target roles. Be specific.
2. Read twenty job postings for those roles and list the recurring skills and certifications.
3. Compare that list with what you already know. The gaps are your learning plan.
4. Choose one certification that closes the biggest gap, and book the exam.
5. Build a lab project for every major topic you study.
6. Make your learning visible through write-ups, GitHub and LinkedIn.
7. Review progress weekly and adjust quarterly.

The takeaway

The difference between a good year of learning and a frustrating one is rarely talent or time. It's focus. Start from the role you want, learn the skills employers ask for, practise everything hands-on and make your progress visible. Then keep going, one step at a time.

What's the one skill you most want to build this year?