When a cybersecurity incident hits, the difference between a manageable situation and a full-blown crisis usually comes down to one thing: whether your business has a tested incident response plan. Most Nigerian SMEs do not. They handle security incidents ad hoc, making critical decisions under pressure with no framework to guide them. The result is slower containment, greater damage, and higher costs.
An incident response plan does not need to be a 100-page document written by a committee. It needs to be clear, practical, and rehearsed. Here is how to build one that actually works for a Nigerian SME.

What an Incident Response Plan Covers
An incident response plan is a documented set of procedures your business follows when a cybersecurity event occurs. It defines who does what, when they do it, and how decisions are made during an active incident. A well-built incident response plan covers six phases: preparation, identification, containment, eradication, recovery, and lessons learned.
Each phase has specific actions, assigned owners, and decision criteria. The goal of the incident response plan is to eliminate guesswork during the most stressful moments of a security event, so your team can act quickly and consistently.
Phase 1: Preparation
Preparation is everything that happens before an incident. This is where your incident response plan takes shape. Start by establishing an Incident Response Team (IRT) with clear roles. At minimum, you need an Incident Commander who has authority to make decisions during an event, a Technical Lead who coordinates the hands-on investigation and containment, a Communications Lead who manages internal and external messaging, and a Legal/Compliance contact who handles regulatory obligations including NDPA breach notification.
For Nigerian SMEs that do not have dedicated security staff, these roles can be assigned to existing team members with clear escalation paths. The important thing is that everyone named in the incident response plan knows their role before an incident happens.
Preparation also includes maintaining an updated asset inventory, ensuring logging is enabled on critical systems, and establishing relationships with external partners such as forensic investigators and legal counsel. If you wait until an incident to find these partners, you will lose valuable hours.
Phase 2: Identification
The identification phase of your incident response plan defines how your business detects and confirms security incidents. Not every alert is an incident. Your plan should include criteria for classifying events by severity: a failed login attempt is different from a confirmed data exfiltration.
Define your detection sources, including security tools, employee reports, customer complaints, and third-party notifications. Many Nigerian businesses discover breaches through external reports (such as customers finding their data exposed) rather than internal detection. Your incident response plan should account for all these discovery channels.
Phase 3: Containment
Once an incident is confirmed, containment is the immediate priority. Your incident response plan should define short-term and long-term containment strategies. Short-term containment stops the immediate bleeding, for example, isolating an infected workstation from the network. Long-term containment involves applying temporary fixes that allow business operations to continue while the investigation proceeds.
A critical containment decision is whether to take affected systems offline entirely or to keep them running while monitoring attacker activity. Your incident response plan should provide guidance on this decision based on the type and severity of the incident.
Phase 4: Eradication
After containment, the eradication phase removes the root cause of the incident. This might involve removing malware, closing the vulnerability that was exploited, revoking compromised credentials, or rebuilding affected systems from clean images.
Your incident response plan should require that eradication is verified before moving to recovery. Skipping verification is one of the most common mistakes in incident response. Many businesses restore operations only to discover that the attacker still has access through a backdoor that was not fully removed.
Phase 5: Recovery
Recovery restores affected systems to normal operations. Your incident response plan should define the order in which systems are restored (business-critical systems first), how data integrity is verified after restoration, and what monitoring is required during the recovery period to detect any re-compromise.
For businesses subject to the NDPA, the recovery phase also includes fulfilling your regulatory obligations. The NDPC requires breach notification within 72 hours. Your incident response plan should include a notification template and a defined process for determining whether notification is required.
Phase 6: Lessons Learned
The final phase of your incident response plan is often the most neglected. After every incident, conduct a post-incident review within two weeks while the details are fresh. Document what happened, what worked well, what failed, and what changes need to be made to the incident response plan.
This review should result in specific, actionable improvements. Update your incident response plan based on real-world experience, not theoretical assumptions. Over time, this creates a continuously improving security posture.
Testing Your Incident Response Plan
An incident response plan that has never been tested is not reliable. Conduct tabletop exercises at least twice a year where your IRT walks through a realistic scenario and practises their roles. These exercises reveal gaps in the plan, confusion about responsibilities, and communication breakdowns that would be catastrophic during a real event.
QuotientSec helps Nigerian SMEs build, test, and refine incident response plans that are practical, compliant with NDPA requirements, and ready for real-world incidents. Contact us to get started with a plan tailored to your business.
Not sure where your business stands on NDPA compliance?
Take our free NDPA Compliance Scorecard to find out in under 5 minutes. Or read our complete NDPA Compliance Guide for a step-by-step breakdown.
Recovery readiness next step
Find the recovery assumptions that would fail first.
A focused readiness review can map backups, restore paths, incident decisions and the controls needed before downtime becomes expensive.