Ransomware response planning for small business

Prepare people, contacts, recovery priorities, and decision owners before a ransomware incident. Use the plan with your IT and incident response advisers.

Start with who decides and who to call

A useful ransomware response plan tells your staff who to contact, how to communicate if email is unavailable, and who can authorize containment and recovery. Write those decisions down before an incident. A list of security products does not answer them.

If you suspect an incident now, contact your designated IT or incident response team through a trusted channel. Follow the response procedure agreed for your systems. Do not wait for a scheduled assessment or use this planning article as a substitute for incident handling.

This guide helps Northern Virginia business owners prepare the people and decisions behind a response. It focuses on coordination rather than another prevention checklist.

Plan for more than unavailable files

A response may need to address disrupted operations, compromised accounts, and possible exposure of information. Restoring a file does not settle all three questions. Keep technical recovery and the investigation of what happened as separate workstreams with named owners.

The joint StopRansomware guide hosted by the FBI covers both ransomware and data extortion. Its response checklist emphasizes coordinated isolation, evidence preservation, and communication outside potentially compromised systems. Your technical responders should adapt those steps to your environment.

Create a contact sheet you can reach without email

Record a primary and alternate contact for each role. Keep an approved offline copy where authorized staff can find it. Confirm that contact details still work when people or providers change.

  • Business decision owner: Can approve a temporary shutdown, spending, and a change to normal operations.
  • Technical response lead: Coordinates investigation, containment, evidence handling, and recovery work.
  • Insurance contact: Explains the reporting process and any applicable requirements for engaging response providers.
  • Legal adviser: Evaluates notification and other obligations based on the incident's facts.
  • Staff and customer communication owner: Publishes approved updates and keeps messages consistent.
  • Critical application contacts: Provide the support routes for the systems needed to reopen.

Do not store passwords, recovery codes, or customer records in the contact sheet. Decide how authorized responders obtain necessary access through your approved process.

Agree on the decisions before the incident

Use this worksheet in a discussion with your provider. Replace role names with the people responsible in your business. Record the alternate when the primary person is unavailable.

DecisionQuestion to settleOwner to name
EscalateWho receives a suspicious activity report, and how does the employee reach them if email is unavailable?Technical lead
ContainWho can authorize isolation that interrupts a shared business service?Technical lead and business owner
InformWho approves staff, customer, insurer, and external updates?Communication owner and relevant advisers
ResumeWhat evidence and business checks are required before a service returns to use?Technical lead and service owner

Give staff a simple reporting prompt: what they observed, when it started, which device or application was involved, and who is affected. Avoid asking employees to investigate, delete suspicious files, or forward sensitive material through unapproved channels.

Put business tasks in recovery order

List the work that must resume first, such as receiving calls, finding an appointment, or fulfilling an order. For each task, name the application, account, device, data, and outside provider it depends on. Ask the task owner what a usable restored service looks like.

Document the backup coverage and the evidence from a relevant restore test with your technical team. A successful backup notification alone does not demonstrate that the business task can resume. Decide which temporary manual process is acceptable and how staff will reconcile records afterward.

For a business with offices in Reston and McLean, a shared sign-in system or application may affect both locations. In your plan, record actual dependencies and site contacts rather than assuming one office can take over for another. This is a planning example, not a UX Genius client result.

Clarify what your support agreement covers

Ask whether your existing agreement includes incident triage, specialist investigation, evidence collection, restoration, and communication support. Identify work requiring a separate provider or approval. Confirm coverage hours, escalation routes, access responsibilities, and how costs are authorized.

Managed IT support, cybersecurity services, and backup and recovery planning can contribute to the plan. None removes every risk or guarantees a recovery time. Keep the agreed scope accessible with the contact sheet.

Practice a scenario without disrupting systems

Run a discussion exercise with the business owner, office manager, and technical lead. Use a hypothetical prompt: staff cannot open a shared folder and one device displays an unfamiliar demand. Do not simulate malware or disconnect production systems for this exercise.

  1. Ask a staff representative how they would report the problem without using company email.
  2. Have the decision owner locate the response contacts and authorization rules.
  3. Ask the technical lead what information is needed before making containment decisions.
  4. Choose the first business task to restore and describe the checks needed before reopening it.
  5. Record missing contacts, unclear authority, and untested assumptions. Assign each gap an owner and review date.

The result should be a short action list. Passing a discussion exercise does not prove that a real recovery will succeed.

Discuss your local support and response plan

UX Genius is based at 11890 Sunrise Valley Dr Ste 540, Reston, VA 20191 and is available 24/7. We serve Reston, McLean, Fairfax, and Falls Church, along with other confirmed service areas. Include the full address, suite, building contact, and access requirements when planning onsite work.

Book a free 30-minute assessment to discuss your response planning. It is a conversation with no obligation. We will contact you to arrange a time and identify a suitable next step. Technical investigation, testing, and implementation are scoped separately. Call (703) 755-0014 to discuss your support needs.

Frequently asked questions

Should employees switch off an affected computer?

Agree on an employee procedure with your responders in advance. The StopRansomware guide prioritizes isolating affected systems and reserves powering down for situations where disconnection is not possible, because shutdown can destroy volatile evidence. Containment decisions need to account for your environment and safety.

Does paying a ransom guarantee recovery?

No. The FBI's ransomware guidance says it does not support ransom payment and that payment does not guarantee data recovery. It also provides an incident reporting route. Involve your response team and relevant advisers rather than letting an employee engage an attacker independently.

How long does recovery take?

There is no reliable generic timeline. The affected systems, investigation, account security, available recovery data, and validation work all matter. Ask your team to distinguish a tested recovery objective from an estimate during an incident.

How often should we review the plan?

Set a review schedule with your team and revisit it when providers, key staff, applications, offices, or recovery arrangements change. Use exercise findings and actual incidents to improve it.

Source documents and current details

Use the original guidance when a policy, product, or contract detail matters to your decision.

Explore the service
Cybersecurity

Put the guide to work

What is already clear?
What needs a conversation?

Mark the things you know. Bring the open questions to your team or to us. This is a planning aid, not a security or compliance score.

0 of 4 things are clear

Anything left unchecked is a useful question to bring to the conversation.

Review my security priorities

30-minute conversation. No obligation.

We’ll contact you to arrange a time. Based in Reston.

Keep the useful
questions coming.

Explore every guide