Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Cybersecurity & Risk 6 min read

Ransomware preparedness for small businesses: a working checklist

A practical ransomware checklist for Bangladeshi SMEs, with named owners, evidence, review frequency and sign-off for each control.

E
EncryptTechBD · 0 comments
Engineer working with fibre optic cables
Photo: Field Engineer / StockSnap

Most small businesses do not need a sixty-page security policy. They need a short list of controls that someone can prove is working. Ransomware preparedness works the same way: not “do we have antivirus?” but “if the file server is encrypted at nine tomorrow, who acts, in what order, and what proves the backups restore?”

This checklist is a working document for a Bangladeshi SME. It covers the controls that change the outcome of an incident, the evidence each should produce, and the review rhythm that stops the document becoming shelfware.

How to use the checklist

Copy the sections into a spreadsheet with seven columns: item, owner, evidence, frequency, last checked, exception and sign-off. Use three states only: in place and tested, in place but untested, or missing. “Partially done” hides the gap that needs funding.

The business owner signs the summary; the technical lead signs the evidence. Review access and backup items monthly, the full list quarterly, and the incident exercise annually. Keep a printed copy with the offline recovery pack.

Identity and access

Stolen credentials are a common starting point for intrusion. These controls reduce the value of a password and limit how far one account can travel.

  • Multi-factor authentication on email, banking, remote access and every admin console. Owner: IT lead. Evidence: enrolment report showing coverage. Frequency: monthly. Sign-off: business owner.
  • Separate administrative accounts from daily email and browsing accounts. Owner: IT lead. Evidence: role list naming each privileged account holder. Frequency: quarterly. Sign-off: technical lead.
  • Remove leaver and contractor accounts within one working day. Owner: HR and IT. Evidence: exit ticket with the date access ended. Frequency: per departure. Sign-off: department head.
  • Retire shared passwords and local administrator rights on staff laptops. Owner: IT lead. Evidence: vault report and local admin group export. Frequency: quarterly. Sign-off: technical lead.
  • Keep a break-glass account with credentials stored offline. Owner: IT lead. Evidence: sealed envelope register and a tested sign-in record. Frequency: annual test. Sign-off: business owner.

Endpoint, email and remote access

An endpoint tool that covers half the estate is a subscription, not a control. Count coverage by device, including the owner's laptop and the machine that runs the accounts package.

  • Endpoint detection and response on every server, laptop and branch device. Owner: IT lead. Evidence: coverage report reconciled against the asset register. Frequency: monthly. Sign-off: technical lead.
  • Patch internet-facing services, operating systems and browsers on a written schedule. Owner: infrastructure lead. Evidence: patch report listing exceptions and expiry dates. Frequency: monthly. Sign-off: technical lead.
  • Filter email and publish SPF, DKIM and DMARC records. Owner: IT lead. Evidence: DNS records and a rejected-message sample. Frequency: quarterly. Sign-off: technical lead.
  • Block internet macros and restrict script execution for ordinary users. Owner: IT lead. Evidence: policy export and an attempted-test result. Frequency: quarterly. Sign-off: technical lead.
  • Reach remote systems through a managed access service with MFA, never an open remote desktop port. Owner: infrastructure lead. Evidence: external scan and access logs. Frequency: monthly. Sign-off: technical lead.

Backups that survive an attack

Ransomware operators often target backups before they encrypt production. A backup that shares credentials or network access with the systems it protects is within reach of the same attacker.

  • Keep three copies, on two media, with one offline or immutable, and use backup credentials separate from domain administration. Owner: infrastructure lead. Evidence: repository configuration, storage list and IAM export. Frequency: quarterly. Sign-off: technical lead.
  • Restore a real business transaction, not just a folder, and confirm the recovery key is available. Owner: operations lead. Evidence: restore log with timestamps, row counts and a reconciliation note. Frequency: quarterly. Sign-off: business owner.
  • Set retention from the time corruption could go unnoticed, not from storage convenience. Owner: business owner and IT. Evidence: written retention decision with the reason. Frequency: annual. Sign-off: business owner.
  • Alert on failed jobs, mass deletion and backup policy changes. Owner: infrastructure lead. Evidence: alert rule list and a test alert. Frequency: monthly. Sign-off: technical lead.
  • Protect the encryption keys and backup catalogue separately from the data. Owner: IT lead. Evidence: key custodian record and recovery test. Frequency: annual. Sign-off: business owner.

Detection, containment and the first hour

The first hour decides whether a small incident becomes a business interruption. Write the sequence before you need it, and give one person authority to disconnect systems.

  • Centralise authentication, endpoint and file-server logs for the agreed retention period. Owner: IT lead. Evidence: log source inventory and a sample search. Frequency: monthly. Sign-off: technical lead.
  • Alert on new privileged accounts, unusual login locations, mass file renames and backup deletion. Owner: IT lead. Evidence: alert rules mapped to a named responder. Frequency: quarterly. Sign-off: technical lead.
  • Segment finance, servers, point-of-sale devices and guest Wi-Fi from one another. Owner: infrastructure lead. Evidence: network diagram and firewall rule review. Frequency: annual. Sign-off: business owner.
  • Document the isolation steps and test them in an exercise. Owner: IT lead. Evidence: one-page runbook with the test date. Frequency: annual. Sign-off: business owner.
  • Keep an offline contact list for the bank, insurer, lawyer, regulator and incident responder. Owner: operations lead. Evidence: printed list with confirmed numbers. Frequency: quarterly. Sign-off: business owner.

People, communications and third parties

Staff usually see the first sign: a file that will not open, a request to approve a payment, a login alert. Make reporting easy and make the response visible.

  • Run a tabletop exercise with the decision-makers, not only the IT team. Owner: business owner. Evidence: scenario, attendance list and five dated corrective actions. Frequency: annual. Sign-off: business owner.
  • Give every employee a reporting route for suspicious messages and a no-blame response. Owner: HR and IT. Evidence: intranet notice and a test report. Frequency: annual. Sign-off: business owner.
  • Prepare customer, supplier and staff messages that can be sent without the email system. Owner: communications lead. Evidence: templates stored offline. Frequency: annual. Sign-off: business owner.
  • List every vendor with remote access, its purpose, owner and contract notification terms. Owner: procurement. Evidence: register reviewed against active accounts. Frequency: quarterly. Sign-off: business owner.
  • Review cyber insurance with a broker and record the exclusions. Owner: finance lead. Evidence: policy summary and exclusions note. Frequency: annual. Sign-off: business owner.

Exceptions, evidence and sign-off

An exception is not a failure. An unrecorded exception is. Every gap should have a risk owner, a compensating control, a completion date and an expiry date.

At the quarterly review, check failed backups, patch exceptions, MFA gaps and stale vendor access. Annually, repeat the restore test, re-run the tabletop and confirm that the contact list reaches a person. Keep signed summaries so a manager, insurer or auditor can see what was tested.

The strongest programme is not the one with the most tools. It is the one where a named person can show, with evidence, that access is controlled, backups restore and the first hour has an owner. Our managed technology team can review the checklist, and the pricing page explains how work is scoped. For the budget side, read the ransomware preparedness cost guide.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes