Train like an analyst. Investigate evidence. Reconstruct attacks. Make defensible SOC decisions.
SOC MODE
EVIDENCEHUNTDETECTRESPOND
INVESTIGATION CASES50Available in the queue
OPEN50Waiting for analyst action
IN PROGRESS0Currently being investigated
CLOSED0Completed investigations
YOUR CURRENT MISSION
Investigate. Don't Guess.
Work the queue like a Tier 1 analyst. Validate the alert, collect evidence, correlate related activity, reconstruct the attack and document a defensible verdict.
ALERT→EVIDENCE→HUNT→DECIDE→PROVE
SOC SKILL STACK
What You Are Building
01InvestigationEvidence-first analysis
02Threat HuntingFind what the alert missed
03Detection EngineeringTurn evidence into detections
04Incident ResponseContainment and escalation
START HERE
Recommended Investigation
01
BOTS-001 · EC2 Instance Metadata Access
Investigate the metadata request, identify the initiating process and determine whether the activity is authorised.
TRAINING ENVIRONMENT
Know Your Data
BlueTeam uses historical BOTS v2 investigation evidence plus clearly labelled synthetic training scenarios. This is a simulated environment — no live customer tenant or production telemetry is connected.
Historical EvidenceSynthetic ScenariosSafe Training
QUICK ACCESS
Choose Your Next Drill
SOC RULE
Never Close on One Clue
One alert is a starting point — not the conclusion. Correlate identity, endpoint, network, email and timeline evidence before making the final decision.
ALERT→CONTEXT→CORRELATION→VERDICT
🧪 BOTS v2 DATASET MODEThe queue contains verified BOTS v2 evidence plus clearly labeled synthetic BlueTeam training scenarios. Synthetic records are not live Microsoft/AWS telemetry and are never presented as BOTS-derived evidence.
Alert ke niche evidence/log extract check karo. BOTS v2 records are source-derived; synthetic records are clearly labeled and are not live telemetry.
Analyst task
Investigation checklist
Use this sequence for each alert:
① Validate alert context
② Review user, device and time
③ Inspect indicators and evidence
④ Decide true or false positive
⑤ Document and close
TRAINING TIP
Do not decide from severity alone. Base your verdict on the evidence in the alert.
KQL Practice
300 KQL use-case queries from the uploaded reference PDF. Select a query, run it, inspect the simulated output, and understand what the query is doing.
300 QUERIES · RUN · OUTPUT · EXPLANATION
HOW THIS WORKS
1️⃣ChooseSelect a use case
2️⃣RunExecute in simulator
3️⃣OutputRead returned fields
4️⃣ExplainUnderstand the logic
Training mode: These results are simulated examples. The page is not connected to a live Microsoft Sentinel workspace. The query text is based on the uploaded KQL reference PDF. fileciteturn65file0L324-L370
QUERY EDITOR
Simulated query output
Click Run query to see simulated results.
Query explanation
Run a query to see the analyst explanation.
KQL Use-Case Library
Search by query number, title, table, Event ID or Azure service.
300 queries
SOC Learning Path
Original beginner-to-advanced SOC curriculum covering cybersecurity foundations, enterprise security, SIEM, detection engineering, threat hunting, incident response and capstone investigations.
24 MODULES · BEGINNER → ADVANCED
Become a SOC Analyst — from Zero to Advanced
Learn the concept → practise in the lab → investigate evidence → write the finding → improve the detection.
This curriculum is written in original wording for BlueTeam SOC Academy. It uses the uploaded handbook's subject areas as a study reference, but does not reproduce its author name, branding, or long-form text.
📘LearnUnderstand the concept
🧪PracticeUse a safe lab
🔎InvestigateCorrelate evidence
📝ReportExplain the finding
🚀AdvanceHunt & engineer
What you will master
Cybersecurity, networking, Windows/Linux and IAM foundations
Cryptography, security technologies, cloud and vulnerability management
SOC operations, telemetry, SIEM and KQL investigation
Incident response, digital forensics, detection engineering and MITRE ATT&CK
Threat hunting, Microsoft-centric investigations, endpoint, email, network and cloud playbooks
Capstone cases, reporting, professional practice and career-ready investigation skills
How each module works
1. Concept: learn the technical foundation.
2. SOC perspective: understand what an analyst looks for.
3. Practical: perform a safe hands-on exercise.
4. Knowledge check: prove understanding before moving on.
Progression
Beginner · 1–5Foundations and core technical knowledge.
Intermediate · 6–16Enterprise controls, SOC operations, telemetry and SIEM.
Advanced · 17–24Detection engineering, hunting, response and capstone work.
Important
All labs should be performed only on systems and accounts you own or are authorized to test. The platform's simulated data is training data unless a page explicitly states otherwise.
24-Module SOC Roadmap
Module 1 · Cybersecurity Foundations
Build the security vocabulary and mental models needed before SOC work.
Beginner
Module 2 · Networking Fundamentals for SOC Analysts
Understand network traffic so you can read IPs, ports, protocols and communication paths.
Beginner
Module 3 · Operating Systems & Windows/Linux Basics
Learn the OS evidence an analyst sees during endpoint investigations.
Beginner
Module 4 · Identity & Access Management
Understand identities, authentication, authorization and modern enterprise access controls.
Beginner
Module 5 · Cryptography & Trust
Understand encryption, hashing, certificates and TLS without confusing their purposes.
Beginner
Module 6 · Enterprise Security Technologies
Understand what each major security control sees and how SOC analysts correlate them.
Beginner–Intermediate
Module 7 · Cloud Security Fundamentals
Move from on-prem concepts to cloud identity, networking, storage and shared responsibility.
Beginner–Intermediate
Module 8 · Vulnerability Management
Learn how security weaknesses are discovered, prioritized and remediated.
Intermediate
Module 9 · Security Operations Center
Understand how a professional SOC operates from alert creation through closure.
Intermediate
Module 10 · Incident Response & Digital Forensics
Learn structured response and evidence preservation from identification to recovery.
Intermediate
Module 11 · Governance, Risk & Compliance
Understand the business side of security operations and why analysts document controls and risk.
Combine domain-specific evidence into repeatable investigation workflows.
Advanced
Module 22 · SOC Capstone: Alert to Executive-Quality Incident Report
Demonstrate end-to-end analyst capability on a realistic multi-source case.
Advanced
Module 23 · Advanced SOC Analyst Professional Practice
Develop the habits that make investigations reliable, scalable and defensible.
Advanced
Module 24 · Global SOC Case Studies & Capstone Investigations
Apply the full methodology to varied attack scenarios and produce defensible conclusions.
Advanced
Lesson Workspace
Select a module above to begin.
0Lessons completed
0Quizzes passed
0%Course completion
CrowdStrike EDR Lab
Dedicated endpoint detection, investigation, incident response and threat hunting workspace. Built as a hands-on training environment.
EDR • IR • THREAT HUNTING
BLUE TEAM PRACTICAL WORKSPACE
CrowdStrike Falcon — From Detection to Response
Learn the endpoint investigation lifecycle: understand endpoint telemetry, review detections, investigate processes and network connections, manage policies and indicators, contain hosts, use authorised Real Time Response actions, and build threat-hunting hypotheses.
🖥️EndpointSensor + telemetry
🚨DetectionSignal / alert
🔎InvestigationProcess + host + user
🧭HuntHypothesis + search
🛡️ResponseContain + remediate
01 · Endpoint Security Foundation
Understand what an endpoint is, why it must be protected, and how endpoint telemetry supports security investigations.
EndpointComputer, laptop, server and other managed devices.
TelemetryProcess, file, connection, system and user activity.
EDRDetection, investigation and response around endpoint behaviour.
Interview focus: endpoint security, EDR vs traditional antivirus, fileless malware, ransomware and common malware terminology.
02 · How EDR Works
EDR collects endpoint context and applies analytics to identify potentially suspicious behaviour. Analysts then validate the evidence rather than accepting an automated verdict blindly.
Process / File / Network / System / User telemetry
↓
Sensor collection & analytics
↓
Detection / investigation context
↓
Analyst decision & response
03 · EDR vs Antivirus vs SIEM
Traditional Antivirus
Primarily focuses on malware prevention and detection using signatures and other detection methods.
Centralises and analyses logs across many sources to support correlation and investigation.
Practical rule
SIEM helps answer “what happened across the environment?” while EDR helps answer “what happened on this endpoint?”
04 · Cyber Kill Chain & MITRE ATT&CK
Use attack frameworks to structure an investigation and communicate where an observed behaviour fits in an attack.
ReconTargeting
WeaponizePayload
DeliverInitial access
ExploitExecution
InstallPersistence
C2 / ImpactObjective
MITRE ATT&CK is used as a behavioural mapping framework. Map only what the evidence supports; do not force a technique onto an alert.
05 · Falcon Platform Administration
Understand Falcon architecture and sensor deployment.
Install / uninstall sensors through authorised procedures.
Monitor sensor health.
Manage hosts, host groups and users.
Understand detection and prevention policy structure.
Create a practice host group
Review sensor health
Review user/host management
Document a policy change
06 · Endpoint Security Controls
Practice the defensive configuration areas covered in the source training: endpoint detections, prevention policies, USB controls, exclusions and indicator management.
PoliciesDetection and prevention configuration.
USB controlUnderstand device monitoring and policy exceptions.
ExclusionsUse narrowly and document the business/security reason.
IOC managementTrack and act on approved indicators.
Indicator graphExplore relationships between indicators and observed activity.
On-demand scanUse scanning as an additional validation step.
07 · Detection Investigation
Work a detection from alert context to evidence-backed disposition.
1Read detection
2Identify host
3Review process
4Check file/hash
5Review network
6Decide + document
Evidence to capture: detection time, hostname, user, process path, command line, parent process, hash, network connections, related detections and any authorised response already performed.
08 · Falcon Search & Timeline Analysis
Search by event, host and hash.
Review hash executions.
Search IP addresses and bulk domains.
Build scheduled searches where appropriate.
Pivot through host, process and user timelines.
Event search
Host search
Hash / IOC
Timeline
Correlation
09 · OSINT & Malware Analysis
Use approved external enrichment tools to add context to indicators. Treat third-party verdicts as evidence, not as the complete investigation.
Static analysisFile metadata, hashes and reputation context.
Dynamic analysisObserve sandbox behaviour in an approved environment.
Script analysisSafely decode or inspect suspicious PowerShell content.
Training rule: never upload confidential company data or live secrets to public analysis services.
10 · Incident Response Using EDR
Connect EDR evidence to the incident-response lifecycle: detection, analysis, containment, eradication, recovery and lessons learned.
DetectIdentify
AnalyseScope
ContainLimit impact
EradicateRemove cause
RecoverRestore
LearnImprove
11 · Host Network Containment
Understand network containment as a response action used to restrict a potentially compromised host while maintaining the required management connectivity.
Confirm affected host
Record reason and timestamp
Contain under authorised procedure
Observe host behaviour
Collect required evidence
Lift containment only when approved
Exercise: in a lab, simulate containment and document the expected host behaviour and recovery decision.
12 · Real Time Response (RTR)
Study the capabilities available for authorised remote response on Windows, macOS and Linux hosts.
ProcessList and investigate running processes; stop a process only when authorised.
NetworkReview active network connections.
FilesNavigate, collect or manage files under procedure.
Host controlRestart or shut down when approved.
ScriptsRun approved scripts/executables.
DiagnosticsCollect logs and system information; Windows may support deeper diagnostics.
Lab exercise: connect to a dedicated test host, use help, inspect processes/network/files, calculate a file hash and document every action.
13 · Threat Hunting
Threat hunting is proactive searching for suspicious activity that automated detections may not have surfaced.
Hypothesis
↓
Define scope + telemetry
↓
Search + pivot
↓
Validate + expand
↓
Document findings + detection gap
14 · Threat Hunting Methods & Pyramid of Pain
StructuredHunt from known patterns or intelligence.
UnstructuredExplore unusual behaviours and anomalies.
SituationalHunt around a specific incident or threat.
Use the Pyramid of Pain to understand that some indicators are easier for attackers to change than others. Prioritise behavioural and higher-value evidence where appropriate.
15 · Threat Intelligence
Understand threat actors and indicators.
Use intelligence to enrich detections and hunts.
Research malware families and campaign context.
Turn useful intelligence into monitoring or detection ideas.
Document source, confidence and relevance.
16 · Malware Case Study: Emotet → TrickBot → Ryuk
Study the multi-stage relationship presented in the training material as an example of how malware can enable follow-on activity.
📧Initial deliveryPhishing / malicious content
🦠EmotetInitial malware stage
🧩TrickBotCredential / access activity
🔐ExpansionPersistence / lateral activity
💥RyukRansomware impact
Use this as a case-study model for building an evidence chain. The exercise should focus on identifying telemetry that supports each stage rather than memorising malware names.
17 · XDR Fundamentals
Understand why security operations evolved from isolated endpoint, network and identity controls toward broader cross-domain detection and response.
XDR
Correlates telemetry across security domains to improve detection, investigation and coordinated response.
SIEM
Centralises logs and provides broad search, analytics and correlation; response may require additional tools.
Key XDR topics
Telemetry and log sources
Detection monitoring
Event investigation and queries
Custom detection logic
Response actions and notifications
18 · XDR Operations & Automation
Data ingestion and source health.
Detection and response configuration.
Event investigation and query workflows.
Scheduled searches and custom detections.
Notification delivery.
Workflow automation and playbook concepts.
Automation should make a repeatable workflow faster, not remove analyst validation from high-impact actions.
19 · Interview & Practical Readiness
Explain EDR vs antivirus
Explain EDR vs SIEM
Walk through a detection investigation
Explain containment vs eradication
Explain RTR use cases
Describe a threat-hunting workflow
Explain MITRE ATT&CK usage
Explain a malware attack chain
20 · Capstone: Complete EDR Investigation
Work one simulated endpoint incident from start to finish.
Read the detection and identify the affected host.
Build a process and user timeline.
Inspect command line, file and hash evidence.
Review network connections and related indicators.
Enrich indicators using approved sources.
Map supported behaviours to ATT&CK.
Determine scope and confidence.
Recommend containment and remediation.
Write the incident timeline and root-cause hypothesis.
Produce the final analyst handover.
AI SOC Manager
Ask for investigation guidance, evidence checklists and escalation advice.
MENTOR DEMO
SIMULATED OFFLINE MENTOR · NOT CONNECTED TO A LIVE AI SERVICE
SOC Manager: Welcome to your shift. Tell me what you are investigating (phishing, UPI, suspicious sign-in, malware, KQL or escalation) and I will give you a practical checklist.
Mentor guidance is prewritten for this prototype. A real-time AI assistant requires a secure backend/API integration later.
Career progression & resume
Build a training portfolio from your completed investigations.
Your analyst progression
L1 Analyst
Build your foundation by completing alert triage labs.
Complete practical labs to build your training portfolio. Your resume draft will appear here.
This is a training portfolio draft, not proof of employment, professional experience or an accredited certification. Review and edit it honestly before applying for jobs.
Progress & score
Your results are saved in this browser on this device.
COMPLETED
0
POINTS
0
ACCURACY
—
REMAINING
4
Reset training progress
This clears your completed-alert scores from this browser only.
BLUETEAM • GLOBAL INCIDENT CASEBOOK
Global Attack & Defense Case Studies
A growing library of major real-world cyber incidents, reconstructed as analyst-focused case studies: what happened, how the attack progressed, what evidence defenders could use, and how organizations can contain, eradicate, recover, and improve.
ATTACK → DETECT → DEFEND
HOW TO USE THIS CASEBOOK
Think Like the Attacker. Defend Like the SOC.
Every case is structured as an investigation rather than a story to memorize. Start with the business context, reconstruct the attacker path, identify the evidence left behind, then design the defensive response.
Escalate immediately to OT specialists, preserve system state, isolate carefully, validate safety-system integrity, and follow plant safety procedures.
CASE 19HIGH
Target 2013
Attackers used access associated with a third-party relationship and then reached retail systems where payment-card data was targeted.
Retail / Third-Party AccessReal-world incidentDefensive case study
Identify affected versions, remove or update the compromised software, hunt for secondary-stage activity, and rotate exposed secrets.
CASE 28CRITICAL
Log4Shell
A widely deployed Java logging component contained a critical vulnerability that created broad exposure across internet-facing and internal applications.
Java / Remote Code ExecutionReal-world incidentDefensive case study
Healthcare organizations need resilient identity controls, segmentation, recovery plans, offline/immutable backups, and tested business continuity.
SOC Decision
Contain affected systems, protect patient-critical services, preserve evidence, restore in a controlled order, and coordinate sector response.
CASE 33CRITICAL
Snowflake-Linked 2024 Incidents
A series of incidents involved compromised credentials and access to cloud-hosted customer data in environments lacking strong protective controls.
Cloud Data Platform / Credential AbuseReal-world incidentDefensive case study
Attacker Path
Credential compromise → cloud account access → data discovery → bulk data access/exfiltration.
Defender View
Strong authentication, credential hygiene, network/access policies, monitoring, and cloud data controls must work together.
SOC Decision
Rotate credentials, revoke sessions, review access logs, identify affected datasets, and hunt for related access across tenants.
CASE 34CRITICAL
Microsoft Storm-0558
An intrusion involving a compromised Microsoft consumer signing key enabled access to certain cloud mail accounts and exposed systemic identity-control lessons.
Cloud Identity / Signing KeyReal-world incidentDefensive case study
Edge appliances need rapid exposure assessment, emergency patching, integrity checks, and centralized logging.
SOC Decision
Identify vulnerable appliances, apply vendor mitigations/patches, inspect for compromise, rotate credentials, and hunt for post-exploitation activity.
CASE 37CRITICAL
Volt Typhoon
A state-linked campaign focused on maintaining access inside critical-infrastructure environments while using legitimate administrative tools to reduce detection.
Critical Infrastructure / Living-off-the-LandReal-world incidentDefensive case study
Protect build pipelines, restrict secrets, verify artifact integrity, and monitor unexpected changes to trusted automation.
SOC Decision
Rotate exposed secrets, audit pipeline changes, identify affected builds, and investigate downstream use of compromised credentials.
CASE 40CRITICAL
Yahoo 2013–2014
A major compromise exposed large volumes of user-account information and demonstrated the long-term consequences of weak credential and session protections.
Account Compromise / Data BreachReal-world incidentDefensive case study