About Us Solutions
Managed IT SupportCybersecurityRegulatoryProfessional ServicesCo-ManagedCMMC ComplianceData BackupCloud MigrationIT ConsultingAI ConsultingMicrosoft 365Microsoft CopilotSD-WAN Services
Industries
Accounting & CPA FirmsManufacturing & DefenseProfessional Services
Process Testimonials Resources Careers
Contact UsBook a Call
Case study · 7 min read

Ransomware recovery in Minneapolis: how an accounting firm contained an attack in 22 minutes

An accounting firm was hit on a Friday evening in tax season, the hour attackers love most. Because managed backups, XDR and a 24/7 security operations center were in place, the attack was over in 22 minutes and Monday looked like any other Monday. Here is the timeline, and what it means for your firm.

Defeated a ransomware attack with zero data loss, and zero ransom paid cover
Download the PDF →Free · PDF · no form
Jump to a section
  1. Friday at 6:41 p.m.
  2. The 22 minute timeline
  3. Why it was different
  4. The results
  5. Lessons for your firm
  6. What to do next
  7. Questions people ask
The short version
  • Attackers detonate on Friday nights and in tax season on purpose. Maximum pressure to pay, minimum people watching the console.
  • Behavior based XDR isolated the laptop in two minutes and a human analyst was engaged in eight. The 22 minutes were preparation, not luck.
  • Immutable backups meant the encrypted folders rolled back from a snapshot nobody could touch. Restore took one afternoon, not three weeks.
  • No ransom, no client notifications, no insurance claim. The incident report became proof of a working program at renewal.

Friday at 6:41 p.m., somebody clicked

Every accounting firm in the Twin Cities has the same soft spot: a senior associate, an inbox full of client documents and a deadline. Ransomware crews know it, which is why they time detonations for nights and weekends, when internal IT has gone home and nobody is watching the console. A Friday evening in tax season is the perfect window, with maximum pressure to pay and minimum people on hand. Ransomware recovery in Minneapolis is usually a story about Monday morning phone calls. This one is about a Friday night phone call that said it was already over.

22 minfrom first alert to confirmed containment
$0ransom paid, no negotiation needed
100%of data recovered, nothing leaked

The firm, a 42 user accounting and advisory practice with one office and hybrid staff, had engaged Solution Builders eighteen months earlier for managed security after a cyber insurance renewal demanded multifactor authentication, endpoint detection and tested backups. Those controls were about to earn their keep.

  • Entry point. A phishing email with a weaponized invoice attachment that looked like it came from a long time client.
  • Target. The file server and the client document library.
  • Controls in place. MFA, managed XDR, a 24/7 MDR team and an immutable backup.
  • Insurance. A policy renewed on the strength of those controls.
Page 2 of the case study: the setup, the first hour timeline and what the attackers expected versus what they got.
Page 2 of the case study: the setup, the first hour timeline and what the attackers expected versus what they got.

The 22 minute timeline, minute by minute

The attachment installed a loader designed to hand control to a ransomware crew. In a firm with no monitoring, the next sound would have been Monday morning phone calls. Here, the next sound was an alert.

  1. 6:41 p.m., loader executesThe attachment runs a script that tries to disable antivirus and reach out to a command server.
  2. 6:43 p.m., XDR flags behaviorProcess behavior, not a known signature, trips a high severity alert. The device is automatically isolated from the network.
  3. 6:49 p.m., analyst engagesA security operations center analyst confirms the pattern, revokes the user's sessions, resets credentials and hunts for lateral movement.
  4. 7:03 p.m., containedNo other device touched. An encryption attempt on two shared folders stopped at 1.4 percent. Firm leadership briefed by phone.
  5. Saturday, restored and verifiedAffected folders rolled back from the immutable snapshot, the device rebuilt, mailbox rules checked, incident report delivered.
What the attackers expected versus what they got

Preparation, not luck

They expected an empty office, a flat network and backups they could delete first. They got an isolated laptop, a live analyst and a backup copy nobody could touch. The 22 minutes were the product of eighteen months of preparation.

Managed detection and response: why this story ended differently

Coveware and Sophos reporting commonly puts downtime from an SMB ransomware incident at about three weeks. This firm lost half a day, on a weekend. The difference was not one product. It was five controls that had been installed, tested and watched for a year and a half before anyone needed them.

ControlRole in the incidentWithout it
Managed XDRDetected behavior in 2 minutes, isolated the device automaticallyLoader runs all weekend
24/7 MDR SOCA human analyst engaged within 8 minutes on a Friday nightAlert sits in an inbox until Monday
Immutable backupSnapshot could not be encrypted or deleted, restore took one afternoonBackups deleted first, ransom is the only option
MFA and conditional accessStolen credentials could not be reused from outsideAttacker logs in as the associate
Email protectionBlocked the attacker's follow up messages to other staffSecond and third victims

Two of those rows deserve a closer look. Managed detection and response is the human half of XDR: the platform raises the alert, and a person in a 24/7 security operations center with authority to act decides what to do in the next five minutes. And immutable backups are the reason the ransom question never came up. Sophos has reported that attackers try to compromise backups in the large majority of ransomware cases, so a backup that cannot be altered or deleted, even by an administrator, is the control that turns a crisis into a restore job.

Page 3 of the case study: the results, the three week versus half a day comparison and the five controls that changed the outcome.
Page 3 of the case study: the results, the three week versus half a day comparison and the five controls that changed the outcome.

Monday looked like any other Monday

Partners spent Friday night worrying about client data and about paying a ransom in the middle of tax season. By Saturday afternoon both worries were gone. The firm filed no insurance claim, kept its premium and used the incident report at renewal as proof of a working program.

1.4%of one shared folder encrypted before isolation
0client notifications required
0.5days of disruption, versus about three weeks for a typical SMB eventCoveware and Sophos reporting
18months since the security program began
I got a phone call at 7 p.m. telling me we had been attacked and that it was already over. I did not know that was possible.Managing Partner, Solution Builders accounting firm client

Zero client notifications is the number the partners remember. Nothing left the building, so there was no breach to disclose, no letters to write and no awkward conversation with the firm's largest clients in the busiest month of the year.

What every Twin Cities accounting firm should copy

Firms with 25 to 500 people in Minneapolis and St. Paul hold exactly what attackers want: tax returns, bank details and the trust of every client. The lessons from this incident are not exotic, and most of them start with a cyber insurance questionnaire.

  • Treat the insurance checklist as the floor. MFA, endpoint detection and tested backups are the minimum. This firm started there and kept going.
  • Buy the human, not just the tool. XDR raised the alert. An analyst contained it. Ask any provider who is watching at 6:49 p.m. on a Friday.
  • Make backups untouchable. Immutable snapshots with quarterly restore tests, so recovery is a procedure, not a prayer.
  • Plan for tax season. Attackers time attacks to your busiest weeks. Your controls have to work when nobody is in the office.
The typical firm

Finds out Monday

  • Antivirus with nobody watching
  • Backups on the same network, deleted first
  • Three weeks of disruption and a ransom decision
The prepared firm

Finds out at 6:43 p.m.

  • Behavior based XDR with a 24/7 analyst
  • Immutable backup nobody can touch
  • Half a day, no ransom, no notifications

Solution Builders runs this program for accounting firms across the Twin Cities on the RISE framework: resilient recovery, integrated controls, 24/7 security and quarterly reviews that add new controls as attackers change tactics.

Page 4 of the case study: why it worked, mapped to the RISE framework, and three ways to start with Solution Builders.
Page 4 of the case study: why it worked, mapped to the RISE framework, and three ways to start with Solution Builders.

Ransomware recovery in Minneapolis starts before your own Friday night

Six things to check this week. If any answer is no, that is the gap an attacker will find first.

  • Multifactor authentication is enforced on every account, including email and remote access.
  • Every laptop and server runs behavior based detection, not just signature antivirus.
  • A named human team watches those alerts 24/7 and has written authority to isolate a device.
  • Backups are immutable and off network, and a restore was tested in the last quarter.
  • Conditional access blocks sign ins from places your staff never are.
  • You have a free 30 minute Security Readiness Snapshot on the calendar with Solution Builders.

Solution Builders has protected Minnesota professional services firms since 1995 from Bloomington, with 50+ engineers, a SOC 2 Type II audited practice and a 24/7 security operations center that handled this incident. The snapshot is a candid conversation about your firm, your controls and the gaps an attacker would find first, whether or not you ever work with us.

Ransomware protection for Twin Cities professional services firms

Solution Builders protects accounting, legal and advisory firms with 25 to 500 people across Minneapolis, St. Paul and the metro from Bloomington. The client in this story is anonymized at its request. Its controls, its 24/7 response team and its immutable backups are the same program we run for every professional services client. Related services: Cybersecurity, Data Backup and Disaster Recovery, Microsoft 365. Contact us or book a 30 minute call.

Free download

Get the full incident case study

Four pages to share with your partners: the complete first hour timeline, the five controls and their role in the incident, the three week versus half a day comparison and the insurance angle.

  • The first hour, minute by minute
  • Five controls and what each one did
  • Typical event versus this firm, in days
  • The insurance and renewal outcome

No form, no gate. Share it with your leadership team.

Defeated a ransomware attack with zero data loss, and zero ransom paid preview
FAQ

Questions Twin Cities leaders ask about ransomware recovery.

Minutes, when the pieces are in place. In this case behavior based XDR isolated the laptop two minutes after the loader ran, a security operations center analyst was engaged within eight minutes, and containment was confirmed at 22 minutes with 1.4 percent of one shared folder encrypted. Without a human watching on a Friday night, the same attack typically runs all weekend and surfaces as Monday morning phone calls.
It depends entirely on what was in place before the attack. A firm with managed XDR, a 24/7 response team and immutable backups contains the attack in minutes and restores from a snapshot in an afternoon, with no ransom and often no breach notification. A firm with antivirus and network attached backups faces about three weeks of disruption and a ransom decision. Solution Builders provides the first kind from Bloomington for firms across the Twin Cities.
An immutable backup is a copy that cannot be altered or deleted for a set period, even by an administrator with stolen credentials. Attackers try to find and destroy backups before they encrypt, so a normal backup on the network often disappears first. An immutable snapshot survives, which is why this firm restored two shared folders in one afternoon and never had to consider paying.
Most carriers now require multifactor authentication on email and remote access, endpoint detection and response, tested and separated backups, and some form of security awareness training before they will renew. This firm started its program because of that questionnaire. Eighteen months later the same controls contained a live attack, and the incident report served as proof of a working program at the next renewal.