A ransomware incident is rarely a single event. It usually starts with a stolen credential, a malicious attachment or an unpatched internet-facing service, then spreads through shared drives and backup systems. For a small business in Bangladesh, the recovery cost is not only the ransom demand, which should never be treated as a budget line. The larger costs are downtime, lost orders, staff time, data reconstruction and the loss of customer trust.
That is why ransomware preparedness should be bought as a set of capabilities, not as a single product. This guide explains what drives cost, how to scope the work, and what to ask before you sign anything.
What preparedness actually covers
A credible programme has four layers. Many programmes buy prevention and skip recovery, which is the expensive mistake.
- Prevent: patching, multi-factor authentication, least privilege, endpoint protection, email filtering and secure remote access.
- Detect: central logging and alerting on unusual logins, privilege changes, mass file changes and backup deletion attempts.
- Contain: network segmentation, an isolation procedure, restrictions on macros and scripts, and a clear decision-maker.
- Recover: tested backups with at least one offline or immutable copy, a restore runbook, and a communication plan for customers and staff.
Prevention without recovery is a hope, not a plan. A backup that has never been restored is a file collection, not a capability.
Four questions that set the scope
- How many identities, endpoints and servers? Cost follows counts, not company age or headcount alone.
- Which systems would stop the business? An order system, a payment gateway integration and a warehouse system carry different recovery priorities.
- What recovery time and recovery point can the business tolerate? A few hours of lost orders is different from a few days.
- Who decides during an incident? If the answer is unclear, part of the budget should go into defining authority, not into another tool.
These answers change the price more than any vendor's rate card. A quote that does not ask them is a template with a logo.
The cost model
Build the budget from seven lines. Ask every provider to price against the same lines so you can compare.
- Assessment and scoping: interviews, asset inventory, identity review, backup review and a written gap list.
- Identity and access: MFA rollout, password manager or SSO, admin account separation and removal of stale accounts.
- Endpoint and email: endpoint detection and response, email filtering, patch management and device encryption.
- Backup and recovery: additional backup capacity, immutable or offline copies, restore testing and documentation.
- Detection and response: log collection, alert rules, monitoring hours and an escalation retainer.
- Playbook, training and exercises: a one-page incident plan, a tabletop exercise and short staff awareness sessions.
- Internal time: the hours your team spends gathering evidence, testing restores and attending exercises.
Internal time is the hidden line. A project that ignores it will look cheaper on paper and cost more in delivery.
A simple scoping calculator
You do not need a proprietary calculator to compare quotes. Use a scope score based on observable counts:
scope score = identities + endpoints + (servers x 2) + (sites x 3) + (critical applications x 2) + (backup sets x 2)
Separately, rate each of the four layers from 0 to 3, where 0 means "nothing in place", 1 means "informal", 2 means "documented but untested" and 3 means "tested and owned". The gap between the current score and the target score is the work. This gives you a defensible basis for comparison without pretending that a single number is a price.
What changes the cost most
- Number of sites: each branch adds network, device and response complexity.
- Legacy systems: unsupported operating systems and custom applications need compensating controls.
- Regulatory exposure: financial services, healthcare and education carry more evidence and privacy requirements.
- Recovery ambition: a four-hour recovery target costs more than a two-day target because it requires redundancy, testing and standby capacity.
- Monitoring model: business-hours alerting is cheaper than around-the-clock response, but it leaves a gap you must accept explicitly.
- Internal capability: a team with a sysadmin and a documented change process needs less hand-holding than a team with no dedicated IT staff.
In Bangladesh, financial institutions work under Bangladesh Bank cybersecurity directives, and businesses handling personal data need to account for the Personal Data Protection Act, 2026. Even where an SME is not directly regulated, customer due-diligence questionnaires often ask for the same evidence.
Where SMEs overspend and underspend
Overspending usually happens in three places: buying an enterprise platform nobody will administer, paying for a penetration test before fixing basic access control, and purchasing cyber insurance without reading the control requirements in the policy. Underspending usually happens in backup testing, identity hygiene and incident decision-making.
A useful rule is to fix the boring controls first. MFA on email and admin accounts, a tested restore, a patch routine and a leavers checklist reduce more real risk than a glossy dashboard that nobody reads.
Questions to ask a provider
- What exactly is in scope, and what is explicitly excluded?
- Will you test a restore, or only confirm that a backup job ran?
- Which alerts will you monitor, during which hours, and what is the response time?
- Who writes the incident playbook, and will you run an exercise with our team?
- What happens when we leave? Do we keep the documentation, configurations and evidence?
- How do you measure success in 90 days?
- Can you provide references from a business with a similar stack, without naming clients publicly?
A 90-day plan
- Days 1-10: inventory identities, devices, servers and backup jobs. Confirm the business-critical systems and the recovery targets.
- Days 11-25: close access gaps: MFA on email and admin accounts, remove stale users, separate admin accounts.
- Days 26-45: fix the backup: add an offline or immutable copy, run a restore test and record the result.
- Days 46-60: establish patching and alert review routines with named owners.
- Days 61-75: write a two-page incident playbook and run a tabletop exercise.
- Days 76-90: review metrics, document gaps and set the next quarter's plan.
Metrics that show progress
- Percentage of staff and admin accounts protected by MFA.
- Time from patch release to deployment on internet-facing systems.
- Percentage of critical data covered by a restore test in the last quarter.
- Number of stale or orphaned accounts removed.
- Time to detect and time to isolate a simulated incident.
- Percentage of staff who completed awareness training.
Where this fits in our work
If you need help scoping the work, start with Managed Technology & Cybersecurity. Our pricing page explains how we structure scope and retainers. For the recovery side, read what backup and disaster recovery testing actually involves.
Sources
- NIST Cybersecurity Framework 2.0, accessed 17 November 2026.
- NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management, accessed 17 November 2026.
- CISA StopRansomware, accessed 17 November 2026.
- IBM, Cost of a Data Breach Report 2026, accessed 17 November 2026.
- The Daily Star, "BB issues 17-point cybersecurity directive amid rising threats", 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 *.