An incident response plan is insurance against chaos. The cost is not the document itself. It is the decisions you make before an incident, the contacts you verify, the evidence you can preserve and the practice you do when nothing is on fire. A plan that exists only as a PDF in a shared drive will not survive the first hour of a ransomware event.
This guide explains what a useful plan contains, the scope levels that drive cost, a cost model and a 90-day plan to a tested capability. It does not publish a fixed price, because a price without scope is a guess.
What the plan must contain
- Scope and assumptions: which systems, data, sites and suppliers are covered, and what is out of scope.
- Severity matrix: clear examples of low, medium, high and critical incidents, with decision rights.
- Roles: incident commander, technical lead, communications lead, legal and privacy lead, and a deputy for each.
- Contact tree: internal names, suppliers, hosting, payment provider, bank, insurer, legal counsel and regulator, tested quarterly.
- Playbooks: ransomware, business email compromise, data leak, payment fraud, website defacement and lost device.
- Evidence and preservation: what to capture, where to store it and who can access it.
- Containment and recovery: isolation steps, backup restore, credential rotation and return-to-service criteria.
- Communication: holding statements, customer updates, regulator notification and media handling.
- Post-incident review: a blameless review, corrective actions and an owner for each action.
- Testing: a tabletop exercise at least annually, with a record of what changed.
Four scope levels
1. Template and internal workshop
The team fills in a template, agrees roles and contact details and walks through one scenario. This is a reasonable first step for a small business with a simple stack and an internal owner. The cost is mostly internal time.
2. Facilitated plan development
An external facilitator interviews the owners, maps the critical systems and suppliers, drafts the plan and runs one tabletop exercise. The output is a plan with playbooks, a contact tree and an action list.
3. Plan plus readiness and retainer
The provider develops the plan, helps close priority gaps such as logging, backup restore and identity, and provides an on-call retainer for advice or forensic support during an incident. This suits a business where downtime or data loss has a direct revenue impact.
4. Regulated or 24/7 capability
The plan maps to regulatory expectations, includes tested detection and escalation, and is supported by a 24/7 retainer with defined response times and forensic capacity. This fits regulated firms, critical services and strict customer contracts.
The cost model
Build the budget from these lines:
- Discovery and data mapping: systems, data, suppliers, sites and decision-makers.
- Plan development: severity matrix, roles, contact tree and playbooks.
- Technical readiness: logging, endpoint detection, backup restore, identity, network segmentation and evidence storage. These are often separate projects.
- Exercise and training: facilitation, scenario design, participant time and the corrective action plan.
- Retainer or on-call: included hours, response target, escalation and overage rate.
- Forensics and legal: specialist investigation, counsel, notification and customer communication.
- Internal time: the hours your team spends in interviews, exercises and remediation.
The provider's invoice is only one part; internal time and readiness often decide whether the plan works.
What drives cost
- Number of critical systems and sites: one office and an ecommerce stack is different from five branches, a warehouse and a legacy ERP.
- Data sensitivity: payment data, health data and personal data raise the evidence, notification and privacy requirements.
- Regulatory context: Bangladesh Bank guidance for financial institutions, the Personal Data Protection Act, 2026 and customer contracts can add scope.
- Response expectation: business hours advice is different from a 24/7 on-call commitment.
- Existing readiness: if logs, backups and asset records are weak, more work is needed before the plan can be tested.
The Bangladesh context
Bangladesh Bank has issued cybersecurity directives for the financial sector, and the requirements relevant to your licence should be confirmed with the bank or a compliance adviser. The Personal Data Protection Act, 2026 adds privacy obligations for organisations that process personal data. Even unregulated SMEs are increasingly asked for evidence of an incident process, a tested backup and a named security contact.
Payment mix matters too. Cash, cards and mobile financial services create different evidence trails, and an incident may involve the bank, the payment provider and the wallet operator at once. The contact tree should include each, with an account or merchant ID, not just a general support line.
Questions to ask a provider
- What framework or method will you use, and how will the plan fit our business?
- Who will be interviewed, and how many hours are included?
- Will you test the plan with a tabletop exercise, and who must attend?
- What is included in the retainer: advice, forensics, on-site support or all three?
- What is the response time, and how is it measured?
- Who are the subcontracted experts, and how is our data handled?
- What happens after the incident: a report, a review and a remediation plan?
- What is excluded, and what triggers a change order?
- Can we reuse the plan and evidence with another provider?
A 90-day plan
- Days 1-14: appoint an executive sponsor and an incident owner. List critical systems, data, suppliers and sites.
- Days 15-30: agree the severity matrix and decision rights. Draft roles and the contact tree.
- Days 31-45: write playbooks for the top three scenarios. Verify contacts with a test message.
- Days 46-60: run a tabletop exercise. Record gaps and assign owners.
- Days 61-75: fix the highest-priority gaps: backup restore, logging, MFA and supplier contacts.
- Days 76-90: approve the plan, brief staff, schedule the next exercise and set a review date.
Metrics
Track the time to detect, the time to contain, the percentage of critical contacts verified, backup restore success, the number of exercise actions closed, the share of staff trained and the coverage of playbooks for the top scenarios. Measure retainer response time against the agreement. Review the numbers after every exercise, not only after an incident.
A simple calculator
Estimate the first-year cost as: plan development days multiplied by a blended day rate, plus the number of exercises multiplied by the exercise cost, plus the annual retainer, plus the readiness projects, plus internal hours multiplied by an internal cost rate. Keep the assumptions in a spreadsheet and update them when the scope changes. The output is a range, not a promise.
Where this fits in our work
If you need help scoping a plan, running an exercise or setting up an on-call arrangement, start with Managed Technology & Cybersecurity and review the engagement options on our pricing page. For the year-by-year view, read the SME incident response planning guide.
Sources
- NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management, accessed 17 November 2026.
- NIST, "Cybersecurity Framework 2.0", accessed 17 November 2026.
- The Daily Star, "BB issues 17-point cybersecurity directive amid rising threats", accessed 17 November 2026.
- IBM, "Cost of a Data Breach Report", accessed 17 November 2026.
- DataGuidance, "Bangladesh" data protection overview, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.