Collect Windows and Linux logs in a SIEM and write rules for common attacks.
A small SOC needs a starter set of detections for brute force, new admin accounts and suspicious PowerShell.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
Banking: Spotting account takeover. Attackers logged in with stolen passwords from other countries. SIEM rules for impossible travel and many failed logins, with an analyst playbook. Takeover attempts are caught and accounts locked within minutes.
Hospital: Ransomware early warning. Ransomware encrypted servers before anyone noticed. Endpoint telemetry and SIEM rules for mass file changes and shadow copy deletion, with isolation playbooks. A drill showed the attack being contained before encryption spread.
IT services: Too many alerts. Analysts faced thousands of alerts a day and missed real attacks. Tuned rules, alert grouping and SOAR playbooks that enrich alerts automatically. Analysts handle fewer, better alerts and respond faster.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 12 hours of hands-on work, and it fits best after week 5 of the SOC Analyst course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.