Roadmaps Security roadmaps Core domains

Security Operations (SecOps)

Watch an organisation's systems around the clock, spot attacks in the noise, and respond before they turn into breaches.

Estimated time: 25–43 months · At about 10 hours a week.

  1. BeginnerLogs, alerts and the analyst's toolkit3–4 months
  2. IntermediateInvestigation and endpoint and network visibility4–6 months
  3. AdvancedDetection engineering and automation6–9 months
  4. ExpertLeading and designing security operations12–24 months

Overview

Security Operations is the day-to-day defence of an organisation. A security operations centre (SOC) collects logs and alerts from computers, networks, cloud services and applications, decides which ones are real attacks, and responds to them.

The work mixes investigation (what happened, on which machine, by which account), engineering (getting the right logs in and writing detections that fire on real attacks and not on normal work) and communication (telling the right people, fast, in plain language).

Why it matters

Every organisation gets attacked; what decides the damage is how fast someone notices and acts. SOC roles are also the most common way into a security career, because the job teaches you how attacks really look on real systems.

Typical job roles

  • EntrySOC analyst (Tier 1) Triages alerts, closes false positives, escalates real incidents with clear notes.
  • Mid-levelSOC analyst (Tier 2) / incident responder Investigates escalated alerts end to end and contains threats.
  • Mid-levelDetection engineer Writes, tests and tunes the rules and analytics the SOC relies on.
  • SeniorThreat hunter (Tier 3) Looks for attackers that no alert has caught, starting from a hypothesis.
  • SeniorSecurity engineer (SIEM, SOAR, EDR) Builds and runs the platforms, log pipelines and automations.
  • LeadSOC manager / head of security operations Runs the team, the shift rota, metrics and the relationship with the business.

Prerequisites

  • Comfortable with Windows and Linux: users, processes, services, the file system and the command line.
  • Networking basics: IP addresses, ports, TCP and UDP, DNS, HTTP and what a firewall does.
  • Basic scripting in Python or PowerShell, enough to read and change a short script.
  • Security basics: the CIA triad, common attack types (phishing, malware, brute force) and why logging matters.

Foundations of computer science Cybersecurity

Learning path

  1. Beginner Logs, alerts and the analyst's toolkit 3–4 months

    Topics

    • Windows event logs
    • Linux logs (auth, syslog, journald)
    • SIEM basics
    • Alert triage
    • Phishing analysis
    • MITRE ATT&CK tactics
    • Indicators of compromise
    • Ticketing and escalation

    Skills

    • Read Windows logon events (4624, 4625, 4688) and Linux auth logs and say what happened.
    • Search a SIEM with simple queries and filters.
    • Analyse a suspicious email: headers, links and attachments, safely.
    • Write a short, clear ticket that someone else can act on.

    Hands-on projects and labs

    • Install Wazuh or the Elastic Stack on a laptop or a free cloud VM, connect one Windows and one Linux machine, and watch your own logons appear.
    • Install Sysmon with a community configuration on a Windows VM and compare what it records with the default logs.
    • Work through the free introductory SOC rooms or challenges on a blue team practice platform.

    Done when you can…

    • Explain the difference between an event, an alert and an incident.
    • Take an alert, decide if it is a real threat or a false positive, and justify why in writing.
    • Map a simple attack (password spraying, a malicious macro) to ATT&CK techniques.
  2. Intermediate Investigation and endpoint and network visibility 4–6 months

    Topics

    • EDR telemetry
    • Process trees
    • PowerShell and command-line logging
    • Network security monitoring
    • Zeek and Suricata
    • Threat intelligence feeds
    • Incident response lifecycle
    • Query languages (KQL, SPL, ES|QL)

    Skills

    • Follow an attack from the first email to the last command using several log sources together.
    • Write SIEM queries that join and count, not just search.
    • Use Zeek logs and Suricata alerts to spot beaconing, scanning and data leaving the network.
    • Contain an incident safely: isolate a host, disable an account, block an indicator.

    Hands-on projects and labs

    • Build a home SOC: Security Onion (or Wazuh with Suricata) watching a small virtual network of a Windows client, a Linux server and an attacker VM.
    • Run Atomic Red Team tests in your lab and check which ones your setup detects. Write down the gaps.
    • Investigate the free Boss of the SOC datasets from Splunk and write a full incident report.

    Done when you can…

    • Investigate an alert from start to finish in under an hour and write a report with a timeline.
    • Explain what a good detection needs: the log source, the logic, the expected false positives and the response.
    • Run the response steps for a phishing compromise without a checklist.
  3. Advanced Detection engineering and automation 6–9 months

    Topics

    • Sigma rules
    • Detection as code
    • Detection testing
    • SOAR playbooks
    • Threat hunting methods
    • Cloud logs (AWS CloudTrail, Microsoft 365, Entra ID)
    • Active Directory attacks
    • Purple teaming

    Skills

    • Write, test and version detections in Git, and convert Sigma rules to your SIEM's language.
    • Automate enrichment and routine response with a SOAR tool or scripts.
    • Run a hypothesis-driven hunt and turn what you find into new detections.
    • Measure coverage against ATT&CK and decide what to build next.

    Hands-on projects and labs

    • Set up a detection-as-code pipeline: Sigma rules in a GitHub repository, converted and tested automatically on every change.
    • Build a Shuffle playbook that enriches an alert with threat intelligence and opens a ticket.
    • Run a small purple team exercise in your lab: emulate one ATT&CK technique, check the detection, fix it, repeat.

    Done when you can…

    • Show a set of your own detections with tests, documented false positives and response notes.
    • Lead a hunt and present the findings to a non-technical manager.
    • Explain the trade-offs between alert volume, coverage and analyst time.
  4. Expert Leading and designing security operations 12–24 months

    Topics

    • SOC design and maturity models
    • Metrics (MTTD, MTTR, coverage)
    • Threat-informed defence
    • Log strategy and cost
    • Major incident command
    • Building teams and rotas
    • AI-assisted analysis

    Skills

    • Design a SOC: what to log, which tools, which processes and which people.
    • Lead a major incident with executives, legal and communications involved.
    • Build a detection programme that is driven by the threats your organisation actually faces.
    • Mentor analysts and reduce burnout through automation and good processes.

    Hands-on projects and labs

    • Write a complete SOC design for a fictional organisation of 2,000 people: log sources, retention, budget, staffing and metrics.
    • Contribute detections or documentation to an open-source project such as Sigma or Wazuh.
    • Run a tabletop exercise for a ransomware scenario with friends or colleagues playing executives.

    Done when you can…

    • Defend a security operations budget and roadmap in front of leadership.
    • Run a major incident from first alert to post-incident review.
    • Show measurable improvement in a SOC's detection coverage and response time.

