SOC Analyst: market
Data as of November 19, 2026: 147 open SOC Analyst jobs, 30% remote among jobs that state a work format; median advertised salary $5,661/mo (from 8 postings that state a salary). Source: Zorky, updated daily.
SOC Analyst (Security Operations Center) — an operational security role focused on real-time monitoring, alert triage, incident detection & response. Front-line defense — watches SIEM / EDR / NDR alerts 24×7, investigates suspicious activity, escalates real incidents. The most accessible entry point to cybersecurity (vs Security Engineer / Pentester — require more experience). Role family: SOC Analyst L1 (Tier 1) (alert triage — first responder, validates / dismisses / escalates alerts, often shift work 24×7), SOC Analyst L2 (Tier 2) (deep investigation — analyzes escalated incidents, correlation, scoping), SOC Analyst L3 (Tier 3) (threat hunting + advanced incident response + detection engineering — overlap with Security Engineer), SOC Lead / SOC Manager (team leadership + shift management + metrics), Threat Hunter (proactive — hunt for threats SIEM missed), Detection Engineer (rising 2024+ — writes / tunes detection rules — SOC's engineering arm), Incident Responder (IR) (deep incident handling + forensics — often separate CSIRT team). EDR / XDR (endpoint visibility): CrowdStrike Falcon (leader), SentinelOne, Microsoft Defender for Endpoint, Palo Alto Cortex XDR. Russian: Kaspersky KEDR, MaxPatrol EDR. SOAR (automation — reduces SOC analyst toil): Palo Alto Cortex XSOAR, Splunk SOAR, Tines, Torq, Microsoft Sentinel Playbooks. NDR (Network Detection & Response): Darktrace + Vectra + PT NAD. Threat Intelligence: Recorded Future + Mandiant + MISP (open-source) + VirusTotal + AlienVault OTX. Ticketing / case management: TheHive (open-source SOC case management — popular), Jira Service Management, ServiceNow Security Operations. Frameworks & methodologies: MITRE ATT&CK (adversary TTPs taxonomy — must for modern SOC — alert mapping + coverage analysis), Cyber Kill Chain (Lockheed Martin — attack phases model), Diamond Model (intrusion analysis), Pyramid of Pain (IoC value hierarchy). Analysis tools: Wireshark (packet analysis), VirusTotal (file / URL / hash reputation), any.run + Joe Sandbox + Cuckoo (malware sandboxes), CyberChef (data decoding Swiss Army knife), Volatility (memory forensics — L3), OSINT tools (Shodan + urlscan.io + AbuseIPDB). Detection engineering (L3 / Detection Engineer): Sigma (vendor-agnostic detection rule format — standard 2026), YARA (malware pattern matching), Splunk SPL / Sentinel KQL rule authoring, Atomic Red Team + Caldera (adversary emulation for detection validation). Certifications: CompTIA Security+ → CompTIA CySA+ (Cybersecurity Analyst — SOC-focused), Blue Team Level 1 (BTL1) (Security Blue Team — practical SOC cert — rising 2024+), GIAC GSEC / GCIH / GCFA, Splunk Core Certified, Microsoft SC-200 (Security Operations Analyst). Languages: Python primary (alert enrichment + SOAR playbooks + automation), bash + PowerShell, KQL / SPL query languages. Top stack: cloud, linux, python, aws, azure. Among jobs with a stated work format, 30% are remote.
Data as of:
Key numbers for the SOC Analyst market: open jobs, median salary, observed talent pool and remote share.
The SOC Analyst market currently has 147 open roles, 133 of them freshly observed. Median salary $5,661/mo.
Among jobs with a stated work format, 30% are remote. SOC work cloud-based (SIEM / EDR / SOAR consoles remote-accessible). L1 shift work often remote-able (follow-the-sun MSSP model). Russian bank SOCs + state companies / GosSOPKA — hybrid/office due to regulatory + clearances. Russian MSSP — hybrid or remote after background-check. International MSSP — full-remote standard (MSSP business model — serve clients globally).
⚠ salary known for 8 of 147 jobs; remote share from 126 with a stated format; 133 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many SOC Analyst postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 2 |
| 2026-06-08 | 4 |
| 2026-06-15 | 0 |
| 2026-06-22 | 6 |
| 2026-06-29 | 15 |
| 2026-07-06 | 20 |
| 2026-07-13 | 9 |
| 2026-07-20 | 9 |
| 2026-07-27 | 8 |
| 2026-08-03 | 4 |
| 2026-08-10 | 10 |
| 2026-08-17 | 5 |
| 2026-08-24 | 7 |
| 2026-08-31 | 7 |
| 2026-09-07 | 7 |
| 2026-09-14 | 4 |
| 2026-09-21 | 42 |
| 2026-09-28 | 20 |
| 2026-10-05 | 20 |
| 2026-10-12 | 58 |
| 2026-10-19 | 45 |
| 2026-10-26 | 41 |
| 2026-11-02 | 42 |
| 2026-11-09 | 50 |
Active sources per week
Sources over the period: 63. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 2 |
| 2026-06-08 | 2 |
| 2026-06-15 | 0 |
| 2026-06-22 | 3 |
| 2026-06-29 | 10 |
| 2026-07-06 | 8 |
| 2026-07-13 | 5 |
| 2026-07-20 | 6 |
| 2026-07-27 | 6 |
| 2026-08-03 | 4 |
| 2026-08-10 | 4 |
| 2026-08-17 | 3 |
| 2026-08-24 | 7 |
| 2026-08-31 | 6 |
| 2026-09-07 | 5 |
| 2026-09-14 | 4 |
| 2026-09-21 | 14 |
| 2026-09-28 | 11 |
| 2026-10-05 | 13 |
| 2026-10-12 | 14 |
| 2026-10-19 | 17 |
| 2026-10-26 | 18 |
| 2026-11-02 | 17 |
| 2026-11-09 | 19 |
New sources connected: Jun 29 +9 · Sep 21 +8 · all weeks (17) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +1 | 4 |
| Jun 22 | +2 | 6 |
| Jun 29 | +9 | 15 |
| Jul 6 | +5 | 20 |
| Jul 13 | +4 | 9 |
| Jul 20 | +4 | 9 |
| Jul 27 | +2 | 8 |
| Aug 3 | +1 | 4 |
| Aug 24 | +4 | 7 |
| Sep 7 | +2 | 7 |
| Sep 21 | +8 | 42 |
| Oct 5 | +2 | 20 |
| Oct 12 | +5 | 58 |
| Oct 19 | +2 | 45 |
| Oct 26 | +4 | 41 |
| Nov 2 | +3 | 42 |
| Nov 9 | +3 | 50 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 2 | 2 |
| 2026-06-08 | 4 | 2 |
| 2026-06-15 | 0 | 0 |
| 2026-06-22 | 6 | 3 |
| 2026-06-29 | 15 | 10 |
| 2026-07-06 | 20 | 8 |
| 2026-07-13 | 9 | 5 |
| 2026-07-20 | 9 | 6 |
| 2026-07-27 | 8 | 6 |
| 2026-08-03 | 4 | 4 |
| 2026-08-10 | 10 | 4 |
| 2026-08-17 | 5 | 3 |
| 2026-08-24 | 7 | 7 |
| 2026-08-31 | 7 | 6 |
| 2026-09-07 | 7 | 5 |
| 2026-09-14 | 4 | 4 |
| 2026-09-21 | 42 | 14 |
| 2026-09-28 | 20 | 11 |
| 2026-10-05 | 20 | 13 |
| 2026-10-12 | 58 | 14 |
| 2026-10-19 | 45 | 17 |
| 2026-10-26 | 41 | 18 |
| 2026-11-02 | 42 | 17 |
| 2026-11-09 | 50 | 19 |
Remote work over time
Share of SOC Analyst postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-07-06 | 27.3 |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | 36.4 |
| 2026-09-28 | 0 |
| 2026-10-05 | 45.5 |
| 2026-10-12 | 11.5 |
| 2026-10-19 | 25 |
| 2026-10-26 | 28.1 |
| 2026-11-02 | 54.3 |
| 2026-11-09 | 36.8 |
The series starts on Jul 6: there is no data before that.
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | 27.3 |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | 36.4 |
| 2026-09-28 | 0 |
| 2026-10-05 | 45.5 |
| 2026-10-12 | 11.5 |
| 2026-10-19 | 25 |
| 2026-10-26 | 28.1 |
| 2026-11-02 | 54.3 |
| 2026-11-09 | 36.8 |
Technologies over time
How the share of SOC Analyst postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | cloud | Python | AWS |
|---|---|---|---|
| 2026-10-26 | 64 | 24 | 12 |
| 2026-11-02 | 59.4 | 21.9 | 12.5 |
| 2026-11-09 | 64.3 | 21.4 | 21.4 |
The series starts on Oct 26: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | cloud | Python | AWS | Azure | GCP |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | — | — | — | — | — |
| 2026-09-28 | — | — | — | — | — |
| 2026-10-05 | — | — | — | — | — |
| 2026-10-12 | — | — | — | — | — |
| 2026-10-19 | — | — | — | — | — |
| 2026-10-26 | 64 | 24 | 12 | 16 | 12 |
| 2026-11-02 | 59.4 | 21.9 | 12.5 | 12.5 | 9.4 |
| 2026-11-09 | 64.3 | 21.4 | 21.4 | 14.3 | 14.3 |
Countries over time
How the share of SOC Analyst postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | UK | Australia |
|---|---|---|---|
| 2026-09-21 | 20.7 | 17.2 | 0 |
| 2026-09-28 | — | — | — |
| 2026-10-05 | — | — | — |
| 2026-10-12 | 19.5 | 9.8 | 4.9 |
| 2026-10-19 | 27.8 | 8.3 | 5.6 |
| 2026-10-26 | 28.6 | 3.6 | 3.6 |
| 2026-11-02 | 28.9 | 5.3 | 5.3 |
| 2026-11-09 | 31 | 0 | 19 |
The series starts on Sep 21: there is no data before that.
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | UK | Australia | Poland | India |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | — | — | — | — | — |
| 2026-06-29 | — | — | — | — | — |
| 2026-07-06 | — | — | — | — | — |
| 2026-07-13 | — | — | — | — | — |
| 2026-07-20 | — | — | — | — | — |
| 2026-07-27 | — | — | — | — | — |
| 2026-08-03 | — | — | — | — | — |
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 20.7 | 17.2 | 0 | 0 | 3.4 |
| 2026-09-28 | — | — | — | — | — |
| 2026-10-05 | — | — | — | — | — |
| 2026-10-12 | 19.5 | 9.8 | 4.9 | 7.3 | 7.3 |
| 2026-10-19 | 27.8 | 8.3 | 5.6 | 5.6 | 2.8 |
| 2026-10-26 | 28.6 | 3.6 | 3.6 | 10.7 | 7.1 |
| 2026-11-02 | 28.9 | 5.3 | 5.3 | 2.6 | 2.6 |
| 2026-11-09 | 31 | 0 | 19 | 7.1 | 4.8 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just SOC Analyst.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open SOC Analyst jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 147 |
| Open demand | 147 |
| Observed supply | — not published |
SOC — one of the highest-headcount security segments (24×7 coverage requires many analysts). SOC — the most accessible entry to cybersecurity → high-volume L1 hiring + turnover. Russian MSSP + bank internal SOCs + GosSOPKA centers dominate. International remote via MSSP (Arctic Wolf / eSentire / Expel / Red Canary).
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in SOC Analyst jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 0 |
| $2–3k | 1 |
| $3–4k | 2 |
| $4–5k | 0 |
| $5–6k | 1 |
| $6–7k | 1 |
| $7–8k | 1 |
| $8–9k | 1 |
| $9–10k | 0 |
| $10–12k | 1 |
| $12–15k | 0 |
| $15–20k | 0 |
| $20k+ | 0 |
- usable for the calculation: 8 (5.4%)
- stated but not converted to USD/month: 21 (14.3%)
- not stated: 118 (80.3%)
One in ten postings offers under $2,737, one in ten over $11,250. Half of the postings offer between $3,000 and $7,291. Sample: 8.
⚠ percentiles from 8 salaries out of 147 jobs — a guide on a small sample
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 1 |
| $3–4k | 3,000 | 4,000 | 2 |
| $4–5k | 4,000 | 5,000 | 0 |
| $5–6k | 5,000 | 6,000 | 1 |
| $6–7k | 6,000 | 7,000 | 1 |
| $7–8k | 7,000 | 8,000 | 1 |
| $8–9k | 8,000 | 9,000 | 1 |
| $9–10k | 9,000 | 10,000 | 0 |
| $10–12k | 10,000 | 12,000 | 1 |
| $12–15k | 12,000 | 15,000 | 0 |
| $15–20k | 15,000 | 20,000 | 0 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open SOC Analyst jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 39 | 31.2% |
| Poland | 11 | 8.8% |
| United Kingdom | 9 | 7.2% |
| Philippines | 8 | 6.4% |
| India | 8 | 6.4% |
| Germany | 4 | 3.2% |
| Singapore | 4 | 3.2% |
| Belgium | 3 | 2.4% |
| Thailand | 3 | 2.4% |
| Canada | 3 | 2.4% |
| Other countries | 33 | 26.4% |
Leader by SOC job count — the US (39 positions). Russia — Russian MSSP + bank internal SOC (Sber Cyber Defense Center) + GosSOPKA centers dominate. Poland — SOC-friendly EU hub. Germany — Berlin + Munich enterprise. International remote via MSSP (Arctic Wolf / eSentire / Expel / Red Canary / Secureworks / Rapid7 MDR / Sophos MDR — business model inherently remote).
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 39 |
| PL | 11 |
| GB | 9 |
| PH | 8 |
| IN | 8 |
| DE | 4 |
| SG | 4 |
| BE | 3 |
| TH | 3 |
| CA | 3 |
Which technologies are most often required in the same job as SOC Analyst.
Used together with
Share — how many of the 147 jobs in the SOC Analyst market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top SOC stack 2026: SIEM, EDR/XDR, SOAR (Cortex XSOAR + Splunk SOAR + Tines + Torq + Sentinel Playbooks), NDR (Darktrace + Vectra + PT NAD), Threat Intelligence, ticketing/case management (TheHive open-source + Jira Service Management + ServiceNow Security Operations), frameworks (MITRE ATT&CK must + Cyber Kill Chain + Diamond Model + Pyramid of Pain), analysis tools (Wireshark + VirusTotal + any.run / Joe Sandbox / Cuckoo sandboxes + CyberChef + Volatility memory forensics + Shodan / urlscan.io / AbuseIPDB / GreyNoise OSINT), detection engineering (Sigma vendor-agnostic standard + YARA + SPL/KQL rule authoring + Atomic Red Team / Caldera adversary emulation), Python primary + bash + PowerShell + KQL/SPL query languages.
Learning roadmap: IT fundamentals (networking + OS) → Security+ → CySA+ or BTL1 → SIEM hands-on (Splunk / Sentinel) → MITRE ATT&CK fluency → home lab (Security Onion / Wazuh) → TryHackMe SOC L1/L2 paths + LetsDefend → analysis tools (Wireshark + sandboxes) → incident response basics → detection engineering (Sigma + YARA) → Python for SOC → portfolio.
Chart data
| Name | Count |
|---|---|
| cloud | 65 |
| python | 26 |
| aws | 18 |
| azure | 17 |
| gcp | 11 |
| active directory | 11 |
| servicenow | 10 |
| itil | 5 |
| sql | 4 |
| java | 4 |
| go | 4 |
| rust | 4 |
How many SOC Analyst jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 19 |
| junior | 9 |
| lead | 9 |
| middle | 9 |
| principal | 4 |
SOC — the best entry point to cybersecurity (L1 accepts juniors without commercial experience — with certs + home lab). Career flow: Entry (certs + home lab) → SOC L1 (1-2 years) → L2 (2-3 years) → L3 / Detection Engineer / Threat Hunter → either SOC Lead / Manager, or Security Engineer pivot (broader — higher ceiling), or Incident Responder, or Threat Intelligence Analyst, or Pentester (offensive pivot). SOC L1 — not a dead end, but a proven launchpad: many Senior Security Engineers / Pentesters started in SOC.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 19 |
| junior | 9 |
| lead | 9 |
| middle | 9 |
| principal | 4 |
Who hires the most for SOC Analyst and how concentrated demand is among the largest companies.
Employers
Demand is spread across 122 employers. The largest accounts for 2.8%, the top ten for 17.4%; the remaining 82.6% is long tail.
| share | value |
|---|---|
| top-1 | 2.8% |
| top-3 | 6.9% |
| top-10 | 17.4% |
| long tail | 82.6% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects SOC Analyst jobs from.
Where Zorky sees this market
Observed across 33 sources; the largest accounts for 14.3% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 102 | 0.6939 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 43 | 0.2925 |
| telegram | Telegram | Telegram | 2 | 0.0136 |
The newest SOC Analyst jobs from company career sites.
Recent openings
- SOC Analyst · GB
- SOC Analyst · PH
- SOC Analyst - 3 Month Contract (Extendable) · GB
- SOC Analyst - Global Security Operations · IN
- Менеджер по управлению инцидентами информационной безопасности (SOC Analyst L2) · UZ
- Junior SOC Analyst · BE
- Senior SOC Analyst · BE
- SOC Manager / Leiter Security Operations Center (m/w/d) · DE
Latest open SOC Analyst jobs — most recent positions in the sample (narrow pool of explicit SOC roles — real market significantly wider, SOC — one of the highest-headcount security segments). Full list — in our CRM or via the «see all» link below. For a broader view check the security-engineer page.
Adjacent markets
SOC Analyst overlaps with Security Engineer (SOC L3 → engineering pivot — broader), Threat Hunter (SOC L3 sub-specialty), Incident Responder / IR (escalation target — often separate CSIRT), Detection Engineer (SOC's engineering arm — rising 2024+), Threat Intelligence Analyst, Pentester (offensive pivot — understanding defense helps). Comparison with security-engineer/appsec/cloud-security/iam/pentest/network-security — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Security
Related specializations
Inside SOC Analyst: SOC Analyst L1 / Tier 1 (alert triage — first responder, often shift work 24×7), SOC Analyst L2 / Tier 2 (deep investigation — escalated incidents), SOC Analyst L3 / Tier 3 (threat hunting + advanced IR + detection engineering — overlap with Security Engineer), SOC Lead / SOC Manager (team leadership + shift management + metrics), Threat Hunter (proactive — hunt threats SIEM missed), Detection Engineer (rising 2024+ — writes / tunes detection rules — SOC's engineering arm), Incident Responder / IR (deep incident handling + forensics — often separate CSIRT). Comparison with security-engineer/appsec/cloud-security/iam/pentest/network-security — in the bar below.
Frequently asked questions
Answers recompute automatically.
What stack is most often required from SOC Analyst?
Top 5: cloud, linux, python, aws, azure. SIEM query languages: SPL (Splunk) or KQL (Kusto — Sentinel) — must for investigation + detection. EDR / XDR: CrowdStrike Falcon (leader) / SentinelOne / Microsoft Defender for Endpoint / Palo Alto Cortex XDR. Russian: Kaspersky KEDR / MaxPatrol EDR. SOAR (automation — reduces toil): Palo Alto Cortex XSOAR / Splunk SOAR / Tines / Torq / Microsoft Sentinel Playbooks. NDR: Darktrace / Vectra / PT NAD. Threat Intelligence: Recorded Future / Mandiant / MISP (open-source) / VirusTotal / AlienVault OTX. Ticketing / case management: TheHive (open-source SOC case management — popular) / Jira Service Management / ServiceNow Security Operations. Frameworks & methodologies — must: MITRE ATT&CK (adversary TTPs taxonomy — modern SOC maps all alerts to ATT&CK techniques + coverage gap analysis), Cyber Kill Chain (Lockheed Martin — attack phases), Diamond Model (intrusion analysis), Pyramid of Pain (IoC value hierarchy). Analysis tools: Wireshark (packet analysis) / VirusTotal (file / URL / hash reputation) / any.run + Joe Sandbox + Cuckoo (malware sandboxes — detonate suspicious files) / CyberChef (data decoding Swiss Army knife — base64 / hex / encryption) / Volatility (memory forensics — L3) / OSINT tools (Shodan + urlscan.io + AbuseIPDB + GreyNoise). Detection engineering (L3 / Detection Engineer): Sigma (vendor-agnostic detection rule format — standard 2026 — write once, convert to Splunk / Sentinel / Elastic), YARA (malware pattern matching), Splunk SPL / Sentinel KQL rule authoring, Atomic Red Team + Caldera (adversary emulation for detection rule validation). Languages: Python primary (alert enrichment + SOAR playbooks + automation) + bash + PowerShell + KQL / SPL query languages.
SOC Analyst vs Security Engineer vs Threat Hunter vs Incident Responder — what's the difference?
SOC Analyst (this page) — operational role, real-time monitoring + alert triage + incident detection. Front-line defense. L1 / L2 / L3 tier structure. Often shift work 24×7. The most accessible entry. Security Engineer (general) — engineering role, builds + maintains security infrastructure (SIEM / EDR / IAM / network security configuration). Strategy + automation focus, not real-time monitoring. See Security Engineer (general). Threat Hunter — proactive specialty: hunt for threats that SIEM signature-based detection missed (hypothesis-driven hunting using ATT&CK + behavioral analysis). Often a SOC L3 sub-specialty. Incident Responder (IR) — reactive deep specialty: handles confirmed major incidents (containment + eradication + recovery + forensics + post-mortem). Often separate CSIRT team or external IR consultancy. Detection Engineer (rising 2024+) — SOC's engineering arm: writes + tunes detection rules (Sigma / SPL / KQL), reduces false-positive rates, builds detection coverage against ATT&CK. Bridge SOC ↔ Security Engineering. Reality 2026 (relationship): SOC L1 (triage) → L2 (investigation) → L3 (advanced — often = Threat Hunter / Detection Engineer hybrid). Security Engineer builds the tools SOC uses. IR takes over when SOC confirms a major incident. Career flow from SOC: SOC L3 → either Security Engineer (broader engineering — higher ceiling), or Threat Hunter (proactive deep), or Incident Responder (reactive deep), or Detection Engineer (engineering-leaning), or SOC Manager (people management), or Pentester (offensive pivot — understanding defense helps), or Threat Intelligence Analyst. SOC — the best launchpad: gives broad exposure to all security domains, then specialize.
How is SOC tier structure organized — L1 / L2 / L3 responsibilities?
Classic SOC tier model 2026 (some modern SOCs are transitioning to a «tierless» model, but the tier structure remains dominant): L1 (Tier 1) — Alert Triage Analyst: Responsibilities: monitor SIEM / EDR / NDR alert queue 24×7, perform initial triage (validate alert — true positive / false positive / benign), follow established playbooks, enrich alerts (look up IPs / hashes / domains in threat intel), escalate confirmed / suspicious incidents to L2, dismiss false positives. Skills: SIEM basics, alert interpretation, playbook execution, attention to detail under repetitive load. Typical: shift work (often 12-hour shifts 24×7 rotation), entry-level (1-2 years experience or fresh with certs). Burnout risk is high (repetitive + night shifts) — typical L1 tenure 1-2 years before promotion. L2 (Tier 2) — Incident Responder / Investigator: Responsibilities: deep investigation of escalated incidents, correlation across data sources (SIEM + EDR + network + cloud logs), scope incident (what is affected, timeline reconstruction), determine attack technique (MITRE ATT&CK mapping), recommend containment actions, handle malware analysis (basic — sandbox detonation), document incident thoroughly. Skills: investigation methodology, log analysis depth, malware analysis basics, ATT&CK fluency, SIEM query mastery (SPL / KQL). L3 (Tier 3) — Senior Analyst / Threat Hunter / Detection Engineer: Responsibilities: handle most complex / sophisticated incidents (APT-level), threat hunting (proactive — hypothesis-driven search for threats SIEM missed), detection engineering (write + tune detection rules — Sigma / SPL / KQL — reduce false-positive rates + improve coverage), advanced malware analysis + reverse engineering basics, forensics (memory — Volatility, disk), mentor L1 / L2, develop playbooks, adversary emulation (Atomic Red Team / Caldera to validate detections). Skills: deep technical expertise, threat hunting methodology, detection engineering, programming (Python for automation), forensics. SOC Lead / SOC Manager: team leadership, shift scheduling, SOC metrics ownership (MTTD — Mean Time to Detect, MTTR — Mean Time to Respond, alert volume, false-positive rate, escalation accuracy), SLA management, hiring, customer communication (for MSSP). Cross-cutting: SOC metrics — MTTD / MTTR / dwell time / alert-to-incident ratio / analyst-touch-rate. SOAR can automate repetitive SOC tasks. Team structure and the use of LLMs for alert analysis require quality evaluation and error controls. Shift reality: 24×7 coverage requires follow-the-sun model (multiple geo locations) or night shift rotations (burnout management critical).
What share of jobs are remote?
Among jobs with a stated work format, 30% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is Detection Engineer (rising 2024+) different from SOC Analyst?
SOC Analyst (L1 / L2) — consumes detection rules: responds to alerts that detection rules generate. Reactive. Detection Engineer (rising specialty 2024+ — often evolved from SOC L3) — creates + maintains detection rules: SOC's engineering arm. Day-to-day: 1) Write detection rules (Sigma — vendor-agnostic format — write once, convert to Splunk SPL / Sentinel KQL / Elastic; native SPL / KQL for platform-specific). 2) Tune false-positive rates (badly tuned rules → alert fatigue → real threats missed — Detection Engineer's core mandate: high signal-to-noise). 3) Detection coverage analysis (map detections to MITRE ATT&CK matrix → identify coverage gaps → prioritize new detections). 4) Detection-as-code (treat detection rules as code — version control in Git + CI/CD pipeline + testing + peer review — modern practice). 5) Adversary emulation (Atomic Red Team + Caldera + MITRE Caldera — simulate attacks → validate detections fire correctly). 6) Threat intelligence integration (convert threat intel reports → actionable detection rules). 7) Detection metrics (rule efficacy + false-positive rate + true-positive rate + coverage %). Skills: programming (Python — must), SIEM query languages mastery (SPL / KQL), MITRE ATT&CK deep, understanding of attacker TTPs, Git / CI-CD (detection-as-code). Why rising 2024+: orgs realized — buying more SIEM / EDR tools doesn't help if detection rules are bad. Quality of detections > quantity of tools. Detection Engineering — a recognized discipline (SANS course SEC555, dedicated conferences). Career flow: SOC L2 / L3 + programming skills + detection rule authoring interest → Detection Engineer — 6-12 months. Detection Engineering — one of the best career paths out of SOC (avoids SOC burnout + leverages engineering skills + higher ceiling).
How to start in SOC in 2026?
Roadmap (SOC — the most accessible entry to cybersecurity, can enter without commercial experience): 1) IT fundamentals — networking (TCP / IP / DNS / HTTP / TLS — must), operating systems (Windows internals + Linux basics — where logs live + what gets attacked), basic system administration. CompTIA Network+ a helpful baseline. 2) Security fundamentals — CompTIA Security+ (industry-standard entry cert — must for SOC L1 applications). CIA Triad, common attacks (phishing / malware / lateral movement / privilege escalation), security concepts. 3) SOC-specific cert — CompTIA CySA+ (Cybersecurity Analyst — SOC-focused — behavioral analytics + incident response) or Blue Team Level 1 (BTL1) (Security Blue Team — practical hands-on SOC cert — rising 2024+, highly respected — incident response + SIEM + threat intel + digital forensics). 4) SIEM hands-on — the most important SOC skill. Splunk Fundamentals (free training — SPL query language) or Microsoft Sentinel (Azure free tier — KQL). Build home lab: ingest logs → write queries → create alerts. 5) MITRE ATT&CK fluency — study ATT&CK matrix (tactics + techniques), understand how alerts map to techniques. ATT&CK Navigator hands-on. 6) Home lab — set up SOC home lab: Security Onion (free SOC platform — Suricata + Zeek + Elastic) or Wazuh SIEM + simulate attacks (Atomic Red Team) + practice detection. 7) Hands-on practice platforms: TryHackMe SOC Level 1 + SOC Level 2 paths (best practical SOC training 2026 — affordable), Blue Team Labs Online (BTLO — investigation challenges), LetsDefend (SOC simulation platform — realistic alert triage practice), CyberDefenders (blue team CTF challenges). 8) Analysis tools — Wireshark (packet analysis) + VirusTotal + CyberChef (data decoding) + any.run (malware sandbox — free tier). Practice on real malware samples (malware-traffic-analysis.net). 9) Incident response basics — investigation methodology, the SANS PICERL model (Preparation / Identification / Containment / Eradication / Recovery / Lessons Learned). 10) Detection engineering basics (for L3 path) — Sigma rules + YARA + SPL / KQL rule authoring. 11) Python for SOC — alert enrichment scripts + SOAR playbook basics + automation. 12) Pet project portfolio: a) home SOC lab (Security Onion / Wazuh + simulated attacks + custom detections); b) TryHackMe SOC paths completion + writeups; c) LetsDefend / CyberDefenders investigation writeups (blog). International (eng): TryHackMe SOC Level 1 / 2 paths (best practical 2026), LetsDefend (SOC simulation), Blue Team Labs Online, SANS SEC450 Blue Team Fundamentals + SEC555 SIEM with Tactical Analytics (premium), «Blue Team Handbook» Don Murdoch (canonical SOC reference), «The Practice of Network Security Monitoring» Richard Bejtlich. Books-must: «Blue Team Handbook: SOC, SIEM, and Threat Hunting» Don Murdoch, «Applied Network Security Monitoring» Sanders / Smith, «Intelligence-Driven Incident Response» Roberts / Brown. SOC — entry-level accessible: certs (Security+ + CySA+ / BTL1) + home lab + TryHackMe portfolio → SOC L1 (without commercial experience possible).
How many open jobs are in this sample?
The published sample contains 147 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior SOC Analyst (L3) / Detection Engineer need?
Senior SOC Analyst L3 / Detection Engineer owns the full security operations lifecycle + detection engineering. SIEM mastery deep: Splunk Enterprise Security advanced (SPL mastery — complex correlation searches + macros + lookup tables + data models) or Microsoft Sentinel (KQL mastery — advanced queries + analytics rules + workbooks). Custom detection rule authoring + tuning false-positive rates (core mandate — high signal-to-noise). MITRE ATT&CK mastery: deep fluency with all tactics + techniques + sub-techniques, ATT&CK Navigator for detection coverage gap analysis, map every detection to ATT&CK. Detection engineering: Sigma rule authoring (vendor-agnostic — convert to Splunk / Sentinel / Elastic), YARA rules (malware pattern matching), detection-as-code practices (Git version control + CI/CD + peer review + testing), adversary emulation (Atomic Red Team + Caldera — validate detections fire). Threat hunting mastery: hypothesis-driven hunting methodology (don't wait for alerts — proactively hunt), behavioral analysis, hunting using ATT&CK + threat intelligence, anomaly detection. Incident response: investigation methodology (SANS PICERL), incident scoping + timeline reconstruction, containment strategy, lead L1 / L2 during major incidents. Malware analysis: static analysis basics (strings + PE headers + jadx / Ghidra basics), dynamic analysis (sandbox detonation — any.run / Joe Sandbox / Cuckoo — interpret results), basic reverse engineering. Forensics: memory forensics (Volatility), disk forensics basics, network forensics (Wireshark + Zeek), log analysis depth. Threat Intelligence: IoC workflows, STIX / TAXII, MISP, threat actor profiling, convert intel reports → detection rules. EDR / XDR mastery: CrowdStrike Falcon / SentinelOne / Microsoft Defender advanced — threat hunting queries, custom IOA rules, response actions. SOAR mastery: Cortex XSOAR / Splunk SOAR / Tines — playbook authoring in Python. Programming: Python deep (alert enrichment + SOAR playbooks + detection automation + custom tooling), bash + PowerShell. Cloud security monitoring: AWS CloudTrail / GuardDuty + GCP Security Command Center + Azure Sentinel — cloud-specific detection. SOC metrics: MTTD / MTTR / dwell time / false-positive rate / detection coverage — measure + improve. Soft: clear incident documentation + technical writing, mentor L1 / L2 analysts, calm under pressure (incident handling), shift handover discipline, communication during incidents (stakeholder updates). English for Senior+ MUST — SIEM / EDR vendor docs + threat intel reports + security community are English-language. Certifications: CompTIA CySA+ / BTL1 / GIAC GCIH (Certified Incident Handler) / GCFA (Forensic Analyst) / GCDA (Detection Analyst) / Splunk Core Certified / Microsoft SC-200. Optional bonus: detection engineering open-source contributions (Sigma rules repository / Atomic Red Team), threat hunting writeups / blog, conference talks (Blue Team Village DEF CON / SANS Blue Team Summit) — sharply increase market value for frontier-MSSP (Red Canary / Expel — detection engineering culture) hiring.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.