Incident Response: The Process, Playbooks and a Worked Example
Every organisation will eventually face a security incident. What separates a bad day from a business-threatening disaster is preparation. Incident response (IR) is the organised approach to preparing for, detecting, containing, eradicating and recovering from security incidents, and learning from them afterwards. This lesson explains the lifecycle, the roles, the decisions, the evidence habits and gives you complete playbooks and a tabletop exercise you can run with friends or colleagues.
Event, Alert, Incident: Know the Difference
| Term | Meaning | Example |
|---|---|---|
| Event | Any observable occurrence | A user logs in |
| Alert | An event that a tool flags as potentially interesting | Ten failed logins in a minute |
| Incident | An event or events that actually threaten confidentiality, integrity or availability, or violate policy | Confirmed compromise of an email account |
| Breach | An incident in which data has been accessed or disclosed without authorisation | Customer data downloaded by an intruder |
The Incident Response Lifecycle
NIST SP 800-61 (Computer Security Incident Handling Guide) describes four main phases. Many organisations use the SANS six-step version. They map closely:
| NIST phase | SANS steps | Main goal |
|---|---|---|
| 1. Preparation | Preparation | Be ready before anything happens |
| 2. Detection and analysis | Identification | Spot and understand the incident |
| 3. Containment, eradication and recovery | Containment, Eradication, Recovery | Stop the damage, remove the cause, restore service |
| 4. Post-incident activity | Lessons learned | Improve so it is less likely to happen again |
Note that NIST’s guidance has been updated over time, so always check the current revision of the publication for the latest wording.
Phase 1: Preparation
- Write an incident response policy and plan approved by management.
- Define roles: incident commander, technical lead, communications lead, legal and compliance contact, scribe.
- Maintain an asset inventory and a map of critical data and systems.
- Deploy logging, EDR and backups and test them; see SIEM, Logging and SOC Operations.
- Keep an out-of-band contact list (phone numbers, not just email) and external contacts: legal counsel, insurer, forensic partner, regulators, law enforcement.
- Prepare playbooks for common incident types.
- Run exercises at least yearly.
Phase 2: Detection and analysis
- Triage alerts and user reports quickly; every report deserves acknowledgement.
- Determine scope: which systems, accounts and data are involved? When did it start?
- Assign severity using agreed criteria so that response matches impact.
- Start an incident log with timestamps, actions, decisions and evidence.
- Preserve volatile evidence before changes destroy it; see Digital Forensics Fundamentals.
| Severity | Typical criteria | Response |
|---|---|---|
| Critical | Widespread impact, sensitive data theft, ransomware, safety risk | Immediate, all hands, executive notification |
| High | Confirmed compromise of important system or account | Response within the hour, senior involvement |
| Medium | Contained malware on a single endpoint, policy violation | Same business day |
| Low | Suspicious activity with no confirmed impact | Normal queue |
Phase 3: Containment, eradication and recovery
- Short-term containment: stop the spread without destroying evidence: isolate the host with EDR, disable compromised accounts, block malicious addresses, segment networks.
- Long-term containment: temporary fixes that keep the business running, such as rebuilding an environment in parallel.
- Eradication: remove the root cause and any persistence: delete malicious files and scheduled tasks, patch the exploited flaw, reset all potentially exposed credentials and keys.
- Recovery: restore from known-good backups, rebuild systems, return them to service gradually with enhanced monitoring, and verify integrity.
Containment decisions involve trade-offs between speed, evidence preservation and business impact. Agree who can authorise disruptive actions before the incident.
Phase 4: Post-incident activity
- Hold a blameless lessons-learned review within days: what happened, what worked, what failed, what to change.
- Create tracked action items with owners and due dates.
- Update playbooks, detections and training.
- Produce a report suited to each audience.
Reporting and Legal Duties (India and General)
- In India, the CERT-In directions issued in April 2022 require certain categories of cyber incidents to be reported to CERT-In within 6 hours of noticing them, and for logs to be kept for 180 days. Check the current directions and your sector regulator’s rules.
- The Digital Personal Data Protection Act, 2023 sets duties for data fiduciaries on personal data breaches, including notification to the Data Protection Board and affected individuals as prescribed in its rules.
- Financial, telecom, insurance and listed companies often have additional sector-specific obligations.
- Individuals who are victims of online fraud can report on the national cybercrime portal (cybercrime.gov.in) or call the helpline 1930.
- Involve legal counsel early, and keep communications factual and accurate. Avoid speculation in writing.
Communication During an Incident
- Use a primary and a backup channel that attackers cannot read (assume email may be compromised).
- Provide regular, scheduled updates to leadership.
- Have approved holding statements for customers, staff and media.
- Maintain a “need to know” list and a single source of truth.
Playbook 1: Suspected Compromised Email Account
- Detect: user report, impossible-travel alert or strange forwarding rule.
- Contain: reset the password, revoke active sessions and tokens, enforce MFA re-registration.
- Investigate: check sign-in logs, mailbox rules, forwarding settings, OAuth app consents, sent messages and shared links.
- Eradicate: remove malicious rules and apps; review other accounts the user shares credentials with.
- Notify: warn recipients of suspicious messages sent; inform management and legal if data was accessed.
- Recover and improve: enable phishing-resistant MFA, conditional access and mailbox auditing.
Playbook 2: Malware Alert on an Endpoint
- Triage: confirm the alert, identify the host, user and file.
- Contain: isolate the machine from the network through EDR.
- Collect: capture memory and disk evidence if the severity justifies it.
- Analyse: identify the malware family, the entry point (email, download, USB) and what it accessed.
- Scope: search for the same indicators on other machines.
- Eradicate and recover: reimage the machine rather than trust a cleaned system when compromise is serious; reset credentials used on it.
- Improve: block the delivery path and add detections.
Playbook 3: Ransomware
Summarised from Ransomware: How It Works, Defence and Recovery: isolate affected systems at once (do not power off if memory evidence is needed), identify the scope, protect backups, involve legal, insurer and law enforcement, decide on recovery from clean backups, rebuild identity systems and rotate all credentials, then monitor closely for reinfection. Payment decisions are for senior leadership with legal advice; payment does not guarantee recovery and may breach sanctions rules.
Practice Lab 1: Run a Tabletop Exercise
A tabletop is a discussion-based exercise. Gather two to six people, assign roles, and walk through this scenario, answering each question aloud and writing down the gaps:
- Inject 1 (09:15): The help desk reports three staff members clicked a link in an email that appeared to come from the CEO. One has since noticed their mouse moving by itself. What do you do first? Who do you call?
- Inject 2 (10:00): EDR shows a suspicious process on two laptops and an unfamiliar admin login on a file server. How do you scope this? What do you contain, and who must approve?
- Inject 3 (12:30): Files on the server have been renamed, and a text file demands payment. How do the priorities change? What is the status of your backups?
- Inject 4 (15:00): A journalist emails asking about a rumoured data leak. Who responds, and what do you say?
- Debrief: What was unclear? Which contact was missing? Which decisions took too long? Create at least five action items.
Practice Lab 2: Evidence Collection Basics on a Lab VM
# Record time and identity first
date -u; hostname; whoami
# Volatile information (order of volatility: most fleeting first)
who; w; ps aux; ss -tulpn; ip neigh; lsof -nP -i
# Save with a hash for integrity
ps aux > ps_$(hostname)_$(date -u +%Y%m%dT%H%M%SZ).txt
sha256sum ps_*.txt > hashes.txt
Practice documenting each command, the time and who ran it. The chain of custody habit begins with discipline in small things.
Practice Lab 3: Write Your Own Playbook
Choose one scenario (lost laptop, leaked API key, phishing mail reported, web defacement). Create a one-page playbook with: trigger, severity guide, first five actions, who to notify, evidence to collect, containment options, recovery steps and review checklist. Test it on a friend.
Common Mistakes
- No plan, or a plan nobody has read.
- Wiping systems before collecting evidence.
- Using compromised email for incident communications.
- Resetting one password and declaring victory, while the attacker has other access.
- Skipping the lessons-learned review once the pressure eases.
Practice Exercises
- Explain the four NIST phases to a non-technical manager using the analogy of a fire safety plan.
- Draft severity criteria for a company with an online store and a corporate network.
- List the contacts that should be on an out-of-band incident contact sheet.
- Describe three containment actions and the business impact of each.
- Write the agenda for a one-hour blameless post-incident review.
Mentor tip: During a real incident, people are tired and stressed. A short checklist that anyone can follow beats a hundred-page plan that nobody can find. Print it, and keep a copy offline.
Educational use only: practise evidence collection and exercises on systems you own or are authorised to manage.
- Follow a lifecycle: prepare, detect and analyse, contain, eradicate and recover, then learn.
- Agree roles, severity levels, contacts and approval paths before an incident.
- Preserve evidence and keep a timeline; document every action.
- Know your legal reporting duties, including CERT-In and data protection obligations in India.
- Exercise your plan with tabletops and improve it after each event.