Starting My 6-Month Cybersecurity Journey

özgür yılmaz Posted on Jul 22 Starting My 6-Month Cybersecurity Journey #career #cybersecurity #beginners #blueteam I've always been curious about cybersecurity. Not just "it seems cool," but the real stuff — how systems get broken into, and how someone catches it happening. So today I'm starting something new: six months of focused learning to go from "interested in this" to "could actually do this job." My goal is to become a SOC analyst — someone who watches for and responds to security threats. I'll be honest about why: I want this to become a real job, not just a hobby. Both things are true — I like this stuff, and I need it to pay off too. I'm not a complete beginner. I know some basic networking and Python, and I've already done part of a CCNA course and a cybersecurity bootcamp. But there's a big difference between watching videos and actually being able to look at logs and understand what's happening. That's what I want to fix. Here's The Plan, Roughly: Build a home lab to practice in Learn the tools SOC teams actually use, like Wazuh and the ELK stack Practice real incident response, not just theory Use Python to automate parts of log analysis Build a few real projects I can show in interviews, not just certificates I can give this about 10-15 hours a week. That's not a lot, so I'm writing here regularly to keep myself accountable. If I have to post about it, I'm less likely to quietly give up. Today I set up Linux and installed VirtualBox — small step, but everything else builds on it. Next up is creating my first Kali Linux virtual machine. I also went to a Pure7 cybersecurity training (running July 22-25, 2026). Today had two sessions: SOC Operations, led by Furkan Çelik (Head of Blue Team), and Threat Intelligence, led by Adil Soybalı (Security Engineer). The most useful part was seeing a full SOC laid out as one system instead of separate buzzwords. Logs come in from everywhere — firewalls, IPS, Windows, Linux, mail servers — into a SIEM. The SIEM checks them against threat detection rules based on MITRE ATT&CK. If something looks bad, EDR/XDR and SOAR kick in to respond, while threat intelligence and vulnerability management feed information into the whole loop the whole time. Reading about SIEM and SOAR as separate terms is one thing. Seeing how they actually connect is another. Day 1. The DEV Team Promoted What's a billboard? Manage preferences Report billboard Chasing the Sentry prize for DEV's Summer Bug Smash? Let us know what questions you have. 🛹 DEV's Big Summer Bug Smash is on, and there's a dedicated Best Use of Sentry prize category. Three winners will each take home $500 USD and a Limited Edition Sentry Skateboard. Got questions about Sentry? Drop them on the post and we'll answer them live. Read more → Top comments (0) Subscribe Create template Templates let you quickly answer FAQs or store snippets for re-use. Dismiss Code of Conduct Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse I've always been curious about cybersecurity. Not just "it seems cool," but the real stuff — how systems get broken into, and how someone catches it happening. So today I'm starting something new: six months of focused learning to go from "interested in this" to "could actually do this job." My goal is to become a SOC analyst — someone who watches for and responds to security threats. I'll be honest about why: I want this to become a real job, not just a hobby. Both things are true — I like this stuff, and I need it to pay off too. I'm not a complete beginner. I know some basic networking and Python, and I've already done part of a CCNA course and a cybersecurity bootcamp. But there's a big difference between watching videos and actually being able to look at logs and understand what's happening. That's what I want to fix. Here's The Plan, Roughly: Build a home lab to practice in Learn the tools SOC teams actually use, like Wazuh and the ELK stack Practice real incident response, not just theory Use Python to automate parts of log analysis Build a few real projects I can show in interviews, not just certificates I can give this about 10-15 hours a week. That's not a lot, so I'm writing here regularly to keep myself accountable. If I have to post about it, I'm less likely to quietly give up. Today I set up Linux and installed VirtualBox — small step, but everything else builds on it. Next up is creating my first Kali Linux virtual machine. I also went to a Pure7 cybersecurity training (running July 22-25, 2026). Today had two sessions: SOC Operations, led by Furkan Çelik (Head of Blue Team), and Threat Intelligence, led by Adil Soybalı (Security Engineer). The most useful part was seeing a full SOC laid out as one system instead of separate buzzwords. Logs come in from everywhere — firewalls, IPS, Windows, Linux, mail servers — into a SIEM. The SIEM checks them against threat detection rules based on MITRE ATT&CK. If something looks bad, EDR/XDR and SOAR kick in to respond, while threat intelligence and vulnerability management feed information into the whole loop the whole time. Reading about SIEM and SOAR as separate terms is one thing. Seeing how they actually connect is another. Day 1. The DEV Team Promoted What's a billboard? Manage preferences Report billboard Chasing the Sentry prize for DEV's Summer Bug Smash? Let us know what questions you have. 🛹 DEV's Big Summer Bug Smash is on, and there's a dedicated Best Use of Sentry prize category. Three winners will each take home $500 USD and a Limited Edition Sentry Skateboard. Got questions about Sentry? Drop them on the post and we'll answer them live. Read more → I've always been curious about cybersecurity. Not just "it seems cool," but the real stuff — how systems get broken into, and how someone catches it happening. So today I'm starting something new: six months of focused learning to go from "interested in this" to "could actually do this job." My goal is to become a SOC analyst — someone who watches for and responds to security threats. I'll be honest about why: I want this to become a real job, not just a hobby. Both things are true — I like this stuff, and I need it to pay off too. I'm not a complete beginner. I know some basic networking and Python, and I've already done part of a CCNA course and a cybersecurity bootcamp. But there's a big difference between watching videos and actually being able to look at logs and understand what's happening. That's what I want to fix. Here's The Plan, Roughly: Build a home lab to practice in Learn the tools SOC teams actually use, like Wazuh and the ELK stack Practice real incident response, not just theory Use Python to automate parts of log analysis Build a few real projects I can show in interviews, not just certificates I can give this about 10-15 hours a week. That's not a lot, so I'm writing here regularly to keep myself accountable. If I have to post about it, I'm less likely to quietly give up. Today I set up Linux and installed VirtualBox — small step, but everything else builds on it. Next up is creating my first Kali Linux virtual machine. I also went to a Pure7 cybersecurity training (running July 22-25, 2026). Today had two sessions: SOC Operations, led by Furkan Çelik (Head of Blue Team), and Threat Intelligence, led by Adil Soybalı (Security Engineer). The most useful part was seeing a full SOC laid out as one system instead of separate buzzwords. Logs come in from everywhere — firewalls, IPS, Windows, Linux, mail servers — into a SIEM. The SIEM checks them against threat detection rules based on MITRE ATT&CK. If something looks bad, EDR/XDR and SOAR kick in to respond, while threat intelligence and vulnerability management feed information into the whole loop the whole time. Reading about SIEM and SOAR as separate terms is one thing. Seeing how they actually connect is another. Day 1.