SOC Analyst Playbook: What You Actually Do Every Day
What Does a SOC Analyst Actually Do?
Section titled “What Does a SOC Analyst Actually Do?”A SOC (Security Operations Centre) Analyst monitors an organisation’s networks and systems for security threats, investigates alerts, and escalates incidents — operating as the first line of cyber defence. According to the NIST NICE Workforce Framework (SP 800-181), the SOC analyst role falls under the “Protect and Defend” category, specifically the “Cyber Defense Analysis” work role. CyberSeek.org lists SOC Analyst as the single highest-volume entry-level cybersecurity position, with tens of thousands of open roles across the United States at any given time.
But job descriptions only tell you half the story. What does the work actually feel like? What do you do when you sit down at your desk at 7 a.m. — or 7 p.m. — and open the SIEM dashboard? This page is the honest, hour-by-hour breakdown I wish someone had given me before I started studying for this role.
SOC Analyst is the role I am working toward. The more I learn about it, the more I realise it is not just “staring at a SIEM dashboard” — it is problem-solving under pressure, communicating with teams, and making judgement calls about what is a real threat versus noise. Coming from aged care and real estate in Sydney, I did not know what a SIEM was six months ago. But the core of the job — triaging situations, following procedures, escalating when something is beyond your scope, and documenting everything — is exactly what I did in my previous careers. The tools are different. The thinking is the same.
What Does a Typical Day Look Like? (Hour by Hour)
Section titled “What Does a Typical Day Look Like? (Hour by Hour)”Every SOC is different — a managed security services provider (MSSP) handling 50 clients looks nothing like an internal SOC at a hospital. But the core workflow is consistent. Here is a realistic Tier 1 day shift based on published SOC operations guides and practitioner accounts.
| Time | Activity | Details |
|---|---|---|
| 06:45 | Arrive early, settle in | Log in, open tools, read overnight email — professional habit that experienced analysts notice |
| 07:00 | Shift handoff | Night team briefs you: open incidents, ongoing investigations, anything unusual, alerts to watch |
| 07:15 | Review SIEM dashboard | Check high-severity alerts first, scan for patterns, note anything the night team may have missed |
| 07:30 – 10:00 | Alert triage (primary task) | Work through the alert queue — investigate each alert, classify, document, escalate or close |
| 10:00 | Team standup (15 min) | Share active cases, discuss trends, align priorities with Tier 2/3 analysts and SOC lead |
| 10:15 – 12:00 | Continue triage + investigation | Deeper investigation on complex alerts, review related logs, check IOCs against threat intel |
| 12:00 – 12:45 | Lunch break | Step away from screens — SOC burnout is real, breaks are not optional |
| 12:45 – 14:00 | User-reported incidents | Investigate phishing reports from employees, analyse suspicious emails, respond to security questions |
| 14:00 – 15:00 | Deep-dive investigation | Focus time on a single complex case — correlate events, timeline reconstruction, evidence gathering |
| 15:00 – 16:00 | Documentation and housekeeping | Update tickets, close resolved alerts, tune detection rules based on today’s false positives |
| 16:00 – 16:30 | Shift handoff | Prepare handoff notes for the evening team — open cases, pending escalations, things to watch |
| 16:30 | End of shift | Log out, go home, decompress — resist the urge to check alerts from your phone |
What this tells you about the role: The majority of your day is alert triage — reviewing SIEM alerts, determining if they are genuine, and either closing them with documentation or escalating them. It is structured, procedure-driven work with moments of intense investigation. It is not glamorous, but it is the foundation of every cybersecurity career.
How Does the SOC Alert Triage Workflow Work?
Section titled “How Does the SOC Alert Triage Workflow Work?”Alert triage is the single most important skill for a Tier 1 analyst. You receive an alert from the SIEM, and your job is to answer one question: is this a real threat?
SOC Analyst Alert Triage Workflow
The daily cycle — from shift handoff to documentation
Understanding Alert Classifications
Section titled “Understanding Alert Classifications”Every alert you triage falls into one of three categories. Getting this right is the difference between a good analyst and a liability.
| Classification | Meaning | Example | Action |
|---|---|---|---|
| True Positive (TP) | The alert is real — a genuine security threat | Malware detected on an endpoint, confirmed by hash lookup and behavioural analysis | Escalate to Tier 2, begin containment per playbook |
| False Positive (FP) | The alert fired but there is no actual threat | Antivirus flagged a legitimate IT admin tool as malicious | Close with documentation explaining why it is benign, consider tuning the rule |
| Benign True Positive (BTP) | The detection is technically correct, but the activity is authorised | A vulnerability scanner triggered an IDS alert during a scheduled scan | Close with documentation noting the authorised activity, no tuning needed |
The false positive problem: In most SOCs, 70-90% of alerts are false positives (Ponemon Institute, 2023). This means the majority of your day is confirming that alerts are not threats. That sounds tedious — and sometimes it is — but it requires judgement, attention to detail, and the discipline to investigate each alert thoroughly even when you suspect it is benign. The one real alert you catch in a sea of false positives is the one that matters.
The Triage Process Step by Step
Section titled “The Triage Process Step by Step”When an alert appears in your queue, here is how experienced Tier 1 analysts work through it:
- Read the alert details. What triggered it? Which detection rule fired? What system is involved? What user account?
- Check the context. Is this system normally active at this time? Is this user expected to perform this activity? Has this alert fired before?
- Look up indicators. Check IP addresses, domain names, and file hashes against threat intelligence feeds (VirusTotal, AbuseIPDB, internal threat intel).
- Correlate with other events. Are there related alerts from the same source? Other systems showing similar behaviour? This is where SIEM correlation rules save time.
- Make the call. True positive, false positive, or benign true positive? Document your reasoning.
- Take action. Escalate TPs. Close FPs with clear notes. Flag patterns that suggest rule tuning.
- Document everything. Every step you took, every source you checked, every conclusion you reached. Future analysts — including your future self — will rely on this documentation.
Time per alert: Experienced Tier 1 analysts typically spend 5-15 minutes per standard alert and 30-60 minutes on complex investigations. In a busy SOC, you might triage 20-40 alerts per shift.
What Tools Do SOC Analysts Use Every Day?
Section titled “What Tools Do SOC Analysts Use Every Day?”You do not need to master every tool before getting hired. But you should know what each category does and have hands-on experience with at least one SIEM platform.
SIEM (Security Information and Event Management)
Section titled “SIEM (Security Information and Event Management)”Your primary workspace. The SIEM collects logs from across the entire organisation — firewalls, endpoints, servers, cloud services, email — and correlates them to generate alerts.
| SIEM Platform | Where You See It | Free Training |
|---|---|---|
| Splunk | Enterprise SOCs, MSSPs | Splunk Free tier, Splunk Education, TryHackMe Splunk rooms |
| Microsoft Sentinel | Microsoft-heavy organisations, Azure environments | Microsoft Learn SC-200 path, free Sentinel sandbox |
| Elastic (ELK Stack) | Start-ups, budget-conscious orgs, open-source shops | Free download, Elastic training portal |
| IBM QRadar | Large enterprises, government | IBM Security Learning Academy |
| Google Chronicle (SecOps) | Google Cloud organisations | Google Cloud Skills Boost |
Which one to learn first: If you have no preference, start with Splunk — it has the largest market share and the most job postings mention it. If your target employers run Microsoft environments, Sentinel is the better choice. Both have free learning resources.
EDR (Endpoint Detection and Response)
Section titled “EDR (Endpoint Detection and Response)”EDR tools give you visibility into what is happening on individual endpoints — laptops, servers, workstations. They detect malicious behaviour, isolate compromised devices, and provide forensic data.
- CrowdStrike Falcon — the market leader, common in enterprise SOCs
- Microsoft Defender for Endpoint — integrated with Sentinel, common in Microsoft shops
- Carbon Black (VMware) — popular in larger enterprises
- SentinelOne — growing market share, strong autonomous response
Ticketing and Documentation
Section titled “Ticketing and Documentation”Every alert, investigation, and incident gets tracked in a ticketing system. This is not glamorous, but it is essential.
- ServiceNow — enterprise standard for ITSM and security operations
- Jira — common in technology companies and smaller SOCs
- TheHive — open-source security incident response platform
- Internal wikis/Confluence — for playbooks, runbooks, and knowledge base
Network Analysis
Section titled “Network Analysis”- Wireshark — packet capture and analysis for network-based investigations
- Zeek (formerly Bro) — network security monitoring and traffic analysis
- tcpdump — command-line packet capture for quick network checks
Threat Intelligence
Section titled “Threat Intelligence”- VirusTotal — check file hashes, URLs, and IP addresses against multiple antivirus engines
- AbuseIPDB — community-driven IP address reputation database
- MITRE ATT&CK Navigator — map observed techniques to the ATT&CK framework
- AlienVault OTX — open threat exchange with community-contributed IOCs
What Are the Most Common Alert Types?
Section titled “What Are the Most Common Alert Types?”Knowing what alerts you will actually see helps you prepare. These are the categories that fill most SOC alert queues.
| Alert Type | What It Looks Like | Investigation Steps |
|---|---|---|
| Phishing / suspicious email | User reports or email gateway flags a suspicious message | Check headers, analyse URLs/attachments in sandbox, determine if user clicked, check for other recipients |
| Malware detection | Antivirus or EDR flags a file as malicious | Verify the hash against threat intel, check if it executed, review process tree, determine lateral movement |
| Brute-force login attempts | Multiple failed logins from a single source | Check if any attempts succeeded, verify source IP reputation, determine if accounts are locked, look for credential stuffing patterns |
| Suspicious PowerShell/script execution | EDR detects encoded or obfuscated scripts | Decode the command, review the user context, check if this is legitimate admin activity or potential attack |
| Impossible travel | User logs in from two geographic locations within an impossible timeframe | Verify if VPN was involved, check if the user has multiple devices, look for other suspicious activity on the account |
| Data exfiltration indicators | Unusually large outbound data transfers | Identify the destination, check if it is a known service, verify with the user/team, review data classification |
| Vulnerability scanner triggers | IDS/IPS alerts during a scheduled vulnerability scan | Confirm the scan was authorised and scheduled, classify as benign true positive, document |
What Is the Reality of Shift Work in a SOC?
Section titled “What Is the Reality of Shift Work in a SOC?”This is the part most “become a SOC analyst” content glosses over. Most 24/7 SOCs run in shifts, and if you are Tier 1, you will likely work some combination of days, evenings, and nights.
Common Shift Patterns
Section titled “Common Shift Patterns”- 12-hour rotating: Two day shifts (07:00–19:00), two off, two night shifts (19:00–07:00), two off. This is the most common pattern in MSSPs.
- 8-hour fixed: Three shifts — morning (07:00–15:00), afternoon (15:00–23:00), night (23:00–07:00). Teams rotate monthly or quarterly.
- Follow-the-sun: Global SOCs pass work between time zones so no single location works nights. Common in large enterprises.
- On-call hybrid: Smaller SOCs with business-hours coverage and on-call rotation for nights and weekends.
Burnout Prevention (This Is Not Optional)
Section titled “Burnout Prevention (This Is Not Optional)”SOC analyst burnout is well-documented. The Ponemon Institute found that 65% of SOC analysts have considered quitting due to stress and burnout. The SANS 2023 SOC Survey reported alert fatigue and understaffing as the top two challenges.
Practical burnout prevention:
- Take your breaks. Do not eat lunch at your desk while triaging alerts. Step away from screens.
- Set boundaries around shift work. When your shift ends, stop working. Do not check alerts from your phone.
- Focus on what you can control. You cannot fix the organisation’s entire security posture in one shift. Triage well, document well, escalate well.
- Build skills deliberately. Spending 30 minutes per shift on learning (TryHackMe rooms, certification study, reading threat intel reports) prevents stagnation.
- Talk about it. If the workload is unsustainable, raise it with your manager. SOC staffing is a leadership problem, not a personal failure.
The good news: Most analysts rotate off permanent night shifts within 12-24 months as they advance to Tier 2 or move into a non-shift role (security engineering, GRC, threat intelligence). Night shifts are a temporary trade-off, not a permanent lifestyle.
How Do SOC Tiers Compare?
Section titled “How Do SOC Tiers Compare?”Understanding the tier structure helps you see where you start, what progression looks like, and what skills to develop.
SOC Tier 1 vs Tier 2 vs Tier 3
- Monitor and triage alerts — Review SIEM queue, classify TP/FP/BTP, escalate confirmed incidents
- Follow playbooks — Execute documented procedures for common alert types
- 0-2 years experience — Security+ required, CySA+ helpful
- Shift work expected — 24/7 SOCs mean nights and weekends at Tier 1
- $55K-$75K USD / $65K-$95K AUD — Entry-level compensation varies by market
- Deep-dive investigations — Handle escalated incidents, correlate across data sources, determine scope
- Develop detection rules — Write and tune SIEM correlation rules, reduce false positives
- 2-4 years experience — CySA+ or GCIH typical, scripting ability valuable
- Less shift work — Often business hours with on-call rotation instead of permanent nights
- $70K-$95K USD / $90K-$120K AUD — Mid-level compensation reflects specialisation
Salary figures are approximate, sourced from CyberSeek, BLS, and Hays Salary Guide (Australia) as of 2025. Individual results vary based on location, experience, market conditions, and effort invested.
What Do Hiring Managers Look for in Entry-Level SOC Candidates?
Section titled “What Do Hiring Managers Look for in Entry-Level SOC Candidates?”This is based on published hiring guides from SOC managers, Reddit threads from security hiring managers, and common job posting requirements. These are the things that actually get you hired — not the 47-item wish lists in job descriptions.
Must-Haves (Non-Negotiable)
Section titled “Must-Haves (Non-Negotiable)”| Requirement | Why | How to Demonstrate |
|---|---|---|
| CompTIA Security+ (or equivalent) | Proves baseline security knowledge | Certification on your resume |
| Basic networking | You cannot analyse traffic without understanding TCP/IP, DNS, HTTP, ports | Home lab, TryHackMe Network Fundamentals, explain during interview |
| SIEM familiarity | The SIEM is your primary tool — you need to navigate it | Splunk Free lab, TryHackMe SOC Level 1, mention specific queries you have written |
| Written communication | Every alert requires clear documentation | Bring a sample incident write-up to the interview |
| Genuine curiosity | Hiring managers filter for people who actually enjoy investigating | Talk about something you investigated on your own — a home lab finding, a CTF challenge, a TryHackMe room |
Good to Have (Differentiators)
Section titled “Good to Have (Differentiators)”- CySA+ certification — directly maps to Tier 1-2 work and signals commitment
- Home lab with documented findings — shows initiative beyond certification study
- TryHackMe SOC Level 1 completion — structured, verifiable training that maps to the job
- Basic scripting (Python or PowerShell) — not required at Tier 1, but shows growth potential
- Customer-facing experience — SOC analysts communicate with users, teams, and managers constantly
What Hiring Managers Actually Say
Section titled “What Hiring Managers Actually Say”“I hire for curiosity and communication. I can teach someone to use Splunk in two weeks. I cannot teach them to care about getting to the bottom of an alert.” — SOC Manager, Reddit r/cybersecurity
“If a candidate shows me a home lab and can walk me through an investigation they did on their own, they go straight to the top of the pile. Most applicants just list Security+ and hope for the best.” — MSSP Hiring Manager
“Career changers often underestimate how relevant their previous experience is. I hired a former nurse as a Tier 1 analyst. She was the best at triage, documentation, and staying calm during incidents — because that is exactly what she did in the emergency department.” — SOC Director, CyberCX
Skills You Can Learn on the Job (Do Not Stress About These)
Section titled “Skills You Can Learn on the Job (Do Not Stress About These)”- Proprietary SIEM queries and dashboards — every SOC has its own setup
- Organisation-specific playbooks — you will follow these, not write them initially
- Internal tooling and processes — ticketing workflows, escalation paths, communication channels
- Specific EDR platforms — training is typically provided during onboarding
- Industry-specific compliance — healthcare SOCs care about HIPAA, finance SOCs care about PCI DSS, you learn this in context
Salary Expectations for SOC Analysts
Section titled “Salary Expectations for SOC Analysts”Understanding the compensation landscape helps you set realistic expectations and negotiate effectively.
United States
Section titled “United States”| Level | Typical Salary Range | Key Factors |
|---|---|---|
| SOC Analyst Tier 1 | $55,000 – $75,000 | Higher in major metros (NYC, DC, SF), lower in remote/rural areas |
| SOC Analyst Tier 2 | $70,000 – $95,000 | Specialisation and certifications drive the upper range |
| SOC Analyst Tier 3 / Lead | $90,000 – $130,000+ | Threat hunting, detection engineering, and management |
Australia
Section titled “Australia”| Level | Typical Salary Range (AUD) | Key Factors |
|---|---|---|
| SOC Analyst Tier 1 | $65,000 – $95,000 | Sydney and Melbourne command premium; government roles may require clearance |
| SOC Analyst Tier 2 | $90,000 – $120,000 | CySA+ or GCIH-level certification expected |
| SOC Analyst Tier 3 / Lead | $120,000 – $160,000+ | Threat hunting, team leadership, architecture input |
Salary data sourced from CyberSeek, BLS Occupational Outlook Handbook, Hays Salary Guide, and Seek.com.au as of 2025. Individual results vary based on location, experience, market conditions, and effort invested.
Additional compensation factors:
- Shift differentials — many SOCs pay 10-15% extra for night and weekend shifts
- Certifications — each relevant certification can add $5,000-$10,000 to your negotiating position
- Clearance — government and defence SOCs often pay 15-25% above market for cleared analysts
- Remote work — some SOC roles are fully remote (especially at MSSPs), but many require on-site presence for security reasons
The interview guide includes SOC analyst-specific questions — the exact scenarios and technical questions hiring managers ask entry-level SOC candidates.
Cybersecurity Interview GuideAvailable Now
60+ real interview questions with model answers, STAR frameworks, and salary negotiation.
How to Get SOC Experience Without a SOC Job
Section titled “How to Get SOC Experience Without a SOC Job”This is the catch-22 that every career changer faces: you need experience to get hired, but you need a job to get experience. Here is how to break the cycle.
Build a Home SOC Lab
Section titled “Build a Home SOC Lab”Set up a virtual environment that simulates SOC operations. This is the single most impactful thing you can do.
- Install Splunk Free on a Linux VM — it processes up to 500 MB of logs per day, which is plenty for learning.
- Set up a Windows VM with Sysmon — Sysmon generates detailed endpoint logs that mimic what you would see in a real SOC.
- Forward logs from your Windows VM to Splunk — now you have a mini SIEM environment.
- Generate alerts by simulating attacks — use Atomic Red Team (free) to run safe, controlled attack simulations and watch the alerts appear in Splunk.
- Triage your own alerts — investigate each one as if you were in a real SOC. Document your findings.
Total cost: $0 if you use your existing computer with free virtualisation software (VirtualBox or VMware Player).
Complete Structured Training Paths
Section titled “Complete Structured Training Paths”| Platform | Relevant Path | Cost | Value |
|---|---|---|---|
| TryHackMe | SOC Level 1 | $14/month | Structured, hands-on SOC training with real-world scenarios |
| TryHackMe | SOC Level 2 | $14/month | Deeper investigation, threat hunting, detection engineering |
| LetsDefend | SOC Analyst path | Free tier available | Alert triage practice with realistic SOC simulator |
| Splunk Education | Splunk Fundamentals 1 | Free | Official Splunk training — learn the SIEM most SOCs use |
| Microsoft Learn | SC-200 learning path | Free | Microsoft Sentinel and Defender for SOC operations |
| Blue Team Labs Online | Various challenges | Free tier available | Hands-on blue team challenges and investigations |
Practise With Real-World Data
Section titled “Practise With Real-World Data”- Download sample PCAP files from Malware Traffic Analysis (malware-traffic-analysis.net) and investigate them in Wireshark
- Analyse sample logs from the BOTS (Boss of the SOC) dataset — Splunk’s competition dataset with realistic SOC scenarios
- Complete CTF challenges focused on blue team — TryHackMe Advent of Cyber, SANS Holiday Hack, Blue Team Labs Online
- Write investigation reports for everything you do — this builds the documentation skill that hiring managers care about
Document Everything in a Portfolio
Section titled “Document Everything in a Portfolio”Create a simple blog or GitHub repository that documents your SOC learning journey. For each lab exercise or investigation:
- Describe the scenario and the alert you received
- Walk through your investigation steps
- Explain your classification (TP/FP/BTP) and reasoning
- Include screenshots of your SIEM queries and findings
This portfolio is more valuable than a second certification. It shows hiring managers exactly how you think, investigate, and communicate — the three things they are actually hiring for.
Summary and Key Takeaways
Section titled “Summary and Key Takeaways”The SOC analyst role is structured, procedure-driven work with moments of intense investigation. It is not glamorous, but it is the foundation of every cybersecurity career.
- Alert triage is the core skill. You receive alerts, investigate them, classify them as true positive, false positive, or benign true positive, and take action. Most of your day is this workflow.
- 70-90% of alerts are false positives. Patience, discipline, and thorough investigation of every alert are what separate good analysts from poor ones.
- Shift work is real but temporary. Most Tier 1 analysts rotate off night shifts within 12-24 months as they advance.
- Tools matter less than thinking. Hiring managers can teach you Splunk in two weeks. They cannot teach you curiosity, communication, and investigative discipline.
- Build a home lab. Splunk Free + Windows VM with Sysmon + Atomic Red Team gives you a realistic practice environment at zero cost.
- Document everything. A portfolio of investigation write-ups is more valuable than a second certification for getting hired.
- Career changers have relevant skills. Triage, documentation, following procedures under pressure, and clear communication — if you did these in your previous career, you already have SOC analyst instincts.
- Tier 1 is the beginning, not the destination. SOC → Tier 2 → Security Engineer / IR / Threat Intel / Cloud Security → Architect / CISO. The path is clear and well-worn.
Individual results vary. Career timelines, salary outcomes, and job availability depend on your location, experience, market conditions, and effort. The information on this page is educational, not a guarantee of employment outcomes.
Related
Section titled “Related”- Blue Team Overview for the full picture of defensive cybersecurity
- Alert Triage for a deep dive into the triage process and classification frameworks
- Log Analysis for reading and interpreting the security logs you will investigate daily
- Incident Response for what happens when an alert becomes a confirmed incident
- Home Lab Setup to build the practice environment described on this page
Frequently Asked Questions
What does a SOC analyst do on a daily basis?
SOC analysts spend the majority of their day triaging security alerts from a SIEM platform — reviewing each alert, investigating whether it represents a genuine threat (true positive) or a false alarm (false positive), escalating confirmed incidents to senior analysts, and documenting every investigation step. They also respond to user-reported phishing emails, participate in team standups, and update detection rules.
What tools do SOC analysts use?
Core tools include SIEM platforms (Splunk, Microsoft Sentinel, Elastic) for log aggregation and alerting, EDR tools (CrowdStrike, Microsoft Defender, Carbon Black) for endpoint visibility, Wireshark for packet analysis, ticketing systems (ServiceNow, Jira) for incident tracking, and threat intelligence platforms (VirusTotal, AbuseIPDB) for indicator lookups. You do not need to master every tool before getting hired — SIEM familiarity and one EDR platform are sufficient for Tier 1.
How much do SOC analysts earn?
In the United States, SOC Analyst Tier 1 salaries typically range from $55,000 to $75,000, Tier 2 from $70,000 to $95,000, and Tier 3 from $90,000 to $130,000+. In Australia, Tier 1 ranges from AUD $65,000 to $95,000. Salary varies significantly by location, employer type (MSSP vs enterprise vs government), certifications, and security clearance. Individual results vary based on market conditions and experience.
Do SOC analysts work night shifts?
In 24/7 SOCs, yes — Tier 1 analysts typically work rotating shifts that include nights and weekends. Common patterns are 12-hour rotating shifts or 8-hour fixed shifts. Most analysts rotate off permanent night shifts within 12-24 months as they advance to Tier 2 or move into non-shift roles. Some SOCs operate business hours only with on-call coverage for off-hours.
What is the difference between a true positive and a false positive?
A true positive (TP) is an alert that correctly identifies a genuine security threat — real malware, an actual intrusion, or confirmed malicious activity. A false positive (FP) is an alert that fired incorrectly — the detection rule triggered but there is no actual threat. A benign true positive (BTP) is when the detection is technically correct but the activity is authorised, such as a vulnerability scanner triggering an IDS alert during a scheduled scan.
Can I become a SOC analyst with no IT experience?
Yes. SOC Analyst Tier 1 is specifically designed as an entry-level role. You need CompTIA Security+, basic networking knowledge (TCP/IP, DNS, common ports), familiarity with at least one SIEM platform (achievable through a home lab or TryHackMe), and strong documentation skills. Career changers from healthcare, education, customer service, and other fields have successfully transitioned by demonstrating transferable skills alongside technical preparation.
How do I get SOC experience without having a SOC job?
Build a home SOC lab with Splunk Free and a Windows VM running Sysmon. Complete TryHackMe SOC Level 1 path. Practise with LetsDefend SOC simulator. Analyse sample PCAP files from Malware Traffic Analysis in Wireshark. Complete the BOTS (Boss of the SOC) dataset challenges. Document everything in a portfolio — investigation write-ups showing your process are more valuable to hiring managers than a second certification.
What is SOC analyst burnout and how do I prevent it?
SOC analyst burnout is well-documented — the Ponemon Institute found that 65% of SOC analysts have considered quitting due to stress. It is caused by alert fatigue (70-90% of alerts are false positives), understaffing, shift work, and the pressure of knowing that missed alerts have real consequences. Prevention includes taking breaks, setting boundaries around shift work, building skills deliberately, and raising workload concerns with management. Most analysts move beyond Tier 1 shift work within 12-24 months.
More resources
The official work role definition for SOC analysts within the NIST NICE Workforce Framework.
SANS SOC ResourcesFree SOC operations guides, posters, and the SANS SOC Survey — practical guidance for building and running security operations.
CyberSeek Career PathwayInteractive tool showing SOC Analyst workforce demand, salary data, and career progression paths.
Splunk Free DownloadSplunk Free tier for home lab practice — process up to 500 MB of logs per day at no cost.
Sources: NIST NICE Framework (SP 800-181), SANS SOC Survey 2023, Ponemon Institute, CyberSeek.org, BLS. Salary data from CyberSeek, BLS, Hays, and Seek.com.au as of 2025. Last verified: March 2026.