Blue Tree Technology®

Malware, ransomware, backup & recovery

Ransomware: What Should the Business Do First?

Published · Last reviewed · Next review due:

Start the incident-response process immediately. Employees should contact the designated IT/security or incident-reporting contact through a trusted channel. The authorized incident lead should coordinate technical response, notify the cyber insurer through the policy's required process, and involve appropriate legal counsel promptly. These workstreams may need to happen in parallel.

There is no universal "lawyer first, insurer second, MSP third" sequence. Your response plan should identify the contacts and authority before an event. During an incident, follow applicable policy and legal requirements without postponing urgent containment while waiting for a coverage decision. CISA and the FTC emphasize coordinated response, limiting further damage, and preserving evidence. [1, 2]

Who handles which call?

ContactWhat they help doWhat not to assume
IT/security responder or MSPAssess, contain, preserve technical evidence, and coordinate recovery within their scope.Ordinary help-desk coverage includes specialist forensics or every incident expense.
Insurer's designated incident channelRecord notice and explain the policy process, required consent, and approved responders.Telling the MSP or broker automatically completes the insurer's notice requirements.
Appropriate breach/privacy counselAdvise on legal duties, notifications, evidence handling, and legal coordination.Calling any lawyer makes every communication privileged or every cost covered.
Business incident leaderAuthorize priorities and spending, coordinate people, and keep decisions recorded.A technician should decide every legal, financial, or customer-facing question.

An insurer may provide access to breach counsel and specialist responders. Travelers describes how a breach coach can help coordinate legal and incident-response questions. The actual engagement and payment arrangements still depend on your policy and circumstances. [3]

Read the policy's incident instructions, not just the limits page

Keep a protected copy accessible without company email. Have the licensed adviser explain what events trigger notice, the required contact method and timing, who may submit notice, and what information is initially needed.

Check whether specified costs or outside providers need prior consent, whether a responder panel applies, and how emergency mitigation is handled. Record the notice, claim or incident reference, contact name, instructions, and approvals. Do not assume a broker message, a voicemail, or a provider's invoice proves the required process was completed. Ask the insurer to confirm receipt.

These are policy questions to resolve, not universal conditions in every insurance contract. Coverage, retentions, exclusions, and payment decisions depend on the actual terms and facts. [4]

Do not let unanswered coverage questions become continued damage

Use the approved emergency route rather than waiting in a routine ticket queue. If email, identity, or the MSP's usual access may be compromised, use a known independent contact route. Ask whether the provider can safely respond or needs an independent incident specialist.

Follow the incident lead's containment instructions. CISA prioritizes isolating affected systems and preserving evidence. Avoid independent wiping, cleanup, repeated reboots, or restoring over affected systems. Do not negotiate with attackers, promise payment, or authorize unfamiliar remote access on your own. [1]

Give the responders facts, not a diagnosis you cannot support

Report when the problem was noticed, which business work is affected, visible messages, known changes, and actions already taken. Clearly separate observations from assumptions. Preserve relevant evidence through the approved process; do not circulate sensitive files or credentials to a large email group.

Assign someone to maintain the decision log and the next update time. Counsel and the incident lead should coordinate any required notices to customers, regulators, or law enforcement; contacting the insurer does not discharge every other reporting duty. [2]

Recovery starts with priorities and verification

Identify essential work, trustworthy recovery points, required identities, and supplier dependencies. Technical responders should establish an appropriate recovery path before reconnecting restored systems. A backup notification alone cannot tell you when the business will be operational.

Before an incident, ask Blue Tree Technology® and your insurance adviser to map who receives the first report, who makes the parallel calls, and who may authorize each action. Rehearse those decisions in a tabletop exercise and test restoration separately.

General education, not legal or insurance advice. During an actual event, use your established response plan and qualified responders.

Sources and further reading

[1] CISA and partner agencies: #StopRansomware Guide

[2] FTC: Data Breach Response - A Guide for Business

[3] Travelers: What Is a Cyber Breach Coach?

[4] FTC: Cyber Insurance - small-business guidance

Back to the Knowledge Hub

More in this topic

Discuss your business technology needs

Review your priorities with Blue Tree Technology®.

Schedule a discovery call