Live sessions run Tuesday and Thursday evenings, 6:30 to 8:30 PM Central, with a Saturday lab block from 10:00 AM to 1:00 PM Central. That is 35 hours live with your instructor, plus graded assignment work each week.
Week 0, from the day you enroll: Foundations
Included in your tuition and open the moment you enroll. Short lessons, each one followed by a small hands on task in a sandbox corner of the range: how computers work, Windows and Linux basics, what an IP address and DNS and a port actually are, how the internet and email flow, the security words the field uses, and what a ticket is. You finish with a readiness check you certify yourself and a live orientation on Saturday, November 7 that doubles as your range tech check. If you already work in IT, you take the readiness check and test out. Nobody starts week one lost.
Week 1, November 10 to 14: Start the job
What a SOC actually does all day. Networking that matters for investigations: addresses, subnets, ports, DNS, the TCP handshake. Command line work on Windows and Linux. Your first shift in the range, working a queue of noisy, mostly benign tickets to the documentation standard. Graded assignment: networking questions answered as ticket work, using evidence you pulled from the range yourself.
Week 2, November 17 to 21: Endpoints, Linux, logs and the SIEM
Finding authentication evidence in Linux logs. Windows event logs and endpoint telemetry. Searching the SIEM to answer a specific question and building a timeline from raw events. Identity joins the evidence this week: the firm signs in through Microsoft Entra ID, you enroll in multi factor authentication, and you work two identity investigations as tickets, a password spray and an MFA fatigue attack, from the Entra sign in logs correlated with the SIEM. You rerun the core of one investigation in Splunk, writing real SPL, and that work is graded, because SPL is the dialect employers name most. You also meet Microsoft Sentinel, the Microsoft stack console, while its trial window runs, and the firm AWS findings from GuardDuty and Security Hub land in your queue as tickets, because that is the job now. The AI assistant switches on this week, under the verification discipline described below. Graded assignment: a full SIEM investigation write up, including a note on what the AI got wrong.
Thanksgiving week, November 23 to 28: Self paced lab week
No live sessions. A lighter week that still behaves like a real job, because the queue does not stop for holidays. You harden a Windows and a Linux machine against CIS Benchmark settings and prove it with before and after evidence, clear a backlog of low priority tickets, and get an early look at packet analysis. Your instructor also demonstrates PingCastle against the firm domain before and after the hardening, the same posture report real firms hand to auditors, and you take your first BloodHound look at how an attacker could move through the domain. Graded assignment: a CIS hardening report.
Week 3, December 1 to 5: Seeing attacks, packets and phishing
Wireshark in depth: following conversations, spotting scans, beaconing and data leaving the network, with Zeek connection and DNS records beside the captures so you learn when metadata answers the question and when only the packets will. Then phishing: how attacks on a law firm actually look, and full header analysis on real messages from the firm mailbox. The week ends with the simulated SOC shift on Saturday, December 5: three hours working a live queue while real incidents develop in the network, a user reports a suspicious email mid shift, and you finish by writing the handoff note the next shift will rely on. Confirmed incidents from the shift are opened as cases in TheHive, the case layer that sits above the ticket queue in a real SOC, and every indicator you check goes against the firm MISP instance. Graded assignment: a complete phishing investigation, including the scope check and the reply to the user who reported it.
Week 4, December 8 to 12: Exposure and detection engineering
Vulnerability scanning with Nessus, and how to prioritize by real risk instead of raw scores. Firewall rules and logs. IDS and IPS alerts. Investigating an endpoint alert in Microsoft Defender for Endpoint and isolating a host. Mapping the firm domain with BloodHound so you can see the attack path your detection rule has to defend. MITRE ATT&CK as the shared language of the SOC. You also build your first security automation: a phishing triage playbook in Splunk SOAR that enriches indicators, opens the case and drafts the ticket for analyst approval. On the evening of Wednesday, December 9, you get paged: an on call escalation drill where you respond inside a set window and hand off to standard. Graded assignment: a Sigma style detection rule you wrote from a real event, mapped to ATT&CK, with test evidence showing it fires on attack data and behaves on benign data. Your BloodHound path map goes in with it, with the step your rule defends marked.
Week 5, December 15 to 19: AI in the modern SOC, careers and the capstone
A full session on AI in security operations, described in the next section. Then careers: your resume built line by line from your own graded work, your portfolio put in order, and a mock technical interview run the way a hiring manager runs one, with scored feedback. You also claim your own free ServiceNow developer instance and rebuild one of your security tickets there as an enterprise incident, so the ITSM system most large employers run is not new to you on day one. You build one automation story in your own free Tines account, and inside the Microsoft tenant you set a Microsoft Purview data loss prevention policy for client matter data and triage the alert when the data exposure incident from the AI session trips it. The program closes on Saturday, December 19 with the capstone and graduation.