Cybersecurity Analyst (SOC & SIEM)
Welcome, champion! π₯
You've mastered 0 of 74 lessons. Start your first lesson free β no signup needed.
About this course
A security operations centre analyst spends the shift deciding which alerts are real, using logs as evidence. This online SOC analyst course on Abekus starts with one burst of failed logins and builds up through log sources, SIEM collection and correlation, MITRE ATT&CK, Sigma detection rules, common attack detections, threat intelligence, incident response and threat hunting, in short reading-card lessons each followed by an MCQ quiz.
Who this SOC analyst course is for
It is written for Indian engineering students and early-career IT or security staff preparing for a tier 1 or tier 2 SOC analyst role. The course starts with a single alert: a run of failed logins is read line by line, counted against a baseline, grouped by source address and by user name, and then escalated, contained or closed. By the end you can read Windows, Linux and network logs, triage and escalate alerts, map activity to MITRE ATT&CK, write and tune Sigma rules, and follow an incident from first alert to report.
The course is vendor-neutral. It follows MITRE ATT&CK Enterprise v20 with its 15 tactics, writes detection rules as Sigma YAML that pySigma and sigma-cli convert into product queries, and uses NIST SP 800-61 Rev. 3 for incident response, STIX and TAXII 2.1 and TLP 2.0 for sharing intelligence, and the CERT-In Directions of 28 April 2022 for Indian reporting duties. Logs appear as raw text lines from the Windows Security log, Sysmon, Linux auth logs and syslog, firewalls, web proxies and DNS, in examples set in Indian banks, universities and IT services firms. It leaves out SIEM, SOAR and EDR console screens, product query languages such as SPL, KQL and EQL as lesson subjects, malware reverse engineering, in-depth disk and memory forensics, and offensive tooling.
How the lessons work
Each lesson is a short set of reading cards on one log source, concept or detection, usually built around a few raw log lines or a short Sigma rule, followed by a quiz of multiple-choice questions that often ask what the evidence shows. Lessons go from basics up: a first alert and SOC roles, then log sources and key Windows events, then how a SIEM collects and correlates data, then ATT&CK, Sigma rule anatomy and tuning, detections for credential attacks, execution, persistence and network signals, then threat intelligence, incident response, threat hunting, and finally comparisons and worked cases. You move at your own pace.
MCQ practice vs video courses for SOC analysts
Video courses on Udemy, Coursera or Cybrary are a good choice if you want to watch an instructor work through a console. This course is built for a different job: a short explanation followed straight away by questions about real evidence, such as whether a burst of event 4625 entries is brute force or password spraying, what logon type 10 means, which ATT&CK technique a scheduled task maps to, what a Sigma condition will match, or whether an incident must be reported to CERT-In within six hours. Triage is a series of quick, evidence-based decisions, and practising them right after each idea makes them stick. Many learners use both: a video to see a tool, and questions to sharpen judgement.
Common SOC analyst mistakes
The course corrects these directly:
- Saying ATT&CK Enterprise has 14 tactics including Defense Evasion. Since v19 it has 15: Defense Evasion became Stealth and Defense Impairment.
- Reading event 4625 as a successful logon. Event 4624 is success; 4625 is failure.
- Treating logon type 10 as a network logon. Type 3 is network; type 10 is RemoteInteractive, which is RDP.
- Describing password spraying as many passwords against one account. That is brute force; spraying tries one or a few passwords across many accounts.
- Quoting the four-phase incident response cycle as current. That was SP 800-61 Rev. 2; Rev. 3 uses the CSF 2.0 Functions.
- Using TLP:WHITE for public information. TLP 2.0 renamed it TLP:CLEAR.
- Relying on blocking hashes and IP addresses. They are the easiest indicators for an attacker to change; TTPs sit at the top of the Pyramid of Pain.
Best way to learn SOC analysis
Read real logs. Take a set of events, ask what happened, who did it and from where, and decide on a verdict before you look at anyone else's. Then write the detection as a Sigma rule and test it against sample logs. The last part of the course is built around the choices analysts make: SIEM versus SOAR versus XDR, signature versus anomaly detection, Sigma versus YARA versus Snort rules, when to tune and when to suppress an alert, and which log sources are worth their cost, applied to ransomware precursor detection in a bank SOC, a compromised cloud email account and phishing triage for a university.