This curriculum spans the technical and operational rigor of a multi-workshop security engineering program, addressing the same breadth of challenges encountered in enterprise SOC deployments—from log normalization and correlation tuning to compliance reporting and cross-team governance.
Module 1: SIEM Architecture and Platform Selection
- Evaluate on-premises vs. cloud-hosted SIEM deployments based on data residency requirements and network egress costs.
- Compare schema flexibility across platforms when integrating custom application logs with non-standard formats.
- Assess vendor lock-in risks when adopting proprietary correlation engines or data models.
- Determine scalability thresholds by stress-testing ingestion rates during peak event bursts from endpoint agents.
- Implement high availability and disaster recovery configurations for SIEM components in multi-region environments.
- Negotiate data retention policies with legal and compliance teams to align with incident response timelines and storage budgets.
Module 2: Log Source Onboarding and Normalization
- Standardize syslog formats from network infrastructure devices to ensure consistent parsing across firewall, switch, and router vendors.
- Configure Windows Event Forwarding with appropriate subscription scopes to avoid overwhelming the SIEM with verbose audit logs.
- Map custom application log fields to the Common Information Model (CIM) without losing context from proprietary identifiers.
- Resolve timestamp discrepancies from devices with unsynchronized clocks using NTP validation and offset correction rules.
- Design parsing rules that tolerate schema drift in third-party SaaS application logs delivered via API polling.
- Implement log sampling strategies for high-volume sources like web proxies when full ingestion exceeds licensing tiers.
Module 3: Correlation Rule Development and Tuning
- Construct multi-stage correlation rules to detect lateral movement by chaining authentication failures with subsequent successful logins across systems.
- Adjust threshold-based alerts for brute force detection to account for legitimate batch job behaviors in development environments.
- Suppress false positives from scheduled vulnerability scans by cross-referencing scanner IP addresses in correlation logic.
- Use statistical baselining to identify anomalous data exfiltration patterns from file servers without predefined thresholds.
- Integrate threat intelligence feeds to enrich correlation rules with known malicious IPs while managing feed update latency.
- Document rule justification and expected alert volume to support audit reviews by compliance officers.
Module 4: Threat Detection Engineering
- Develop behavioral analytics rules for privileged user activity by establishing baselines from historical access patterns.
- Implement UEBA rules that flag deviations in geographic login locations while accounting for legitimate remote work scenarios.
- Design detection logic for living-off-the-land binaries (LOLBins) by correlating command-line arguments with process ancestry.
- Balance sensitivity and specificity in ransomware detection rules to minimize disruption from false positives on file encryption tools.
- Integrate EDR telemetry into SIEM detection workflows to validate process injection patterns observed in endpoint alerts.
- Version-control detection rules using Git to track changes, enable rollback, and support peer review processes.
Module 5: Incident Response Integration
- Configure automated SIEM-to-ticketing system workflows with field mappings that preserve critical context like source IPs and timestamps.
- Define escalation paths for high-severity alerts that trigger on-call rotations and require manual acknowledgment within SLA windows.
- Enrich incident tickets with contextual data from directory services, such as user role and department, during alert creation.
- Implement feedback loops from SOC analysts to update rule thresholds based on post-incident review findings.
- Coordinate with network teams to ensure firewall or endpoint isolation actions initiated from SIEM are logged and auditable.
- Test failover procedures for incident response workflows when downstream systems like SOAR platforms are unreachable.
Module 6: Performance Optimization and Resource Management
- Partition and tier historical data across hot, warm, and cold storage to balance query performance and cost.
- Optimize search queries by leveraging indexed fields and avoiding regular expressions in frequently run dashboards.
- Monitor parser CPU utilization and offload processing to forwarders when central node load exceeds 70% sustained usage.
- Implement data summarization jobs to pre-aggregate metrics for long-term trend analysis without querying raw events.
- Schedule resource-intensive compliance reports outside of business hours to avoid contention with real-time detection.
- Audit user-created saved searches to identify inefficient patterns that strain system resources.
Module 7: Compliance, Auditing, and Reporting
- Configure immutable audit trails for SIEM administrative actions to meet SOX and ISO 27001 control requirements.
- Generate quarterly attestation reports demonstrating log coverage across critical systems for internal auditors.
- Align log retention periods with GDPR right-to-be-forgotten requests while preserving data for active investigations.
- Produce executive dashboards showing mean time to detect (MTTD) and mean time to respond (MTTR) using incident timeline data.
- Validate completeness of audit logs by comparing expected vs. observed event volumes from domain controllers.
- Respond to regulatory inquiries by exporting incident data in standardized formats acceptable to external assessors.
Module 8: Governance, Maintenance, and Continuous Improvement
- Establish a change advisory board (CAB) process for approving updates to production correlation rules.
- Conduct quarterly rule reviews to deprecate or re-tune alerts with sustained low signal-to-noise ratios.
- Track SIEM uptime and availability in service level agreements with operations teams supporting backend infrastructure.
- Coordinate schema updates with application owners before major software releases that impact log output.
- Measure analyst workload per alert type to identify opportunities for automation or rule refinement.
- Integrate lessons learned from purple team exercises into detection rule enhancements and coverage gap remediation.