Secure ScreenConnect playbook for on-premises servers
ConnectWise is still investigating the November 2026 attacks. This PDF is the step-by-step method we used to secure our own on-premises ScreenConnect server. Use it on top of the vendor steps, not instead of them.
One-time payment. Instant PDF download. No refunds.
- Our own fully patched server had rogue sessions. We’ve seen none since we secured it. One server, not proof.
- Step-by-step instructions. No extensions or new software required.
- Exact, platform-specific steps, plus testing and rollback.
- Free email support if you get stuck.
Why review ScreenConnect security now?
Reports now include on-premises servers, and ConnectWise is still investigating how attackers got in.
- November 11: attackers used the Run Command feature on MSPs’ ScreenConnect consoles to push rogue ScreenConnect clients onto managed endpoints (Huntress, BleepingComputer).
- November 13: Huntress reported a second wave, including a self-hosted server. ConnectWise’s update that day says researchers are reporting activity against on-premises servers where the extensions are still enabled (ConnectWise advisory).
- ConnectWise’s advice: disable the named extensions, update every technician client to 26.6.5 or later, revoke sessions and enforce MFA. The client fix blocks the attempted endpoint-to-technician spread. The initial access method remains under investigation.
Timeline, vendor steps and sources: ScreenConnect attacks, November 2026: what to do now.
What we saw on our own ScreenConnect server
One server: what we saw, and what we did about it.
Our on-premises ScreenConnect server had no extensions installed and was on the latest version. It still showed rogue unattended sessions we did not create. We didn’t wait for an answer.
We secured it ourselves, with no extensions and no new software.
Since then, we have seen no new rogue sessions and no brute-force login attempts.
That is one server, not a study. We don’t know how the rogue sessions got there or whether they were related to SCKit, and the quiet since then doesn’t prove our changes are what stopped them. We still patch and still follow the vendor’s steps. The method is an extra layer on top of them.
What is in the ScreenConnect playbook?
Step-by-step instructions, plus testing and rollback so you can check your changes and undo them.
- Why we wrote it: our own server
- The November 2026 attacks: what to do today
- What it does and doesn’t protect
- Is the method right for your setup?
- Before you start: preparation checklist
- The step-by-step method
- Exact, platform-specific steps
- Testing and rollback
- Ongoing maintenance
- If you find rogue sessions: a compromise checklist
- Bonus: the same approach for other remote-access services
Check the ScreenConnect playbook scope before buying
- On-premises only. The method needs an on-premises server; it doesn’t apply to ScreenConnect Cloud.
- Do the vendor steps too. Disable the named extensions, update technician clients and revoke sessions. The method doesn’t replace any of them.
- No refunds. Check that you use ScreenConnect on-premises before buying.
- It doesn’t remove what’s already there. Rogue clients that are already installed need incident response. The playbook includes a compromise checklist to help you find them.
Secure ScreenConnect playbook
One-time payment. No refunds.
- No extensions, no new software.
- PDF, instant download
- Free email support on the solution: [email protected]
- Updates to this edition sent through the same link
FAQ
Do I need new software?
No. The method uses what you already have, and there are no extensions to install. You get step-by-step instructions in a PDF, plus free email support if you need help applying them to your own setup.
Does it work with ScreenConnect Cloud?
No. This playbook is for ScreenConnect on-premises and does not apply to ScreenConnect Cloud. Check which deployment you use before buying. If you use Cloud, follow ConnectWise's current campaign guidance and investigate any suspected compromise with your security provider or separate response tools.
Can I get help applying the playbook?
Yes. Buyers get free email support for questions about applying the solution in the PDF. Write to [email protected] if you need help with the steps. The playbook also covers testing and rollback so you can check your changes and reverse them if needed.
What format is it, and how do I get it?
You get a PDF download link after checkout. The price is $79 as a one-time payment. There are no refunds. Updates to this edition use the same link, and buyers get free email support at [email protected] for questions about applying the solution.
Is there a patch?
Partly. Client version 26.6.5 or later blocks the toolkit's attempted spread from an endpoint to a technician, so update every technician client. It does not fix how attackers got in, and no update removes access already established. No fixed RMM+ extension version has been announced. Follow ConnectWise's current advisory; the playbook adds to those steps.
The ThreatListPro blocklist is a separate product for VPN brute force protection: 5.4M+ IPv4 addresses, checked for new attackers every 6 hours. You can try it with a 14-day free trial, no card.