CAREERS

What a SOC analyst actually does all day

A walk through a typical shift in a security operations centre: the alert queue, the investigations, the handovers, and why so much of the job is writing.

Ashwood Education · 5 min read · Sept 2026

An analyst working at a desk with two monitors in an open-plan office

People picture a security operations centre as a dark room full of screens, with someone typing furiously while a breach unfolds. The screens are real. The rest is mostly not. A junior SOC analyst’s day is closer to careful casework: read an alert, work out whether it matters, write down what you found, and pass it on cleanly.

Here is what that looks like across a typical shift, and what it means if you are thinking about the job.

What a SOC is for

A security operations centre (SOC) watches an organisation’s systems for signs of attack and responds when it finds one. Some organisations run their own. Many more pay a managed security provider to do it for them, which is why a lot of junior SOC jobs sit in those firms, watching several customers at once.

Most SOCs split the work into tiers:

  • Tier 1, triage: reviews incoming alerts, closes the false positives, and escalates anything real with enough context for the next person to act.
  • Tier 2, investigation: digs into escalated cases, works out what was affected, and leads the response.
  • Tier 3, threat hunting and engineering: looks for attackers who have not triggered an alert yet, and tunes the detections everyone else relies on.

New starters almost always begin at tier 1, so that is where this walk-through sits.

Start of shift: the handover

Many SOCs run around the clock, so the day starts with a handover from the previous shift. You read the notes on open cases, anything waiting on a customer, and anything unusual the last team saw but could not close. A good handover note saves an hour. A vague one costs you the morning.

The queue

Then you open the queue. Alerts arrive from a SIEM (a security information and event management platform, such as Microsoft Sentinel or Splunk), from endpoint detection and response (EDR) tools on laptops and servers, from email security, and from cloud platforms.

Most of these alerts are not attacks. A login from an unusual country turns out to be someone on holiday. A suspicious PowerShell command turns out to be the IT team’s own script. Working through these quickly and correctly is the core skill of tier 1, and it is harder than it sounds, because the one alert that is real usually looks a lot like the fifty that were not.

For each alert you are asking the same few questions:

  1. What exactly triggered this, and on which user or machine?
  2. Is this normal for this user, this machine or this organisation?
  3. Is anything else happening around the same time on the same account or device?
  4. If this is malicious, what would the attacker be trying to do next?

Most teams have playbooks for common alert types, such as phishing reports, logins from two distant places at once, or malware detections. Playbooks keep the work consistent, but they do not replace judgement. Knowing when an alert does not fit the playbook is what gets people promoted.

Phishing: the alert you will see most

A large share of a junior analyst’s day goes on reported or detected phishing emails. You check the sender and the message headers, look at where any links actually lead, open attachments safely in a sandbox, and search for the same message in other mailboxes. If someone clicked, the case changes shape: you check their sign-ins, reset credentials if needed, and look at anything the account did afterwards.

Lines of colour-coded text filling a computer screen

Writing it down

This is the part nobody mentions in the job advert. Every alert you touch needs a note: what you checked, what you found, and why you closed or escalated it. If you escalate, the tier 2 analyst should be able to pick up your case without asking you a single question.

Good SOC writing is short, specific and in time order. “Checked sign-in logs for the user: three failed attempts from the company VPN range, no successful login, closed as benign” is a useful note. “Looked into it, seems fine” is not. If you are considering this career, practise writing up investigations as much as you practise the tools.

Escalation and response

When something is real, the job shifts from investigation to coordination. You raise it with tier 2 or the incident lead, contain what you are allowed to contain (isolating a laptop through the EDR tool, for example), and keep the timeline up to date. Most of the drama people imagine happens here, and most of it is still careful communication rather than heroics.

Quieter hours

When the queue is under control, analysts tune noisy detection rules, update playbooks, read threat intelligence about current campaigns, or practise in a lab. Teams that use these hours well get better every month. Teams that do not end up drowning in the same false positives forever.

What the job asks of you

The skills that matter most at tier 1 are less exotic than people expect:

  • Comfort with logs. Reading Windows event logs, sign-in logs and web proxy logs, and searching them with a query language such as KQL or SPL.
  • Networking basics. IP addresses, DNS, ports, and what normal traffic looks like.
  • How attacks unfold. Frameworks such as MITRE ATT&CK give you a shared vocabulary for the steps an attacker takes.
  • Clear writing. Covered above, and worth repeating.
  • Patience. Most of the job is ruling things out.

Many SOC roles involve shift work, particularly at managed providers. Check the shift pattern before you accept an offer, because it suits some lives better than others.

Is it a good first job in security?

For many people, yes. Tier 1 teaches you how real organisations are attacked, how their defences actually behave, and how to investigate under time pressure. From there people move into incident response, threat hunting, detection engineering or penetration testing.

If this is the direction you are considering, our Cyber Security course covers the foundations, SOC operations and SIEM investigation, and incident response. The Cyber Security + Ethical Hacking course goes further over twenty-four weeks, adding vulnerability management, authorised testing and forensics.

Want to work at Ashwood?

We hire practitioners to teach and mentor each cohort.

See open roles