A SOC is a team of different roles
People often picture a SOC as one job: watching alerts. In practice a SOC has analysts who triage, responders who contain incidents, hunters who look for what alerts missed, engineers who build the detections and analysts who track attackers. They share a foundation and then specialise.
Our post on SOC L1, L2 and L3 explains the seniority tiers. This roadmap is about the role branches across those tiers, and what to learn for each.
Stage 2: the branch for each SOC role
Each branch matches a role page on our site.
SOC Analyst (L1)
Alert triage in IBM QRadar and Splunk, reading offenses, writing clear tickets and knowing when to escalate. First proof: three triaged alerts with your verdict and reasoning.
Security Monitoring Analyst
Firewall, proxy, IPS and WAF logs, dashboards and spotting unusual patterns across sources. First proof: a monitoring dashboard with documented use cases.
Incident Response Analyst
The response lifecycle, playbooks and runbooks, containment, eradication and recovery, plus a clean handoff. First proof: a full incident report with a timeline.
Threat Hunter
MITRE ATT&CK, the Kill Chain, IOCs and IOAs, Sysinternals and hypothesis-led searches for activity no alert caught. First proof: a hunt write-up from hypothesis to finding.
SIEM Engineer
Onboarding log sources with Win Collect, parsing, writing and tuning correlation rules and reducing false positives. First proof: a detection rule with test results before and after tuning.
Threat Intelligence Analyst
Collecting and enriching indicators, OSINT with Google Dorks, CyberChef and mapping adversaries to ATT&CK. First proof: a short intel report on one threat group.
Stage 3: where each SOC role leads
How SOC careers usually grow beyond the first role:
- SOC Analyst L1 → L2 → L3 / Senior Analyst → SOC Team Lead → SOC Manager.
- Security Monitoring Analyst → Detection Engineer → Detection Engineering Lead.
- Incident Response Analyst → DFIR Specialist → Incident Response Manager.
- Threat Hunter → Senior Threat Hunter → Threat Hunting or Red/Purple Team Lead.
- SIEM Engineer → Security Engineer → Security Architect.
- Threat Intelligence Analyst → Senior CTI Analyst → Threat Intelligence Lead; long term, CISO via management.
Certifications that fit each SOC branch
Pick the one that matches your branch rather than collecting all of them:
- Starting out: ISC2 Certified in Cybersecurity (CC) or CompTIA Security+.
- L1, monitoring and triage: EC-Council Certified SOC Analyst (CSA) or Microsoft SC-200.
- SIEM engineering: IBM QRadar SIEM certification, or the vendor certification for the SIEM your team uses.
- Incident response and hunting: CompTIA CySA+, then GIAC GCIH as you gain experience.
Which SOC branch suits your starting point
Most people start at L1 or monitoring, then specialise. Your background hints at where you will go next.
You are careful and like clear procedures
L1 triage and incident response reward consistent, well-documented work.
You are curious and like digging
Threat hunting and threat intelligence suit people who keep asking "what else did the attacker do?"
You come from system or network administration
SIEM engineering builds directly on your knowledge of logs and infrastructure.
You are a fresher
Aim for L1 or security monitoring first. Every other branch is easier after a year of real alerts.
Quick answers about the SOC analyst roadmap
Short answers to the roadmap questions SOC learners ask most.
What should I learn first to become a SOC analyst?
Networking, Windows and Linux basics, then how a SOC works and how a SIEM shows alerts. These come before any advanced tool.
Which SIEM should I learn?
Learn one well, such as Splunk or IBM QRadar. The concepts of searches, offenses and correlation rules transfer between SIEMs.
Is threat hunting a fresher role?
Usually not. Most threat hunters start in L1 or L2 roles and move into hunting once they know what normal activity looks like.
What is the difference between a SOC analyst and a SIEM engineer?
A SOC analyst investigates the alerts. A SIEM engineer builds and tunes the log sources and rules that create those alerts.
How is the SOC roadmap different from the cyber security roadmap?
The cyber security roadmap covers offensive and defensive roles. The SOC roadmap goes deeper into the defensive side: monitoring, response, hunting and detection.
Go deeper on each SOC role
Open the role page for your branch, or read the guides that fill in each stage.
Start where every SOC career starts
Set up a small lab with one Windows and one Linux machine sending logs to a free SIEM. Triage the alerts it raises for a week. Whichever part you enjoyed most, triage, digging deeper or tuning the rules, points to your branch.

