Other Articles
- Getting Started with the Organization Setup
- How to add employee details step by step?
- Getting Started with Policies
- Getting Started with Trainings
- Getting Started with Vendor Management
- Risk Module – User Help Guide
- Pentest Flow – Adding and Managing Penetration Test Findings
- Controls Module – Step-by-Step User Guide
- Privacy and Data Governance: A Comprehensive Guide for Modern Organizations
- Guide to Hiring Assessment: Referral-Based and Standard Hiring
- Guide to Background Verification: Referral-Based and Standard Hiring
- Employee Performance Review: A Complete Guide
- Succession Planning: How to Prepare Your Business for Key Employee Changes
- Data Breach Communication: What Should You Tell Affected Customers?
- Business Continuity Planning: A Practical Guide for Startups
- Guide to Vendor Risk Assessment and Management
- Guide to Vendor Questionnaire: Assessment and Due Diligence
Incident Response Plan: Steps to Prepare Your Business for Security Incidents
5 November, 2026
When a security incident occurs, does everyone know what to do?
An employee reports a suspicious email. Someone notices unusual login activity on a company account. Or a customer informs the team that their information may have been exposed.
In these situations, the challenge is often knowing who should respond, what needs to happen first, and who should be informed. Without a defined process, employees may take conflicting actions or delay escalation while trying to understand the problem.
An Incident Response Plan helps organizations manage these situations through defined responsibilities and response procedures. It does not prevent every incident, but it helps teams respond in a coordinated and timely manner.
What is an Incident Response Plan?
An Incident Response Plan (IRP) is a documented procedure for identifying, reporting, assessing, containing, and recovering from security incidents.
Incidents may include phishing attacks, compromised accounts, malware infections, unauthorized system access, data exposure, or lost company devices.
The plan establishes how incidents should be handled, who is responsible for taking action, and how affected stakeholders should be informed.
How to prepare an Incident Response Plan
A startup does not need a dedicated security team to establish a basic response process. The following steps provide a practical starting point.
1. Establish incident reporting procedures
Employees should know where to report suspicious activities and whom to contact. Provide a clear reporting channel, such as a dedicated email address or designated incident contact.
Record basic information such as the date and time, reporter's details, affected system or account, and a description of what happened.
Encourage employees to report suspected incidents even when they are unsure whether a security breach has occurred.
2. Assign roles and responsibilities
Identify who will coordinate the response, investigate the incident, approve significant actions, and manage communication.
| Role | Responsibility |
|---|---|
| Incident Coordinator | Coordinates the response and tracks actions. |
| IT / Technical Owner | Investigates, contains, and supports system recovery. |
| Management | Reviews business impact and approves significant decisions. |
| HR / Legal / Privacy Contact | Supports employee communication and assesses applicable notification obligations. |
In smaller organizations, one person may perform multiple responsibilities. Identify alternate contacts for critical roles.
3. Assess and contain the incident
Once an incident is reported, assess its severity based on the affected systems, information involved, potential business impact, and whether unauthorized activity is ongoing.
A simple classification can help prioritize the response.
| Severity | Example | Response priority |
|---|---|---|
| Low | Suspicious email with no evidence of compromise | Investigate and document. |
| Medium | Account compromise or suspected unauthorized access | Prompt investigation and containment. |
| High | Confirmed data breach, ransomware, or widespread system compromise | Immediate escalation and coordinated response. |
After assessment, take appropriate steps to limit further impact. This may include disabling compromised accounts, isolating affected devices, restricting unauthorized access, and preserving relevant logs and evidence.
Record the actions taken, who performed them, and when.
4. Recover systems and manage communication
Once the incident is contained, address the underlying cause before restoring affected systems. This may involve removing malicious software, fixing vulnerabilities, securing accounts, and restoring data from verified backups.
The organization should also determine whether employees, customers, service providers, or regulators need to be informed.
For customer communication, provide accurate information about what happened, the potential impact, actions taken, and any steps customers should consider.
Notification requirements depend on the incident, applicable laws, contractual commitments, and the type of information involved.
For example, CERT-In's Directions dated 28 April 2022 require specified entities to report the cyber incidents listed in Annexure I within six hours of noticing them or being informed of them. Where personal data is involved, organizations should separately assess applicable data protection notification requirements.
Sample Incident Response Plan Template
A documented plan helps employees follow an agreed process instead of making decisions independently during an incident.
Downloadable Incident Response Plan Template (.xlsx)
The template can be used to record incident details, affected systems, severity, response owners, containment and recovery actions, communication, and closure information.
Customize it with your organization's actual contacts, systems, escalation arrangements, and applicable reporting requirements before use. Do not include passwords or access credentials in the incident record.
Review and test the plan
An incident response plan can become outdated as employees, systems, and business processes change. Review it periodically and whenever significant changes or incidents occur.
A practical review process should include:
- Periodic review: Check contact details, responsibilities, and response procedures at defined intervals.
- Tabletop exercises: Discuss a hypothetical incident, such as a compromised administrator account, to understand how the team would respond.
- Action tracking: Record gaps identified during reviews or actual incidents and assign owners and target dates.
- Lessons learned: After an incident, identify what worked, what caused delays, and what needs improvement.
The objective is to ensure that the people responsible can access the plan and carry out the required actions when an incident occurs.
Further reading
- NIST SP 800-61 Rev. 3 — Incident Response Recommendations and Considerations for Cybersecurity Risk Management: Guidance on integrating incident response into cybersecurity risk management.
- CERT-In — Cyber Security Directions: Official Indian directions on cyber incident reporting and related requirements.
- CERT-In — Cyber Incident Reporting: Official resources and guidance for organizations reporting cyber incidents.
Organizations should assess their applicable regulatory, contractual, and internal requirements when preparing and reviewing an incident response plan.