-
We’re Here to Help!
Every organisation will face a security incident sooner or later: a phishing compromise, ransomware, a leaked database or a hijacked cloud account. What separates a manageable event from a business crisis is preparation. An incident response plan tells your team exactly what to do, who decides and how to communicate when every minute counts.
This guide explains what an incident response plan should contain, how to build one step by step and how to test it so it works under pressure, with specific notes for organisations operating in India.
An incident response plan is a documented set of roles, processes and communication steps for detecting, containing, investigating and recovering from cyber security incidents. It turns a chaotic situation into a coordinated response and helps you meet legal and contractual reporting obligations.
In April 2025, NIST published SP 800-61 Revision 3, which aligns incident response with the NIST Cybersecurity Framework 2.0. It treats incident response as part of overall cyber risk management, connected to governance, protection, detection, response and recovery, rather than a stand-alone technical activity.
| Component | What to include |
|---|---|
| Scope and objectives | Which systems, data and locations the plan covers and what it aims to achieve |
| Roles and responsibilities | Incident lead, technical responders, legal, communications, management and external partners |
| Severity levels | Clear criteria for classifying incidents and the response expected at each level |
| Detection and reporting | How incidents are identified and how staff report suspicious activity |
| Response phases | Steps for containment, eradication, recovery and post-incident review |
| Communication plan | Internal updates, customer notices, regulator reports and media handling |
| Evidence handling | How logs and systems are preserved for investigation |
| Contact list | Up-to-date contacts for staff, vendors, legal counsel, CERT-In and other authorities |
| Playbooks | Scenario-specific procedures for the most likely incidents |
A plan that has never been exercised often fails at the first real incident. Tabletop exercises walk your team through a realistic scenario to find gaps in roles, decisions and communication. For a deeper test, a red team engagement can show whether your detection and response hold up against a realistic, unannounced attack. Regular VAPT also reduces the number of incidents you have to handle in the first place.
An incident response plan sets out the overall approach: roles, responsibilities, severity levels, communication and escalation. Playbooks are step-by-step procedures for specific scenarios, such as ransomware, a data breach or a compromised account, that sit underneath the plan.
Run a tabletop exercise at least once a year, and update the plan after any real incident, significant organisational or technology change, or new regulatory requirement such as updated CERT-In or DPDP obligations.
Yes, although it can be short. Even a few pages covering who to call, how to contain common incidents, how to preserve evidence and when to report to CERT-In or affected customers can greatly reduce damage and confusion during a real incident.
An incident response plan is one of the most valuable security investments an organisation can make. With clear roles, practical playbooks, regulatory reporting steps and regular testing, your team can contain incidents faster, meet CERT-In and DPDP obligations and protect customer trust.
Need help building or testing your plan? Learn about our incident response planning service or contact the Offensium Vault team. You can also explore all our cybersecurity services.
Free 30-minute consultation
Talk to our ISO 27001 certified team about penetration testing, cloud security or compliance. No obligation, and we are happy to sign an NDA.