Skip to main content

Offensium Vault

How to Build an Incident Response Plan: Step-by-Step Guide

How to Build an Incident Response Plan: Step-by-Step Guide
Spread the love

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.

What Is an Incident Response Plan?

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.

Why Indian Businesses Need One Now

  • CERT-In reporting: specified incidents must be reported to CERT-In within six hours of being noticed. See our CERT-In guidelines guide.
  • DPDP obligations: personal data breaches must be reported to the Data Protection Board and affected individuals. Our DPDP Act compliance guide explains the details.
  • Customer contracts: enterprise customers increasingly require prompt breach notification and evidence of a tested plan.
  • Business continuity: a clear plan shortens downtime and reduces recovery costs.

Key Components of an Incident Response Plan

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

How to Build an Incident Response Plan: Step by Step

  1. Identify critical assets and risks. Know which systems and data matter most and which threats are most likely. A threat and risk analysis is a strong starting point.
  2. Define roles and authority. Decide who leads, who can take systems offline and who approves external communication.
  3. Set severity levels. Agree what makes an incident low, medium, high or critical, and the response timelines for each.
  4. Document the response process. Cover detection, triage, containment, eradication, recovery and lessons learned.
  5. Write playbooks. Start with the most likely scenarios: phishing and account compromise, ransomware, data leakage, cloud credential exposure and website defacement.
  6. Plan communication and reporting. Prepare templates and decision points for CERT-In, the Data Protection Board, customers and partners.
  7. Make sure logging supports investigation. Confirm critical systems are logged, time-synchronised and retained long enough.
  8. Test and train. Run tabletop exercises and update the plan based on what you learn.

Example: Ransomware Playbook Outline

  • Isolate affected systems from the network without powering them off where possible.
  • Disable compromised accounts and rotate privileged credentials.
  • Identify the scope: which systems, data and backups are affected.
  • Preserve evidence and engage forensic support if needed.
  • Assess reporting obligations, including the six-hour CERT-In window.
  • Restore from clean, tested backups and monitor for reinfection.
  • Hold a lessons-learned review and fix the root cause.

Testing Your Plan

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.

Common Mistakes to Avoid

  • Writing a long document that nobody reads or can find during an incident.
  • Leaving out legal, communications and management roles.
  • Not keeping contact details and escalation paths up to date.
  • Assuming backups work without testing restores.
  • Never reviewing the plan after incidents or changes.

Frequently Asked Questions

What is the difference between an incident response plan and a playbook?

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.

How often should an incident response plan be tested?

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.

Do small businesses need a formal incident response plan?

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.

Conclusion

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.

Where we work: Offensium Vault provides penetration testing for businesses in India, UAE, USA, UK, Australia and clients worldwide, delivered remotely from India.

Free 30-minute consultation

Want an expert view of your security?

Talk to our ISO 27001 certified team about penetration testing, cloud security or compliance. No obligation, and we are happy to sign an NDA.

Book a Free ConsultationExplore our services →
Penetration testing for businesses in India · UAE · USA · UK · Australia and clients worldwide — delivered remotely from Bhubaneswar, India.
Chat on WhatsApp