Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 4 · Lesson 2 of 5
Standard processes: playbooks, runbooks and the case record
1 min read
When only one expert knows how to handle a case type, results change with whoever is on shift. Writing the procedure down gives consistency and makes handover possible, and it gives the team something to review and improve. It does not replace a trained analyst, and it is not mainly about being faster than the expert.
| Document | What belongs in it | Example item |
|---|---|---|
| Playbook | Decision points, who holds authority, escalation and notification order | Who may approve isolating a production server |
| Runbook | Exact commands, queries and system steps, with expected output | How to capture a memory image on an affected host |
Keeping the two apart lets technical steps change without renegotiating decision rights. The third piece is one authoritative case record.
When notes live in chat threads, personal spreadsheets and email, handovers lose work and nobody can say how long a case took. A single timeline per case lets the next shift pick up the work and is where the operation's own metrics come from.
It does not remove the need for notes or a verbal handover, and a ticket by itself does not give the record special weight as court evidence. Example: an exam option claims the ticketing system makes shift conversations unnecessary; that overstates what one case record does.
Check yourself
1. A team is separating its ransomware documentation into a playbook and a runbook. Which item belongs in the runbook?
2. Analysts keep their investigation notes in chat threads, personal spreadsheets and mail trails, while the ticket holds only the alert name. Shift handovers repeatedly lose work and the manager cannot say how long a case took. What does moving every case into one authoritative case record give the operation?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, NIST AI Risk Management Framework (AI RMF 1.0, NIST AI 100-1)
CompTIA CySA+ cheat sheet: every key fact on one page →