Study guide
0.1 Current Exam Facts, Blueprint, and Study Plan
EC-Council Certified SOC Analyst CSA 312-39
Track your progress as you read
Finished sections get a check mark.
1 Introduction: Current Exam Facts and Blueprint
0.1 Current Exam Facts, Blueprint, and Study Plan
2 Chapter 1: Security Operations and Management Fundamentals
1.1 SOC Overview, Capabilities, and Operational Workflow 1.2 SOC Architectures, Sourcing Models, and Organizational Components 1.3 SOC Maturity, Generations, Metrics, and KPIs
3 Chapter 2: Cyber Threat Vectors, TTPs, and Attack Techniques
2.1 Network, Host, and Password Attack Techniques 2.2 Application, Web, and Session Attack Vectors 2.3 Social Engineering, Email Threats, and Insider Attacks
4 Chapter 3: Threat Frameworks, Methodologies, and Indicators
3.1 Indicators of Compromise (IoCs), Indicators of Attack (IoAs), and Pyramid of Pain 3.2 Cyber Kill Chain and Diamond Model of Intrusion Analysis 3.3 MITRE ATT&CK and MITRE D3FEND Frameworks for SOC Defense
5 Chapter 4: Log Management, Formats, and Centralized Architecture
4.1 Log Fundamentals, Sources, and Host Logging 4.2 Network Device, Web Server, and Database Logs 4.3 Centralized Logging Architectures and Pipeline 4.4 Log Parsing, Normalization, and Field Extraction
6 Chapter 5: SIEM Architecture, Deployment, and Use Case Engineering
5.1 SIEM Architecture, Components, and Deployment Models 5.2 SIEM Use Case Development Lifecycle 5.3 Detection Rule Engineering and Sigma Rules
7 Chapter 6: SIEM Alert Triage, Detection Scenarios, and SOC Operations
6.1 Host and Application-Level Incident Detection Use Cases 6.2 Network-Level and Behavioral Anomaly Detection Use Cases 6.3 Alert Triage Methodology and False Positive Elimination 6.4 SOC Dashboards, Visualizations, and Reporting
8 Chapter 7: Cyber Threat Intelligence (CTI) and Threat-Informed Defense
7.1 Cyber Threat Intelligence (CTI) Lifecycle and Intelligence Types 7.2 Threat Intelligence Sources, Formats, and Platforms 7.3 Integrating Threat Intelligence into SOC and SIEM Operations
9 Chapter 8: Threat Hunting Methodologies and Proactive Detection
8.1 Threat Hunting Principles, Frameworks, and Process 8.2 Threat Hunting Techniques with PowerShell and Scripting 8.3 YARA Rule Crafting and Threat Hunting Tooling
10 Chapter 9: Incident Response Lifecycle, Governance, and Handling Procedures
9.1 Incident Response Frameworks and the SOC-IRT Interface 9.2 Incident Triage, Ticketing, and Prioritization 9.3 Containment, Eradication, Recovery, and Root Cause Analysis
11 Chapter 10: Incident Response Playbooks and SOC Automation
10.1 Specialized Incident Response Playbooks 10.2 Endpoint Detection and Response (EDR) and Extended Detection and Response (XDR) 10.3 Security Orchestration, Automation, and Response (SOAR) Playbooks
12 Chapter 11: Digital Forensics and Evidence Handling for SOC Analysts
11.1 Digital Forensics Fundamentals and Evidence Preservation 11.2 Host, Network, and Memory Forensics Triage 11.3 Malware Analysis Techniques for SOC Responders
13 Chapter 12: Cloud SOC Architectures and Monitoring
12.1 Cloud SOC Foundations and Shared Responsibility 12.2 Azure Security Operations with Microsoft Sentinel 12.3 AWS and Google Cloud Platform SOC Architectures
0.1 Current Exam Facts, Blueprint, and Study Plan
Key Takeaways Explain This Topic AI
EC-Council identifies the current Certified SOC Analyst examination as exam 312-39 with 100 multiple-choice questions and a three-hour time limit.
Independent exam candidates need one year of Network Administration or Security experience and must document eligibility unless they complete official EC-Council training.
The CSA v2 blueprint has eight domains; Incident Detection and Triage and Incident Response are the largest at 25% each.
EC-Council’s certification site publishes a 70% passing score for CSA but no standalone voucher price, so candidates must confirm the current fee in their booking channel.
Use the blueprint weights to prioritize SIEM detection, triage, and incident response while still covering every listed subdomain.
Last updated: September 2026
Verify the Exam Before You Study
This guide prepares you for EC-Council Certified SOC Analyst (CSA), exam 312-39 . EC-Council’s current certification page describes a 100-question, three-hour, multiple-choice examination delivered through the EC-Council Exam Portal. The same page states that an independent candidate must have one year of work experience in Network Administration or Security and provide proof through the application process; completing official EC-Council training waives that experience-application route.
Use the current EC-Council CSA certification page and the official CSA v2 exam blueprint as the controlling sources. EC-Council’s certification site lists the CSA exam details as 3 hours, 100 questions, and a 70% passing score , delivered at the ECC Exam Centre. Neither the certification page nor the current training page publishes a standalone exam-voucher price, so treat any fee you see on a reseller page as unofficial; verify the price, delivery method, identification rules, and eligibility status in the portal or authorized booking channel before paying.
- Published exam fact Current official value
- Exam title Certified SOC Analyst
- Exam code 312-39
- Format Multiple choice
- Questions 100
- Time limit 3 hours
- Passing score 70%
- Delivery EC-Council Exam Portal / ECC Exam Centre
Independent-candidate eligibility 1 year of Network Administration or Security experience, with proof through the application process
- Official-training route The experience application is waived for candidates who attend official training
- The Eight-Domain CSA v2 Blueprint
The official blueprint lists 59 explicit subdomains. Several are tightly coupled—for example, dashboard management and SOC reporting—but none may be skipped merely because it has a small weight.
- Domain Weight Approximate share of a 100-question form
- Security Operations and Management 5% about 5 questions
- Understanding Cyber Threats, IoCs, and Attack Methodology 8% about 8 questions
- Log Management 15% about 15 questions
- Incident Detection and Triage 25% about 25 questions
- Proactive Threat Detection 12% about 12 questions
- Incident Response 25% about 25 questions
- Forensics Investigation and Malware Analysis 5% about 5 questions
- SOC for Cloud Environments 5% about 5 questions
The question estimates are planning aids obtained by applying the published percentages to a 100-question exam. They are not a promise that every delivered form will contain exactly that count in each domain.
A Weight-Aware Study Sequence
Build the operating model. Learn SOC functions, people/process/technology, sourcing models, workflow, maturity, and metrics.
Understand the adversary and the evidence. Connect network, host, application, social-engineering, email, and insider TTPs to indicators and attack frameworks.
Master telemetry before tools. Practice reading Windows, Linux, macOS, firewall, router, web, database, and email logs, then learn centralized collection and normalization.
Spend half of your core review on detection/triage and response. Together these two official domains account for 50% of the blueprint. Work through SIEM architecture, deployment, use cases, AI-assisted rule development, alert analysis, reporting, vector-specific response, playbooks, and EDR/XDR.
Add proactive detection and investigation. Cover threat-intelligence sources and platforms, threat hunting, PowerShell, YARA, evidence handling, vector-specific investigation, and static/dynamic malware analysis.
Finish with cloud context. Compare shared responsibility and the native SOC services in Azure, AWS, and Google Cloud.
After each chapter, use the free CSA practice questions to test whether you can apply the concepts to a scenario. When a question exposes a weak area, return to the matching section and explain why each rejected option is wrong; recognizing a tool name is not enough.
Build a Traceable Review Loop
Keep an error log organized by the eight blueprint domains. For each missed practice item, record the observable evidence, the incident phase, the control or data source you chose, why the keyed action fits, and why each distractor fails. Tag the miss as a knowledge gap, sequencing error, tool-confusion error, or overreaction. Revisit high-weight Incident Detection and Triage and Incident Response gaps first, but do not let a low-weight domain remain uncovered.
Use short, controlled lab exercises where practical: parse a Windows or Linux authentication event, normalize a small syslog sample, write a narrowly scoped Sigma or YARA rule, trace a mock phishing message, and map a response decision to evidence-preservation needs. A lab is valuable only when you can explain the resulting telemetry and limitations. Tool output without interpretation is not analysis, and an alert without corroboration is not automatically an incident.
Exam-Day Reasoning
CSA questions commonly reward operational sequencing. First decide whether the evidence describes an event, an alert, or a confirmed incident. Then identify the phase—collection, triage, investigation, containment, eradication, recovery, or lessons learned—and choose the action that preserves evidence while reducing risk. Treat numeric alert thresholds, severity labels, and service-level targets in examples as organization-defined unless EC-Council’s blueprint explicitly fixes them.