Anatomy of a Ransomware Attack
What can happen when hackers strike
“Ransomware attack? That’ll never happen to my company.”
Here’s hoping it doesn’t. But if does, here’s how events could unfold.
8 a.m. – Your computers aren’t working, and your employees are idle. Someone says the “R” word. With a racing heart and pounding head, you swing into action.
- Unplug all computers from the network.
- Power down your Internet router, network switches, and wireless access points.
- Call your IT company (if you have one). If so, you…
- Hold your breath while they Inspect local drives and network server drives for encrypted files and locate any malware tools and scripts that could have been used to look for and copy data.
- Watch for a notification from the perpetrator, and…
- Gulp as you’re told to reckon with this reality: Your company will be down for 3-5 days at a minimum—and possibly weeks.
- Wonder if you have cybersecurity coverage.
- Call your insurance carrier’s Cyber Claims Hotline (if they have one) for next steps.
- Speak with a “cyber breach coach/extortion negotiator”—they have those? Seriously?
- Try to absorb the grim news that even if you pay and get encryption keys, it’s rare to fully recover all your encrypted and/or stolen data. (They also tell you to forget the idea that some kid here in the U.S. wants your data—odds are a cybercriminal organization overseas found a vulnerability in your system and just wants money. Lots of it.)
- Ask the IT expert to perform a data restoration.
- Try not to obsess over the fact that even though you’re paying your employees, they can’t really do their jobs.
- Check to see if your employees saved their data in the right place and if your IT company has been performing back-up restoration tests.
- Cross your fingers and hope data can be restored from your backups. Or, worst case, that ransomware payments will be minimal and you can resolve the problem quickly.
- Reel from the news that the data restorations didn’t work because your IT people haven’t been performing regular disaster recovery tests.
- Hop back on the phone with your breach coach/negotiator.
Day 1, 2 p.m. through days 2, 3, 4, 5…days 6, 7, 8…and beyond
- Begin negotiations to reduce the $100,000 ransom
- Try to smile as the negotiator tells you your ransom has been reduced to “only” $50,000.
- Establish a relationship with a bitcoin exchange
- Watch your team’s morale sink further.
- Keep paying your restless employees—not to do actual work, but to deal with unhappy customers.
- Start sweating as sales slip and revenue dips.
- Struggle to sleep.
- Wire enough money to purchase $50K worth of bitcoin.
- Get the first decryption key and learn that some files do decrypt.
- Fork over more bitcoin and gets a few more keys.
- Yell “Those lying, #&^%@ criminals!” when IT techs run decryption keys on all systems and only half work.
- Agonize over your hurting business.
- File an insurance claim for the $50,000 ransom…
- And $250,000 more for business interruption…
- Add IT services remediation, and data recovery.
- Make it an even $325,000 to pay off your maxed out credit line.
- Wait to see what your insurance carrier says.
- Get a notice—“Claim denied.” (See why carriers deny most claims in this blogpost.)
- Call to appeal, plead, beg…then rant and yell.
- Wrestle with questions like: Are we going to make it? Will I ever sleep again?
It doesn’t have to be this way. There are steps you can take BEFORE disaster strikes. Want to make sure you’re safe from ransomware attacks. Give us a call.
We can help you sleep better.
About the author
Todd Whitlock is a technology leader who executes high-ROI software, hardware, and mobile support road maps aligned with your business objectives. Since 1998, company stakeholders have partnered to formulate strategic plans that guide the direction for their IT vision and daily operations. By leveraging forward-thinking intuition, Franklin IT Solutions is able to recognize new tools and technologies that prevent problems, reduce complexity, save money, and protect organizations.