JOHN DANKOjohn@danko:~/projects/soc-incident-response-playbook
OPEN TO SOC ROLES
~ / projects / soc-incident-response-playbook
Personal project ยท Original playbooks ยท Fall 2026

SOC Incident Response Playbook.

A set of original, practical incident response playbooks for SOC analysts. Each walks through the same eight phases so an analyst can pick up any alert type and know what to do next.

OWNERJohn Danko
PATH~/projects/soc-incident-response-playbook
REPOjohn-danko-cyber/SOC-Incident-Response-Playbook
TYPECase study
01

Workflow

Incident response workflow: Preparation, Detection, Triage, Investigation, Containment, Eradication, Recovery, Lessons Learned, with a feedback loop to Detection

Diagram from the repository. NIST SP 800-61 groups handling into four phases; I split them into eight operational SOC steps so each maps to concrete analyst actions.

02

Scenario

An alert fires. The analyst picks the matching playbook, fills in the standard triage fields (host, user, IP, process, hash, severity, time) on the ticket, works through the phases in order, uses the escalation table to decide when to bring in a senior analyst, and closes with lessons learned that feed back into detections.

03

Playbooks

๐Ÿ“ง Phishing

Suspicious or reported email, credential harvesting

Open โ†’

๐Ÿฆ  Malware

Endpoint alert, unknown process, persistence (includes a real applied example)

Open โ†’

๐Ÿ”‘ Brute Force

Password guessing, spraying, credential stuffing

Open โ†’

๐Ÿ”’ Ransomware

Encryption activity, ransom notes

Open โ†’

๐ŸŒ Suspicious Login

Impossible travel, unknown device, MFA fatigue

Open โ†’

โœ… IR Checklist

Used on every incident

Open โ†’
04

Tools & Frameworks

  • NIST SP 800-61
  • MITRE ATT&CK
  • CISA IR Playbooks (reference)
  • Markdown documentation
05

Example: Phishing Investigation Steps

  1. CollectOriginal message with full headers
  2. Review headersReturn-Path, Reply-To, Received chain, SPF/DKIM/DMARC
  3. ExtractURLs, domains, attachments; SHA256 attachments; check reputation without opening
  4. ScopeSearch mail logs for every recipient of the same sender/subject/URL
  5. Check exposureProxy/DNS logs for visits; sign-in logs for users who entered credentials
  6. Look for persistenceNew mailbox forwarding or inbox rules
06

MITRE ATT&CK Coverage

T1566.001/.002SpearphishingPhishing
T1574.002DLL Side-LoadingMalware
T1547.001Registry Run KeysMalware
T1053.005Scheduled TaskMalware
T1110.001/.003/.004Brute ForceBrute force
T1486Data Encrypted for ImpactRansomware
T1490Inhibit System RecoveryRansomware
T1078Valid AccountsSeveral
T1621MFA Request GenerationSuspicious login
T1550.004Web Session CookieSuspicious login

Partial list. Each playbook has its full mapping in the repo.

07

Evidence

08

What I Learned

  • Splitting NIST's four phases into eight concrete steps makes each analyst action clear.
  • Recording the same triage fields first makes every alert type easier to hand off and escalate.
  • Preparation (logging, detection rules, access rights) decides how fast you can respond.
  • Lessons learned should feed straight back into detections and playbooks.