In July 2021, a ransomware attack spread through Kaseya VSA, a remote monitoring and management (RMM) tool that managed service providers use to look after their customers’ computers. Because one compromised tool reached many networks at once, the incident is still one of the clearest examples of a supply-chain attack on small and mid-sized businesses.
What happened
According to CISA’s incident guidance, attackers used a vulnerability in Kaseya’s on-premises VSA product to push ransomware to managed service providers and their downstream customers, starting on July 2, 2021. Kaseya shut down its SaaS servers that day as a precaution and told customers running VSA on their own servers to shut those down too. On July 11, 2021, Kaseya began restoring service and released a patch for on-premises VSA. The flaw is tracked as CVE-2021-30116.
The attack was attributed to REvil, a ransomware group the BBC reported had been blamed for attacks on hundreds of businesses worldwide. On July 13, 2021, the group’s payment and blog sites went offline without explanation.
Why one tool reached so many networks
An RMM tool exists to run commands on every computer it manages. That is what makes it useful, and it is also what makes it a target: whoever controls the RMM server controls every endpoint connected to it. The attackers did not need to break into each business separately. They went through software those businesses already trusted.
The same pattern applies to any vendor with privileged access to your systems:
- your IT provider’s management and remote support tools
- line-of-business software that a vendor maintains remotely
- integrations that connect your accounting, payroll or email to outside services
- remote access tools a vendor installed years ago and nobody removed
What still applies
The specific flaw was patched long ago. The lessons were not tied to it.
- Know which vendors can reach your systems. Keep a list of every vendor account, remote access tool and integration that can sign in to your network or cloud services, and remove the ones nobody uses.
- Ask how your IT provider protects its own tools. Multi-factor authentication on the management console, separate admin accounts, prompt patching of the tools themselves, and logs that show who ran what.
- Set security expectations before you sign. It is much easier to agree on access, logging and breach notification during contract negotiation than after a vendor is already connected.
- Keep backups that the management tool cannot delete. CISA’s advice to affected customers included keeping backups current and air-gapped from the organization’s network. If the same credentials that manage your computers can also erase your backups, one compromise takes both.
- Use MFA everywhere and limit admin rights. CISA recommended multi-factor authentication on every account under the organization’s control and least privilege for admin accounts.
- Plan a manual fallback. CISA told customers whose management service was down to switch to manual patching that follows vendor guidance. Decide in advance who would do that work.
Watching the tools that watch you
A trusted tool doing something unusual looks routine at first, which is why detection matters as much as prevention. Endpoint detection and response (EDR) watches what programs actually do on each computer, so a management agent that starts encrypting files or switching off security software stands out. Titan Tech uses SentinelOne for EDR and Huntress for SIEM and managed detection and response. The SIEM and MDR page explains how that monitoring works.
What to do next
Start with the vendor list. For each entry, write down what it can access, who at your company owns the relationship, and when that access was last reviewed. Then check that at least one copy of your backups sits outside the reach of your everyday admin accounts. If you want help reviewing either, you can request a Blind Spot Scan.