This curriculum spans the design and operation of a mature security operations center, comparable to a multi-workshop program for establishing 24/7 monitoring, detection engineering, and incident response coordination across SIEM, EDR, network, and SOAR systems.
Module 1: Establishing SOC Governance and Operational Frameworks
- Define escalation paths for incident response based on severity thresholds aligned with NIST SP 800-61.
- Select and document roles and responsibilities for SOC analysts, incident responders, and escalation managers.
- Implement a shift-based staffing model to ensure 24/7 monitoring coverage with overlap for knowledge transfer.
- Integrate SOC operations with existing ITIL change and incident management processes.
- Establish a formal charter outlining SOC authority, scope, and reporting lines to CISO and executive leadership.
- Develop service level agreements (SLAs) for mean time to detect (MTTD) and mean time to respond (MTTR).
- Conduct quarterly tabletop exercises to validate incident response workflows and governance decisions.
Module 2: Threat Intelligence Integration and Prioritization
- Subscribe to and normalize threat feeds from commercial, open-source, and ISAC partners using STIX/TAXII.
- Map intelligence to MITRE ATT&CK techniques to contextualize alerts within adversary behavior patterns.
- Build automated enrichment pipelines to correlate IOCs with internal telemetry from EDR and SIEM.
- Establish a threat scoring model based on relevance, confidence, and potential business impact.
- Assign ownership for maintaining threat intelligence use cases and updating detection rules accordingly.
- Filter out irrelevant IOCs to prevent alert fatigue and reduce noise in detection systems.
- Conduct biweekly threat landscape reviews with threat hunters and incident responders.
Module 3: SIEM Architecture and Log Source Management
- Design log retention policies balancing compliance requirements with storage cost and query performance.
- Standardize log collection formats using Syslog, WEF, or agent-based forwarding across heterogeneous systems.
- Validate parsing accuracy for critical log sources (e.g., Windows Event Logs, firewall flows, proxy logs).
- Implement parsing normalization to ensure consistent field naming across vendors and platforms.
- Establish onboarding checklists for integrating new log sources with validation and alerting baselines.
- Monitor log source health and detect gaps using heartbeat alerts and volume deviation thresholds.
- Segment SIEM data access using role-based access control (RBAC) to limit analyst privileges.
Module 4: Detection Engineering and Rule Development
- Develop detection rules using Sigma or YARA-L syntax for cross-platform SIEM compatibility.
- Balance sensitivity and specificity in correlation rules to minimize false positives without missing threats.
- Implement a version-controlled repository (e.g., Git) for detection rule lifecycle management.
- Conduct peer reviews of new detection logic before deployment to production SIEM.
- Baseline normal activity to differentiate anomalies from legitimate operational behavior.
- Use purple teaming results to refine detection coverage for specific adversary tactics.
- Tag rules with MITRE ATT&CK IDs and data source requirements for coverage gap analysis.
Module 5: Incident Triage and Analysis Workflows
- Standardize triage checklists for common alert types (e.g., malware beaconing, brute force, lateral movement).
- Configure automated enrichment actions (e.g., DNS lookups, file hash reputation, user context).
- Document decision criteria for escalating alerts to Level 2 analysts or incident responders.
- Integrate SOAR playbooks to automate repetitive triage steps like endpoint isolation or user disablement.
- Use timeline analysis to sequence events across endpoints, network, and identity systems.
- Preserve chain of custody for evidence collected during initial analysis for potential legal proceedings.
- Apply threat context to determine if an incident is isolated or part of a broader campaign.
Module 6: Endpoint Detection and Response (EDR) Operations
- Configure EDR agents to collect process execution, network connections, and file activity without degrading performance.
- Define containment policies for automated response actions based on detection confidence levels.
- Conduct live response investigations using EDR console to collect memory dumps and running processes.
- Validate EDR sensor coverage across all critical assets and enforce compliance via configuration management.
- Develop custom detection queries to identify suspicious behaviors not covered by vendor rules.
- Coordinate with endpoint management teams to patch or reimage compromised systems post-containment.
- Review EDR alert volume trends to tune detection thresholds and reduce analyst workload.
Module 7: Network Monitoring and Traffic Analysis
- Deploy network TAPs or span ports to ensure full packet capture for critical network segments.
- Configure NetFlow collection from firewalls and routers with sufficient sampling rates for visibility.
- Use Zeek (Bro) or Suricata to generate application-layer metadata from encrypted traffic.
- Establish baselines for normal traffic patterns to detect C2 beaconing or data exfiltration.
- Integrate network evidence with SIEM and EDR data to reconstruct attack paths.
- Manage decryption policies for TLS traffic in accordance with privacy regulations and legal requirements.
- Monitor DNS query logs for tunneling attempts and connections to known malicious domains.
Module 8: SOC Automation and Orchestration (SOAR)
- Map repeatable incident response tasks to SOAR playbook capabilities (e.g., phishing email quarantine).
- Integrate SOAR platform with email security, firewall, and identity providers via APIs.
- Design playbook decision trees that include human-in-the-loop approvals for high-risk actions.
- Log all SOAR actions for auditability and post-incident review.
- Measure automation effectiveness using metrics like time saved and playbook success rate.
- Conduct regular security reviews of SOAR playbook logic to prevent unauthorized access or misuse.
- Use sandboxed environments to test playbook updates before production deployment.
Module 9: Continuous Improvement and Metrics Reporting
- Track key performance indicators (KPIs) such as alert volume, closure rate, and mean time to escalate.
- Conduct root cause analysis for missed detections or delayed responses using blameless post-mortems.
- Update detection rules and playbooks based on lessons learned from recent incidents.
- Benchmark SOC maturity against NIST CSF or CIS Controls to identify capability gaps.
- Present quarterly metrics to executive leadership focusing on risk reduction and operational efficiency.
- Rotate analysts through threat hunting and red team exercises to maintain skill sharpness.
- Conduct third-party SOC assessments to validate detection coverage and response effectiveness.