IOC lifecycle, threat feeds, MITRE ATT&CK tactics and techniques, and the threat hunting workflow that finds attackers who have already bypassed your controls.
IOC lifecycle, threat feeds, MITRE ATT&CK tactics and techniques, and the threat hunting workflow that finds attackers who have already bypassed your controls.
Not every alert is a P1 incident. A severity framework: P1 (Critical) — active ransomware, ongoing data exfiltration, complete system compromise; P2 (High) — confirmed malware on multiple systems, compromised admin account; P3 (Medium) — single malware infection, policy violation; P4 (Low) — false positive, blocked attack attempt. Severity drives response time, staffing, and management notification requirements.
SOAR (Security Orchestration, Automation, and Response) automates response actions triggered by SIEM alerts: isolating an infected host via EDR API, blocking a C2 IP in the firewall, and creating a ticket in the case management system. Platforms: Palo Alto XSOAR, Splunk SOAR, TheHive (open source). Case management tracks the full investigation lifecycle: evidence, timeline, analyst notes, and closure.
Internal communication: IT leadership notified within 1 hour of P1 confirmation, senior management within 2 hours, legal/compliance within 4 hours. External communication: customers if PII is breached (GDPR 72-hour notification requirement, state breach notification laws). Law enforcement: FBI CyberDivision for nation-state/ransomware. Public statement: legal reviews before any external disclosure. Never confirm or deny to media during active incident.
# TheHive case creation via API
# POST /api/case
{
"title": "P2: Suspected Cobalt Strike Beacon - WORKSTATION-42",
"severity": 2,
"tlp": 2,
"tags": ["cobalt-strike", "lateral-movement", "T1059.001"],
"description": "Sysmon detected powershell.exe network connection to "
"known Cobalt Strike team server 198.51.100.10:443. "
"Host isolated via CrowdStrike. Investigation ongoing.",
"tasks": [
{"title": "Isolate host", "status": "Completed"},
{"title": "Memory acquisition", "status": "InProgress"},
{"title": "Identify patient zero", "status": "Waiting"},
{"title": "Scope lateral movement", "status": "Waiting"},
{"title": "Draft stakeholder notification", "status": "Waiting"}
]
}
Create a complete SOC runbook for a ransomware incident. Include: detection criteria, P1 declaration checklist, isolation steps, evidence preservation, stakeholder communication template, and recovery checklist.
The foundations from today carry directly into Day 5. In the next session the focus shifts to Automation with SOAR and Python — building directly on everything covered here.
Before moving on, verify you can answer these without looking:
Live Bootcamp
Learn this in person — 2 days, 5 cities
Thu–Fri sessions in Denver, Los Angeles, New York, Chicago, and Dallas. $1,490 per seat. June–October 2026.
Reserve Your Seat →