While most of us were firing up the grill and heading to the beach for the Fourth of July, a ransomware gang was working through the holiday weekend. On Friday afternoon, July 2, attackers used Kaseya VSA, a remote management tool used by many IT service providers, to push ransomware out to businesses that had nothing to do with each other except who managed their computers.
We are an IT provider ourselves, so we have been following this one closely. It raises a fair question that every business owner who outsources IT should be asking right now: what happens when the tools your provider uses to protect you become the way in?
What happened
Kaseya is a software company whose VSA product lets IT teams and managed service providers (MSPs) monitor and manage lots of computers from one console. It can push updates, install software, and run scripts across every machine it manages. That is what makes it useful, and it is also what made it dangerous in the wrong hands.
Attackers exploited previously unknown vulnerabilities in on-premises VSA servers, the copies that MSPs and companies run themselves. They then used VSA's own software distribution feature to send out what looked like a routine update. It was actually ransomware from the REvil group, one of the most active ransomware operations this year.
Kaseya quickly urged all customers to shut down their on-premises VSA servers immediately and took its cloud-hosted version offline as a precaution. According to Kaseya, around 60 of its direct customers were compromised, many of them MSPs, and in turn somewhere under 1,500 downstream businesses were affected. The effects reached well beyond the U.S.; a large grocery chain in Sweden had to close hundreds of stores because its checkout systems went down. REvil has reportedly demanded $70 million for a universal decryption tool.
The investigation is ongoing, and Kaseya has said it is working on a patch before bringing VSA back online.
Why the timing and the target were no accident
Criminals picked a holiday weekend on purpose. Offices were empty, IT staff were off, and it could be hours or days before anyone noticed. We saw the same logic with other high-profile attacks this year, including the one we wrote about in our post on the Colonial Pipeline attack.
Targeting an IT management tool is the other half of the strategy. Break into one tool, and you can reach every business that tool manages. It is the same basic idea as last December's SolarWinds breach: go after something trusted, with broad access, and let it carry you inside.
The tools that let an IT provider help a hundred businesses at once can also let an attacker hurt a hundred businesses at once.
Should this change how you feel about managed IT?
Honestly, no, but it should change what you expect from your provider. Remote management tools are how modern IT support works. They are what allow patches to be installed on time, problems to be spotted before users notice, and help to arrive without a technician driving across the bridge. Going back to one person manually updating each computer would leave most businesses far less protected, not more.
What Kaseya shows is that those tools need to be treated as the crown jewels they are. An IT provider holds a lot of trust and a lot of access. How carefully they guard that access matters as much as anything they do on your own network.
Questions to ask your IT provider this week
A good provider will welcome these questions. If yours gets defensive or cannot answer, that tells you something too.
- Were you affected by the Kaseya incident, and do you use VSA? Simple and direct.
- What remote management tools do you use to access our systems, and how are they kept up to date?
- Is multi-factor authentication required for every technician who can log in to those tools?
- Who has access to our environment, and is it limited to the people who need it?
- Would you notice if your tools started doing something unusual, like pushing out a file nobody scheduled, especially on a weekend?
- Are our backups protected from the same tools? If an attacker controlled your management console, could they reach our backups too?
- What is the plan if your tools are compromised? How would you tell us, and how fast?
Backups are still the last line of defense
For the businesses hit this weekend, the question now is simple: can they restore? The ones with recent, tested backups stored somewhere the ransomware could not reach are in a much better position than the ones considering a ransom payment. That means at least one copy of your data that is offline, immutable, or otherwise walled off from the everyday network and management tools. If you have not tested a restore recently, our earlier post on whether your backup is actually working is a good place to start.
What to do now
- Ask your IT provider whether they use Kaseya VSA and whether they were affected.
- Get a clear list of every remote tool and account that can access your systems.
- Confirm that multi-factor authentication protects all administrator and provider access.
- Make sure at least one backup copy is isolated from your network and your provider's management tools.
- Test a restore, not just the backup job itself.
- Ask how your provider monitors for suspicious activity outside business hours, including holidays.
- Write down who you would call, and in what order, if ransomware showed up tomorrow.
Outsourcing IT should mean more protection, not a new blind spot. The right provider is open about the tools they use, careful about how they secure them, and happy to answer hard questions. If you want to know how we approach managed IT services and the security of our own tools, email us at info@pinellasit.com or use our contact form. We will give you straight answers.
