SOC Analyst Interview Questions and Answers
Last updated 2026-11-19
A security operations centre analyst watches telemetry, decides which alerts are real and escalates or contains incidents. Interviews therefore test triage reasoning, log literacy and calm communication more than exploit knowledge. This page has 15 worked questions: the alert lifecycle, SIEM concepts, Windows and Linux log events worth knowing, MITRE ATT&CK, phishing and malware analysis basics and how to hand over an incident.
Queries are shown in generic SQL-like or Splunk-style form so you can adapt them to your SIEM. For broader security knowledge read the cybersecurity questions, and for networking the network security questions.
| Tiers | Tier 1 triage, Tier 2 investigation and response, Tier 3 threat hunting and engineering |
|---|---|
| Tools you will meet | SIEM (Splunk, Microsoft Sentinel, Elastic), EDR, SOAR, threat intelligence platforms |
| Frameworks | MITRE ATT&CK, NIST incident response lifecycle, Cyber Kill Chain |
Windows events worth memorising
Event 4624 is a successful logon and 4625 a failed one; the logon type field matters, for example type 3 is network, type 2 interactive and type 10 remote interactive (RDP). Event 4672 shows special privileges assigned to a new logon, 4688 is process creation (with command line if auditing is enabled), 4720 is a user account created, 4732 a member added to a security-enabled local group, 1102 means the audit log was cleared, 4768 and 4769 are Kerberos ticket requests, and 7045 is a new service installed. Sysmon event 1 records process creation with hashes, 3 network connections and 11 file creation. Knowing these lets you answer log-reading questions confidently.
SOC Analyst Interview Questions and Answers: questions with worked answers
1 Describe what a SOC does and the typical analyst tiers.
easyA SOC continuously monitors an organisation's systems, detects security events, investigates them and coordinates response. Tier 1 analysts triage alerts, confirming whether each is a true or false positive and escalating with notes. Tier 2 investigates in depth, correlates across sources, contains threats and directs remediation. Tier 3 or threat hunters search proactively for undetected activity, tune detections and analyse malware. Supporting roles include detection engineers, threat intelligence analysts and an incident manager. A SOC runs 24 by 7 in shifts, so clear handover notes and documented playbooks are essential.
2 What is a SIEM and how does it work?
easyA security information and event management system ingests logs from endpoints, servers, network devices, cloud services and applications, normalises them to a common schema, stores them for search and retention, and runs correlation rules and analytics that generate alerts. Examples include Splunk, Microsoft Sentinel, Elastic Security and QRadar. Value comes from correlating across sources, for example a VPN login from a new country followed by a mailbox forwarding rule. Common problems are missing log sources, poor time synchronisation, noisy rules and parsing failures, so a SIEM is only as good as its data and tuning.
3 Define true positive, false positive, true negative and false negative in alert triage, and why false negatives are the worst.
easyA true positive is an alert on real malicious activity; a false positive is an alert on benign activity; a true negative is silence on benign activity; a false negative is silence on real malicious activity, meaning a missed attack. False negatives are the most damaging because nobody knows to respond, so detection coverage and logging gaps matter. Too many false positives cause alert fatigue, which raises the chance of missing a real one, so analysts tune rules with allow-lists, thresholds and better context. Track precision of each rule and retire or rewrite the poor ones.
4 Walk me through how you would triage an alert of multiple failed logins followed by a success.
mediumFirst establish context: the account, source IP and geography, time, target system and the authentication method. Count the failures and the interval, and check whether the success came from the same IP. Look at whether the account is privileged, whether the source is a known corporate range or an anonymiser, and whether the user is travelling. After the success, examine what happened: new process launches, mailbox rule creation, MFA changes, data downloads and lateral movement. Contact the user out-of-band if suspicious. If compromise is likely, disable the account or reset credentials, revoke sessions, block the IP and escalate to Tier 2 with timestamps, evidence and what you already did.
textindex=wineventlog (EventCode=4625 OR EventCode=4624) Account_Name=jsmith | bin _time span=10m | stats count(eval(EventCode=4625)) AS failures count(eval(EventCode=4624)) AS successes values(Source_Network_Address) AS src by _time Account_Name | where failures >= 10 AND successes >= 15 Explain MITRE ATT&CK and how a SOC uses it.
mediumATT&CK is a knowledge base of adversary tactics (the goals, such as initial access, execution, persistence, privilege escalation, defence evasion, credential access, discovery, lateral movement, collection, command and control, exfiltration and impact) and techniques (the methods, each with an ID such as T1059 for command and scripting interpreter). A SOC maps detection rules to techniques to see coverage and gaps, tags alerts so analysts see where in the attack chain activity sits, guides threat hunts, and plans purple-team exercises. It describes behaviour, not specific malware, which makes detections longer-lived than indicators like file hashes.
6 A phishing email was reported. What is your investigation process?
mediumCollect the original email as an .eml or msg to keep headers. Check sender, reply-to and return-path mismatches, SPF, DKIM and DMARC results, and the sending IP's reputation. Extract URLs and attachments without opening them on a workstation: detonate in a sandbox, check URL reputation and the redirect chain, and hash attachments. Search the mail platform for other recipients and delivery of the same message, and in proxy and DNS logs for anyone who visited the URL. Contain by purging messages, blocking domains, URLs and hashes, and resetting credentials for users who submitted them. Record indicators of compromise and send feedback to the reporter.
7 How do you distinguish a benign PowerShell execution from a malicious one?
mediumLook at the process tree and the command line. Suspicious signs: encoded commands (-enc or -EncodedCommand), hidden windows (-w hidden), execution policy bypass, download cradles such as Invoke-WebRequest or DownloadString followed by Invoke-Expression, parent processes such as Word, Outlook or a browser, unusual users or hosts, and connections to rare external domains. Benign administration usually comes from known admin accounts and servers, with scripts from approved paths. Enable script block logging (event 4104) so decoded content is visible, and decode Base64 yourself to read what runs. Check the hash and prevalence of anything it drops.
bash# the encoded PowerShell argument is UTF-16LE Base64 echo 'SQBFAFgA...' | base64 -d | iconv -f UTF-16LE -t UTF-88 What are indicators of compromise and indicators of attack?
easyIndicators of compromise are artefacts showing a system has been breached, such as malicious file hashes, IP addresses, domains, registry keys and mutex names; they are useful for retrospective searches but easy for attackers to change, so they age quickly. Indicators of attack describe behaviour in progress, for example a Word document spawning PowerShell that connects outbound, which is harder for adversaries to alter and catches new tools. Good detection programmes use both, with intelligence feeds supplying IOCs and ATT&CK-based analytics providing behaviour detection. Always record the source and confidence of an indicator.
9 What is EDR and how does it differ from antivirus?
easyTraditional antivirus mainly matches files against signatures and some heuristics, blocking known bad. Endpoint detection and response continuously records endpoint telemetry (process creation, file and registry changes, network connections, user activity), applies behavioural analytics, lets analysts search across the fleet, and offers response actions such as isolating a host, killing a process, quarantining a file or collecting a forensic package. EDR provides the visibility to reconstruct what happened after an alert. Modern products blend both, and extended detection and response correlates endpoint data with identity, email and cloud sources.
10 How do you analyse a suspicious network connection from a firewall or proxy log?
mediumIdentify the internal host, user, destination IP or domain, port, bytes in and out, and timing. Check destination reputation and age of the domain, whether the traffic is a regular beacon (connections at fixed intervals with similar sizes), whether it uses an unusual port or protocol for the service, and whether large outbound transfers suggest exfiltration. Correlate with DNS queries, endpoint process data for the owning process, and other hosts contacting the same destination. A long-lived connection to a rare domain with periodic small requests from a user workstation is a classic command-and-control pattern.
sql-- beaconing candidates: many regular connections from one host to one rare destination SELECT src_ip, dest_domain, COUNT(*) AS conns, AVG(bytes_out) AS avg_out, STDDEV(EXTRACT(EPOCH FROM gap)) AS gap_jitter FROM ( SELECT src_ip, dest_domain, bytes_out, ts - LAG(ts) OVER (PARTITION BY src_ip, dest_domain ORDER BY ts) AS gap FROM proxy_logs WHERE ts > NOW() - INTERVAL '24 hours' ) t GROUP BY src_ip, dest_domain HAVING COUNT(*) > 100 AND STDDEV(EXTRACT(EPOCH FROM gap)) < 5 ORDER BY conns DESC;11 Explain the incident response steps for a confirmed malware infection on a workstation.
mediumContain first: isolate the host from the network using EDR while preserving it powered on so memory evidence remains, and disable the user's account if credentials may be exposed. Scope: search for the same hashes, domains and behaviours on other hosts, and identify the initial vector such as an attachment or drive-by download. Eradicate and recover: remove persistence, reimage the machine when trust is lost, reset credentials and tokens, patch the exploited weakness. Throughout, document a timeline and maintain chain of custody for evidence. Afterwards run a lessons-learned review and update detections and awareness.
12 What is lateral movement, and how can it be detected?
hardLateral movement is an attacker using a foothold to reach other systems, often through stolen credentials, pass-the-hash, remote services such as RDP, SMB and WinRM, or remote execution tools such as PsExec and WMI. Detect it with network logon events (4624 type 3) from workstations to many servers, new service creation events (7045), admin shares accessed, one account logging on from many hosts in a short time, unusual RDP paths between workstations, and EDR alerts on remote process creation. Defend with network segmentation, local admin password rotation (LAPS), restricted admin tiers and blocking workstation-to-workstation SMB.
13 What logs do you check on Linux when you suspect a compromised server?
mediumAuthentication logs (/var/log/auth.log on Debian-based systems or /var/log/secure on Red Hat-based) show SSH logins, sudo use and failures. Review last and lastb, shell history, cron entries and systemd timers for persistence, new users in /etc/passwd, authorised_keys changes, unexpected listening ports with ss, odd processes and their network connections, recently modified files in sensitive directories, and web server logs for exploitation attempts. Use journalctl for service logs. Where auditd is enabled, its records give exact syscalls and file access.
bashgrep 'Accepted\|Failed' /var/log/auth.log | tail -50 last -a | head; lastb -a | head ss -tulpn find / -xdev -mtime -2 -type f -not -path '/proc/*' 2>/dev/null | head -50 cat /etc/crontab; ls -la /etc/cron.d /var/spool/cron 2>/dev/null awk -F: '$3==0' /etc/passwd14 What is SOAR and what would you automate first?
mediumSecurity orchestration, automation and response platforms connect tools and run playbooks that automate repetitive investigation and response steps. Good first candidates are high-volume, low-risk tasks: enriching alerts with IP, domain and hash reputation, checking whether a user is on leave or travelling, extracting and detonating attachments from reported phishing, creating tickets with context, and revoking sessions for confirmed compromised accounts after human approval. Keep a human in the loop for destructive actions such as isolating a production server, and measure automation by time saved and error rate.
15 How do you write a good escalation or shift-handover note?
easyMake it standalone and factual: what was detected and when, the affected users, hosts and accounts, the evidence gathered with log references or queries, what you have already done (for example containment), your assessment and confidence, what you do not yet know, and the specific next action you recommend with an urgency level. Avoid vague phrases such as looks suspicious. Use UTC timestamps and ticket IDs, and keep notes updated as facts change. A reader on the next shift should be able to continue without calling you.
Frequently asked questions
What skills do I need for an entry-level SOC analyst job?
Networking basics, Windows and Linux logs, how common attacks work, familiarity with a SIEM through a home lab or free trial, and clear writing. A certificate such as Security+ or a vendor SOC course helps.
Do SOC analysts need to code?
Light scripting in Python or PowerShell helps with parsing logs and automation, and SQL or a query language such as SPL or KQL is used daily. Heavy development is not expected at Tier 1.
Are SOC jobs always night shifts?
Many SOCs run around the clock in shifts, though some use follow-the-sun models across regions. Ask about shift patterns and rotation during the interview.
How can I practise SIEM skills for free?
Install Elastic Security or Wazuh in a home lab, send logs from a few virtual machines, generate test attacks in your own environment and write detections. Free tiers of commercial SIEMs also exist and their terms change.
Related guides
- Cybersecurity Interview Questions and Answers
- Ethical Hacking Interview Questions and Answers
- Network Security Interview Questions: Cryptography, Firewalls and Attacks
- Linux Commands Interview Questions with Examples
- SQL Interview Questions and Answers
- Site Reliability Engineer (SRE) Interview Questions and Answers
More in Role-wise Interview Questions by Job and Tech Stack
- Software Engineer Fresher Interview Questions and Answers
- Spring Boot Interview Questions and Answers (Spring Boot 3)
- Statistics for Data Science Interview Questions and Answers
- Tableau Interview Questions and Answers
- Terraform Interview Questions and Answers
- Web Performance Interview Questions and Answers
- Web Security and OWASP Interview Questions and Answers
- A/B Testing Interview Questions and Answers
- Android Developer Interview Questions and Answers
- Angular Interview Questions and Answers (Angular 18 and Later)
- Ansible Interview Questions and Answers
- API Testing and Postman Interview Questions