Tools and technologies

  • Wazuh Open source Open-source SIEM and XDR: log collection, file integrity monitoring and alerting.
  • Security Onion Open source A free Linux distribution for network security monitoring, log management and hunting.
  • Elastic Security Free community edition SIEM and endpoint security on the Elastic Stack; the free tier covers a home lab.
  • Sysmon Free Microsoft's tool that logs detailed process, network and file activity on Windows.
  • Zeek Open source Turns network traffic into rich, searchable logs.
  • Suricata Open source Network intrusion detection and prevention engine.
  • Sigma Open source A generic format for writing detections once and using them in any SIEM.
  • Velociraptor Open source Endpoint visibility and collection at scale, for hunting and response.
  • MISP Open source Threat intelligence sharing platform.
  • Shuffle Open source Open-source SOAR for automating alert handling.
  • Atomic Red Team Open source Small, safe tests mapped to ATT&CK to check whether your detections work.
  • CyberChef Open source Decode, decrypt and transform data in the browser.
  • Splunk Enterprise Security Commercial A widely used commercial SIEM; many job ads ask for it.
  • Microsoft Sentinel Commercial Microsoft's cloud SIEM and SOAR, using the KQL query language.

Certifications

Take them in roughly this order. Costs and details for the ones marked with a link are on the Certifications page.

  1. Entry Security+ CompTIAThe usual first certification for SOC roles.Cost and exam details
  2. Intermediate CySA+ (Cybersecurity Analyst) CompTIABuilt for analysts.Cost and exam details
  3. Intermediate Security Operations Analyst Associate (SC-200) MicrosoftPick this if the jobs near you use Microsoft Sentinel and Defender.Cost and exam details
  4. Intermediate Certified Defensive Security Analyst (CDSA) Hack The BoxHands-on exam that proves you can investigate.Cost and exam details
  5. Advanced GIAC Certified Incident Handler (GCIH) GIAC (SANS)Respected incident handling certification; often employer-funded.Cost and exam details
  6. Advanced GIAC Certified Detection Analyst (GCDA) GIACFor detection engineering and SIEM work.
  7. Advanced CISSP ISC2For SOC managers and senior leaders.Cost and exam details

Resources

Frameworks and standards

All frameworks and standards

Career path

A common progression. Titles vary between companies.

  1. IT support or junior SOC analyst0–2 years
  2. SOC analyst (Tier 2) or incident responder2–4 years
  3. Detection engineer or threat hunter4–7 years
  4. SOC lead or security operations manager7+ years
  5. Head of security operations or CISO10+ years

Related domains to move into

All security roadmaps Back to top

Last reviewed: . Found a mistake, or want a roadmap written sooner? Contact