Ransomware is a business-continuity concern as well as a security concern. CISA describes it as malware used to deny access to devices or data in its device-data guidance. A business needs to consider what work would stop, who would make decisions and which dependencies must be restored.
If your company suspects an incident, use its approved response process and qualified assistance. Plan for outages while you have time to check access, recovery steps and the evidence you will need.
Find the Functions the Business Must Recover
List the work that depends on accessible data and apps. Include customer communications, business records, billing and any deadline-driven activity. Ask the business owner of each function what a prolonged outage would prevent. The purpose is to understand priorities, not to invent a financial loss estimate without evidence.
For each function, find the data, app, identity service and vendor involved. Recovery can require more than a restored document. A staff member also needs an authorized account, a supported device and a working app. Record these dependencies together so leadership can understand why restoring one component may not yet restore the complete business task.
Ask What the Backup Record Actually Proves
A backup inventory should describe the systems and data covered, the responsible admin and the recovery process. A successful job report is useful evidence about that job. It is different from a demonstration that the business data needed for a particular task can be restored and used. Ask the team to explain that distinction.
CISA's StopRansomware Guide addresses prevention, response and recovery, including backup practices. Use it as context for an IT review. Check your own setup rather than assuming that a cloud subscription, synchronization tool or service name sets the required backup coverage. Record gaps as findings with an owner and next action.
Test Restoration with Approved Data
Choose a controlled exercise that answers a specific question. For example, ask the responsible team to restore an approved test record to a separate location and demonstrate the app access needed to use it. Agree on what will be tested, who approved it and what success looks like before you start. Do not use private customer data when a safe test record will answer the question.
Record what was restored, which access was required and which dependencies remained unresolved. A test should make the next decision more concrete. If the recovery process fails, document the observed problem and assign the follow-up. Avoid turning one successful exercise into a claim that every system can be restored within the same time or under every incident condition.
Define Who Coordinates an Incident
Leadership needs a named decision path for an incident affecting business systems. Find the internal contact, IT provider and any specialist resources included in the existing arrangements. Check how the business will contact those people if ordinary email or teamwork is not working. Keep the record accessible through the approved continuity process.
Clarify which party can authorize production changes, external communication and specialist assistance. These tasks should reflect the business's contracts and needs. Do not assume that the IT provider can make every business or legal decision. Ask qualified advisers how your insurance terms and legal requirements apply to an incident.
Make Staff Member Reporting Practical
Staff should know how to report a suspicious message, unusual account behavior or inaccessible data. Explain the channel and useful context. Staff do not need to set the full cause before asking for help. The initial report should help the responsible team assess the situation without spreading needless private files or speculation.
Practice the communication path with an ordinary example. Ask a staff member where they would report the concern and what data they would include. If the answer is unclear, improve the instructions. Avoid making the only reporting route depend on the very app that could be not working. The approved process should account for that needed step and explain the alternative contact method.
Review Access and Supported IT
Use the preparation exercise to find unowned accounts, unsupported devices and unclear vendor limits. The purpose is to set who can investigate and maintain the setup. Admin access and ordinary staff member permissions should follow approved tasks. Ask the IT team to explain the actual setup and unresolved exceptions.
Keep specialist systems separate from assumptions about office IT. Production equipment, clinical devices and vendor-controlled apps may need their own procedures and contacts. Record those needs before introducing a change. Your continuity plan should show which systems depend on others. It should specify which devices IT may reset or restore, and which need approval.
Agree How Work Continues During Recovery
Ask business owners which tasks can be paused, which need an alternative process and which cannot proceed without the supported system. Describe the approved fallback in practical terms. Do not promise a manual or offline method until the responsible people have checked whether it is suitable and usable. Some workflows have dependencies that make a proposed workaround unsuitable.
Communicate who decides when normal work resumes. IT uptime is one factor, but app owners may need to confirm the data and workflow. Record the acceptance process so staff are not receiving conflicting instructions. A tabletop discussion can find gaps without making live production changes. Turn the findings into a short list of decisions and tests that leadership can approve.
Keep the Preparation Current
An office move, app replacement or vendor change can affect recovery. Review the needed step record when those changes occur and update the contacts responsible for decisions. The plan should remain usable by somebody other than the person who originally wrote it. Keep evidence of completed tests separate from capabilities that still need checks.
A 20-minute fit call can identify whether you need a recovery review, help assigning security tasks or regular IT support. Start with the business function and evidence needed to plan its return.
Related Services
Connect This Guidance to Your Business
See how these steps fit your business. Start with managed IT services and security tasks. Our guide for service firms covers access, staff tasks and client work.
Free Checklist for Business Owners
Cyber Insurance Application ChecklistThe security controls insurers ask about, and what to have ready before you apply or renew.
