What should we do after recovering from a possible RMM vendor breach?

November 16, 2026 5 answers
Asked by 8k+datacrank_617

Our managed service provider's remote monitoring and management vendor may have been breached, and our data was hit by ransomware. The investigation is still underway, so we don't know exactly what happened.

We have local and offsite backups, but haven't done a full restore test. Assuming we can recover, what should we tackle next, and what should we ask the provider?

Answers

r.608~tagthimble

Don't wait until everything is restored to make the first calls. Contact your cyber insurer if you have one, and check the policy's reporting and response requirements. Get legal counsel involved too, particularly around your provider contract and any notification obligations.

Coordinate evidence preservation with the incident responders before wiping or rebuilding affected systems. They may need logs or forensic images to determine how access was gained and whether data was taken. Public guidance from CISA or a state cybersecurity agency can also help you structure the response.

Reply to this answer
_x53!gearspoon.8

I'd treat credentials shared with the provider as potentially exposed until the investigation says otherwise. Rotate them, review privileged accounts and remote access, and look for persistence before bringing systems back into service. Monitor closely afterward. A clean restore won't help much if the same access path is still open.

p.307!drummarker:

Coordinate the cleanup with whoever is preserving evidence, so you don't erase useful traces while trying to close access.

Reply to this answer
6b+radarbutton_751

Verify the backups yourselves. Ask where each copy lives, who can administer it, what dates are available, and whether the backup environment was affected. Having several copies is good, but it doesn't prove they're usable.

Run a full restore test when the response team says it's safe, including the dependencies needed to make the system usable. Check the restored data and record how long it takes. Then review whether your copies are sufficiently independent, including one offsite, and whether you need a backup the provider cannot administer.

Reply to this answer
d.682+ferruleflag

Ask the provider for a written account of what they know, what remains uncertain, and when they'll update you. Which systems and accounts were exposed? Was the management tool involved? Do they have evidence of data access or exfiltration? What have they done to contain the incident and prevent the same route back in?

Also ask who is handling forensics, what logs they can share, and how they verified the backup service. Their response and the contract should help you decide what changes to make to the relationship once the immediate incident is under control.

Reply to this answer
4e+paperwrench_763

Use the downtime exercise to map the systems you couldn't fully explain. Document owners, dependencies, recovery order, and where the data lives. Compare that with what actually happened during recovery, then turn the gaps into specific fixes for the migration and disaster recovery plan.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions