What L1, L2 and L3 mean in a SOC team
Think of a hospital emergency ward. The first nurse who sees you checks how serious it is and decides who to call. A specialist then examines the case properly, and a senior consultant takes the hardest ones. A SOC works the same way, and the tiers exist so that the right level of skill is spent on the right level of problem.
Tier 1, or L1, is the front line: alert monitoring and triage. Tier 2, or L2, takes escalated cases and investigates them thoroughly. Tier 3, or L3, deals with the most complex incidents and also improves the SOC itself through threat hunting and better detection. Some companies add a Tier 0 or split things differently, so treat these labels as a guide rather than a law.
What each SOC analyst tier is responsible for
Here is a practical comparison of the three levels, in the order the work flows.
- L1 analyst: watches the SIEM queue, checks alerts against context, closes false positives and escalates suspicious activity with notes
- L1 skills to show: log reading, basic network knowledge, ticket discipline and calm under a long queue
- L2 analyst: takes escalations, correlates events across several log sources, confirms whether an incident is real and starts containment
- L2 skills to show: strong SIEM searching, malware and email analysis basics, familiarity with playbooks and runbooks
- L3 analyst: leads major incidents, hunts for threats that no alert caught, and tunes or writes detection rules
- L3 skills to show: MITRE ATT&CK fluency, threat intelligence use, forensic-style investigation and mentoring juniors
SOC L1, L2 and L3 side by side on five points
Read these as tendencies and not as fixed rules.
What each level is responsible for
L1 watches the alert queue, checks each alert against context, closes false positives and escalates the suspicious ones with notes. L2 takes escalated cases, correlates several log sources, confirms whether an incident is real and starts containment. L3 leads complex incidents, hunts for threats no alert caught and improves detection rules.
Which decisions each level is trusted to make
L1 decides whether an alert is a false positive or needs escalating, usually by following written steps. L2 decides whether an incident is confirmed, how severe it is and which containment step fits the playbook. L3 decides whether a rule or playbook must change. Taking a critical system offline usually needs approval higher still.
How deep each level goes in the tools
L1 uses the SIEM to view alerts, run prepared searches and write tickets. L2 writes its own searches across firewall, proxy, endpoint and mail logs, and uses CyberChef and Sysinternals for basic analysis. L3 tunes correlation rules, builds detections, hunts with MITRE ATT&CK and may script automation.
Where each level sends a case next
L1 escalates to L2 with a timeline and evidence, or closes the alert with a reason. L2 resolves the case, brings in service owners and IT teams, or passes the hardest cases up. L3 works with engineering to fix detection gaps and advises on major incidents.
How much of the shift is live alert work
L1 spends most of the shift on live alerts and tickets. L2 splits time between escalations and deeper investigation. L3 spends more time hunting, tuning and reviewing incidents, but is pulled in whenever something serious lands.
One strange DNS pattern handled at L1, then L2, then L3
This example is invented. The SIEM raises an offense: a finance application server has sent an unusually high number of DNS queries to one long, random-looking domain. At L1, the analyst confirms the server belongs to finance, checks it is not a backup or monitoring agent, sees the domain is new, writes a short timeline and escalates.
At L2, the investigator pulls DNS, firewall and endpoint data and sees the queries repeat at regular intervals, which resembles automated beaconing. The endpoint console shows which process is making them. Following the playbook, and with the service owner's approval, L2 isolates the server, preserves evidence and blocks the domain.
At L3, the questions widen. How did this get on the server, and is it anywhere else? The hunter searches all hosts for the same domain and pattern, maps the behaviour to a MITRE ATT&CK technique for DNS-based command and control, and writes a detection rule so the next case is caught sooner. Each level answered a different question about one alert.
Interview questions to be ready for at each level
These are typical, not a fixed script. Practise answering aloud.
- L1: Walk me through how you would triage a large number of failed logins on one account.
- L1: How do you decide an alert is a false positive, and what do you write in the ticket?
- L1: What is the difference between an event, an alert and an incident?
- L2: An alert shows a workstation contacting an unknown domain. Which sources do you check, and in what order?
- L2: How do you decide between containing a machine at once and gathering more evidence first?
- L2: Explain how you would analyse a suspicious email header and attachment.
- L3: How would you hunt for attacker persistence on Windows machines, using MITRE ATT&CK?
- L3: A rule produces many false positives. How do you tune it without creating a blind spot?
- L3: What goes into a post-incident review, and how do you turn it into better detection?
How to tell which level a SOC job listing really is
Titles can mislead. These six checks tell you what the job is.
Read the verbs and not the title
Monitor and triage point to L1. Investigate, correlate and contain point to L2. Hunt, tune, build detections and lead incidents point to L3.
Check whether the role owns the queue or receives escalations
An analyst who opens alerts first is working at L1, whatever the title says. One who receives cases from others is at L2 or above.
Look at how deeply the listing uses the tools
Viewing dashboards is different from writing searches and rules.
Ask who is allowed to contain a machine
The answer shows how much decision-making the role carries.
Ask about shifts, on-call and rotation
Higher levels may be on call for serious incidents, and providers may rotate people between levels.
Ask who tunes the rules and how analysts give feedback
A SOC where analysts can flag noisy rules and see them fixed is a better place to learn.
How to move from SOC L1 to L3
Promotions rarely come from waiting. They come from doing visible, useful work slightly above your current tier.
Get good at SOC L1 duties first
Get your triage fast and accurate, keep your ticket notes clean and learn why your false positives happen. A reliable L1 who understands the rules is far more promotable than a fast but sloppy one.
Ask L2 for feedback on your escalations
When L2 closes a case you escalated, read their notes and ask what clues you missed. That feedback loop is the fastest free training available inside a SOC.
Learn SIEM searches and rule tuning
Move from viewing offenses to writing searches, building reference sets and tuning correlation rules. Being the person who can reduce false positives makes you useful very quickly.
Add incident handling skills for SOC L2
Study the incident response lifecycle, playbooks and runbooks, and practise containment decisions in simulations. L2 is where response begins, so your judgement here is being watched.
Learn threat hunting with MITRE ATT&CK
Start forming hypotheses such as "if an attacker used this technique, what would it leave in our logs?" and test them. This is the bridge from reactive work to L3 thinking.
Add SOC analyst certifications
Certifications like CompTIA CySA+, EC-Council Certified SOC Analyst, Microsoft SC-200, IBM QRadar SIEM and GIAC Certified Incident Handler each map to a stage in the ladder. They are proof, not a shortcut.
Mentor new SOC joiners and write playbooks
Write playbooks, train new joiners and present findings. Leaders are promoted for making the team better, not only for their own tickets.
Why some SOC analysts stay at L1 for years
The usual reason is not lack of talent. It is comfort. An L1 queue can keep you busy indefinitely, and if you never look beyond it you can repeat the same year several times. People who move up tend to treat every closed alert as a small case study.
Another reason is tool shallowness. Someone who only knows the dashboard and not the underlying log sources hits a ceiling fast. Investing time in how logs from Windows, Linux, firewalls, proxies and IPS or WAF devices actually look pays off more than most people expect.
Which SOC tier fits which background
You do not have to want L3 on day one, but it helps to know where different backgrounds naturally slot in.
A fresher with strong fundamentals aiming at L1
Aim at L1 and Security Monitoring Analyst openings. Show that you can triage, document and escalate cleanly, and that you are already learning the SIEM in depth.
An IT admin with two or three years of experience
You may be able to interview for L1 with a faster path to L2, since you already understand infrastructure and troubleshooting.
A current L1 analyst aiming for L2
Focus on SIEM tuning, incident response and threat hunting. That combination is the usual bridge into L2 and toward incident response and hunting tracks.
Someone who wants to lead a SOC team eventually
Technical depth comes first, but start building reporting and communication skills early. SOC Team Lead roles reward analysts who can explain clearly and organise others.
How our SOC training covers every tier
The five modules were sequenced so that a learner sees the whole ladder, even though most freshers will start at L1.
SOC tier structure module
The Inside a Security Operations Center module teaches SOC structure, roles and the escalation path from Tier 1 to Tier 3, so you know what each level expects of you.
SIEM skills for SOC L1 and L2
Five weeks on IBM QRadar and Splunk cover correlation rules, false positives, reference sets and tuning, the skills that make an L1 valuable and prepare an L2.
Response and hunting skills for SOC L2 to L3
The final module covers the incident response lifecycle, playbooks and runbooks, MITRE ATT&CK, threat intelligence and a Threat Hunting Project.
Internship and profile help for SOC tiers
A two-month real-time internship, together with resume, GitHub and LinkedIn help, gives you evidence of the work you have done so far.
Mock interviews on SOC tier questions
Mock interviews cover the "what would you do at L1 versus L2" style of question, and placement support includes resume reviews and a hiring-partner network.
SOC analyst roles and pay by tier
Numbers are indicative only and depend on the employer, city and your skills. They are not a promise.
- L1 stage: SOC Analyst (L1), Security Monitoring Analyst, Alert Triage Specialist
- L2 stage: SOC Analyst (L2), Security Analyst, Incident Response Analyst
- L3 and specialist stage: Junior Threat Hunter, Threat Intelligence Analyst, SIEM or Security Engineer
- Leadership stage: SOC Team Lead, Security Architect, and over the long term a CISO path
- An indicative India range of about ₹3L to ₹9L per year for entry-to-mid SOC roles, typically rising with certifications and shift experience
- An indicative global range of about $50K to $95K per year in mature markets for equivalent roles
Begin the SOC ladder with careful triage
You do not need to know your L3 destination today. You need to learn the tier you are aiming at and start practising one level above it. Do that consistently and the titles tend to follow.

