N-able has shut down hosted versions of its RMM software and advised self-hosted customers to turn it off after a security incident. What should affected teams focus on while details are still coming out?
N-able RMM is down after a security incident. What should we do?
Answers
For self-hosted deployments, follow the vendor's advice to disable the service. Treat that as an immediate containment step, not proof that nothing was compromised.
Document when it was taken offline and preserve relevant logs. Review remote access and administrative activity as the investigation develops, and wait for verified guidance before bringing the service back.
Reply to this answer
Plan for the operational gap too. If monitoring, remote access, or scheduled maintenance depend on the RMM, work out which systems need another way to be checked or supported while it's unavailable.
Reply to this answer
There are public reports of vulnerabilities, but the discussion doesn't establish which ones are connected to this shutdown or whether customers were compromised. I'd avoid treating exploit descriptions as a complete incident report.
Check the vendor's official updates for affected products, remediation steps, and any guidance on investigation. If the status page is slow or unavailable, try again later and use other official support channels where possible.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_n73~mivdexa.6:
That distinction matters. A published vulnerability can explain why a service is at risk without confirming what happened in a particular environment.