First hour: stop the spread
If you're reading this mid-attack, do these things in this order.
Unplug the affected machines from the network. Pull the ethernet cable and turn off Wi-Fi. Don't shut them down unless you have to, because memory can hold evidence an investigator will want.
Then disconnect backups. Ransomware crews go after them first.
Don't wipe anything. Don't reboot every server out of habit. And don't try to negotiate from the ransom note's chat link yet.
Photograph the ransom note with your phone. Write down the time you noticed, what staff saw, and which systems act strangely.
Why Myrtle Beach businesses get hit
The Grand Strand runs on small and mid-sized operations: hotels, restaurants, golf courses, medical and dental offices, property managers, law firms, marinas. Most have one part-time IT person or an outside vendor who handles everything from Wi-Fi to the point-of-sale system.
That setup is efficient, and it's exactly what attackers look for. Reservation systems, guest data and card payments sit on the same flat network. Seasonal staff get temporary logins that never get removed. Summer is the worst time to be down, and attackers know it.
I can't give you a local attack count because I don't have a source I can name. The pattern is simple, though. Businesses that can't afford a week offline are the ones most likely to be pressured into paying.
What recovery actually involves
Recovery isn't one task. It's five, and they overlap.
- Containment. Find which machines are infected and cut off the attacker's access.
- Investigation. Work out how they got in, usually a stolen password, an unpatched VPN or firewall, or a phishing email.
- Eradication. Remove the attacker's footholds. If you skip this, you restore everything and get hit again.
- Restoration. Rebuild systems and bring back data from clean backups.
- Notification and reporting. Tell the people the law says you must tell.
Step three is the one small businesses skip, and it's the one that causes repeat incidents.
Realistic timelines and costs
These are rules of thumb from how incident response usually goes, not measured figures.
- A small office with good backups: 2 to 5 days to be working again.
- A business with partial backups or a flat network: 1 to 3 weeks.
- A business with no usable backups: weeks, and some data may never come back.
Incident response firms commonly bill somewhere around $200 to $450 an hour. A small engagement often runs into the low five figures once forensics and rebuild work are counted. Get a written scope and an estimate range before work starts, and ask what's included.
Here's a number you can calculate yourself. Take your average daily revenue, add daily payroll for staff who can't work, and multiply by seven. That's the rough cost of a one-week outage. For many Myrtle Beach businesses in July, it's more than a year of good backups and security tools would cost.
Should you pay the ransom?
I wouldn't. The FBI discourages paying, and the practical reasons are stronger than the principle.
Payment doesn't guarantee a working decryptor. Even a good one is slow and often leaves files corrupted. You'd still need to rebuild every affected system, because you can't trust a machine the attacker controlled. And a payer is marked as a payer.
The one exception is a business with no backups and data it can't live without. Even then, bring in a professional negotiator and your insurer before you send anything. Don't do it alone, and don't do it from the ransom note's chat window at 2 a.m.
Backups: what I'd pick and what I wouldn't bother with
If you're choosing a backup approach after an incident, here's where I land.
I'd pick immutable cloud backups. These are copies that can't be changed or deleted for a set retention period, even by an admin account. Cost is usually modest for a small business, often $50 to $300 a month depending on data volume. That's a rule of thumb, so get quotes.
I wouldn't bother with a USB drive that stays plugged into the server. It gets encrypted along with everything else. Rotating drives that go home with someone work, but they depend on a person remembering every day, and people forget.
Whatever you choose, follow these basics:
- Keep three copies of your data on two types of storage, with one offsite.
- Back up critical systems daily. Back up databases like reservations or patient records more often, hourly if the business can't afford to re-enter half a day of work.
- Test a restore every quarter. A backup you've never restored from is a guess.
- Keep backup credentials separate from your main network login.
Local legal and reporting duties
South Carolina's breach notification law, S.C. Code § 39-1-90, requires businesses to notify affected residents when certain personal information is exposed. If more than 1,000 people are involved, you must also notify the Consumer Protection Division of the S.C. Department of Consumer Affairs and the national consumer reporting agencies. Have an attorney confirm what applies to you.
Other rules may stack on top:
- Medical and dental offices fall under HIPAA, which has its own notification clock. Don't treat 60 days as a target. It's the outer limit.
- Restaurants and hotels that take cards should call their payment processor early. PCI requirements can trigger a forensic investigation of their own.
- Everyone should report the attack to the FBI through ic3.gov. The FBI's Columbia field office covers South Carolina. Reporting doesn't cost anything and sometimes leads to decryptors or useful intelligence.
Call your cyber insurance carrier before you hire anyone. Many policies require you to use their approved responders, and going outside the panel can cost you coverage.
Choosing a recovery partner
Ask these questions before signing.
- Do they respond within hours, or "next business day"?
- Will they work with your insurer's requirements?
- Do they do forensics, or only restore files? You need both.
- Can they give you references from businesses your size?
- Will they put the scope and hourly rate in writing?
A local firm can be on-site fast, which helps when machines need to be physically inspected or rebuilt. A remote-only firm can still be excellent, but make sure someone can reach your office if needed. During hurricane season, which runs June 1 through November 30, ask how they'd handle an evacuation or storm outage during a response.
What to do before anything happens
Prevention is cheaper than any of the above. In rough order of value:
- Turn on multi-factor authentication for email, VPN, remote access and admin accounts. This is free or close to it and blocks a large share of stolen-password attacks.
- Patch firewalls and VPN devices within days of security updates, not months.
- Separate your networks. Guest Wi-Fi, payment terminals and back-office computers shouldn't share one flat network.
- Remove old accounts every time a seasonal employee leaves.
- Write a one-page incident plan with phone numbers for your IT provider, insurer, attorney and bank. Print it. Your files may not be reachable when you need it.
- Consider cyber insurance. Small business policies often run roughly $1,000 to $3,000 a year, though that varies widely with revenue and controls. Insurers will ask whether you use MFA and backups. Say yes honestly, because a false answer can void a claim.
The short version
Isolate, document, call your insurer, bring in professionals, restore from clean backups, and report. Don't pay unless you've run out of every other option.
The best recovery plan is the one you tested in April, long before the summer rush.